This is the most common objection I get to any argument about expansion, and it's the right instinct pointed at the wrong number.
The instinct is correct. There are conditions under which expansion isn't the answer, and running an expansion motion inside one of them makes things worse rather than merely slower. So I want to be specific about what those conditions are, because "we have a lot of churn" isn't one of them.
There's a stronger version of this objection, which is that expansion hurts the customer. That one is worth reading first, because the harm and the inflated forecast turn out to be the same missing piece. This piece is the diagnostic underneath it.
Churn Isn't the Unit
Churn is an outcome with at least three different causes behind it, and they point in opposite directions.
Delivery-failure churn. Customers left because they didn't get what they paid for. This one stops you.
Natural attrition. Companies go under, get acquired, change strategy, lose the champion to a better job. This is the cost of being in a market and it precludes nothing.
Outgrew-you churn. The customer left for something you could have sold them and didn't. This isn't a warning. It's the strongest expansion signal in the business, because it's proof the demand was real, specific, and unserved, and that you already had the answer. That's worse than having churn.
So "we have a lot of churn" isn't a reason to stop. It's a reason to find out which one you have. One of those three answers means fix delivery. The other two mean you're late.
The First Condition: Are You Delivering What You Already Sold
Here's the question, and notice that it's deliberately not a churn rate.
Of your last twenty churned customers, how many left because they didn't get the outcome they bought? Not budget. Not acquisition. Didn't get what was promised.
If that number is large, expansion is precluded. Not harder. Precluded. You can't outrun failed delivery with expansion revenue and the math never works, because the customers still with you in a delivery-failure business aren't staying out of enthusiasm. They're staying because switching is painful. Hostages don't buy more.
The work is delivery. Everything I argue about the customer base assumes delivery is real.
One warning, because this is exactly where the diagnosis goes wrong. Delivery failure wears a natural-attrition costume. "Budget cut" is what a customer says when the value didn't justify defending the line item. Take exit reasons at face value and you'll file a delivery problem under market conditions, then conclude you're clear to proceed.
The Second Condition: Is the Customer Arguing About What You're Worth
This one almost never gets named, and it blocks just as hard.
Are customers currently arguing about price, threatening to rebuild what you sell, or asking for discounts to stay?
You can't ask for more money from someone who is mid-argument that you're worth less than they already pay. Every expansion conversation you open lands on a foundation they're actively disputing.
The work here's positioning rather than delivery. Establish what they're actually buying before asking them to buy more of it.
What makes this one dangerous is that it shows up on accounts that look healthy by every measure you track. Nothing about the product changed. What changed was their estimate of what the alternative costs.
"We Aren't Sure" Isn't a Pass
The gate has three states, not two.
Clear means you checked and the answer was no. Precluded means you checked and the answer was yes. The third state is that nobody has looked, and it isn't the same as clear.
I built this rule into the software I use for this work: an unanswered precondition returns unverified, never clear. That's deliberate, because the failure mode here isn't the company that checks and gets bad news. It's the company that never asks and reads the silence as permission.
If you can't answer the twenty-customer question right now, that's your finding.
The Number Isn't Unactionable. It's Wrong.
It's tempting to say that sizing expansion inside a delivery failure gives you a correct number nobody can act on. That's the wrong diagnosis, and it hides the actual mechanism.
You can't size an opportunity that doesn't exist.
Run the real calculation. An expansion forecast is customers approaching a readiness milestone, times the share who take the offer attached to it, times the value of that offer. Now put a crashing customer into that formula. What's the probability they reach the milestone? Near zero. So their contribution is near zero, and the thousand a month sitting on the far side of a milestone they will never arrive at was never expansion revenue. It doesn't belong in the forecast, and a forecast that contains it isn't unactionable. It's overstated.
Which means delivery failure isn't a gate bolted onto the outside of the expansion math. It's already inside the math, and it works through the readiness term.
So why does the precondition need to exist at all?
Because almost nobody can run that calculation. Defining readiness milestones is the most common zero in the six questions. A company that can't answer that one doesn't size expansion by counting who is approaching a milestone. It sizes by proxy: seats times an average, ARR times a target uplift, a benchmark NRR someone saw in a deck. None of those formulas contain a readiness term at all, which is exactly why none of them can see that a third of the base is on its way out the door.
The precondition exists because most companies can't yet run the calculation that would make the precondition unnecessary.
Two Numbers, and Only One of Them Is a Forecast
There's a legitimate number in here and it's worth keeping clear of the illegitimate one.
Latent revenue is a counterfactual: what this customer base would be worth if delivery were real and the machinery existed. That number is honest, and in a delivery-failure company it's precisely the size of the prize for fixing delivery. Keep it. Use it to fund the repair.
An expansion forecast is a different object: who will actually reach a milestone, in what month, with what attached. In a company with failing delivery that number is small, and it's supposed to be small, because it's the one telling you the truth.
The error is presenting the counterfactual as though it were the forecast. That's how a company acquires a target it was never going to hit, misses it, and concludes that expansion doesn't work here rather than that delivery is broken. The inflated number doesn't merely waste a quarter. It manufactures evidence against the right answer.
"They Just Want the Thing They Bought to Work"
This is the strongest version of the objection and it deserves a straight answer, because it contains two completely different situations wearing one sentence.
If it doesn't work as sold, you owe them that. It isn't an expansion opportunity, it's a debt. Charging to fix what you already promised is theft, and the customer knows it even while they pay.
If what would actually make it work is something you never sold them and never promised, that's a different thing entirely. That's inventory you haven't built or haven't packaged: the services, the enablement, the capacity, the tier that actually fits. Not all of it looks like a subscription. Withholding it isn't restraint. It's the failure mode of the vendor who lets a customer struggle politely.
The line is what was promised. Teams wreck retention by collapsing those two and selling the remedy for their own failure. Teams also leave money uncollected, and leave customers stuck, by treating every unmet need as an apology they owe.
What the Gate Actually Is
It isn't permission to proceed. It's a diagnostic, and it has three outcomes.
If delivery is failing, you found your real problem and it was never an expansion problem. If customers are disputing your value, you found a positioning problem, and it was going to surface at renewal whether or not you went looking. And if neither is true, then the churn you were worried about is either the cost of being in a market or proof that customers wanted something you already could have sold them.
Two of those three say go faster.
Where does your company stand? Take the Latent Revenue Test: the six questions, self-served. Ninety seconds, no email required.
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.