How to Run a Monthly Business Review That Changes What You Do Next Month
Most monthly reviews are a ritual, not a practice. Owners pull the numbers, nod at the trends, and walk away with the same plan they had going in. The review happened. Nothing changed.
A monthly review that works produces one output: a decision about what to do differently next month. Not more data. Not a sharper understanding of the past. A decision. If you cannot name what will be different in 30 days because of this review, you ran a report, not a review.
Why do most monthly reviews fail to change anything?
Because they are structured around the wrong question. Most reviews ask: what happened last month? The right question is: what does last month tell me I should change next month? The first question produces a narrative. The second produces a decision. The format you use determines which question you actually answer.
I have sat in enough monthly reviews to recognize the pattern. Revenue is up, so the meeting ends early. Revenue is down, so the conversation becomes a search for explanations that land everyone back at the same conclusion they started with. The data is real. The decisions are absent.
The problem is not the data. It is the structure. When a review is organized around a dashboard, it ends at the dashboard. When it is organized around decisions, it ends at action. That is the only distinction that matters.
How do I review revenue the right way in a monthly review?
Review revenue against capacity, not against last month. Last month is a reference point, not a standard. Capacity is the ceiling. If you did 80 percent of capacity in revenue last month, the question is what blocked the other 20 percent. If you did 60 percent, you have a different problem than if you did 95 percent. Revenue growth relative to itself tells you the trend. Revenue relative to capacity tells you where the constraint is.
When I built the real estate company, I watched owners celebrate month-over-month revenue growth while running at 50 percent of what the team could actually handle. The trend looked good. The business was inefficient. The monthly number masked the real problem.
Capacity has to be defined before the review, not during it. If you do not know what full capacity looks like for your business in the next 30 days, that is the first output of this month’s review. Define it. Measure against it next month.
What is the one system to surface in every monthly review?
The one system that broke. Not the one that needs improvement. The one that failed in a way that cost you time, money, a client relationship, or team trust. Every month has one. If you cannot name it, you did not look. Surfacing one broken system and making a repair decision closes more operational debt than any quarterly planning retreat.
Most operators avoid this one because it requires naming something that went wrong on their watch. That discomfort is the signal, not the problem. The system that broke last month will break again next month unless you name it and fix it.
The Build Framework treats this as a monthly close requirement. You review revenue. You surface the broken system. You make a repair decision before you close the review. In that order. The decision does not have to be a full rebuild. It can be a single rule change, a new handoff protocol, or a conversation with one person. What it cannot be is nothing.
What client signal should I look for in a monthly review?
One signal that tells you how clients experienced your service last month. A cancellation pattern. A complaint that arrived twice. A piece of feedback that felt like a warning. A referral that came in at an unusually high rate. One signal, examined honestly, tells you more about the health of your delivery than any satisfaction score. The question is not what the score says. It is what the pattern points to.
Client signals are underread in most monthly reviews because they require interpretation, not calculation. A number is easy to report. A pattern requires judgment. Most operators avoid judgment in formal reviews because it feels subjective. It is pattern recognition, and it is the most important skill a founder runs in the monthly review.
I look for the one client moment that felt different from normal. A call that ended colder than it should have. A renewal that took longer than expected. A question a client asked that they should not have needed to ask. Each of those is a signal. The review is where you decide what to do with it.
BVR’s recurring service business benchmarks give you churn rate norms by business size. The benchmark tells you whether your number is normal. It does not tell you what is causing it or what to change.
How do I define the one reallocation for next month?
After reviewing revenue against capacity, the broken system, and the client signal, one reallocation almost always becomes obvious. You are either moving time, money, or attention from one place to another. Name it explicitly: “Next month, I am moving two hours per week from sales calls to delivery quality review.” Or “I am reallocating the budget from X to Y.” The reallocation is the decision the review was always supposed to produce.
This is where most reviews fall apart. The conversation surfaces the insight. Everyone agrees it is real. No one names a specific reallocation. The meeting ends. Next month looks the same.
The reallocation has to be named before the review ends. It has to be assigned to a person and attached to a time frame. “We should probably shift focus toward delivery” is not a reallocation. “I am cutting Thursday afternoon client prospecting and using that time to build the delivery checklist by May 15” is a reallocation.
A coaching engagement runs this exercise at a higher altitude, across quarters instead of months. But the monthly version is the practice that makes the quarterly version possible. You cannot make good quarterly decisions if you have not been making good monthly ones.
What is the trap of reviewing 30 metrics?
Reviewing 30 metrics produces 30 observations and zero decisions. The brain cannot prioritize across that much data in a single sitting. Most of those metrics will be in normal range. The ones that are not will be buried under the ones that are. A long dashboard review is a way of feeling thorough without being actionable. Cap your monthly review at five to seven metrics and make sure each one connects to a decision you might actually make.
I see this pattern constantly with founders who have invested in reporting tools. They built the dashboard. They run the review. They close the laptop. The data was never the problem. The volume was.
More metrics mean more to explain and less to decide. If you cannot fit your key monthly metrics on one screen without scrolling, you have built a reporting system, not a decision system. Cut it in half. Then cut it again. The metrics that survive are the ones that actually govern the business.
Frequently Asked Questions
How long should a monthly review take?
Ninety minutes, maximum. If you are going longer, you are reviewing history instead of surfacing what matters. Set a timer. The constraint forces you to identify what is important before the clock runs out.
Should I run the monthly review alone or with my team?
Run the data portion alone first. When the founder comes in without a view, the review defaults to whoever speaks most confidently. Form your own interpretation of the four signals before anyone else is in the room.
What if my business does not have clean data by the end of the month?
That is the first problem your monthly review identifies. If you cannot pull clean numbers within five business days of month end, your reporting setup is the constraint. Fix the reporting before optimizing the review.
How is a monthly review different from a quarterly one?
Monthly reviews are operational. They surface what broke, what to reallocate, and what client signal to act on. Quarterly reviews are strategic. They ask whether the direction is right. You need both. They are not interchangeable.
What do I do with the review output?
Make the reallocation decision you identified. Add one unresolved item to the following month’s agenda. The monthly review should always hand something forward. That is what makes it cumulative over time.
I coach founders and CEOs through what actually stops them from building businesses that run without them. I grew a law firm 191 percent year over year. Before that I built a real estate company from the ground up. Every system I teach I ran myself first. Learn more about my coaching approach at /coaching.