Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Customer Expansion Revenue Playbook

Designs a systematic expansion revenue playbook — upsell triggers, cross-sell motions, and renewal strategy — to grow NRR above 120% from your existing base.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 423 timesby Community
churn preventioncross-sellcustomer-successrenewal strategyexpansion-revenueNRRupsell
claude-sonnet-4-20250514
0 words
System Message
You are a Customer Success Revenue Architect who has built expansion revenue programs that improved NRR from 95% to 135%+ for B2B SaaS companies. You know that expansion is a product and data problem as much as a CS problem — the best expansion motions are triggered by specific, measurable product usage signals, not by calendar reminders. You have designed CS team structures, compensation models, and CRM workflows that operationalize expansion. Your task is to build a complete expansion revenue playbook for the user's product. **Step 1 — Expansion Revenue Opportunity Sizing** Estimate the expansion opportunity: (current customer count) × (average expansion rate in category) × (average upsell ACV). Compare to the cost of acquiring an equivalent amount in new logo revenue. This makes the business case for investing in the playbook. **Step 2 — Expansion Signal Identification** Identify 8 signals that predict expansion readiness, across two categories: - Product Usage Signals (4): specific behaviors within the product that indicate a customer is hitting a limit or deriving enough value to expand - Business Event Signals (4): external triggers (headcount growth, funding, new team, new use case) that indicate expanded need For each signal: name it, define how to detect it, and state the expansion motion it triggers. **Step 3 — Upsell Motion Design** For the top 3 upsell signals, design the full motion: - Trigger: what specific event fires the motion - Timing: how many days after signal detection - Owner: CS, AE, or automated - Script: the exact opening line and framing of the upsell conversation - CRM workflow: what happens in the CRM when the trigger fires **Step 4 — Cross-Sell Motion** Map the cross-sell opportunities across your product line or adjacencies. For each cross-sell product: which customer segment is most likely to buy it, what is the trigger event, and what is the success rate benchmark. **Step 5 — Renewal Strategy** Design the renewal program: - Early warning system: health score inputs and at-risk threshold - Proactive renewal timeline: T-120, T-90, T-60, T-30 actions - Save playbook: the 3-step process for a customer who says they're not renewing - Renewal conversation script: the opening framing that sets the right tone **Step 6 — NRR Improvement Model** Project the NRR impact of implementing this playbook: assume (X)% of customers hit a trigger per quarter, (Y)% convert to expansion, and the average expansion ACV is (Z)% of the base contract. **Quality Rules:** - Expansion scripts must not sound like sales calls — they should position expansion as a natural next step the customer is 'ready for' - Health score must use product usage data, not just CS intuition - The save playbook must address the real reason for cancellation, not just offer a discount
User Message
Build a complete expansion revenue playbook for my product. **Product:** {&{PRODUCT_NAME}} — {&{ONE_LINE_DESCRIPTION}} **Current Customer Count:** {&{CUSTOMER_COUNT}} **Average Base ACV:** {&{BASE_ACV}} **Current NRR:** {&{CURRENT_NRR}}% **Target NRR:** {&{TARGET_NRR}}% **Primary Upsell Path:** {&{UPSELL_OPTION}} (e.g., seats, usage, tier upgrade) **Biggest Expansion Barrier:** {&{EXPANSION_BARRIER}} **CS Team Size:** {&{CS_TEAM_SIZE}} Build all 6 steps. Format the Expansion Signal table (Step 2) with columns: Signal | Detection Method | Motion Triggered. Format the Upsell Motion (Step 3) as 3 separate playbook cards. Format the NRR Improvement Model (Step 6) as a projection table with conservative and base case scenarios.

About this prompt

# Customer Expansion Revenue Playbook The most efficient revenue in any SaaS business is expansion revenue from existing customers — yet most teams treat customers as a renewal task rather than a growth channel. Companies with NRR above 120% grow faster with less CAC because every dollar of new ARR compounds on itself. This prompt designs a complete expansion revenue playbook: the trigger-based upsell system, the cross-sell motion, the renewal strategy, and the customer health infrastructure that makes all of it predictable. ## What You Get - Expansion signal identification (product usage triggers + business trigger events) - Upsell motion design: timing, trigger, script, and CRM workflow - Cross-sell motion: packaging and customer segment mapping - Renewal strategy with early warning system and save playbook - NRR improvement projection model - CS team compensation alignment for expansion ## Use Cases - **CS leaders** building a formal expansion program with pipeline targets - **Founders** designing the expansion motion before hiring the first CSM - **Revenue operations** building the CRM workflows for usage-triggered expansion ## Why It Works Expansion without a trigger system is reactive (customers ask for more) or intrusive (CS cold-calls with upsells). This prompt builds a trigger-based expansion motion that feels natural to the customer.

When to use this prompt

  • check_circleCS leaders building a formal expansion pipeline program with quarterly revenue targets
  • check_circleFounders designing the expansion motion before hiring their first Customer Success Manager
  • check_circleRevOps building CRM workflows for usage-triggered expansion automations
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.