If you are a B2B founder working on expansion revenue playbook, this is for you. Expansion revenue is a process, not a hope. For B2B founders past product-market fit, the difference between doing this well and doing it badly is sequence, not effort. Start smaller than feels comfortable, pick the one number that tells you it is working, and review that number weekly. The sequence below is the one we use.
Health scores should be simple and actionable
A customer health score has one job: tell you which customers need attention this week. If your health score requires a data scientist to calculate, it is too complex. If it does not lead to a specific action, it is too abstract. The best health score is three signals combined into red, yellow, green.
The three signals that matter for most B2B products: usage frequency, breadth of feature adoption, and relationship strength. Usage frequency is how often they log in. Breadth is how many of your core features they use. Relationship is whether your champion is engaged and responsive. Weight them equally, review weekly, and act on every red account within forty-eight hours.
QBRs are for the customer, not for you
The quarterly business review is not a report on your product's usage statistics. It is a strategic conversation about the customer's business and how you are helping them achieve their goals. If your QBR is a slide deck of login counts and feature adoption rates, you are doing it wrong.
The QBR that works: thirty minutes, three topics. Topic one is the customer's goals for the quarter and how you contributed. Topic two is what is not working and what you are doing about it. Topic three is what is next on your roadmap that maps to their needs. The customer should talk more than you do. If they are not engaged in the conversation, the QBR is a waste of both your time and theirs.
Support is a product feedback channel
Every support ticket is a product decision waiting to be made. A bug report is a quality issue. A how-to question is a UX issue. A feature request is a roadmap signal. If you are only resolving tickets without categorizing and analyzing them, you are throwing away your cheapest source of product intelligence.
Categorize every ticket: bug, UX confusion, feature request, or account issue. Review the categories weekly. If twenty percent of tickets are the same UX confusion, fix the UX. If ten customers request the same feature, consider building it. Support volume is a product health metric. Rising volume means your product is getting harder to use, not that your customers are getting needier.
Customer feedback should change your roadmap
If your roadmap looks the same after three months of customer feedback, you are not listening. Customer feedback should be the primary input to your product prioritization. Not the only input, but the primary one. The customers who use your product every day know things about it that you do not.
The system: collect feedback from support tickets, sales calls, customer success conversations, and NPS surveys. Categorize it by theme. Count the mentions. When a theme reaches ten mentions from different customers, it goes on the roadmap. This is not scientific, but it is better than building what the loudest customer asked for last week.
Renewals start ninety days before the contract ends
The renewal conversation does not start when the contract is up. It starts ninety days before. That is when you should be assessing health, identifying risks, and planning the expansion conversation. By the time the renewal date arrives, the outcome should already be determined by the value you have delivered.
The ninety-day renewal plan: day ninety, review the health score and usage data. Day sixty, have a value conversation with the champion: what have we accomplished together, what is next? Day thirty, address any concerns and present the renewal proposal. Day zero is a formality, not a negotiation. If you are negotiating on day zero, you started too late.
Frequently asked questions
What is the most important thing to know about expansion revenue playbook?
The most important thing about expansion revenue playbook is that it is a discipline, not a project. It requires consistent attention and regular adjustment as your company grows and your market shifts.
How long does it take to see results with expansion revenue playbook?
Most founders see initial signals within thirty to sixty days of focused effort. Meaningful, durable results typically take a full quarter of consistent execution before the pattern becomes clear.
What is the biggest expansion revenue playbook mistake founders make?
The biggest mistake is treating expansion revenue playbook as someone else's job. In the early stage the founder owns it directly. Delegating too early, before you understand it yourself, is the most common failure mode.
When should you start investing in expansion revenue playbook?
Start before you feel ready. If you wait until it hurts, you have already lost ground. The best time to build the habit is when the stakes are low enough to experiment without existential risk.
How does expansion revenue playbook change as you scale past twenty people?
What works at five customers breaks at fifty. The fundamentals stay the same but the systems, tools, and people you need change at each stage. Rebuild the process at every doubling.