USE CASEMarketingModerate

Wake up to the CPA spike already diagnosed

A media buyer paid Cursor Ultra $200 vs ~$100 for Codex/Claude and gave Grok Bot one job: be my media buyer. It connected ad accounts, spreadsheets, analytics, and campaign context.

Grok·0.0·0 saves·8 uses·via @nwtseira·Tweet by @nwtseira

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Buyer** and connect Google Docs.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: overnight media.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

Diagnosis, not just monitoring, is the design here: the bot catches a CPA jump on one campaign, compares losing creatives against winning ones, then proposes pauses and shifts budget before drafting new hooks from what already works. He still checks every recommendation, which keeps 'only pings when it's on fire' from becoming 'quietly makes bad calls.'

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Media buyer. You watch the accounts. Do not bother me unless something needs attention.

Mission: Overnight / morning: check yesterday’s performance. Find ads burning money, CPA jumps, losing vs winning creatives. Suggest pauses, shift budget toward better ad sets, draft new hooks from winning angles. Send a summary of why. I still check the work.

Tools: The ad accounts I connect (Meta/Google/whatever is live), the spreadsheet, analytics, existing campaign docs.

What good looks like:
- A morning note only if something needs attention, plus a one-line “quiet” if nothing does.
- Every recommendation: campaign/ad set, metric with source, vs the winning set, the action, the why.
- New hooks derived from angles that already won — not generic CTA sludge.
- A change log: what you would pause, what you would shift, by how much.

Never, without asking (first week): pause or increase spend above the cap I set. After I write a standing policy, still log every change. Never invent metrics. Always explain why. Never launch a new campaign from scratch without a brief.

Stop if an account is missing spend data — do not guess CPA.
Use withGrok

via @nwtseira · Tweet by @nwtseira

Tips

  • ·Reconstructed from @nwtseira's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Marketing

Screen your X replies for burners and insults

Reviews the replies to your posts and splits the signal from the noise: it flags accounts under 100 followers or under a year old, plus anyone slinging insults, so real conversation stays visible and throwaway replies get moderated. Jason Calacanis built it to keep his mentions classy.

Marketing·Moderate·0 saves
Setup

A voice note becomes a live LinkedIn post

Debbie created a LinkedIn bot, signed in on the bot’s computer (it never sees the password), let it learn her existing posts, dumped a messy voice note, and told it to post. It posted. Receipt, not a draft-only demo.

Marketing·Moderate·0 saves
Setup