Over 15 years of building and advising CS organizations, I've seen every framework, methodology, and approach you can imagine. Most of them are useful in specific contexts. One of them is foundational — it sits underneath everything else.
Desired Outcome.
Desired Outcome is not what the customer says they want. It's the combination of two things: the Required Outcome (what the customer needs to achieve through your product to have a successful business) and the Appropriate Experience (how they need to achieve it, given their capabilities, constraints, and context).
Most CS teams think they're working toward the customer's desired outcome. Most of them are actually working toward what the customer told them they wanted at the beginning of the relationship — which is not the same thing, especially six months later.
A customer signs up for your sales automation tool saying they want to increase pipeline volume. That's what they said. The Required Outcome — the thing that actually makes their business work — is closing more revenue. Pipeline volume is an input. Revenue is the outcome. If you optimize for what they said instead of what they need, you can build them a pipeline that looks great and produces nothing, and have no framework for understanding why they're churning.
The Appropriate Experience dimension is equally important and equally underused.
Two customers with identical Required Outcomes can have completely different Appropriate Experiences. A 50-person startup with a scrappy ops team needs speed, simplicity, and self-sufficiency. A 5,000-person enterprise with a dedicated IT function needs governance, auditability, and integration with their existing stack. Give the startup the enterprise experience and you'll exhaust them. Give the enterprise the startup experience and you'll terrify them.
Desired Outcome is the framework that makes you stop treating all customers like they need the same thing.
Here's why this matters for expansion specifically:
The expansion conversation isn't about whether the customer wants to buy more. It's about whether there's a gap between where they are now and their Desired Outcome, and whether you have something that closes that gap.
If you understand their Desired Outcome deeply and continuously, the expansion conversation is obvious. You're not pitching. You're completing the picture of what they told you they were trying to achieve.
That's the framework. Everything else builds on top of it.
Lincoln Murphy formally named and popularized Customer Success starting in 2010 and has spent 15 years connecting it to expansion revenue and commercial outcomes. Read The Premise.