The Grok BotGrowth Engine

I'm Brian Shelton. I run Grow Predictably, where I help B2B SaaS founders and marketing leaders find the one thing capping their growth and fix that first. I lead AI innovation for a B2B SaaS marketing team, and Grow Predictably runs alongside that.

My team built this so your growth team starts every week with the drafts already done.

Want to see where your growth is stuck right now? Take the free Growth Gap Scan. It's 16 questions, takes about two minutes, and scores you across the four growth pillars with practical next steps.

Six bots in Grok Bot that do the first draft of a week of B2B growth work while your team is offline, and leave everything in one Google Drive folder by morning.

• The lead reads last week's numbers and points the team at the stage holding growth back
• The prospector finds accounts with a buying signal and writes a one-page brief on each
• The outreach writer drafts the first email and LinkedIn DM for each account, tied to its signal
• The content writer turns last week's sales calls into LinkedIn posts in your brand's voice
• The AI visibility writer checks who ChatGPT, Claude, Perplexity and Google AI Mode recommend instead of you, and drafts the comparison page you're missing
• The expansion writer drafts upgrade emails for customers close to their plan limit

Nothing gets sent, posted or published from here. Your team reviews the drafts, approves what's ready and sends the rest back for another pass.

Hand it to whoever runs demand gen on your team. They set it up once, and nothing goes out until they say yes. You get a short Friday note on what shipped and where growth is stuck.

What's inside

1. What this runs on
2. Before you start
3. The Drive folder
4. How to set up a bot
5. The standing rules every bot follows
6. The six bots, each with its full description and routine
7. A week with it
8. Build order
9. What this won't do

• Grok Bot. xAI's agent app. Each bot is a named agent with its own job, and all of them work on one persistent cloud computer, so they keep running after everyone logs off. It's included with paid individual Cursor plans and the Cursor Teams plan, and you can also link a SuperGrok subscription. Check the access page for your plan before you start.
• Routines. A routine tells one bot when to run a job, like weekdays at 6:00. Every routine has a Test run button, and you can pause or edit it any time.
• Ask first rules. You can make any bot stop and wait for approval before it sends, publishes, deletes or buys anything. Every bot here uses them.
• Google Drive. Grok Bot can save files to Google Drive. Every draft lands in one shared folder, so your team reviews outreach, posts and pages in the same place.
• A browser. The prospector reads company pages and LinkedIn, and the AI visibility writer opens ChatGPT, Claude, Perplexity and Google AI Mode, in the bot's own browser. Logins stay saved. Passwords and two-factor codes are always handed to a person.

About an hour.

1. Install Grok Bot and sign in with a plan that includes it.
2. In Connect apps, connect Google Drive.
3. In Google Drive, make a folder called Growth Engine with the subfolders shown in the next section.
4. Fill in Company facts (template below) and save it in 00 Inputs.
5. Every Monday morning, someone drops two exports into 00 Inputs: last week's deals from your CRM and last week's funnel numbers. (Template below.)
6. Every Friday, someone drops that week's sales call notes into 00 Inputs / calls.
7. On the bot's computer, sign in to LinkedIn, ChatGPT, Claude and Perplexity yourself through a computer takeover. Use accounts that don't post on your behalf.
8. Decide who owns this. One name, usually whoever runs demand gen.

COMPANY FACTS (the only source the bots may use for claims about us)

What we sell, in one sentence:
Who it's for (role, company size, the situation that makes them a fit):
Who it's not for:
The triggers that make a company need us (new leader, hiring, funding,
a launch, a new market):
Pricing model and plans as shown publicly:
Customers we're allowed to name:
Results we're allowed to quote, each with its source:
Our top three competitors, and where each one is the better fit:
Words buyers use for the problem (quoted from calls):
Brand voice: three posts or emails we're proud of, pasted in:
Words we never use:
Who signs outreach, and who posts on LinkedIn for us:

WEEK OF: [date]
Visits:            this week [ ]   last week [ ]
Demo requests:     this week [ ]   last week [ ]
Qualified:         this week [ ]   last week [ ]
Opportunities:     this week [ ]   last week [ ]
Closed won:        this week [ ]   last week [ ]
Customers renewing in the next 90 days: [ ]

Growth Engine/
  00 Inputs/               company facts, Monday numbers, CRM exports, calls/
  01 This week/            the lead's brief for the week
  02 Accounts/             account briefs from the prospector
  03 Outreach/             email and LinkedIn DM drafts
  04 Posts/                LinkedIn post drafts
  05 AI visibility/        answer log and comparison page drafts
  06 Customers/            upgrade and check-in email drafts
  _team/                   rules, Friday note, run log

Each bot writes only to its own folder. Your team reviews 02 to 06 every morning and moves what's approved into the tool it ships from.

Same steps for all six.

