← All Posts

You'd Never Say Sales Doesn't Work

If your sales motion misses the number, do you say sales doesn't work?

Of course not. You diagnose it. Coverage is thin at the top of the funnel. Discovery is shallow, so deals stall at procurement. Ramp is nine months and you budgeted six. The comp plan pays the same for a bad-fit logo as a good one. Maybe the VP goes.

What you don't do is conclude that selling to strangers is a dead end and move the budget to something else. The failure attaches to how it was run, not to whether it can work.

Now watch what happens when the expansion number misses.

"Expansion doesn't work here." "Our customers aren't like that." "Our market's different."

Same evidence shape. Opposite verdict. One failure gets a diagnosis and a fix, the other gets the category retired.

Why the verdicts differ, and it isn't stupidity

You can only blame execution if you can say what good execution would have looked like.

Sales has thirty years of that language. Pipeline coverage, win rate by stage, ramp, quota attainment, territory design, discovery quality, deal desk, enablement. Every one is a named place to put a bad quarter. When the number misses, there are a dozen candidate explanations before anyone questions the motion itself, and each one is measurable enough to argue about.

Expansion has none of that. Ask what good expansion execution looks like and you get metrics, not mechanics. NRR is an outcome. So is expansion ARR. Neither tells you what anybody should have done differently on a Tuesday.

So when the attempt underperforms, there's nowhere to put the blame. No stage was skipped, because there are no stages. No condition went uninstrumented, because nobody named a condition. The only available explanation is the one at the top: the thing itself doesn't work.

The verdict is binary because the diagnostic vocabulary doesn't exist. Not because anyone is being lazy.

What that costs

A binary verdict can't be appealed. That's the whole problem.

If sales misses, next quarter you change something and run it again. The failure is a data point in an ongoing process. If expansion misses, the conclusion is terminal, and it quietly rewrites what the company will attempt for years. The belief goes on to prevent the only experiment that could disprove it, which is how a single bad quarter turns into a permanent position.

And the attempt that produced the verdict was almost always the same attempt: a number assigned to somebody, a quarter to hit it, and the only playbook on the shelf, which was the new-logo playbook pointed at people who already bought.

That attempt failing tells you something real. It tells you that aiming acquisition pressure at existing customers doesn't work. It's not a finding about expansion, any more than a bad cold call is a finding about your product.

But nobody can say that in the room, because saying it requires naming what the attempt was missing. And naming what it was missing requires the vocabulary that doesn't exist.

What a playbook is actually for

Here's the part I think gets missed, including by people who agree with everything above.

A method isn't only instructions for doing the thing well. It's what makes a bad result readable.

Once you can name the parts, a failure stops being a verdict and becomes a location. You didn't name a next thing on thirty-seven of your last thirty-nine calls. You never installed a readiness condition, so the offer went out on a calendar date to people who hadn't achieved anything yet. Nothing was held back, so there was nothing to point at when they were ready. Every promise on the call was one your delivery had to chase.

None of those sentences is "expansion doesn't work here." Every one of them is fixable, and every one of them is checkable against what was actually said.

That's the difference between a category you've retired and a process you're running badly. It's the same difference sales has had for thirty years and expansion has never had.

The test worth running

If you've already concluded that expansion doesn't work in your business, you're holding evidence and you should keep holding it. Don't throw the finding away.

Just make sure you know what it's a finding about.

Go back to the calls that produced it. Not the pipeline reports, the actual conversations. Look for whether anyone named a next thing, whether any condition was tied to something the customer would achieve rather than a date, whether anything was deliberately held back.

If those were all present and it still failed, you've learned something real about your market. That's worth knowing and almost nobody gets there.

If they weren't present, you didn't run the experiment you think you ran. You ran the other one, and it failed the way it always does.

Either way you'll have a location instead of a verdict.


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.

Access the 5x LTV Case Study.

See how one CRM SaaS drove 5x LTV in 90 days. Full framework, milestone breakdown, and cohort analysis.

← Previous
Expansion Isn't Cheap. You're Underpaying For It.
Next →
Whatever You Show Them Becomes The Point