CHURN IS DEAD
The 30-Minute Monthly Business Review
11 min read · Strategy
Archive note: This issue predates the evidence ledger introduced in August 2026. Treat uncited benchmarks and examples as editorial analysis, not independently verified findings.
The head of enterprise CS at a $200M SaaS company spent 40 hours last quarter preparing for QBRs. PowerPoint decks filled with trailing 90-day metrics. Charts showing improvement trends. Customer health scores trending green. Executive summary slides highlighting wins and learnings.
Two weeks after the final QBR, their biggest customer churned.
The reason? A competitive evaluation that started six weeks earlier. The kind of strategic shift that shows up in customer behavior long before it hits your dashboard. The type of decision-making process that gets discussed in hallway conversations, not captured in health scores.
None of it came up in any quarterly review.
This isn't a story about better customer intelligence. It's not about health score accuracy or predictive analytics. It's about the fundamental flaw in how most CS organizations structure their most important meeting.
The QBR format assumes that looking backward helps you move forward. It assumes that quarterly reporting cadence aligns with customer decision-making timelines. It assumes that executive attention is best spent on historical analysis rather than future resource allocation.
All of these assumptions are wrong.
While this CS leader was building slide decks, her customer was building a vendor evaluation matrix. While she was analyzing last quarter's NRR performance, her customer was scheduling demos with competitors. While she was preparing to present improvements, her customer was preparing to leave.
The QBR failed because it was designed around the vendor's reporting calendar, not the customer's business timeline.
Customers don't make decisions quarterly. They make decisions when market conditions change, when leadership changes, when business priorities shift, when competitive alternatives emerge. These events don't wait for your QBR schedule.
Yet most CS organizations still structure their highest-leverage meeting around historical performance rather than forward-looking resource allocation. They still spend executive attention on outcome analysis rather than obstacle removal. They still treat quarterly reviews as reporting events rather than decision-making sessions.
The result is predictable: executives sitting through presentations about problems they can't fix, trends they can't influence, and outcomes they can't change. Meanwhile, the decisions that will determine next quarter's results are happening in real-time, without their input or support.
The QBR Theater Problem
Traditional QBRs follow a predictable script. Health scores by segment. NRR trends over time. Win/loss analysis. Customer feedback themes. Action items for next quarter.
The format encourages performance theater rather than business decision-making. Teams spend weeks crafting narratives that explain why metrics moved the way they did. They build compelling explanations for trailing indicators while next quarter's leading indicators go unexamined.
Executives nod along, ask clarifying questions about methodology, and approve vague action items that won't get reviewed until the next QBR. The meeting ends with everyone feeling informed but no one feeling equipped to make different decisions.
This is expensive theater. Not just the 40+ hours of preparation time. Not just the executive calendar slots consumed by reporting sessions. The real cost is opportunity: while teams analyze last quarter's outcomes, this quarter's results are being determined by resource allocation decisions that never get the benefit of cross-functional input.
The Monthly Business Review Alternative
The most effective CS leaders have replaced quarterly reviews with Monthly Business Reviews (MBRs) that flip the entire format.
Instead of asking "What happened last quarter?", MBRs ask "What decisions do we need to make this month?"
Instead of reporting on trailing indicators, they focus on leading indicator resource allocation.
Instead of analyzing historical performance, they identify forward-looking obstacles and assign ownership for removal.
The shift from QBR to MBR isn't about meeting frequency. It's about meeting purpose. QBRs optimize for reporting compliance. MBRs optimize for decision velocity.
This changes everything about how CS leaders spend their time and how executives engage with customer success outcomes.
The Monthly Business Review (MBR) Architecture
The MBR framework consists of four components that transform quarterly reporting into monthly decision-making:
1. Forward-Looking Resource Analysis
Instead of reviewing what resources were deployed last quarter, MBRs identify what resources will be needed next month based on current customer behavior patterns.
This means analyzing pipeline risk not as historical trend data, but as forward-looking resource requirements. If enterprise segment shows early adoption challenges, the question isn't "What happened?" but "What additional onboarding capacity do we need and where will it come from?"
If renewal conversations are starting earlier due to economic conditions, the focus shifts to "How do we reallocate CSM time to support extended evaluation cycles?" rather than "Why did renewal cycle length increase?"
The analysis becomes: "Given what we see happening now, what resources do we need to deploy differently next month?"
2. Decision Points Identification
Every MBR identifies the specific decisions that need executive input or cross-functional coordination to execute the forward-looking resource plan.
These aren't strategic decisions about CS methodology. They're operational decisions about resource prioritization that can't be made at the individual contributor level.
"Do we pull implementation resources from new customer onboarding to support renewal risk mitigation?"
"Should we fast-track the integration roadmap for customers showing early adoption plateau?"
"Do we need to adjust pricing discussions with Sales given current renewal conversation patterns?"
Decision points are specific, actionable, and time-bound. Each one gets assigned to a DRI with a decision deadline before the next MBR.
3. Obstacle Inventory & Ownership
QBRs treat obstacles as explanatory context for performance variance. MBRs treat obstacles as inventory items that need ownership and removal timelines.
The engineering bottleneck that's delaying key customer implementations doesn't get discussed as context for why onboarding NPS dropped. It gets catalogued as "Obstacle #3: API documentation gaps causing 2-week implementation delays" with engineering DRI and resolution target.
The pricing confusion that's extending renewal cycles doesn't get analyzed as a contributing factor to cycle length trends. It becomes "Obstacle #7: Package comparison complexity adding 3 weeks to renewal evaluation" with product marketing ownership and solution timeline.
Obstacle inventory forces specificity. Instead of "communication challenges between teams," you get "Customer escalation handoff between CS and Support taking >4 hours during business hours due to Slack-only coordination protocol."
Every obstacle gets a DRI, a resolution timeline, and a success metric. Obstacles that don't get resolved by the next MBR get escalated or deprioritized explicitly.
4. Success Metric Projection
Instead of reporting on last quarter's NRR, churn, or expansion results, MBRs project next month's performance based on current decision velocity and obstacle removal progress.
These aren't forecasts in the traditional sense. They're projections that assume current resource allocation and decision-making patterns continue unchanged.
"If we maintain current implementation support allocation and don't resolve the API documentation obstacle, we project 15% of new customers will hit their first value milestone more than 30 days late next month."
"If renewal conversations continue to require two additional stakeholder meetings due to pricing complexity, we project renewal cycle length to increase by another week on average."
The projections create urgency around resource reallocation and obstacle removal. They make the connection between this month's decisions and next month's outcomes explicit and measurable.
This isn't predictive analytics. It's scenario planning that helps executives understand the trajectory they're currently on and the specific interventions needed to change course.
From Theater to Business Impact
The MBR format transforms CS reviews from reporting events into decision-making sessions. Executives leave with specific resource allocation decisions, obstacle removal commitments, and performance projections that assume those decisions get executed.
Instead of slide decks explaining historical variance, you have resource reallocation plans.
Instead of trend analysis presentations, you have obstacle removal timelines.
Instead of action items that get reviewed next quarter, you have decision commitments that get tracked monthly.
The meeting becomes operational rather than analytical. The focus shifts from "How do we explain what happened?" to "How do we influence what happens next?"
This is the difference between CS reporting and CS business management.
Making the Transition
Moving from QBRs to MBRs requires changing meeting structure, preparation methodology, and executive expectations.
Start by auditing your current QBR agenda against business decision requirements. For each agenda item, ask: "Does this help us make better resource allocation decisions or remove obstacles faster?"
Items that don't pass this test get eliminated or reformulated. Historical performance analysis gets replaced with forward-looking resource requirements. Trend explanations get replaced with obstacle identification and ownership assignment.
The preparation shifts from deck building to decision preparation. Instead of crafting explanations for why metrics moved, teams identify what resources need reallocation and what obstacles need removal to improve forward-looking projections.
Executive expectations need explicit resetting. The meeting will no longer provide comprehensive historical analysis. Instead, it will provide specific decision recommendations and resource requirement projections.
Some executives resist this shift because they're comfortable with reporting formats and uncomfortable with decision velocity requirements. This resistance reveals whether executives want CS information or CS business impact.
Implementation Protocol
Week 1: Audit your current QBR agenda using the framework criteria. Identify which agenda items drive forward-looking decisions versus historical analysis.
Week 2: Design your first MBR agenda focusing on resource allocation decisions needed for next month based on current customer behavior patterns.
Week 3: Run your pilot MBR with explicit expectations set about the format change. Capture decision points, obstacle ownership, and resource commitments.
Week 4: Execute the decisions and obstacle removal commitments made in the pilot MBR. Track progress against projections.
Month 2: Run your second MBR reviewing decision execution and obstacle removal progress, then identifying next month's resource requirements.
The key is maintaining monthly cadence and decision focus. The moment you skip a month or revert to historical analysis, you're back to theater.
Most CS leaders spend their highest-leverage meeting explaining the past instead of shaping the future. The companies that make this transition spend their executive attention on the decisions that determine tomorrow's outcomes.
The choice is binary: reporting theater or business impact. You can't optimize for both.
By Kuber Sethi · All issues · Subscribe