Monthly Business Review for a Small Team: A One-Hour Agenda, Who Preps Each Number, and a Pre-Read Built in Slack

Most small teams that try a monthly business review stop after three months, and the prep is usually what breaks it. The founder spends the evening before opening Xero, HubSpot, Stripe and Google Analytics, pasting numbers into slides, and messaging people for the context behind a bad week. The meeting then becomes a reading of numbers nobody has thought about, and the decisions made in it are gone by the following Tuesday.

This guide is about the prep. You get a one-hour agenda you can copy, a table of who owns each section and which tool its numbers come from, a way to have the numbers assembled in a Slack thread days before the meeting, and a simple log that keeps decisions from evaporating.

The short answer

A monthly business review that survives past the third month has four parts:

1. A fixed date. The pre-read is assembled in the first few working days after month end. The meeting happens a few days later, same slot every month.
2. Named owners. Every section of the review has one person who explains it. The founder is not the default owner of everything.
3. A pre-read, not a presentation. Numbers arrive in writing before the meeting, with a short comment from the owner on anything that moved. The meeting is for questions and decisions.
4. A decision log. Every decision gets an owner and a date, written down the same day, and the next review opens by checking it.

The rest of this article implements those four parts for a team of 5 to 100 people that works in Slack.

Why monthly reviews fall apart at small firms

Large companies have finance and operations staff whose job includes the review pack. At Amazon, the model described in Working Backwards' notes on business reviews has each group leader write their own section with help from their team and a finance counterpart, within five to ten business days of month end, with written commentary on any metric above or below plan. A Hacker News commenter describing Amazon management gives the same picture from the inside: each team writes up the state of its own small part of the business, and the reviews roll up from there. That is one person's account, but it matches the published model.

A ten-person agency or a thirty-person software company has none of that support. So the founder becomes the finance counterpart, the analyst and the presenter at once. Three predictable failures follow:

• The numbers arrive late. If the numbers are pulled the night before, nobody has time to ask why revenue dipped, so the meeting turns into guessing.
• Raw data instead of insight. Mercury's guide to the monthly financial review advises that a founder with a team should bring the team insights rather than raw data. That is impossible when the person presenting saw the numbers an hour ago.
• No record. The same Mercury guide names skipping months and not taking notes among the common mistakes. Both come from the same cause: the review depends on one tired person.

The fix is to move the work earlier and spread it across owners, with the mechanical part (fetching numbers from tools) done by something that does not get tired.

A one-hour monthly business review agenda you can copy

This agenda assumes a team where five to eight people own a decision or a number. Keep the meeting at an hour. If it regularly runs over, the pre-read is not doing its job.

For each metric, use the format KPI Fire recommends for the monthly review: the target, the actual value, a red, yellow or green status, and one short comment on why. A red number with no explanation produces a ten-minute discussion; a red number with a two-line explanation produces a decision.

If you want a longer list of reports to draw from, the Deliberate Directions monthly business review template lists the statements a small business usually pulls each month: profit and loss, balance sheet, cash flow, and receivables and payables. Most small teams need fewer than that. Pick the five to eight numbers that would change a decision, and leave the rest in the accounting system.

A weekly business review is a different meeting

Some teams try to fold everything into a weekly business review. Weekly check-ins are good for operational numbers that change fast, like open support tickets or pipeline added this week. They are bad for profit, cash runway and budget, which need a closed month to be meaningful. Keep both if you have both kinds of numbers, but do not let the weekly meeting absorb the monthly one. If you already post weekly KPIs, see our guide to automating weekly KPI reports in Slack without publishing bad numbers; the monthly review then reuses those definitions.

Who preps each number, and from which tool

Most monthly business review templates show the slide and leave out who fills it in. Write this table once, in the channel where you run the review, and the prep stops depending on the founder's memory.

Each owner writes three lines at most: status, reason and what they propose. That is the written commentary from the Amazon model, cut down to something a busy person will actually do.

Build the pre-read in a Slack thread

Here is how the mechanical part can run in Slack with the Kipwise agent. It works inside the tools your team already uses, each connected with the person's own access: Xero, QuickBooks, HubSpot, Pipedrive, Stripe, Analytics, Search Console, Google Sheets and the project tools above.

You set the pre-read up once as a scheduled request in your review channel. A worked example (made up for illustration):

