Expansion CAC applies the acquisition math to revenue you buy from customers you already have. The numerator is the spend aimed at upsell and cross-sell. The denominator is the expansion ARR that spend produced in the same period.
``` Expansion CAC = Spend on Upsell and Cross-Sell / Expansion ARR Closed ```
Why it needs its own number
A single blended CAC lets the installed base subsidize the acquisition engine. Expansion generally costs less per dollar of ARR because the trust, the security review, and the procurement path already exist. As the base grows, expansion becomes a larger share of new ARR, blended CAC falls, and a leadership team can spend a year congratulating itself on acquisition efficiency that came entirely from mix.
Splitting the two also fixes a budgeting error that runs the other way. Teams underfund expansion because it has no line item, then wonder why net revenue retention drifts down while headcount is added to outbound.
What to count
| Cost | Belongs in expansion CAC |
|---|---|
| Expansion AE and account manager payroll | Yes, fully loaded |
| Commission on upsell and cross-sell bookings | Yes |
| Lifecycle marketing to existing customers | Yes |
| Customer marketing events and user conferences | Yes, the growth portion |
| CSM time spent on upgrade conversations | Yes, allocated |
| CSM time spent on adoption and support | No, cost of revenue |
| Renewal management | No, retention cost |
| Product work that builds upgrade paths | No, R&D |
Reading it against retention
Expansion CAC explains what net revenue retention costs to produce. Two companies reporting the same NRR can be running completely different businesses if one buys expansion with a dedicated sales team and the other gets it from usage-based pricing with no incremental spend. NRR alone will never show that difference.
Forecast expansion as its own stream
Expansion behaves differently from new business. The population is known, usage signals precede the purchase, and timing clusters around renewal dates. Forecast accuracy on new and expansion business commonly lands around 90% in ORM customer data, and reaching that level takes considerable manual effort, which argues for modeling expansion separately rather than folding it into one pipeline number.
Once the stream is separate, expansion CAC becomes a lever you can plan against instead of a residual you discover after the quarter closes. Pair it with forecast accuracy tracking so the cost and the volume of expansion move in the same model.
Frequently Asked Questions
Should renewal costs go into expansion CAC?
No. Renewal holds revenue that already exists, so its cost belongs with retention. Expansion CAC covers only the spend aimed at growing an account beyond its current contract value. Mixing the two makes every account team look expensive and hides which motion is producing growth.
Why measure expansion CAC separately from new-logo CAC?
Because blending them lets a growing installed base mask a new-logo problem. Expansion usually costs less per dollar of ARR, so a shift in mix toward expansion improves blended CAC without any improvement in the acquisition engine. Separating the two makes each motion accountable for its own economics.
How do you allocate a CSM who both supports and upsells?
Split the loaded cost by logged time or by the share of expansion bookings that role is credited with, then apply the same rule every quarter. Support and adoption work belongs in cost of revenue. Only the portion aimed at growing contract value belongs in expansion CAC.
What is a reasonable target for expansion CAC?
There is no universal figure, and the useful comparison is internal. Track expansion CAC against your new-logo CAC and against the payback on each. When expansion CAC starts approaching new-logo CAC, the installed base is getting harder to grow and the product or packaging is the likely cause.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like expansion cac into prescriptive action for your team.
Schedule a Demo