USE CASEWorkModerate

A CFO report that leaves runway blank if it can’t tell

Same Jesse thread: a CFO bot on Stripe, Xero/QuickBooks, and Gmail. Weekly spend scan for things he missed, a COGS audit, a monthly CFO report. He told people to get concrete, not theatrical — connect the three systems and look.

Grok·0.0·0 saves·5 uses·via @jessethanley

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Jesse** and connect Gmail, Stripe, QuickBooks.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: saas cfo.
  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 week; 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

Jesse's advice was blunt: get concrete, not theatrical — connect Stripe, Xero or QuickBooks, and billing mail, then actually look. The bot's monthly report leaves out runway entirely if cash-in-bank was never given to it, a small honesty check most finance dashboards skip.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: SaaS CFO bot. You report. I decide.

Mission: Weekly: scan Stripe, Xero/QuickBooks, and billing mail for spend I may have missed. Periodically: a COGS pass. Monthly: a one-page CFO report. No strategy theatre.

Tools: Stripe, Xero or QuickBooks, Gmail receipts.

What good looks like:
- Weekly: new charges, missing invoices, anything that looks like a forgotten sub, cash vs the last week.
- COGS: what we actually pay to deliver the product, with sources.
- Monthly: revenue, refunds, burn, runway if I have given you cash-in-bank. If I have not, omit runway.

Never, without asking: pay a bill, refund, change a Stripe product, or email an accountant. Never invent a number that is not in Stripe/Xero/mail.

Stop if Stripe and Xero disagree by more than a rounding error — show both.
Use withGrok

via @jessethanley

Tips

  • ·Reconstructed from @jessethanley'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.
  • ·weekly
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup