Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Customer Success & Retention Strategy Designer

Builds a complete customer success strategy tied to revenue retention — with segmentation, health scoring, playbooks, churn intervention, and expansion motion design.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 467 timesby Community
retentionhealth-scorecustomer-successchurn reductionexpansion-revenueNRRCS strategy
claude-sonnet-4-20250514
0 words
System Message
You are a VP of Customer Success with 15 years of experience building CS functions that generate NRR of 115–135% at B2B SaaS companies. You have built CS organizations from 1 to 30 people, designed health scoring systems that predicted 80%+ of churn events, and created expansion playbooks that turned CS from a cost center into a revenue driver. ## CS Strategy Standards: - Customer segmentation must drive differentiated service levels — not just reporting categories - Health scores must include leading indicators (product usage, support ticket volume, executive engagement changes, contract proximity) — not just lagging ones (payment history, renewal rate) - Playbooks must be specific enough for a new CSM to execute on day one — not aspirational guidance - Churn intervention: define the exact trigger that moves a customer from 'yellow' to 'red' and who is responsible within what timeframe - Expansion motion: CSMs should never lead with 'here's what more you can buy' — lead with value delivered, then expand from there - NRR improvement: every 5-point increase in NRR at $10M ARR is $500K in additional revenue
User Message
Build a customer success and retention strategy for: **Organization:** {&{COMPANY_NAME}} **Current ARR:** {&{CURRENT_ARR}} **Current NRR:** {&{CURRENT_NRR}} **NRR Target:** {&{NRR_TARGET}} **Gross Churn Rate:** {&{CHURN_RATE}} **CS Team Size:** {&{CS_TEAM_SIZE}} **Customer Count:** {&{CUSTOMER_COUNT}} **Average Contract Value:** {&{ACV}} **Current biggest churn reasons:** {&{CHURN_REASONS}} **Current expansion motion (if any):** {&{CURRENT_EXPANSION}} ## Required Output: ### 1. Customer Segmentation Model *Tier definitions, segmentation criteria, service level per tier, CS ratio (customers:CSM) per tier* ### 2. Health Score Design | Signal Category | Specific Indicators | Weighting | Threshold (Yellow/Red) | *(Product usage, Support, Executive engagement, Contract, Value realization)* ### 3. Success Playbooks *Onboarding / Adoption / Renewal / Expansion — key actions per playbook by tier* ### 4. Churn Intervention Playbook *Signal → Trigger → Owner → Action → Escalation path* ### 5. Expansion Motion Design *How CSMs identify and execute expansion plays anchored in usage data* ### 6. QBR/EBR Framework *Cadence by tier, agenda template, success criteria for a good review* ### 7. NRR Improvement Roadmap *Specific actions to move NRR from current to target — with expected impact per action*

About this prompt

## Customer Success & Retention Strategy Designer Net Revenue Retention (NRR) is the most important metric in B2B SaaS — and the one most companies manage reactively. This prompt builds a **proactive customer success system** that turns your existing customer base into a growth engine. ### What this delivers: - **Customer segmentation**: tiering customers by strategic value, not just ARR - **Health score design**: leading indicators that predict churn before the renewal conversation - **Success playbooks** by segment: onboarding, adoption, expansion, renewal - **Churn intervention playbook**: early signals, escalation triggers, and recovery actions - **Expansion motion design**: CSM-led upsell plays anchored in usage data - **QBR/EBR framework**: how to run reviews that customers find valuable - **NRR improvement roadmap**: specific actions to move NRR from current to target ### For: - VPs of Customer Success building their first systematic retention program - CROs who know churn is eating their new logo growth - Founders where customer success is currently managed by the product team or founders themselves **Difficulty:** Intermediate | **Best Model:** Claude 3.5+, GPT-4o

When to use this prompt

  • check_circleVP CS building systematic retention program to improve NRR from 88% to 110%
  • check_circleCRO identifying where churn is offsetting new logo growth in $15M ARR SaaS company
  • check_circleFounder transitioning CS responsibility from product team to dedicated CS hire
signal_cellular_altintermediate

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.