01
Tonight
One ICP and a stop rule.
Give the Bot one buyer definition and a batch size you can finish in the morning. Replace the brackets in the prompt and keep the stop rule.
Give Grok Bot one ICP and a stop rule before you sleep. Wake up to a review list in Revora. Send from the workspace. Do not let the Bot enroll anyone while you are offline.

Give Grok Bot one ICP and a number you can review before the workday starts. A smaller list with evidence is more useful than a large list you will ignore.
Keep the Bot description clear: research and draft only. Never send, never enroll, and never sign into LinkedIn on the Bot computer.
Open each promising lead in Revora. Remove bad fits, check the trigger, and cut any draft that makes a claim you cannot support.
Launch from Revora with conservative limits and send windows. Read account safety before you increase volume. The overnight run is preparation, not the conversation.
SpaceXAI lets you save a path the Bot followed and run it on a schedule. Keep the same stop: review list, not send.
No. A written ICP plus a Revora lead finder is enough. A CRM view is useful if you already live there.
Skip the overnight run. An unread list is a more expensive way to ignore your pipeline. Overnight is the wrong idea on a week you cannot sit with the list.
No. Change the promise or the segment. Meetings come from the inbox, not from how many notes the Bot wrote while you slept.
No. Warm a new LinkedIn account, or a recently recovered profile, first. Human pacing lives in account safety and send windows.
No. Grok Bot is still in beta and sits on expensive plans. If you do not already have it, start in Overview. Connect steps: how do I connect Grok Bot to Revora.
More on Grok Bot
Prefer markdown? Overnight outbound with Grok Bot.md