46 — Expansion Strategy
Status: CANONICAL · Commercial OS
Owner: Founder (CS + sales)
Last verified: 2026-07-21
Purpose
How land becomes expand: the three expansion vectors, their triggers, and the plays that convert earned trust into ARR without ever feeling like upsell. Expansion is architecturally native here — same Spine, new benches — and the strategy's job is to harvest what the architecture plants.
Target audience: CS (trigger detection), sales (expansion deals), founder (NRR planning).
1. The Expansion Model
NRR target ≥ 120% built from three vectors (mirrors the packaging ladder 31):
| Vector | Motion | Typical uplift |
|---|---|---|
| V1 Seats — same department grows | New CSMs/AMs onboard into existing benches | +10–20%/yr organic |
| V2 Tiers — trust matures | Growth → Command (the approval-and-memory upgrade) | ~2x on upgraded seats |
| V3 Benches — new departments | Sales, RevOps, Exec workbenches on the same Spine | The compounding vector: +50–200% |
The structural advantage (say it to buyers): expansion isn't a new implementation. The Spine already holds the organization's truth; a new department is a new projection of it. "Turning on the Sales workbench" is closer to adding a seat than buying software — day-one value inherits all accumulated truth and memory.
2. Trigger Catalog (CS detects; logged weekly 44 §2)
V1 seat triggers: new-hire announcements in the account team · login-shared-screen smells (two names, one seat — convert gently) · manager asking for "a view for the new person."
V2 tier triggers (Growth accounts): suggestions frequently executed manually in tools (approving in spirit — the Command pitch writes itself) · TruthLayer questions ("can it remember that we decided…?") · security/audit asks that map to Command governance features.
V3 bench triggers (the big ones):
- The forwarded morning: a CS workbench screenshot lands in a sales/exec Slack — "what's that?" (Ask champions to tell us when it happens; it always happens.)
- The QBR guest: a sales leader or COO attends a QBR where CS presents Twin-prepared, evidence-chained material ("why doesn't my team have this?")
- The handover proof: an account transfers between CSMs with full continuity; the VP notices what turnover used to cost
- The catch that crossed departments: an expansion signal CS surfaced becomes sales pipeline — sales just experienced the product's value without owning it
3. Expansion Plays
Play V2 — "You're already approving in spirit" (CS-led, 2 weeks)
Evidence: pull 5 examples where the team manually executed what the Twin suggested → show the delta (same judgment, plus the gate, execution, and receipt) → 14-day Command trial on those exact workflows → decision at trial review with realized numbers. Convert rate target ≥ 50%.
Play V3 — The Second Bench (CS opens, sales closes, 30–45 days)
- Champion brief: arm P2/P3 with the internal case (their own realized-value review — 64 template internal variant)
- Cross-department demo: their data already in the Spine — demo the Sales workbench on accounts the CRM already connected. Recognition is instant; this is our highest-converting demo (39 variant)
- Scoped land: 10–15 seats in the new department, own success criteria (45 runs again, faster — hydration already done)
- Commercial: new order form at list (design-partner discount does not auto-extend to new departments — 30 §3)
Play V3-Exec — The Enterprise Conversation (founder-led)
Trigger: 2+ departments live or P5 engaged. The pitch elevates from department outcomes to organizational continuity: one Spine across CS+Sales+Ops, exec workbench, Enterprise tier (SSO, policy, SLA). This is where ACV crosses $75K (30 deal math).
4. Rules
- Expansion follows evidence, never precedes it. No V3 play before the wedge's day-90 realized-value review exists. Premature expansion burns the champion's credibility — and ours.
- CS opens, sales closes, one story. The expansion deck is the customer's own numbers; sales adds commercial structure (37 Play 7).
- Never call it upsell in front of the customer. The language: "extending what's already working" — because architecturally, it is.
- Instrument the triggers. "Forwarded morning" and "QBR guest" moments get logged when detected; they're leading NRR indicators (75).
KPIs: NRR ≥ 120% (at scale; design-partner cohort tracked separately) · V2 conversion ≥ 40% of Growth accounts within 12 mo (31 §4) · V3: ≥ 30% of customers add a second bench within 12 mo · expansion ARR ≥ 40% of new ARR by end-2027 (77) · trigger-to-play conversion tracked per play.
Related: 31 Packaging · 44 CS Playbook · 47 Renewal · 35 Journey