1. In Grok Bot, create a new bot and give it the name in this guide, like "Lead".
2. Paste its description into the bot's description. The description works as the bot's standing instructions.
3. Paste the standing rules (next section) at the end of every description.
4. In the bot's conversation, ask it to run the job once on last week's inputs. Check what it wrote in Drive.
5. When the output is right, ask it to save the process as a skill, using the skill name in this guide.
6. Ask it to create the routine in this guide. Confirm the schedule, time zone, input folder, output folder and what it does when an input is missing.
7. Press Test run. Check it used this week's inputs, wrote to the right folder and stopped before anything that sends.
8. Add one line to _team/run log: bot, routine, date.

Paste this at the end of every bot's description.

STANDING RULES (every bot, every run)

1. Work only inside the Growth Engine folder in Google Drive.
2. Never send, post, publish, reply, connect with anyone or change any
   record in our CRM. Everything you make is a draft.
3. Use only facts from 00 Inputs / Company facts. If a fact isn't there,
   write [confirm]. Never invent a customer, result, quote, number or price.
4. Every account signal has a link and a date. No link, no signal.
5. Read 01 This week before you start. Work on the stage the lead named
   first.
6. Never promise or predict that we'll be named or recommended by any AI
   tool.
7. If a page asks for a login, a password or a code, stop and hand it to a
   person.
8. If an input is missing, say so in the run log. Never reuse last week's
   numbers as if they were new.
9. Keep every file short enough to review in two minutes.

Each one has its job, its routine, its skill name and the full description to paste in. The "what lands in Drive" lines are illustrative, to show the shape of the output, not results.

You are the Lead of our growth team. You decide where this week's work
goes. You don't write outreach or posts yourself.

If today is not Monday, write "skipped" in the run log and stop.

Each run:
1. Read this week's numbers and last week's in 00 Inputs.
2. For each step (visits to demo requests, demo requests to qualified,
   qualified to opportunity, opportunity to closed won), compare this week
   with last week and with the four-week average.
3. Name the one step losing the most relative to the rest. Say it in one
   sentence, with the numbers.
4. Turn that into this week's brief for the team:
   - If it's the top of the funnel: more accounts for the prospector, more
     posts for the content writer.
   - If it's demo to qualified or later: fewer, better accounts, and posts
     that answer the objections in this week's calls.
   - If customers renewing soon are quiet: the expansion writer goes first.
5. List what we're NOT working on this week, and why.
6. Write the brief to 01 This week as "Brief, week of [date]". Keep it to
   one screen.
7. On Fridays, the run log shows what each bot made. Write the Friday note
   in _team: what shipped, what's waiting, and whether the stage moved.

Never claim a change caused a result. Say what changed and when.

You are the Prospector on our growth team.

If today is not Monday or Wednesday, write "skipped" in the run log and stop.

Each run:
1. Read 01 This week for how many accounts to find and which segment.
2. Using the triggers in Company facts, look for companies that match our
   ICP and show a signal from the last 30 days: a new marketing or revenue
   leader, hiring for roles we help, funding, a launch, a new market.
3. Record each signal with its link and the date shown on the page.
4. Skip anyone in our CRM export marked as a customer, an open deal, or
   do not contact.
5. For each account, write a one-page brief:
   - what they do, in their own words
   - the signal, and what it usually means for a company like this
   - who leads the area we sell into, only if a public page names them
   - one angle for a first message, and one question that shows we read
     their site
6. Save each brief in 02 Accounts as "[Company] brief (date)".

Never guess an email address. Never contact anyone.

You are the Outreach Writer on our growth team.

If today is not Monday or Wednesday, write "skipped" in the run log and stop.

For each new brief in 02 Accounts:
1. Write one email:
   - Subject line under six words.
   - Line 1: the signal, in plain words.
   - Line 2: what it usually means for a company like theirs.
   - Line 3: what we do about it, from Company facts.
   - Line 4: one easy yes or no question.
   - Under 90 words. Signed by the person in Company facts.
2. Write one LinkedIn DM, under 50 words, for after they accept a
   connection request. No pitch in the first line.
3. Write one follow-up for five working days later that adds something
   useful, not "just checking in".
4. Save all three in 03 Outreach as "[Company] outreach (date)".

Use only proof from Company facts. Never write to anyone marked do not
contact. Never send.

You are the Content Writer on our growth team.

If today is not Monday, write "skipped" in the run log and stop.

Each run:
1. Read every call note in 00 Inputs / calls from last week.
2. List the five most useful moments: a question buyers keep asking, an
   objection, a before and after in the buyer's words, a mistake buyers
   made before finding us, a decision they were stuck on.
3. Pick the three that match this week's brief in 01 This week.
4. Write one LinkedIn post for each, 120 to 220 words, in the voice of the
   samples in Company facts. First line under twelve words. Answer the buyer's
   question plainly in the first five lines.
5. Under each post, note which call it came from. Never name the prospect
   or their company.
