The most expensive discount in your business is the thing you threw into the initial deal because the buyer was in the room.
Strategic unbundling is the counter-discipline: deciding, on purpose, what comes out of the initial sale. The first deal contains what the customer needs and can use now. Everything else is held back, attached to the milestone that earns it, and presented at full value when its value is obvious. I've made the pricing case already: timing is a price, and the $50 one-click stuffed into the first deal is the $500 offer it could have been at month six. I first made the 10x version of that argument in 2025. This is the operating discipline behind it.
And to be precise about what this is: sequencing, not subtraction. Nothing is taken away from the customer. It's re-timed to the moment they can actually capture it.
The Market-Complete Test
The first objection is always the same. If we hold things back, the core will feel thin next to competitors who bundle everything. Legitimate fear, wrong conclusion. The rule is that the core must be market complete: it enables the customer's first win without workarounds. What you hold back is what creates no value on day zero.
Three questions decide what stays in the core. Does the customer need it for their first win? Would its absence force them to slow down, switch tools, or change process on day one? Would most qualified prospects treat its absence as a blocker rather than a preference? Any yes, and it stays in the core. All no, and it's a candidate for sequencing: name the milestone that earns it, and hold it back.
Default expectations don't equal default value. Competitors bundle features because bundling closes demos, not because customers can use everything on day one. Most of what gets bundled is noise during onboarding and becomes signal later, when the bottleneck it solves finally shows up. Cut into the first win and you've cut too deep. Hold back what isn't missed until it's needed, and you've created expansion leverage.
Parity is a floor, though, not the whole answer. There's a second reason to put something in the first deal, and one test that decides both.
Tell Them What's Coming
Held back never means hidden. The play depends on telegraphing: at onboarding, the customer hears what the path looks like. When you hit that milestone, we're going to talk about the next thing. You're not ready yet. When you are, we will.
That sentence does two jobs. It makes the absence feel like design instead of stinginess: not we don't include that, but you don't need that yet, and here's when you will. And it puts the future on display, which is where the second engine starts. A customer who can see the next milestone has a reason to stay and work toward it.
Rebundle at the Milestone
When the milestone arrives, the offer isn't a line item added to an invoice. It's a rebundle: the product reframed around the customer's new operating reality. You closed the deals, the volume is here, this is what the next stage looks like. You're not adding functionality. You're consolidating their new stage into a clearer outcome.
That's also the test for timing. If presenting an item now would just add features, hold it. When it consolidates real progress into the next level of operation, that's the moment it earns its full price.
It Doesn't Come Back to Parity. It Comes Back Higher.
Here's the part people miss, and it's the part that makes this worth doing rather than merely tidy.
The intuition is that unbundling trades a smaller first deal for the same total later. Break even, at best, with better renewal hygiene. That isn't what happens, because the item doesn't return at the price it had inside the bundle. It returns at the price it's worth at the moment it's earned, and those are very different numbers.
Run it with real figures. Everything in the bundle, the deal is $1,000 a month.
Now pull one item out. Often the deal is still $1,000 a month, because the buyer wasn't valuing that item anyway; it was noise in a list. But take the pessimistic case and say you have to come down to $800 to close it.
Three months in, the customer hits the milestone that makes the held-back item obviously relevant. It is tied to progress they just made themselves. They can use it today, not eventually. And it accelerates something that's already working, which means it isn't a speculative purchase, it's the next step in something with proof behind it.
At that moment the item prices at $600 a month on its own.
So the account runs at $1,400 a month, or $1,600 if the initial deal never dropped. Against $1,000 for the bundled version of exactly the same software.
Inside the bundle, that item was worth $200. Presented at the milestone that earned it, the same item is worth $600. The only variable was when.
That is the whole mechanism, and notice what it isn't. Nothing was invented, nothing was repriced upward out of greed, and the customer wasn't squeezed. They paid more for the second item than they would have because it was worth more to them then than it would have been on day one, when they couldn't have used it and had no evidence it would help.
Which is why the pessimistic case still wins by 40%. Even when unbundling costs you something at the front door, timing pays it back with interest that compounds into every renewal after.
But They'll Use It Eventually
The obvious objection: if the customer is going to be ready in three months, and they already own the thing, they will start using it then. And if adoption is the worry, we'll drive adoption. We'll make sure they use it.
Three problems, and the last one is the one that should change your mind.
The first three months aren't neutral. They're paying for something they can't use. Not won't, can't, because they haven't reached the point where it does anything for them. Every month of that's a line on the invoice with nothing behind it, and at renewal the buyer audits exactly that: what did we pay for, what did we use. That audit is where contraction comes from, and you spent three months writing the evidence for it.
Will you, though? The plan to drive adoption at the right moment requires knowing when the right moment arrived. That means the milestone is defined, the signal is instrumented, and somebody owns acting on it. If a company has all of that, it doesn't need this argument. If it doesn't have all of that, then we'll make sure they use it's a hope with a calendar attached, and hope is what got the item stuffed into the deal in the first place.
And be honest about the incentive, because that's the real reason it doesn't happen. The item is already paid for. If the customer activates it, you collect nothing additional. If they never touch it, you lose nothing this year, and the worst case is they trim it at renewal. So the work of watching for readiness, reaching out, and walking them through it carries no payoff whatsoever. Nobody prioritizes unpaid work against a quarter that has actual numbers in it. That isn't a character flaw, it's arithmetic, and it's why bundled items sit dormant for nine months in companies full of diligent people.
And now the part that decides it. Suppose you do it perfectly. You defined the milestone, you saw the customer cross it, you reached out, you helped them adopt the thing they already own. Excellent work.
That is the identical work, at the identical moment, with the identical customer, as presenting it as an earned offer. Same milestone. Same conversation. Same readiness. Same person doing it.
The labor is exactly the same. Only the invoice is different.
One version of that conversation adds $600 a month, because the customer is buying something they can now clearly see the value of. The other version activates a feature they paid roughly $200 for as part of a bundle nine months ago, and everybody agrees it went well.
So the objection doesn't actually defend bundling. It describes orchestration, accidentally, and then declines to charge for it. If you're capable of the adoption push, you were always capable of the offer. The only thing bundling bought you was the privilege of doing the work for free.
Unbundling Manufactures the Forecast
Now watch what changes when that same item sits outside the deal.
Getting the customer ready, and getting them to the moment where the offer is obvious, is suddenly worth $600 a month. The adoption work has a payoff attached, so it gets done, by someone with a reason to do it. That alone is worth the restructuring.
But the larger thing is what it does to the number.
If you know that a customer of this shape reaches this milestone around month three, and that the offer attached to that milestone runs $600 a month, you have a forecast. Not a hope. A specific expectation, about a specific account, in a specific month, which adds up across the base into a figure you can put on a wall.
And a forecast that goes unmet is a loss.
That matters more than it sounds like it should. Expansion is normally the only revenue motion with no loss in it, which is exactly why nothing in the organization fights for it: no stated number, no variance, nobody accountable when it doesn't happen. Unbundling attacks that structurally rather than by persuasion. Hold the item back, attach it to a milestone, put a price on it, and the expansion you should have collected becomes a number somebody can miss.
Bundled, that $600 was never anywhere. Unbundled, it's in the forecast, and now somebody notices when it doesn't arrive.
Why Unbundling Fails Alone
Here's the root cause piece, and it's the reason unbundling can't be adopted as a standalone pricing trick. Companies front-load the initial sale exactly to the degree they distrust their future revenue from that customer. Hold something back without the machinery to sell it later, no milestones instrumented, no owner, no orchestrated motion, and the held-back item simply never sells. Which re-teaches the org that stuffing was right all along.
So the sequence matters: the number, the inventory, the milestones, the owner. Belief without that machinery is how unbundling dies in a quarter. With it, every held-back item has a moment, a price, and a person responsible for presenting it.
Competitors can win the checklist. You win the sequencing.
The bundle-everything competitor is playing acquisition. You're playing lifetime. They bought the demo with a feature list and gave away their expansion leverage to do it. You kept yours, told the customer exactly when it's coming, and priced it for the moment it matters. Strategic unbundling is a price increase that never appears on the pricing page, and it takes effect with the next contract you sign.
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.