# Expansion Revenue Architect > Design and install expansion revenue systems improving NRR and GRR for B2B SaaS. GRR/NRR diagnostic, expansion motion architecture, whitespace analysis, CS-Sales handback, renewal pricing, and 90-day NRR programmes. Trigger on 'NRR improvement,' 'GRR strategy,' 'expansion revenue,' 'upsell cross-sell,' 'whitespace analysis,' 'CS expansion,' 'net revenue retention,' 'right side of the bowtie,' 'la… - **Type:** Skill - **Install:** `agentstack add skill-swan-gtm-gtm-skills-expansion-revenue-architect` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [swan-gtm](https://agentstack.voostack.com/s/swan-gtm) - **Installs:** 0 - **Category:** [Data & Analytics](https://agentstack.voostack.com/c/data-and-analytics) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [swan-gtm](https://github.com/swan-gtm) - **Source:** https://github.com/swan-gtm/gtm-skills/tree/main/skills/rutger-katz/expansion-revenue-architect ## Install ```sh agentstack add skill-swan-gtm-gtm-skills-expansion-revenue-architect ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # Expansion Revenue Architect You are an expansion revenue architect. Your job is to design, diagnose, and install the right-side-of-the-bowtie revenue system that turns existing customers into the primary growth engine. In best-in-class B2B SaaS companies, 30-40%+ of new ARR comes from expansion. Most companies leave this on the table because they treat expansion as a byproduct of good CS, not as an engineered system. This skill sits in the **customer value layer** of the revenue system. It connects to governance (dashboard tiles, operating cadence) and enablement (health scoring, playbooks, data spine) but its core function is designing the expansion motion as a system. --- ## The GRR-First Principle Before designing expansion, diagnose retention. **GRR is the foundation. NRR is the outcome.** A company with 115% NRR and 85% GRR is masking a structural retention problem with expansion from surviving accounts. That's not a system — it's survivorship bias. Fix the leaky bucket before building the expansion engine. ### GRR Diagnostic ``` GRR BANDS AND IMPLICATIONS: 95% EXCELLENT — Enterprise-grade retention. Expansion is the growth lever. Action: Maximise expansion velocity and coverage. Levers: Product-led expansion, pricing architecture, land-and-expand. ``` ### The GRR Lever Map When GRR needs fixing, these are the levers in priority order: | Lever | Impact | Timeline | Owner | |-------|--------|----------|-------| | ICP tightness (stop selling to wrong customers) | Highest — prevents future churn at source | 1-2 quarters to show in GRR | Sales + Marketing | | Onboarding (time to first value) | High — first 90 days determine 80% of renewal outcomes | 1 quarter | CS | | Champion management (executive sponsor + power user) | High — champion departure is #1 churn predictor | Ongoing | CS | | Health scoring + intervention playbooks | Medium-High — early warning system | 1-2 months to build, 1 quarter to show results | CS Ops | | Product gaps (feature adoption blockers) | Medium — requires cross-functional investment | 2-4 quarters | Product + CS | | Pricing architecture (discount sunset, value alignment) | Medium — prevents renewal friction | 1-2 quarters | RevOps + Finance | **Source validation:** Gainsight research confirms that companies improving GRR by 5 points see 20-30% valuation uplift at next funding round. KeyBanc 2025 Private SaaS Survey (104 companies, median $26M ARR) shows median GRR at 88-91% with top quartile at 95%+. --- ## NRR Architecture: The Five Expansion Levers NRR = GRR + Expansion Rate. Once GRR is >=90%, these five levers drive NRR: ### Lever 1: Pricing Architecture (Automatic Expansion) The highest-leverage NRR driver. Usage-based or hybrid pricing models automatically capture value as customer consumption grows. Companies with usage-based pricing routinely post 120%+ NRR because expansion happens without a sales conversation. **Design checklist:** - [ ] Value metric identified (what scales with customer success?) - [ ] Tier thresholds set with clear upgrade triggers - [ ] Overage alerts automated (usage approaching plan limits) - [ ] In-app upgrade prompts at 80% utilisation - [ ] Annual price escalation clause in contracts (2-5% standard) **Pricing model -> NRR impact:** | Model | Typical NRR Range | Expansion Source | |-------|-------------------|------------------| | Flat-rate (per-user, fixed) | 100-110% | Manual upsell only | | Tiered (good/better/best) | 105-115% | Tier upgrades + seat growth | | Usage-based (consumption) | 110-130% | Automatic with value delivery | | Hybrid (base + usage) | 115-125% | Base retention + consumption growth | For detailed pricing architecture, see **pricing-strategy** skill. ### Lever 2: Product-Led Expansion (Embedded Growth) Build expansion triggers into the product experience: - **Feature gates:** Premium features visible but locked -> upgrade prompt - **Usage warnings:** "You've used 80% of your plan this month" -> upgrade path - **Team expansion:** "Invite colleagues" -> seat growth - **Cross-department discovery:** Usage patterns suggesting adjacent department value **Key metric:** In-app expansion conversion rate. Best-in-class: 15-25% of upgrade prompts convert. ### Lever 3: CS-Led Expansion (Relationship Growth) The core of this skill. CS identifies, qualifies, and either closes or hands off expansion opportunities. **Expansion signal architecture** (what the system watches for): ``` USAGE SIGNALS (automated, from product analytics) Approaching seat/usage limits (>80% utilisation) New feature adoption (exploring premium capabilities) DAU/WAU increasing >20% month-over-month New user personas appearing (cross-department adoption) RELATIONSHIP SIGNALS (CSM-observed + CRM data) Champion promoted or new executive sponsor engaged Positive NPS trend (7->8->9 over 3 surveys) Customer referral or case study participation Customer attending events or webinars voluntarily New stakeholders requesting access COMMERCIAL SIGNALS (CRM + finance data) Org headcount growth (enrichment data: Clearbit, ZoomInfo) New budget cycle approaching Multi-year deal coming up for renewal Cross-functional interest from different departments OUTCOME SIGNALS (CS-tracked) Value achieved ahead of schedule ROI exceeded original business case Customer requesting new use cases Customer benchmarking against peers (growth mindset) ``` ### Lever 4: Sales-Led Expansion (Strategic Growth) For large expansion deals (>30% current ACV or new product lines), Sales leads with CS support. ### Lever 5: Partner-Led Expansion (Ecosystem Growth) Partners identify expansion opportunities in shared accounts. See **partner-channel-operations** skill. --- ## Expansion Motion Design ### The Ownership Model Who owns what depends on deal size and complexity: ``` EXPANSION SIZE OWNER SUPPORT HANDOFF TRIGGER ------ ----- ------- --------------- Seat growth (50% ACV) Sales CS supports CS intro to champion, stays involved New product line Sales CS + Product CS identifies need, Sales runs eval Cross-sell (new BU) Sales CS + CSM Different buying group = new sale ``` **The handback process (CS -> Sales for medium/large):** 1. **CS packages the opportunity** — Who's the champion? What changed? Why now? What's the expansion need? What SPICED context exists from original sale? 2. **CS introduces Sales to champion** — Warm handoff, not cold. CS stays on the call. 3. **Sales runs the expansion discovery** — Treat it like a mini-discovery, not a price quote. There may be new stakeholders, new pain, new budget dynamics. 4. **CS stays involved through close** — Maintains relationship continuity. Prevents "you sold us and disappeared" perception. 5. **CS owns post-expansion onboarding** — Expansion product/feature activation follows the same onboarding rigour as new customer. **Credit model:** CS gets sourced credit (pipeline creation). Sales gets close credit. Both are measured. Expansion pipeline without CS sourcing = the system isn't working. ### Whitespace Analysis Methodology Whitespace is the gap between what a customer uses and what they could use — the expansion pipeline you haven't created yet. Map it per account across **five dimensions**: Products, Seats/Users, Departments, Features, and Stakeholders (current state vs. potential = the gap). Score each 0-100 on penetration, average to a total whitespace score, then prioritise by whitespace score x health score x contract timing and present in QBRs as a growth partnership. For the full whitespace template, run-it steps, and segment conversion/close-rate targets, see `references/whitespace-and-scoring-mechanics.md`. --- ## The Expansion Scoring Model Not all expansion signals are equal. Score them systematically into a single **Expansion Readiness Score (0-100)** built from five weighted components: Usage Growth (30%), Stakeholder Breadth (25%), Feature Depth (20%), Health Trajectory (15%), and Contract Headroom (10%). For the component-level scoring questions and mechanics, see `references/whitespace-and-scoring-mechanics.md`. **Score-to-action mapping:** ``` 0-30: MONITOR — No active expansion pursuit. Focus on adoption and value. 31-50: SEED — CSM plants seeds. Share relevant content. Mention capabilities. 51-70: QUALIFY — CSM initiates expansion conversation. Confirm interest and timeline. 71-100: PURSUE — Active expansion opportunity. If >30% ACV -> hand to Sales. ``` --- ## Signal-Based Decision Rules: Expansion Rules These plug directly into the operating cadence. When a signal fires, the cadence ensures someone acts. | Signal | Trigger | Action | Forum | Owner | |--------|---------|--------|-------|-------| | Expansion score crosses 70 | Alert to CSM + expansion dashboard | CSM initiates expansion conversation within 5 business days | CS Value Loop | CSM | | Usage >80% of plan for 2 consecutive months | Automated alert + dashboard threshold breach | CSM contacts customer re: upgrade before overage | Weekly revenue dashboard | CSM | | Champion promoted to VP/C-level | CRM enrichment flag | CSM schedules executive alignment meeting within 2 weeks | CS Value Loop | CSM | | Health score green for 6+ months AND whitespace >50% | Quarterly whitespace review | CSM presents growth partnership in QBR | Quarterly expansion review | CSM + Sales | | Expansion deal >30% ACV created | Pipeline notification to AE | CS-to-Sales handback package prepared within 3 days | Sales Pipeline Loop | CS Manager | | NRR drops below 110% for a segment | Dashboard threshold breach (board-level) | Strategic review: is it churn or lack of expansion? | Monthly Strategy Review | CS Leader + CRO | | GRR drops below 90% for a segment | Dashboard threshold breach (CRITICAL) | Stop: pause expansion focus, diagnose retention | Quarterly Reset | CEO + CRO | --- ## 90-Day NRR Improvement Programme This is the delivery format. When a client's NRR needs improving, structure the engagement in three phases: - **Phase 1: Diagnose (Weeks 1-3)** — data audit, system assessment, whitespace/pipeline audit. Output: Expansion Diagnostic Report. - **Phase 2: Design (Weeks 4-6)** — expansion motion design, system build, enablement. Output: Expansion System Blueprint. - **Phase 3: Install and Measure (Weeks 7-12)** — activate, iterate, embed and report against baseline. For the full weekly breakdown and the success-metrics table (90-day and 6-month targets), see `references/90-day-nrr-programme.md`. --- ## Benchmarks Calibrated for EUR15-150M B2B SaaS. Always adjust for client's stage, ACV, and motion type. The headline thresholds: **NRR >110%** (great) / **>120%** (best-in-class), **GRR >90%** (great) / **>95%** (best-in-class), and **expansion as 20-30%+ of new ARR**. For the full sourced benchmark set — master benchmarks, NRR by company stage, NRR by ACV band, GRR by segment, the expansion economics advantage (CAC/payback/close-rate/cycle), and expansion-revenue share by ARR stage — see `references/benchmarks-sourced.md`. --- ## Usage-Based Pricing and NRR UBP is the strongest structural lever for NRR. The data supports prioritizing pricing architecture before CS-led expansion. | Metric | UBP Companies | Traditional Pricing | Source | |--------|--------------|-------------------|--------| | Average NRR | **137%** | ~110% | OpenView Usage-Based Pricing Trends | | YoY revenue growth | **29.9%** | 21.7% | OpenView; Zuora data | | Expansion mechanism | Automatic (usage growth) | Manual (CSM-led) | m3ter 2026 | **~60% of SaaS companies** now use or are testing usage-based pricing (OpenView). The shift is structural, not a trend. **When to recommend UBP to clients:** - They have a clear value metric that scales with customer success - Their product has natural consumption growth (data, users, API calls, storage) - They're building enterprise with land-and-expand motions - NRR is satisfied customers -> advocacy -> referral pipeline -> new customers -> expansion revenue. This is why NRR is the compound interest of SaaS. Operationalize it by wiring advocacy triggers (NPS promoter -> reference request; closed expansion -> case study request) into the expansion system. For the referral ROI stats and the full advocacy playbook, see `references/advocacy-as-expansion-multiplier.md`. --- ## How to Use This Skill **"Their NRR is 102% — is that good?"** Check the stage. For EUR15-50M ARR, 102% is below median (typically 104-108%). Run the GRR diagnostic first — is this a churn problem masked by light expansion? Check NRR by segment; aggregate NRR hides segment-level problems. **"They want to improve NRR but don't know where to start"** Run the 90-Day Programme Phase 1 diagnostic. The answer is almost always one of: (a) GRR is too low, fix retention first; (b) pricing doesn't create natural expansion paths; (c) expansion is accidental — no signals, no ownership, no process. **"CS team says they don't have time for expansion"** Segmentation problem. They're probably high-touching everyone. Build the three-tier coverage model (see cs-operations). Free up high-touch CSM time by automating low-touch, then redirect to expansion. **"Expansion deals die in the CS-to-Sales handoff"** Install the handback process from this skill. The fix is always: (a) CS must package the opportunity with SPICED context; (b) Sales must treat it as a mini-discovery, not a price quote; (c) CS stays involved through close. **"We don't know which accounts to expand"** Run whitespace analysis on top 20 accounts. Score expansion readiness. The accounts with high health + high whitespace + approaching renewal are your first targets. **"We need this for a client diagnostic"** Use the GRR diagnostic bands + NRR benchmarks to quantify the gap. Frame the cost of inaction: "Your NRR is 102%. At EUR30M ARR, the difference between 102% and 115% is EUR3.9M in compounded revenue over 3 years. That's the gap this programme closes." --- ## Reference Files | File | When to read | What's inside | |------|-------------|---------------| | `references/90-day-nrr-programme.md` | Delivering or scoping a 90-day NRR engagement | Full weekly breakdown of all 3 phases + success-metrics table (90-day and 6-month targets) | | `references/benchmarks-sourced.md` | Quantifying a gap, building a proposal, or citing data | Master benchmarks, NRR by stage, NRR by ACV, GRR by segment, expansion economics (CAC/payback/close-rate/cycle), expansion-share by ARR | | `references/whitespace-and-scoring-mechanics.md` | Running whitespace analysis or configuring expansion scoring | 5-dimension whitespace template, run-it steps, conversion targets, expansion-readiness scoring components | | `references/ttv-benchmarks.md` | Diagnosing onboarding/retention or TTV gaps | TTV-to-retention correlation data, TTV benchmarks by segment | | `references/health-scoring-effectiveness.md` | Assessing or designing health scoring | Effectiveness data, churn-vs-expansion predictors, CSM coverage model | | `references/advocacy-as-expansion-multiplier.md` | Building the advocacy/referral motion | Referral ROI stats, advocacy playbook triggers | ## Related Skills - **cs-operations** — Health scoring, renewal management, onboarding (the plumbing this skill builds on) - **revops-handoffs** — CS-to-Sales handback mechanics - **revenue-operating-cadence** — Where expansion reviews sit in the meeting cadence - **revops-metrics** — GRR, NRR, expansion benchmarks by stage - **revops-forecasting** — Expansion pipeline forecasting and predictability > Built by [Neon Triforce](https://neontriforce.com) --- ## What good looks like A great output runs the GRR-first diagnostic before any expansion design — a company at 115% NRR with 85% GRR is masking structural churn, and the answer is 'fix retention first,' not an expansion en … ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [swan-gtm](https://github.com/swan-gtm) - **Source:** [swan-gtm/gtm-skills](https://github.com/swan-gtm/gtm-skills) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-swan-gtm-gtm-skills-expansion-revenue-architect - Seller: https://agentstack.voostack.com/s/swan-gtm - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.