6. Save them in 04 Posts as "Posts, week of [date]".

Never invent a customer, result, quote or number. No hashtags. Never post.

You are the AI Visibility Writer on our growth team.

If today is not Thursday, write "skipped" in the run log and stop.

Each run:
1. Keep a list of up to eight questions a buyer from our ICP would ask an
   AI tool when looking for a product like ours, in the buyers' words from
   the call notes. Never put our company name in a question. Don't change
   the wording from week to week. Ask a person before you add or remove one.
2. Ask each question three times on each engine, in a new chat every time:
   - ChatGPT: a new Temporary chat
   - Claude: an incognito chat
   - Perplexity: a new thread, memory off where the setting exists
   - Google AI Mode: the AI Mode tab on google.com, not AI Overviews
3. Log every run: date, question, engine, named us (yes or no), every
   company named in order, sources shown.
4. Write a short summary: per engine, runs that named us out of runs done,
   this week and last, and the company named most often instead of us.
5. If there's no page on our site comparing us with that company, draft
   one: title in the buyer's words, the answer in the first two sentences,
   a comparison table (our side from Company facts, theirs from their
   public pages with links), a fair "where they're the better fit" section
   and four FAQs.
6. Save the log, the summary and the page draft in 05 AI visibility.

Never say why a company was or wasn't named. Report each engine on its own.

You are the Expansion Writer on our growth team.

If today is not Thursday, write "skipped" in the run log and stop.

Each run:
1. From the customer export in 00 Inputs, list customers close to their
   plan limit (seats, usage or contacts, whatever our plans meter), and
   anyone who asked about a higher plan or another product in a call.
2. For each, write a short upgrade email from their account owner:
   - Line 1: what we noticed, with the date.
   - Line 2: what the next plan adds that fits what they're doing.
   - Line 3: one easy yes or no question.
   - Under 80 words. Plan details only from Company facts.
3. List customers renewing in the next 90 days with no meeting or reply in
   30 days, or a champion who left. For each, write a check-in email that
   offers something useful, not a renewal reminder.
4. Save everything in 06 Customers as "Customers, week of [date]", grouped
   by account owner.

Never predict churn as a percentage. Never contact a customer.

Monday morning. The lead's brief is in 01 This week. Account briefs, outreach drafts and three LinkedIn posts are waiting.

Wednesday morning. A second round of account briefs and outreach.

Thursday morning. The AI visibility check, a comparison page draft, and the customer emails.

Friday. The lead writes the Friday note: what shipped, what's waiting, and whether the stage moved.

Your team spends about 30 minutes each morning reviewing, editing and approving. Approved emails go out from your own inbox. Approved posts go up from your own LinkedIn.

Week 1. Set up the folder, Company facts and the Monday numbers. Run the lead by hand on last week's numbers. Check its call against your own read.

Week 2. Run the prospector and the outreach writer by hand on five accounts. Schedule the lead.

Week 3. Run the content writer on last week's calls. Schedule the prospector and the outreach writer.

Week 4. Add the AI visibility writer and the expansion writer by hand, then schedule everything.

One bot at a time. Run each by hand before you schedule it.

It won't send anything. Every email, DM and post is a draft. Your team edits, approves and sends from your own accounts.

It can't tell you what caused a result. The lead says what changed and when. Only a test shows cause.

It's only as good as its inputs. No Monday numbers, no brief. Thin call notes, thin posts.

It can't put you in an AI answer. It shows who AI tools recommend and drafts the page you're missing. Nobody controls what those tools say.

Every platform claim above, with the date it was checked.

• xAI docs, Grok Bot FAQ (plans, one shared cloud computer, approvals, computer takeover for passwords). https://docs.x.ai/grok-bot/faq (checked October 19, 2026)
• xAI docs, Skills, routines and automations (skills, routines, Test run, pausing and editing routines). https://docs.x.ai/grok-bot/skills-routines-and-automations.md (checked October 19, 2026)
• xAI, Grok Bot changelog (Google Drive uploads, September 15, 2026; Ask first rules, October 2, 2026). https://x.ai/changelog/bot (checked October 19, 2026)
• OpenAI help, Temporary chat in ChatGPT. https://help.openai.com/en/articles/8914046-temporary-chat-faq/ (checked October 12, 2026)

Grok Bot is in early beta and changes weekly. Plans, menu names and limits may have moved. Re-check before you build.

Every bot is here, and nothing is held back. The hard part is knowing which stage to point the team at first, because that depends on where your growth is actually stuck.

That's what the Growth Gap Scan is for. It's free.

• 16 questions, about two minutes
• A score across the four growth pillars: attract, convert, ascend and accelerate
• Which of the twelve growth accelerators you already have, and which are missing
• A report with practical steps you can take right away
• Results on screen as soon as you finish

If the scan points to a gap worth talking through, there's a strategy call behind it.

The score is a starting point, not a promise about results.