Expansion Revenue Playbook

Purpose

This recipe builds a segment-specific expansion revenue engine — defining activation thresholds, configuring upsell triggers, implementing cross-sell methodology, and establishing CSQL pipelines — that drives measurable NRR improvement. The output is a working expansion system with per-account readiness scores, automated trigger alerts, segment playbooks (SMB/Mid-Market/Enterprise), and an NRR tracking dashboard. [src1]

Prerequisites

• Customer health scores operational in CS platform or spreadsheet — minimum 3 months of scoring history
• Product usage data accessible via analytics platform API or export — feature adoption, login frequency, usage vs. plan limits
• Current NRR calculated by segment — baseline metric required before optimization
• Customer segmentation defined in CRM — SMB/Mid-Market/Enterprise tiers with ACV boundaries
• Billing system access — ability to query contract dates, current plan, add-on history
• CS platform or spreadsheet — tool for tracking CSQLs and expansion pipeline

Constraints

• Activation-first rule: never initiate expansion motions on accounts that have not reached defined activation milestones. Premature upselling degrades trust and accelerates churn. [src6]
• Expansion CAC must remain below $0.28 per $1 of expansion ARR to preserve the 4x cost advantage over new logo acquisition. [src1]
• Health score must be green (75+/100) before any expansion conversation. Expanding unhealthy accounts creates negative NRR drag. [src3]
• Segment NRR targets differ materially: Enterprise 118%+, Mid-Market 108%+, SMB 97%+. One-size-fits-all expansion plays underperform. [src4]
• QBR cadence must precede expansion motions. Accounts without regular business reviews show 36% fewer expansion opportunities.

Tool Selection Decision

Which path?
├── Early-stage (< 200 accounts) AND no CS platform
│   └── PATH A: Spreadsheet-Based — Google Sheets + CRM + manual triggers
├── Growth-stage (200-1000 accounts) AND CS platform available
│   └── PATH B: Platform-Assisted — CS platform + product analytics + CRM
├── Scale-stage (1000+ accounts) AND full stack
│   └── PATH C: Automated Pipeline — CS platform + PQL engine + CRM + BI
└── Product-led growth model
    └── PATH D: PLG Expansion — Product analytics + in-app triggers + self-serve upgrade

Execution Flow

Step 1: Define Expansion Readiness Criteria

Duration: 1-2 days · Tool: CS platform or spreadsheet

Define the activation milestones that must be met before any account is eligible for expansion. These form the "expansion readiness gate."

Verify: Review 20 recently-expanded accounts against criteria. 80%+ should have met them pre-expansion. · If failed: Criteria too strict (< 15% qualifies) or too loose (> 60%). Recalibrate with historical data.

Step 2: Identify and Configure Upsell Triggers

Duration: 2-3 days · Tool: Product analytics + CS platform

Build a trigger library — specific, measurable events that signal expansion readiness. Each trigger should have an automated alert and a defined response. [src2]

Verify: Run against 90 days of historical data. Each trigger should fire on 5-15% of eligible accounts per quarter. · If failed: Adjust thresholds; instrument missing analytics events.

Step 3: Build Cross-Sell Methodology

Duration: 2-3 days · Tool: CRM + CS platform

Cross-sell introduces a different product/module, not more of the same. Build a whitespace analysis framework. [src5]

Verify: Whitespace analysis identifies cross-sell opportunities in ≥ 30% of accounts above health threshold. · If failed: Broaden product adjacency map; review QBR notes for unmet needs.

Step 4: Create Segment-Specific Expansion Playbooks

Duration: 2-3 days · Tool: Document + CS platform configuration

Build three distinct playbooks based on segment economics and buyer behavior. [src4]

Verify: Each playbook has triggers, channels, timelines, owners, and success metrics. · If failed: Start with the largest-opportunity segment first.

Step 5: Implement Tracking and CSQL Pipeline

Duration: 3-5 days · Tool: CS platform + CRM

Build the operational infrastructure to track expansion from trigger through close. [src3]

Verify: 2-week pilot with 20 accounts. CSQLs move Trigger → Qualified within 7 business days. · If failed: Reduce trigger sensitivity or raise health threshold.

Step 6: Measure NRR Impact and Iterate

Duration: Ongoing (first measurement at 90 days) · Tool: BI dashboard + CS platform

Build an NRR impact dashboard and continuous improvement loop: NRR by segment, expansion ARR, CSQL funnel, trigger effectiveness, expansion CAC, and time-to-expansion.

Iteration cadence: Weekly pipeline review, monthly trigger tuning, quarterly full playbook review.

Verify: NRR shows improvement trend at 90 days. · If failed: Audit whether expansion motions are cannibalizing retention (check expanded-account churn vs. non-expanded).

Output Schema

{
  "output_type": "expansion_system",
  "format": "multi-document",
  "components": [
    {
      "name": "expansion_readiness_scorecard",
      "format": "spreadsheet",
      "columns": ["account_id", "segment", "health_score", "activation_status",
                   "expansion_readiness", "active_triggers", "recommended_motion",
                   "estimated_expansion_acv"],
      "sort_order": "expansion_readiness descending",
      "deduplication_key": "account_id"
    },
    {
      "name": "segment_playbooks",
      "format": "document",
      "sections": ["SMB", "Mid-Market", "Enterprise"]
    },
    {
      "name": "nrr_dashboard",
      "format": "configured platform",
      "metrics": ["nrr_by_segment", "expansion_arr", "csql_funnel",
                   "trigger_effectiveness", "expansion_cac"]
    }
  ]
}

Quality Benchmarks

If below minimum: Review trigger thresholds (likely too broad), check CSM capacity, or verify activation criteria (expanding unready accounts tanks conversion rates).

Error Handling

Cost Breakdown

Anti-Patterns

Wrong: Expanding Before Activation

Pushing upsells on accounts that haven't reached core feature adoption or time thresholds. Trust erodes, churn spikes within 2 quarters. [src1]

Correct: Gate All Expansion Behind Activation

Enforce the readiness scorecard. No CSQL is created until activation milestones pass. Reduces pipeline 30-40% initially but improves close rates 2-3x and eliminates expansion-driven churn.

Wrong: One Playbook for All Segments

Running the same CSM-led expansion motion for SMB and Enterprise. SMB cannot support QBRs; Enterprise will not respond to automated prompts. [src4]

Correct: Segment-Specific Motions

SMB: product-led self-serve. Mid-Market: CSM-led with sales overlay. Enterprise: strategic multi-threaded. Measure NRR per segment independently.

Wrong: Treating Cross-Sell Like Upsell

Approaching cross-sell as "buy more of what you have." Without a bridge narrative, cross-sell conversion stays below 10%. [src5]

Correct: Build the Bridge Narrative

Map each cross-sell pair: "Because you achieved X with Product A, you can now unlock Y with Product B." Support with peer case studies from same segment and industry.

When This Matters

Use when an agent needs to build an actual expansion revenue system with working triggers, segment playbooks, and tracking — not a strategy document about why expansion matters. Requires operational health scores and product usage data. Most valuable for SaaS companies with 100+ accounts that lack a formal expansion motion.