Grok Bot for founders: a Monday report from a CFO Bot and an analyst

You can have a few Grok Bots put your week's bank, Stripe and user numbers into one group chat every Monday, then fix their mistakes in the same thread. On Oct 2, solo SaaS founder Justin Butlion described that setup: a CFO Bot on his Mercury bank account, an Analyst Bot that assembled the report, and a Chief of Staff Bot that posted it to a group chat called Weekly Report Review. It fits founders who run the money side themselves. It's his own account, and we haven't run it.

Not tested: we have no Mercury or Stripe account to run it against.

Who runs it#

Butlion writes the Coffee + Revelation newsletter. His X bio reads "All things SaaS." and lists several apps, including Project Echo, LiveWire and SLA Monitor, plus "+ 10 more ($7k MRR)". The org chart in his Oct 2 post labels him "Founder, Hawkeye Ventures". He wrote that he "already had a $60 a month Cursor subscription" when he started, and that at the time "I’ve got 8 bots on the “team”".

Disclosure: Butlion is building LiveWire, which bills itself as a way to "Monitor your entire business in a single live feed" and lists "AI agent teams" as a use case (LiveWire). He pitches it partly against agent reports: on Oct 30 he wrote "You would need to set up multiple recurring tasks for the agents to stay on top of the activity and then share it to you somehow." His Bots also work on his own apps. The last sections of his Oct 2 post are for paid subscribers only, and we read only the free part. We found no staff role at Cursor, xAI, SpaceXSI or Mercury in his bio or posts.

The Monday loop#

From his Oct 2 post, in his words:

Why a CFO Bot. "since Mercury, the digital bank I use for my businesses has an MCP server, I knew I could benefit from having a CFO agent."
One door to Stripe. "CFO and Chief of Staff are the only agents allowed to use the Stripe connectors."
One group chat. "I have only one group chat, the Weekly Report Review. In this group chat I have the Chief of Staff, CMO, CFO and analyst."
What the report covers. "Each Monday the Chief of Staff shares a detailed weekly report in the group chat." It covers "my productivity, financial performance of the businesses, cash flow, loan payments, activity of users in my new SaaS (SLA Monitor & Project Echo), my social media output, and more."
Who builds it. "The analyst is responsible for putting the report together from the CMO, CFO and Chief of Staff, and the Chief of Staff is responsible for reviewing it and sharing it in the group chat."
What he does with it. "I then review it every Monday, use it to set up tasks for the week, and make minor improvements so that the next week’s report is even more useful."
Numbers against targets. "I’ve also started to document the KPIs I’ve assigned the business so they are accessible to the agents and they can see if the weekly report numbers are positive or negative."

The sidebar screenshot shows the CFO Bot's last message as "I've sent Analyst this week's Mercury pack" (cut off after that). Another screenshot shows the correction he describes. The blog version: "I noticed the CFO assumed some of the expenses in Mercury were personal expenses rather than business expenses." His message in the group chat reads "To be clear, all expenses are business. The Mercury accounts are business accounts only." It goes on with an exception the blog leaves out: "Perhaps 1 - 3 times a year I will process a personal expense using the business cards but those are rare and will be shared with you when they happen."

His Chief of Staff Bot, asked to introduce itself in another screenshot, says it combines "the CFO's Stripe numbers and the Analyst's SaaS activity into the Daily Report" and that "Every Monday I deliver the company-wide report to the Weekly Report Review group". It adds: "I don't send anything outside the team without Justin's okay". The Bot wrote that text, not Butlion.

Still running? On Oct 21 he wrote "I have automations and a daily summary shared to me using @bot which does give me totals per Stripe account and other useful info". On Oct 31 he wrote "I use Grok Bot myself and love it but I wanted something visual." His Oct 23 post used a different group chat for a one-off newsletter review: "I set up a group chat in Grok Bot and together with my agents, we started to go through all the information that was available." None of these name the Monday report.

