✦ 65 · solid

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.

verified 2026-08-21 ~30 min setup finance & ops
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Jesse and connect Gmail, Stripe, QuickBooks.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: saas cfo.
  3. Give 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. Run it each week; it acts once you approve each step.
  5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

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.

Why it’s cool

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 reconstructed by the Curator from @jessethanley's published setup — not their verbatim text

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.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

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.
by @jessethanley

related

✦ 62 · worth a look

A daily declutter capped at ten items you approve

Peter Yang’s five-bot tutorial includes a digital Marie Kondo that audits Gmail, Google Drive, and paid subscriptions, then proposes a cleanup plan. It only unsubscribes, deletes, renames, or cancels after he approves each action. Same tweet as the advisor / YouTube / X-scout crew.

via @petergyang · 𝕏
✦ 71 · solid

The win-back bot that paid for its own subscription

Liam gave Grok Bot one job: win back churned customers. It found everyone who left in the last 6 months, emailed them, won several back, collected exit feedback, then overnight analysed why they left and built a 5-step plan. The bot covered its own subscription cost. 3.

via @liam_fallen · 𝕏

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.