Free preview·One standard operating procedure per section is free. Start your free trial to unlock the rest.
Start free trialAccount Expansion Playbook SOP
2,171 words · ~10 min read
Document ID: sop-account-expansion-playbook
Version: 1.0 — Premium Curriculum
Owner: Customer Success / Account Management
Review Cycle: Quarterly
Classification: Proprietary — Clozo Academy No-Code Growth System
Purpose and Scope
This SOP defines the end-to-end process for identifying expansion signals on existing customer accounts and converting them into upsell revenue on a no-code or low-code platform. Expansion ARR is the cheapest revenue a no-code company will ever earn — a healthy mid-market book delivers 25-40% net ARR growth purely from existing accounts at one-fifth the cost of new acquisition. Most platforms leave expansion to passive in-product upgrade flows and miss 60-80% of available expansion revenue. This document replaces passivity with a structured trigger detection system, persona-tuned talk tracks, and contract-uplift scripts that consistently convert signal into closed expansion deals within 60 days.
The scope covers any active customer account regardless of size. The same trigger framework applies to SMB (handled by automated CS plus a final-mile rep), mid-market (handled by named CSM), and enterprise (handled by CSM + AE pair). The SOP excludes new logo acquisition (handled by the trial-conversion and enterprise discovery SOPs) and renewal-only conversations (which trigger their own renewal SOP).
Definitions and Terminology
Expansion Signal: A behavioral or relational indicator that an account is ready to spend more.
Trigger Threshold: The quantitative bar at which a signal warrants a human-led conversation.
Talk Track: The verbatim opening, discovery, and ask script for each persona.
Contract Uplift: The mechanism for adding paid scope mid-contract (amendment, addendum, or new SO).
Net Revenue Retention (NRR): Trailing 12-month expansion ARR + renewals minus churn / starting ARR.
Roles and Responsibilities
| Role | Responsibility | Backup | Escalation Path |
|---|---|---|---|
| CSM (Mid-Market / Enterprise) | Detects signals, runs the expansion play | Senior CSM | Head of CS |
| AE (Enterprise) | Closes the contract; named on accounts > $50K | Senior AE | VP Sales |
| RevOps | Maintains the trigger detection system in CRM | Operations Lead | Head of Revenue |
| Deal Desk | Approves uplift pricing and contract structure | Finance Lead | CFO |
| Product Marketing | Provides updated upgrade messaging by feature | Senior PMM | Head of Marketing |
Pre-Conditions
[ ] Product telemetry tracks: seat usage, feature usage, plan-limit proximity, integration connections, environment count, audit log volume.
[ ] CRM has account-level fields for: ARR, plan tier, seat count, expansion forecast, last expansion date.
[ ] Slack or email alerts are wired for trigger threshold breaches.
[ ] Talk tracks for each trigger and each persona are stored where the CSM can access them in 30 seconds.
[ ] Pricing book is current; uplift discount authorities are documented.
Procedure Steps
Phase 1: Trigger Detection (Continuous, Automated)
Step 1.1 — The Six Primary Expansion Signals
| Signal | Threshold | Detection Method | Owner |
|---|---|---|---|
| **Seat additions / utilization >85%** | Account at or above 85% of paid seats for 14+ days | Telemetry job, weekly | CSM |
| **Plan-limit proximity** | Account at or above 80% of any plan limit (storage, requests, environments, integrations) | Telemetry job, daily | CSM |
| **New use case introduced** | New project / workflow type detected outside primary use case | Behavioral classifier, weekly | CSM |
| **Integration depth increase** | Three or more new integrations connected in 30 days | Integration audit, monthly | CSM |
| **Multi-team adoption** | A second team domain creates accounts under same parent | Domain detection, weekly | CSM + AE |
| **Compliance / governance ask** | Customer requests SAML, SCIM, audit log export, dedicated environment | Support ticket tag | CSM + AE |
Step 1.2 — Alerting
When any threshold breaches, an alert fires to the named CSM (and AE for enterprise) within 24 hours. The alert includes:
Account name and ARR.
Triggered signal and exact value.
Suggested talk track link.
Recommended action.
Deadline for first outreach (7 days from trigger).
Phase 2: Account Diagnostic (Within 7 Days of Trigger)
Step 2.1 — Pre-Outreach Diagnostic
Before reaching out, the CSM completes the Expansion Diagnostic Worksheet:
Current ARR, plan tier, seat count, renewal date.
Trigger evidence (specific data points).
Buyer map: economic buyer, champion, IT contact, end-user contacts.
Last 3 support tickets and their resolution status.
Last QBR notes — were any expansion signals already flagged?
Pricing scenario: what does the upsell look like, what does it cost, what is the discount authority?
Step 2.2 — Diagnostic Decision
Based on the worksheet, the CSM classifies the opportunity:
Hot: Champion is engaged, signal is strong, decision window is open. Move to Phase 3 immediately.
Warm: Signal is real, no champion mapped yet. Do champion development first.
Cold: Signal is ambiguous; account history is rough. Hold for next QBR.
Phase 3: Talk Track Execution (Persona-Specific)
Step 3.1 — Persona Detection
The CSM identifies which of three personas they are speaking with:
**Operator (end-user / lead user):** Cares about productivity, hours saved, broken workflows fixed.
**Manager (team lead / department head):** Cares about output, team growth, justifying budget.
**Buyer (VP / Director / CFO):** Cares about TCO, vendor consolidation, business outcomes, predictability.
Step 3.2 — Operator Talk Track (for end-user signals)
"Hi [Name] — I noticed your team has connected three new integrations and is up to 18 active workflows since the last QBR. That's serious adoption. Two questions:
>
1. What's the next workflow you wish you could build but can't because of [specific limitation]? 2. If we could double your monthly automation runs and add the [premium feature] without you having to ask for budget, would that change what your team ships?
>
I'm asking because there's a path to that — let me show you what it looks like."
Step 3.3 — Manager Talk Track (for team-level signals)
"Hi [Name] — I'm seeing your team grow on the platform. You're at 14 of your 15 paid seats and your ops team just connected our [tool]. Three things:
>
1. Who else internally has been asking about getting on? 2. What's the bottleneck that would let your team move faster — more seats, more environments, or the [feature] you mentioned last QBR? 3. If I could put together a proposal that solves that bottleneck and gets you predictable budget for the next 12 months, when's the right time to walk through it — this week or early next?"
Step 3.4 — Buyer Talk Track (for compliance / governance / multi-team signals)
"Hi [Name] — three things have surfaced on your account that I want to discuss together. Your team is at 95% seat utilization. You asked support about SCIM provisioning last week. And we're seeing accounts created from a second domain — looks like the [other team] is starting to use the platform.
>
Each of these alone would be worth a conversation. Together they suggest you're at the moment where it makes sense to look at our enterprise tier and a multi-year agreement that locks in pricing, gets you the governance you need, and rolls in the [other team] expansion at preferred rates.
>
I'd love to put together a proposal in the next two weeks. Could I borrow 30 minutes with you and [IT contact] for the technical piece?"
Phase 4: Discovery and Scoping (15-30 Minutes)
Step 4.1 — Verify the Pain
Even with strong telemetry signals, the CSM verifies the underlying pain on the call:
"What's the cost of staying at the current limit?"
"Who's frustrated, and what would change for them if we expanded?"
"What's blocking you from making this move today?"
Step 4.2 — Scope the Deal
Quantify the proposed expansion:
New seats and price.
New tier and price (if upgrading).
New features and value to specific personas.
New term length (annual vs multi-year discount).
Effective date.
Total contract value uplift.
Phase 5: Pricing and the Contract Uplift Script
Step 5.1 — Pricing Reveal
"Based on what you said, here's what I'd put in front of you:
>
Add 10 seats, move from [current tier] to [target tier], and lock in a 24-month term at our annual rate. The math: - Current ARR: $[X] - Expanded ARR: $[Y] - Net change: +$[delta] / month, or +$[annualized] / year - Discount applied for the multi-year: [%]
>
What you get: [3 specific things they explicitly said they need].
>
What's your reaction?"
Wait. Do not fill silence with discounts.
Step 5.2 — The Contract Uplift Mechanics
| Mechanism | When to Use | Approval Authority |
|---|---|---|
| Mid-term amendment | Same term, more scope | CSM with Deal Desk co-sign |
| New SO appended to MSA | New product line or significant scope | AE + Deal Desk |
| Co-terminus extension | Lengthening term to align with new scope | AE + Deal Desk |
| Full renewal pull-forward | Replacing current contract early | VP Sales + Finance |
Step 5.3 — Three-Way Close on Expansion
Same Yes / Maybe / No structure as the trial conversion call.
Yes Path:
"Great. I'll send the amendment in the next two hours. While I do, can we book the kickoff for next Tuesday so [new team / new feature] starts ramping immediately? I'd hate to lose two weeks to legal."
Maybe Path:
"Totally fair. What's the specific concern — price, timing, internal approval, or fit? And who specifically do you need to bring in? Could I save you a meeting by joining that conversation directly?"
Always book the next step on the call.
No Path:
"Got it. Tell me one thing — is this not the right time, or not the right offer? If it's timing, when's better? If it's the offer, what would have changed it? I'd rather know."
Phase 6: Contract Execution and Handoff
Step 6.1 — Paperwork
Within 24 hours of verbal yes:
The amendment or new SO is generated and sent.
Updated invoice schedule is communicated.
Internal CRM is updated: ARR, tier, seats, term, expansion source.
The new revenue is forecast in the AE/CSM compensation system.
Step 6.2 — Onboarding the Expansion
Within 7 days of countersignature:
Kickoff call with the expanded team or for the new use case.
Updated success plan with expansion-specific milestones.
Adjusted QBR cadence if the account has crossed a tier threshold.
Phase 7: 90-Day Expansion ROI Review
Step 7.1 — Verify the Expansion Stuck
90 days post-expansion, the CSM verifies:
The new seats are being used.
The new feature is being adopted.
The new use case is producing output.
The customer believes they got their money's worth.
If any verification fails, intervene immediately. An expansion that doesn't stick is a renewal that won't happen.
Quality Verification
Trigger-to-outreach SLA: 100% of triggers receive first outreach within 7 days.
Outreach-to-close SLA: 50% of qualified expansion opportunities close within 60 days.
Expansion ARR target: 20-25% of ARR base growing from existing accounts annually (NRR component).
Expansion close rate: 35-45% of qualified opportunities close.
Quarterly review: Head of CS reviews 5 expansion deals per quarter for talk-track quality, deal structure, and downstream stickiness.
Common Mistakes
Waiting for the QBR. Triggers happen continuously; 90-day cadence misses 70% of windows.
Discounting before asking. Many customers will pay full price if asked confidently; discount-first leaves margin on the table.
Skipping the buyer map. Pitching to the Operator without engaging the Buyer is a 60-day wait for a deal that dies.
Generic talk tracks. Persona-specific language converts at 2-3x the rate of generic.
Forgetting the multi-team signal. A second domain in the customer's workspace is the highest-value expansion signal there is.
No 90-day check-in. Stuck expansions become renewal risk.
AE / CSM rivalry. Expansion is a team sport. Compensate both, route credit clearly.
Implementation Checklist
[ ] Wire the six trigger detections into the data pipeline with daily / weekly cadence.
[ ] Configure CRM alerts and trigger fields.
[ ] Build the Expansion Diagnostic Worksheet template.
[ ] Train CSMs (and AEs for enterprise) on the three persona talk tracks with role-plays.
[ ] Document the four contract uplift mechanisms with approval authorities.
[ ] Establish a weekly expansion forecast review with Head of CS and VP Sales.
[ ] Track NRR and the expansion-trigger conversion rate as top-line CS KPIs.
[ ] Run a quarterly talk-track refresh based on close-rate data.
Clozo Academy Proprietary Curriculum