When Customer Success becomes the junk drawer of the company, this framework shows you what to build first, what can wait, and how to create measurable impact on retention and expansion.
You became a CS leader and immediately inherited a list of responsibilities that had nothing to do with customer success. Getting case studies for Marketing. Reference calls for Sales. Building a Customer Advisory Board for the CEO. Managing feature requests and release notes for Product. And of course, support escalations that somehow became your problem.
But that’s only part of it. On top of all that, you’re firefighting to keep accounts that Sales overpromised to. You’re in back-to-back departmental meetings most of the day. You’re trying to manage a team, run 1:1s, and in many cases, carry your own book of business too.
And somewhere underneath all of that, you were supposed to be building a revenue-generating department.
This isn’t a you problem. It’s a structural problem that shows up in almost every CS org that grows faster than its systems. Customer Success becomes the “junk drawer” department because it sits closest to the customer, and proximity gets mistaken for ownership.
The result: you spend most of your time trying to keep your head above water, and almost no time building.
More effort won’t fix it. A system will. Specifically, a system that tells you what to build in what order, works inside the chaos rather than pretending the chaos isn’t there, and creates measurable progress even when you only have an hour a day to work on it.
That’s what the House of CS framework is. Before we get into the framework itself, it helps to understand why reactive mode is so hard to escape in the first place.
Key Takeaways
- Customer Success becomes reactive when it owns every unowned problem in the company.
- The fix is not more effort. It’s building the right parts of your CS operating system in the right order.
- Phase 1 is segmentation, Customer Value Realization Maps, clean data, and repeatable playbooks.
- Health scores come later, after you have a proven motion and trustworthy data.
- Retention comes before expansion if you want CS to create measurable revenue impact.
Why Reactive Mode Is Not a Discipline Problem
If you’re drowning in reactive work, it’s not because you’re disorganized or lack discipline. It’s because you’re operating without a system, and no amount of willpower fixes a structural gap.
When you’re constantly putting out fires, your brain never gets to the mode where real thinking happens. You’re in threat mode all day, which means strategy keeps getting pushed to “when things calm down.”
And things don’t calm down. Not without a system.
CS leaders who are just getting through the week rarely build anything lasting. Not because they aren’t trying. Because trying harder doesn’t fix a structural problem.
The House of CS asks you to do less, not more. It asks you to do the right things in the right order, so that each layer you build reduces the reactive load rather than adding to it.
The Three Mistakes That Keep CS Departments in Reactive Mode
Most CS leaders I work with have made at least one of these before they find the framework.
Trying to fix everything at once. When everything is a priority, nothing gets the focused attention it needs to change. You end up with a dozen half-built initiatives and nothing meaningful to show for any of them.
Building one customer journey based on what the company does, not what the customer is trying to achieve. Customers don’t buy your product to use your features. They buy it to get a result. If your journey maps your process instead of their path to that result, you’ll always be misaligned.
Buying a CS tool before you have clean data or the right processes to program into it. A CS tool is not an easy button. If you implement one before you know what you’re tracking and why, you end up with an expensive system full of noise, and you still can’t see what’s happening with your customers.
The framework solves all three by giving you a sequence, and a clear rule for when each piece gets built.
The House of CS: Four Phases of Maturity
The House of CS is built around four maturity phases. Each phase has a clear goal, a set of things to build, and a measurable signal that tells you when you’re ready to move to the next one. You don’t skip phases. You don’t run them in parallel. You move through them in order.
Every phase you complete reduces the reactive work of the phase before it. By the time you reach Phase 4, you’re no longer fighting fires. You’re running a system that prevents them.
Phase 1: Reactive
Goal: Build the foundational infrastructure that makes everything else possible.
This is where every CS department starts, and it’s where most CS leaders are when they come to me. Information is siloed, you can’t get ahead of anything, and you’re reacting to customer feedback rather than anticipating it. The focus here is on the who, the what, and the how.
The first thing to do is segment your customers, by use case and by revenue. Not all customers want the same thing from your product, and not all customers are worth the same to your business. You need to know both before you can build anything that works. If you need a deeper framework for that, customer segmentation is the place to start.
Once you’ve segmented, you build a Customer Value Realization Map for each segment.
This is different from a standard customer journey map. A customer journey typically maps what your company does. A Customer Value Realization Map maps two things in parallel: every step your team has to take on your end, and every step the customer has to take on their end, to get to their desired business outcome. Their goal, not your process.
(In the CS Leadership Academy, we build your Customer Value Realization Maps with you, step by step.)
This matters because goal achievement is what drives retention and expansion. Customers don’t renew because they like your CSM. They renew because they got the result they came for.
Before you can build any of this accurately, you also need clean data. You need to understand how your customers have historically gotten to their goals, what worked, what didn’t, and where they got stuck along the way.
If you don’t trust your numbers, you can’t measure anything, and you definitely can’t report on it.
Once you have proven Customer Value Realization Maps, you’re ready to build repeatable playbooks. And once you have clean data and solid processes, you’re ready to get a CS tool. Not before.
What you’re building in Phase 1:
| Component | Why It Comes First |
|---|---|
| Customer segmentation (by use case and revenue) | You can’t build one journey for everyone |
| Customer Value Realization Maps (per segment) | Maps both company steps and customer steps to goal achievement |
| Clean, trustworthy data | You can’t measure or improve what you can’t see |
| Repeatable onboarding playbooks | Built from your maps, not just “we trained them” |
The signal you’re ready for Phase 2: You have a repeatable way to get customers to their goal with your product. Not just pretending that onboarding + QBRs = renewal and expansion. Because it doesn’t.
This takes longer than most people want it to. But it’s the foundation. Everything else gets built on top of it.
Phase 2: Informed
Goal: Centralize your information and operationalize your CS motion with a tool.
Once your foundations are in place, it’s time to get a CS tool. This is a much bigger project than it looks like from the outside, and it’s exactly why you don’t want to do it too early. Without clean data and documented processes, you’re setting up an expensive system full of noise. If you want the full pre-buy checklist, see before you buy a customer success tool.
A CS tool isn’t an easy button. But it is essential for moving past reactive. What it does is get all your customer information in one place, so you can see patterns across your customer base instead of relying on what individual CSMs remember. That only works if you have good customer usage data feeding the system, which is why customer usage data matters so much.
In Phase 2, you start with simple automations built directly from your Customer Value Realization Maps. You already know the steps a customer needs to take to reach their goal. Now you automate the prompts and check-ins that keep them on track.
What you’re building in Phase 2:
- Your CS tool, properly configured with clean data and documented processes
- The tool as a single source of truth. All your customer information in one place, so your team stops chasing context across the CRM, the ticketing system, and a folder of call notes
- Time-based playbooks first. The ones that run on a schedule no matter what the customer does, rather than the ones triggered by customer behavior. Get those running and confirmed before you build anything that reacts to a signal
- Improved forecasting, so you can predict revenue more accurately
One thing you are not building in Phase 2: a health score.
I know that’s the part everyone wants to start with, and it’s what every demo leads with. But a health score is a summary of a motion you haven’t proven yet. Most CS leaders skip straight to health scores and risk alerts, and that’s where the wheels come off. This is crawl, walk, run, and Phase 2 is the crawl.
So keep doing what you’re already doing. Sentiment, responsiveness, whether anyone has complained recently. It isn’t sophisticated, but your team already knows how to read it, and it will carry you to Phase 3. The real score gets built once you know which signals predict retention and risk for your customer base. Not someone else’s. Yours.
The signal you’re ready for Phase 3: You can see patterns across your customer base and make data-driven decisions. Your forecasting is more accurate. You’re getting ahead of things instead of always being behind.
Phase 3: Proactive
Goal: Build a partially automated CS motion powered by data.
This is what most of us are aiming for when we talk about “proactive CS.” With your foundations solid and your data centralized, you can build the programs that let you get ahead of customers before there’s a problem, and create real expansion opportunities before they slip away.
Phase 3 is where you build the health score. Not the sentiment read you’ve been running, an actual score pulling in usage data, engagement signals, and support trends, telling you something true about where a customer is headed. You can build it now because Phases 1 and 2 are what taught you which signals matter for your customers.
Once it’s live, it does the thing you’ve been doing by hand. Usage drops for two weeks straight, the tool flags it and prompts your CSM to reach out before the customer goes dark.
What you’re building in Phase 3:
- A health score built on usage data and leading indicators. Not perfect, but reliable enough to act on
- Risk playbooks triggered by health score signals, so you’re intervening before a customer is already halfway out the door
- Expansion playbooks that identify the right moment for upsell and cross-sell conversations, based on data, not gut feel
- Optimized GRR, often into the mid-to-high nineties at this stage
- Growing NRR as expansion becomes more systematic
One important note on expansion. A lot of C-suites right now are pushing CS to prioritize upsell and cross-sell above everything else. I get why. But customers won’t expand if they haven’t achieved their goals yet. Phase 3 is where expansion becomes reliable, because you’ve done the work in Phases 1 and 2 first.
The signal you’re ready for Phase 4: Your GRR is strong, NRR is improving quarter over quarter, and you can point to specific programs driving those numbers, not just good CSMs working hard.
Phase 4: Predictive
Goal: Build a CS department that runs as a growth engine, not a firefighting team.
This is the phase most CS leaders never reach, because they never fully complete Phase 1. At Phase 4, it’s no longer a question of what the data means. You know what it means. So you can automate the low-value, repetitive tasks in the customer lifecycle and put your team’s energy into the strategic conversations that require human judgment.
What you’re building in Phase 4:
- Maximum automation of routine customer lifecycle tasks
- Strategic conversation frameworks for the moments that still require a human
- Predictable expansion: you can forecast when customers are likely to grow, not just hope they do
- A CS org that doesn’t depend on you to function day to day
The signal you’ve arrived: You have a real seat at the table. Not because you asked for it, but because the C-suite is pulling you into strategy conversations before decisions get made, not after.
How to Figure Out Which Phase You Are In
Most CS leaders I work with think they’re in Phase 2 or 3. When we dig in, they’re usually in Phase 1, with some Phase 2 work layered on top of an unstable foundation. That’s why the reactive work never stops.
Here’s a fast diagnostic. Answer honestly.
You’re in Phase 1 if:
- You have an onboarding checklist and QBRs, but they’re more of an internal to-do list than a guide for getting the customer to their goal
- You have one customer journey, the same for every customer regardless of what they’re trying to achieve
- You haven’t segmented your customers by use case and revenue
- You track customer health by gut feel: whether they’re responsive, whether anyone has complained recently
- You don’t fully trust your data, or you’re pulling it from multiple places (CRM, support tickets, CS notes) and it never quite adds up
You’re in Phase 2 if:
- You have a CS tool but you’re still getting the data clean and the logic figured out
- Your health score exists but you’re not sure it’s telling you the right story
- You manually double-check everything in the tool anyway, because you don’t fully trust what it shows
- You can see warning signs in the tool, but you’re not always sure they’re accurate
You’re in Phase 3 if:
- Your tool is live with health scores and automatic notifications, but too many alerts are firing and your team spends more time triaging them than working accounts
- You have expansion conversations, but they’re ad hoc rather than triggered by data
- Your NRR is improving, but leadership still sees CS as overhead rather than a revenue driver
You’re in Phase 4 if:
- Your systems run without your daily involvement
- You can forecast expansion, not just hope for it
- Leadership pulls you into strategy conversations before decisions get made, not after
If you’re in Phase 1 or early Phase 2, the most important thing you can do is resist the pressure to skip ahead. The executives pushing you toward upsell and expansion programs before your foundations are solid aren’t wrong about the destination. They’re wrong about the sequence.
What the House of CS Is Not
A few things worth clarifying before you take this into your next leadership meeting.
It’s not a rigid checklist. The phases are a sequence, not a script. What Phase 1 looks like at a 30-person startup is different from what it looks like at a 500-person scaleup. The principle is consistent. The execution is contextual.
You can’t build it alone. It takes buy-in from the C-suite, cooperation from Sales and Product, and the trust of your team.
Most executive teams genuinely don’t understand what’s involved in CS. They think it’s sending QBR decks, doing renewal calls, and having upsell conversations. They don’t see the work that has to happen behind the scenes to make any of those successful.
Customers don’t succeed with a product just because they bought it. Teaching the C-suite that, carefully and without making anyone feel defensive, is part of the job.
This is also where the framework earns its keep with your executives. When they see the map of how CS gets built and why it’s built in that order, they stop asking for things that are two phases away and start asking how to help you get to the next phase faster. And once they see exactly what it takes for a customer to reach their goal, they stop assuming retention just happens. Sometimes you do need more headcount while you’re building. The trick is making that case in the language of revenue, not workload.
You’ll build it more than once. You’ll revisit each phase as your company scales. What worked at $5M ARR will need to change at $20M. The House of CS is a discipline you keep practicing, not a destination you arrive at.
It won’t lead your team for you. The framework tells you what to build. It doesn’t tell you how to lead a team through uncertainty, manage up to a skeptical CFO, or make the hard calls when resources are constrained. Those skills are a separate layer, and they matter just as much as the strategy.
The good news is that the framework is genuinely prescriptive. Every phase has a clear sequence of initiatives, and inside the CS Leadership Academy, each one comes with the exact steps, templates, and scripts to implement it. The coaching is for when you hit a real-world snag: a difficult stakeholder, a security constraint, a C-suite that keeps moving the goalposts. The framework tells you what to do. The coaching helps you do it in the actual environment you’re working in.
How to Start Building Your House of CS
If you’ve gotten this far and you’re nodding along, here’s the honest next step: identify your current phase and pick one thing to build.
Not five things. One.
The most common mistake at this point is writing a 90-day plan with twelve initiatives across all four phases. That plan won’t survive contact with your actual week. Pick the single highest-leverage gap in your current phase and close it. Then pick the next one.
The sequence that works:
- Audit your current state. Use the diagnostic above. Be honest about which phase you’re in, not which phase you wish you were in.
- Find the one thing missing from your current phase that’s causing the most friction. Usually it’s something in Phase 1: a customer journey that maps your process instead of the customer’s path to their goal, or segments based on ARR instead of use case.
- Build that one thing. Not perfectly. Well enough to be consistent.
- Check whether it moved the metric you expected it to move. Tweak and revise. You don’t have to get it right the first time. You have to get it working well enough to learn from.
- Repeat until your phase is stable, then move to the next one.
This sounds slow. It’s not. CS leaders who follow this sequence consistently tell me they see meaningful progress within 60 to 90 days, because they’re finally fixing root causes instead of symptoms.
What to Do If You’re Under Pressure to Move Faster
You’re probably being asked to show results before your foundations are ready. That’s a real constraint, and I don’t want to be glib about it.
The answer is to get better at explaining what you’re building and why it will produce the results the C-suite wants. A CFO who understands that your NRR problem is a data problem, not a headcount problem, will give you the space to fix the right thing. A CFO who thinks you’re “just working on CS strategy” will keep pushing for upsell conversations before your retention is solid enough to support them.
Translating CS strategy into the language of revenue and retention is one of the highest-leverage skills a CS leader can develop. It’s also one of the things I spend the most time on in the CS Leadership Academy.
The Real Measure of a CS Operating System
The goal of all of this isn’t a beautiful org chart or a perfectly documented playbook. It’s a CS org that creates measurable, attributable revenue impact.
That means:
- Gross Revenue Retention (GRR) that is stable or improving, because churn is caught early and addressed systematically
- Net Revenue Retention (NRR) above 100%, because expansion is a program, not an accident
- A team that can execute without you in every conversation, because they have the systems, the training, and the clarity to do their jobs well
- A seat at the table, because you can walk into a board meeting and show exactly how CS contributed to growth last quarter
That last one matters more than most CS leaders realize. McKinsey’s analysis of public B2B SaaS companies found that those with net revenue retention of 120 percent or more trade at a median 21 times revenue, against nine times for those below it.
The organizations that can attribute NRR improvement to specific programs are the ones that get funded. The ones that can’t make that case get cut.
You became a CS leader because you care about your customers and you want to make sure they achieve real value with the product. The House of CS is how you make that happen in the messy real world, where things aren’t perfect and Customer Success isn’t the company’s top priority.
Frequently Asked Questions
What is the House of CS framework?
The House of CS framework is a sequenced way to build customer success operations in the right order. It helps CS leaders decide what to build first, what to defer, and how to create measurable retention and expansion impact without trying to do everything at once.
What are the four phases of the House of CS?
The four phases are Reactive, Informed, Proactive, and Predictive. Each phase builds on the one before it, starting with segmentation and customer value maps, then moving into tooling, health scores, and more automated customer success motions.
Why should CS leaders not start with a health score?
A health score is only useful after you have clean data, clear processes, and a proven customer motion. If you build one too early, it usually becomes noise instead of a reliable signal, which makes the team trust it less.
What should a CS leader build first?
Start with customer segmentation and a Customer Value Realization Map for each segment. Those two things make it clear how customers actually reach value, which gives you a better foundation for onboarding, playbooks, reporting, and later automation.
How does this framework help retention?
It helps retention by making customer value achievement more repeatable and visible. When you can see where customers get stuck and build around those blockers, you reduce preventable churn and make it easier to show impact to leadership.
Ready to build yours?
You can absolutely use this framework to start on your own. Pick your current phase, identify the one thing to build next, and get to work.
Or, if you’d rather not reinvent the wheel at every turn, that’s exactly what the CS Leadership Academy is for.
The CS Leadership Academy is a 12-week group coaching program where you get the complete House of CS framework, with every initiative for each phase broken down step by step, along with the scripts, templates, and playbooks to implement them. You also get weekly live coaching calls where you can bring your real-world situations and get help applying the framework to your specific company, team, and C-suite.
Over 250 graduates. A third get promoted or land a better-paying job within 6 months of completing the program.
