Concept card

Cross-Selling & Upselling

As of 2026-07-24T14:00:00Z

Edited by Cédric-Olivier Mâry, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Cross-Selling & Upselling?

Cross-sell and upsell cost 5-10x less per deal than new-logo acquisition (2-3 hours vs 8-12 hours) yet most consultants avoid them from discomfort, not economics.

Cross-selling means offering an existing customer something different from what they originally bought — the client who purchased a Business Data Cloud migration is later offered Joule deployment governance. Upselling means offering more of the same, or a higher tier — a twelve-week migration engagement becomes a standing strategic advisory retainer. Both motions exploit the same underlying asymmetry: earning the first engagement is the hardest sale a consultant makes, because it requires building trust and context from nothing. Every engagement after that rides on trust and context already established, which is why cross-sell and upsell are structurally cheaper to close than new-logo acquisition, even though many consultants under-invest in them out of a reluctance to seem like they're always selling.

Why it matters

The effort asymmetry is large. Landing a new logo typically means a sustained account-based marketing effort spread over many months before a first conversation even happens. Selling into an existing relationship, once trust is established, can be a single well-timed conversation. For SAP analytics consultants running anchor-customer relationships, cross-sell and upsell together typically generate the majority of lifetime revenue after the first year — which means a consultant who never revisits an existing client after go-live is leaving the highest-margin, lowest-effort revenue on the table in favor of chasing new logos that cost far more attention per euro earned.

How it works

Why it matters in practice

Cross-sell + upsell typically generate 50-70% of customer lifetime value after year one in anchor-customer relationships.
Five concrete SAP-analytics adjacencies exist (BDC→Joule, Datasphere→SAC Planning, technical→advisory, LoB-to-LoB, implementation→managed-service) — each a scripted opening, not a hard sell.
NPS 9-10 at engagement-end is the go/no-go gate — proposing cross-sell to an NPS ≤6 customer signals tone-deafness, not opportunity.

Key points

Cross-sell = different offering to same customer; Upsell = more/higher-tier of same offering.
Hour cost: cross-sell 2-3h vs new-logo ABM 8-12h — 5-10× cheaper per deal.
After Y1, 50-70% of anchor CLV from cross-sell + upsell.
Five SAP-adjacencies: BDC→Joule · DSP→SAC · Tech→Advisory · LoB→LoB · Implementation→Operate.
Three upsell motions: scope expansion · duration extension · tier upgrade.
Trust prerequisite: NPS ≥ 9; NPS ≤ 6 = no-go.
Three timing windows: 4-6w pre-end · 2-3mo post-go-live · annual budget cycle.
Saturation cap: 3-5 active threads / anchor; 5+ in 2 years = pull-back.
Cross-Selling & Upselling is mastered only when it changes a named buyer decision.
Start with the semantic contract and control model before demonstrating the tool.

Terms used on this page

Cross-sell: Selling a different offering to an existing customer (e.g., BDC migration → Joule deployment governance).
Upsell: Selling more of the same offering or a higher tier (e.g., 12-week engagement → 24-week extension).
Trust-asymmetry rule: Cross-sell needs NPS ≥ 9 from current engagement. NPS ≤ 6 = no-go.
Five canonical adjacencies: BDC→Joule · Datasphere→SAC · Technical→Advisory · LoB→LoB · Implementation→Operate.
Timing window: Three high-conversion moments: 4-6w before engagement end · 2-3mo after go-live · annual budget cycle.
Saturation cap: Maximum 3-5 simultaneous active engagement threads per anchor before relationship retracts.
Switching-cost multiplier: Customer with 2-3 active threads has 3-5× the switching cost of single-engagement customer.
Cross-sell map: 12-month per-anchor planning artefact: which services, when, who sponsor, rough scope. Reviewed quarterly.

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →