How to run a monthly business review on Starch
A monthly business review is the meeting — or the document that spawns the meeting — where you take stock of what actually happened last month: revenue, burn, hiring, pipeline, key wins, open risks. Most operators run some version of it. The problem is it takes longer to prepare than to run. Someone pulls numbers from Stripe, someone else checks the bank, a third person digs up last month's deck to remember what you said you'd do, and by the time everything is in one place the meeting is already late.
What this looks like in practice varies. A SaaS founder's MBR centers on MRR, churn, and runway. A services business cares more about utilization and pipeline coverage. A CPG operator is watching inventory turns and channel margins. The underlying job — gather the data, make sense of it, decide what to do next — is the same across all of them.
On Starch, the output you walk into that meeting with is a current dashboard showing real burn rate and runway from your live bank and revenue data, a drafted narrative with your top metrics and month-over-month context, and a clean record of what was decided last time and what's still open. No exports, no copy-paste, no rebuilding the same slide from scratch. You describe the review format you want — what numbers matter, how you want them framed, where action items should land — and that structure is waiting for you at the start of every month.
Why it matters
Skip the MBR or run it on stale numbers and you make decisions a month behind reality. You miss the month burn ticked up before it became a runway problem. You forget the commitment you made to a key hire or a customer. You walk into a board or investor conversation without a clear story. Run it well and you have a documented trail of what you decided and why, which makes the next decision faster and keeps the whole team pointed at the same priorities.
Common pitfalls
The most common mistakes: pulling cash-basis numbers from the bank without reconciling against accrual entries, so burn looks different every time someone checks. Conflating last month's actuals with the rolling average, which smooths over one-time spikes that deserve attention. Starting the prep the day before the meeting, which means the review becomes a data-wrangling session instead of a decision session. And not capturing action items in a consistent place, so you spend the first ten minutes of every MBR reconstructing what you agreed to do last time.
Starch apps used
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Choose your operator
A version of this guide tailored to your role — same recipe, different starting context.
The AI stack built for the founder's office.
The AI stack built for small finance teams.
The AI stack built for small RevOps teams.
The AI stack built for small marketing teams.
The AI stack built for small customer success teams.
The AI stack built for small investor relations teams.
The AI stack built for CPG brands.
The AI stack built for DTC founders.
The AI stack built for boutique professional services firms.
The AI stack built for small law and accounting practices.
The AI stack built for emerging fund managers.
The AI stack built for real estate operators.
The AI stack built for independent clinic owner-operators.
The AI stack built for restaurant and hospitality operators.
The AI stack built for small property management firms.
The AI stack built for foundation and nonprofit ops teams.
Related workflows in Internal Comms & Meetings
A Slack announcement sounds simple — you're just telling your team something.
Read guide →An all-hands deck is the one artifact that has to make sense to everyone at once — the engineer who wants numbers, the ops person who wants decisions, and the new hire who's still figuring out what the company actually does.
Read guide →An async standup is how distributed and hybrid teams stay aligned without a daily calendar block.
Read guide →A team retrospective is a structured conversation where you look back at a project or sprint, name what worked, surface what didn't, and agree on what changes next time.
Read guide →