Should expansion be a separate pipeline stage?

Yes — use distinct opp type or stage track: Identified → Qualified → Proposal → Closed. Mixing renewal and expansion in one stage hides conversion and owner accountability.

Who owns expansion — AE or CSM?

CSM identifies and qualifies; AE or AM owns proposal and close on mid-market teams. Document the split — ambiguity kills expansion more than lack of leads.

What signals trigger an expansion opp?

Seat overage requests, new department pilots, support cases about advanced features, usage spikes, and explicit upsell interest in account rooms or QBR notes.

Can MCP help prioritize expansion accounts?

Read-first prompts can list accounts with expansion signals and open renewal in 90 days — humans decide opp creation. Write tools only after governance is live.

← Back to Salestrics Today

August 26, 2026 4 min read Salestrics Team

Expansion Pipeline Playbook for Mid-Market Teams

Mid-market teams run tight renewal playbooks — see the renewal playbook — but expansion still lives in hallway conversations: a CSM mentions seat growth, an AE hears it a week late, and nothing hits pipeline until quarter-end. Expansion pipeline is a separate motion with stages, owners, and signals from Resolve, product usage, and account rooms on Connect — not a renewal opp with a bigger number.

Expansion vs renewal (define both)

Motion	Goal	Typical owner	Risk if merged
Renewal	Retain base contract	CSM + AE overlay	Expansion discount buried in renewal
Expansion	Add seats, modules, or lines	AM/AE with CSM source	Renewal churn hides upsell miss
Cross-sell	New product line on account	AE or specialist	Wrong pricing on bundled renewal

First renewal conversations: first renewal guide.

Expansion pipeline stages

Identified — signal logged; CSM or AE validates within 5 business days
Qualified — budget holder named; use case and timeline documented on account
Proposal — Workspace doc on opp; pricing approved per discount policy
Negotiation — legal and procurement engaged; thread on deal room
Closed won / lost — reason coded; lost expansion feeds product feedback

Forecast hygiene applies to expansion too: pipeline forecast hygiene.

Signal sources on the graph

Signal	Where it lives	Action
Seat increase request	Resolve case or mail on account	CSM creates expansion opp Identified
Feature limit hit in product	Usage alert or case category	AM qualifies within 5 days
New department pilot	Connect account room or call notes	AE added; opp Qualified
Support Embed pre-sales misroute	Widget chat → case → sales	Route per embed policy
Positive QBR outcome	Workspace QBR doc on account	Expansion task with owner

Support Embed routing: Support Embed rollout. Desk context: Resolve queue hygiene.

Weekly expansion review (20 minutes)

New Identified opps — source signal and owner confirmed
Stuck Qualified >14 days — unblock or downgrade to nurture
Renewal overlap — accounts with expansion + renewal in same quarter — pricing strategy
CSM → AE handoff — any expansion without AE assigned
Lost reasons — pattern for product and packaging

Add to Monday revenue rhythm: weekly revenue standup.

CSM ↔ AE handoff template

Every Qualified expansion opp needs these fields on the account or opp — not a Slack paragraph:

Trigger — what signal started the motion
Champion — contact role and influence
Scope — seats, module, or line; rough ARR band (internal)
Timeline — tied to renewal or independent close date
Blockers — open P1/P2 cases, exec sponsor gap, budget cycle
Next step — dated task with owner

Sales to CS handoff symmetry: sales to CS handoff.

Pricing and packaging guardrails

Separate quote from renewal — unless customer insists on one paper; document blended discount
Line expansion — Momentum vs Resolve seat adds; line selection guide
One tier upgrades — Team → Growth; One Team vs One Growth
Discount approval — same matrix as new business; no CSM discretionary %

Read-first MCP prompts

List accounts with open Resolve cases tagged expansion or seat increase in the last 30 days, plus renewal date in next 120 days — group by account owner — read only.

Summarize expansion opps in Qualified stage with no activity in 14 days — include linked cases and last mail on account — read only.

Token policy: AI token pools. MCP overview: Salestrics MCP.

Anti-patterns

Expansion in renewal opp only — no stage discipline or forecast
CSM closes alone — pricing exceptions without AE audit trail
Signals in Slack only — never become Identified opps
Ignore desk data — support knows upsell intent before sales
Quarter-end batch — all expansion created last week of quarter

90-day maturity path

Month	Milestone
1	Expansion stages live; CSM trained on Identified creation
2	Weekly review on calendar; AE assignment SLA 48h
3	MCP read in review; lost-reason reporting to product

Worked example: seat overage to closed expansion

A mid-market SaaS customer opens a Resolve case: “Need 15 more seats before rollout.”

Day 0 — CSM creates expansion opp Identified; links case
Day 2 — AM qualifies: VP Ops is champion; timeline 30 days
Day 5 — Workspace proposal on opp; standard seat pricing
Day 12 — Negotiation in Connect deal thread; legal redline minor
Day 18 — Closed won; case resolved; CSM updates account plan

Without pipeline: case closed, seats sold informally, renewal team surprised at true count.