Glossary/Metrics and Revenue

Expansion Revenue

May 27, 2026·By Jeff Moss

Revenue generated from existing customers beyond their initial contract, made up of two distinct motions: vertical expansion (the customer goes deeper in the same outcome, typically moving to a higher tier of the same product family with more capability or scale) and horizontal expansion (the customer takes on a different outcome, often a different department or use case, often a different product). EP uses vertical and horizontal expansion rather than upsell and cross-sell because the framing is value-driven, not product-pushed, and because expansion does not always require revenue (deeper adoption of already-purchased capability counts as expansion too).

"Focus on retention and you will not get retention. Focus on expanding value, and retention takes care of itself."

What it is

Expansion Revenue is revenue generated from existing customers beyond their initial contract. EP frames it as two distinct motions.

Vertical expansion is going deeper in the same outcome. The customer typically moves to a higher tier of the same product family, with more capability or scale, to drive a stronger result against the same metric they have been working on. Same outcome, more of it.

Horizontal expansion is taking on a different outcome. Often a different department, a different use case, often a different product. New outcome, new metric, new value.

EP uses vertical and horizontal expansion rather than upsell and cross-sell for two reasons. The framing is value-driven, not product-pushed. And expansion does not always require revenue. Deeper adoption of capability the customer already paid for, broader use of features already in their tier, more processes flowing through your product, all of that is expansion. The customer is doing more with you. That progression is the substance; the revenue is the consequence.

Most teams treat expansion as a sales motion. Identify accounts with budget, pitch more product. That frame disconnects expansion from customer value and produces short-term wins followed by churn. The mistake is "I have more products to sell, therefore I should call up the customer and see what more they can buy." The correct frame is that every product you build, every solution you add, should be a direct connection to additional value the customer receives, and it should map to specific use cases that require that additional value.

When you drive expansion this way, you automatically get retention. A customer expanding their use of your product almost always renews the original purchase. Expansion and retention are tightly linked when expansion is value-driven, and disconnected when expansion is product-pushed. Treat retention as a byproduct of expansion done well, not as a primary motion in its own right.

Source: methodology-canon/methodology-reference.md > Expansion Revenue

Key Takeaways

•Two motions: vertical expansion (deeper in the same outcome) and horizontal expansion (different outcome). Both can be paid or unpaid.
•Expansion is the natural progression of a customer's value with you. Dollars are the consequence, not the input.
•Driving expansion this way produces retention as a byproduct. A customer expanding their use almost always renews the original purchase.
•Expansion does not always have to be revenue-driven. Deeper adoption of features already purchased counts as expansion too.
•Define expansion motions per use case, not aggregate. Both vertical and horizontal expansion conversations start from the customer's value position, not from your product catalog.

The Mistake Everybody Makes

Most teams treat expansion as a sales motion: identify accounts with budget, pitch more product. That frame disconnects expansion from customer value and produces short-term wins followed by churn. The mistake people make is 'I have more products to sell, therefore I should call up the customer and see what more they can buy.' The correct frame is that every product you build, every solution you add, should be a direct connection to additional value the customer receives, and it should map to specific use cases that require that additional value.

How to Apply

1.Define expansion motions per use case, not aggregate.
2.For vertical expansion, map the customer's progression on the same outcome: where they are on the metric, which actions remain unimplemented, what tier of capability the next progression requires.
3.For horizontal expansion, map adjacent outcomes the customer has signals for: a different department asking, a different use case emerging, a new outcome the customer is starting to talk about.
4.In both cases, the conversation starts from the customer's value position, not from your product catalog.
5.Driving expansion automatically drives retention. Treat retention as a byproduct, not a primary motion.

Where Used in Product

Methodology:The Customer Results Map's pathways encode vertical expansion (deeper on existing outcomes) and horizontal expansion (broader to new outcomes).
Coaching:The AI coach uses the Map plus the per-customer Strategy Planner to script the pre-rationalized next-step expansion conversation.

Jeff Moss

Founder, Expansion Playbooks. A decade studying customer retention and expansion data from 75+ recurring revenue businesses.

Back to glossary