TL;DR
- NDR is partly hardcoded. Different expansion models create different natural ranges.
- Seat, usage, module, tier, and cross-sell expansion are not interchangeable.
- If the ceiling is structural, execution alone will not close the gap.
- The right question is: what expansion model does the product actually support today?
Your NDR target can be unrealistic even if your team is competent.
That sounds uncomfortable because NDR is often treated like a pure execution score. Push sales harder. Improve lifecycle campaigns. Build better playbooks. But those fixes only go so far if the product itself does not contain the right expansion mechanic.
A seat-based product, a usage-based infrastructure product, a modular platform, and a tier-upgrade workflow tool do not share the same natural expansion profile. Expecting them to land in the same range is a category mistake.
This is why Dimension 9 of Product DNA matters so much. If the company is aiming at a retention or expansion benchmark that belongs to a different expansion model, the problem may not be revenue leadership at all. It may be that the product has a different ceiling than the dashboard assumes.
The 5 Expansion Models
The simplest way to diagnose NDR expectations is to ask how revenue is supposed to grow after the first purchase.
1. Seat-based expansion
Revenue rises as more relevant people adopt the product inside the account. This usually fits multiplayer products where each added user creates additional value.
2. Usage-based expansion
Revenue rises as customers consume more. This fits best when value and usage scale together and usage varies materially across customers.
3. Module or feature expansion
Revenue rises when additional teams or stakeholders need adjacent capabilities. This is common in platform-style products serving multiple workflows or user types.
4. Tier-based expansion
Revenue rises when customers move from one plan level to a higher one. This works when the value boundaries between tiers are clear and meaningful.
5. Cross-sell expansion
Revenue rises by selling adjacent products to an existing buyer. This usually requires a stronger platform or portfolio dynamic than a single-product business has.
| Expansion model | What it depends on | Typical natural ceiling |
|---|---|---|
| Seat-based | Multiplayer topology and relevant org size | Higher when departments can spread naturally |
| Usage-based | Value scaling with consumption | High when customer growth automatically increases spend |
| Module-based | Distinct user groups and additional capability needs | Moderate to high depending on platform depth |
| Tier-based | Clear plan boundaries and visible need to upgrade | Usually lower than seat or usage expansion |
| Cross-sell | Adjacent products with a shared buyer | Strong when portfolio fit is real |
Expansion problems often start as product-shape problems.
The pricing audit is useful when the team is debating NDR targets, expansion levers, or whether the current model can support the board's expectations.
What the Ceiling Looks Like in Practice
Public examples help because they show how different products naturally expand.
Slack benefits from a seat-based logic because the product becomes more valuable as teams spread. Twilio benefits from usage-based logic because customer growth drives API consumption. Salesforce benefits from module expansion because different functions buy into adjacent clouds over time. Zoom can support tier upgrades because growing organizations need increasingly advanced controls.
Now flip that logic. A single-player workflow tool using seat pricing has a lower natural ceiling because the account may never need many seats. A narrow product with no adjacent modules has less room for platform-style expansion. A tiered product where 80% of customers cluster on one plan may simply not have much room to expand under the current structure.
If the expansion model is weak, better playbooks only improve performance inside a limited range. They do not create a new range by themselves.
What to Do Instead
If the expansion target feels detached from reality, audit the model before blaming the team.
- Name the true expansion mechanic. Do not assume the current pricing page reflects the real account-growth pattern.
- Check whether the product supports the target range. A tier-based product should not be treated like a usage-based infrastructure business without evidence.
- Separate execution from structure. If the model is strong and the numbers are weak, fix execution. If the model is weak, discuss product change.
- Make the board conversation explicit. If leadership wants a higher NDR range, tie that ambition to a product roadmap, not just a sales mandate.
The most honest framing is simple: our current Product DNA supports this expansion model, which implies roughly this range. If we want more than that, we need a different product shape.
Expansion debates get easier once the product model is visible.
If NDR targets, pricing changes, and board pressure are all getting mixed together, start with the structural read before changing the playbook.
Why This Matters for Board Targets
Board pressure often turns this issue into a morale problem when it is really a classification problem. If leadership wants 130% NDR from a product that naturally behaves like a tier-upgrade business, somebody will look like they are underperforming even if the team is executing reasonably well.
The cleaner conversation is: what expansion model do we have now, what ceiling does that imply, and what product change would be required to shift into a different model? That turns an emotional target discussion into a strategic one.
FAQ
Can a product support more than one expansion model?
Yes. Some businesses combine seat growth, module expansion, and cross-sell. The important question is which model actually drives most of the expansion today.
Does a low NDR always mean the expansion model is weak?
No. It can still be an execution problem. The point is to check whether the ceiling itself is realistic before diagnosing execution.
Can pricing changes alone raise the ceiling?
Sometimes, but only when pricing is currently misrepresenting an expansion mechanic the product already supports. Pricing alone cannot invent an expansion model the product does not have.
What is the fastest sign our board target may be structurally wrong?
When the target resembles the benchmark of a very different product category and nobody can explain what product behavior would actually create that number.
Sources
About the Author
Jake McMahon writes about the structural layer underneath SaaS growth: pricing, expansion, activation, topology, and the revenue expectations teams often import from the wrong product models. ProductQuant helps companies align commercial targets to the product they actually have.
This article is part of the Product DNA series and is designed to sit next to the pricing and board-alignment pieces.
Set the expansion target after you classify the expansion model.
If NDR targets keep feeling disconnected from what the product actually does, start by identifying the ceiling the current product shape supports.