> Founder, in #monthly-review: @Kipwise on the second working day of every month, start a thread with last month's numbers: profit and loss and aged receivables from Xero, payments and failed payments from Stripe, new and won deals from HubSpot, and sessions by channel from Analytics. Tag @Dana for pipeline, @Sam for marketing and @Lee for delivery and ask each for a three-line comment.

Creating the scheduled task shows an Approve or Deny card once; later runs do not ask again. On the second working day the agent posts the figures in a thread in the channel, using the same tools and permissions as a live request from the founder. The owners reply in the same thread with their comments. Anyone can ask a follow-up there, such as which client owns the largest overdue invoice, and plain replies in the thread continue the conversation without mentioning the agent again. You can list or cancel the job, and ask what happened on earlier runs, including failures.

Our post on Slack reminders and recurring checks explains the difference between this and a plain /remind: a reminder tells a person to go and fetch the numbers, while a scheduled request fetches them.

Run it right after month end

Schedule the pre-read for the first working days after month end, not the night before the meeting, because that gap is what gives each owner time to comment on the numbers that moved. Working Backwards puts the written review within five to ten business days of month end, and the sooner the better. For a small team, this is a recommendation: post numbers on day two, collect comments by day four, meet on day five or six. If your books are not closed by day two, move the whole schedule later rather than reviewing half-closed numbers.

Pick the schedule owner by access

A scheduled pre-read can only pull from the tools the person who set it up has connected, so pick the schedule owner by who can see the finance, sales and marketing numbers, and ask every other owner to add their section in the thread. The agent acts with the asking person's permissions, not with a shared admin login. That is the right default for financial data, but it changes the design. If the founder sets up the schedule and has no HubSpot connection, the pipeline numbers will not appear. Do not share a login to work around it. Either the founder connects the tools they already have access to, or the sales lead posts the pipeline section in the thread themselves, or asks the agent in the thread with their own connection.

Keep the decisions from evaporating

Write the decisions into a page on the day of the meeting, because next month's review should open by checking last month's decisions, and a slide deck does not keep them. This is a recommendation built on Mercury's warning about not taking notes and on the first five minutes of the agenda above, which only work if the log exists.

In Slack it is one more reply in the same thread after the meeting:

> Founder: @Kipwise write up the decisions from this thread in the Monthly reviews folder: owner and due date for each.

The agent drafts a Kipwise page from what was said, puts it in the folder you name and posts the link, and it can append to an existing page instead of making a new one each month. The page shows the founder as the author. Next month's thread starts with that link.

Keep the log plain: decision, owner, due date, status. Leave the discussion out, because the next meeting only needs the decisions.

Handle failure and edge cases

• A connection is missing or expired. The agent reports what it could read and does not fill the gap with a guess. Treat a missing section as a red flag for the meeting, not as zero.
• Numbers look wrong. A number that moved by more than you expect is either news or an error. Ask in the thread where it came from; the Stripe figures come with a link to the dashboard page next to them. The owner should confirm the number before the meeting, not during it.
• Several Xero organisations or QuickBooks companies. Each Xero organisation is a separate connection, and a QuickBooks connection is one company. The agent says which organisation or company it read. Check that line before you trust a total.
• An owner does not comment. Do not chase in private messages. Leave the section uncommented in the pre-read so the gap is visible, and give it two minutes in the meeting.
• Someone asks for a change during the review. Changes in a connected tool, such as updating a deal or an invoice, wait for an Approve card that only the person who asked can use. Keep changes out of the review thread unless the decision was made in the meeting.
• What stays with people. The judgement on what a number means, every decision, and anything a client will see. The agent fetches, summarises and writes up, and the decisions stay with you.

Verify it works

Run the first review as a pilot and check these after the second month:

• The pre-read thread was posted on schedule both months, with every section filled in or explicitly missing.
• Each owner commented before the meeting, not in it.
• The meeting finished within an hour.
• The decision page exists, and the second review opened by checking it.
• The founder spent less than an hour on prep. If you track one number about the review itself, track that.

If two of these fail, fix the schedule or the owner table before adding sections. A smaller monthly business review that happens every month is worth more than a complete one that happens twice a year.

Founders who run this alone sometimes use an AI agent per section and skip the team entirely. That can work for a solo business. Once you have a team, the comments from the owners are the useful part, and an agent that only summarises exports cannot write them.

What to do next

Before your next month end, write the owner table above into your review channel with real names and tools, and pick the person whose connections cover the most sections as the schedule owner. Then set one scheduled request for the second working day of the month. If you want the agent to assemble the pre-read, Kipwise costs $10 per user per month with a minimum of three users, as listed on the pricing page.