Why it matters at work#

Our read: a founder's weekly numbers usually live in a bank tab, Stripe, an analytics tool and a social scheduler. Here the Bots bring them into one thread, check them against written KPIs, and he answers in the same place, so a correction like the expense rule lands with the Bot that made the mistake. He gives no time saved and no business result. His Oct 23 post says "sometimes there are periods where very little is working", so the report is a view of the business, not proof it grew.

Set it up#

These steps are ours, built from his post and the docs. His free sections show the jobs, not his prompts or routine settings.

Start with the CFO Bot. Connect your bank's MCP server, if it has one, with read access only (see Good to know).
Give Stripe to one or two Bots. On Oct 2 he limited it to the CFO and Chief of Staff. Our read: fewer Bots touching payment data means fewer places to check when a number looks wrong.
Write the KPIs down first. Put targets in a doc the Bots can read, so the report can say up or down against something.
Make one group chat for the report. Add only the Bots that feed it. In his screenshot, a message tagged to the Chief of Staff says to "always share the full report in this group chat".
Set the Monday routine, then test it. Name who builds the report, who reviews it, and where it goes.
Correct in the thread. Write rules with their exceptions, as he did for personal expenses.

Starter prompt (ours, untested)#

You are my CFO Bot for [company]. You only read. Every Friday, read last week's transactions and balances in [Mercury] and payments and cancellations in [Stripe], and compare them with the KPIs in [KPI doc]. Draft a short finance section for the Analyst Bot: cash in and out, the biggest movers, loan payments due, new cancellations, and anything that looks off, each with the transaction or payment it came from. Treat every expense as a business expense unless I tell you otherwise. Never request a payment or transfer, and never change a category or note; list any change you'd suggest and ask me. Don't message anyone outside this team.

The CFO Bot, Mercury, Stripe, the KPI doc, the business-expense rule and the team-only rule are his. The Friday timing, the section list, the links back to each transaction and the read-only and ask-first rules are ours.

Good to know#

Mercury's MCP can do more than read. It has write tools, and some apply right away: updateTransaction "Updates or clears an existing transaction's note or category immediately. No separate approval in Mercury." Payment requests are different: they need "approval in Mercury before money is sent" (Mercury Docs). Mercury also says "Existing read-only connections do not gain write access automatically" (Mercury Docs). He doesn't say which permissions he granted. Our read: for a Bot that reports, grant read only, so a wrong guess like the personal-expense one stays in the report and not in your books.
Group chats cost usage. "Every Bot reply counts toward your usage, including replies in a group and messages between Bots. Fewer Bots in a group means fewer replies" (Group chats help). His group had four Bots on Oct 2.
Bots hand work to each other. "There is no switch for this." To stop it, the help page suggests telling them: "Don't message other Bots. Ask me first." (Group chats help). Our read: his setup depends on handoffs, so set limits instead of asking for none.
Check the time zone and the first run. "Schedules use the time zone in Settings, under Bot, labeled Timezone", and "A new routine waits for its next scheduled time. It doesn't run when it's created" (Routines help). "A test does real work", so test with read-only access.
Email from a routine may wait. "Email from a routine, an incoming message, or other work you didn't start with that request waits as a draft until you press Send" (Approvals help). His Chief of Staff says it sends the Daily Report by email; he doesn't say whether to himself or from which address.

What to watch#

The paid sections. The title promises 11 routines, but the free part ends before his tool list and shows no routine settings. Signal: a free follow-up post or X thread that shows the Monday routine's instruction.
Whether the report moves to LiveWire. He is building a visual feed for the same numbers. Signal: a post saying LiveWire replaced the Monday report, or LiveWire's early access opening.
Numbers. No time saved or results so far. Signal: a Coffee + Revelation update that credits the report with a decision or a figure.

Sources#

Last checked: Nov 2, 2026, 12:18 to 12:22 PM ET. What changed: first published Nov 2.