Customer Success is the function that turns a signed contract into a renewed one. It's a mix of project management, consulting, relationship work, and — increasingly — writing. Onboarding plans, QBR decks, churn-rescue emails, expansion proposals, executive summaries. Every one of those is a writing task, and every one of them benefits from a sharp prompt.
I've spent the last year building prompt systems for SaaS teams. Here are the 10 prompts I give to Customer Success Managers — the ones that actually get used, not the generic "write me an email" templates. Each one follows a Role → Context → Constraints → Output structure so the model knows what kind of operator it's being, what situation it's in, what it can't do, and exactly what to produce.
1. The 30-60-90 onboarding plan that forces outcome ownership
Most onboarding plans are a list of meetings. This one forces every milestone to own a customer-visible outcome.
Role: You are a Senior Customer Success Manager at a B2B SaaS company.
Context: A new customer just signed. Company: {company}. They bought {product} to solve {pain_point}. Their success metric is {metric}. Their go-live target is {date}. Their internal champion is {champion_name}, {champion_title}. Their technical contact is {tech_contact}. Team size: {N}.
Constraints:
- Every milestone must have ONE owner on the customer side and ONE on our side.
- Phase 1 (days 0-30) = setup + first value. Phase 2 (days 31-60) = adoption across team. Phase 3 (days 61-90) = habit + measure against the success metric.
- No milestone can be "kickoff meeting" alone — it must be "kickoff meeting → outcome."
- Include the specific feature/module they must activate in each phase.
Output: A markdown table with columns: Phase | Day range | Milestone (outcome, not activity) | Customer owner | Our owner | Feature activated | Success signal.
Why it works: The "outcome not activity" constraint kills the most common onboarding failure mode — a calendar full of check-ins where nobody shipped anything.
2. The stakeholder map from a messy kickoff call
CSMs inherit accounts with unclear reporting lines. This prompt turns scattered notes into a decision-making map.
Role: You are a Customer Success Strategist.
Context: I just had a 45-minute kickoff call with a new enterprise account. Here are my raw notes:
{paste_notes}
Constraints:
- Identify who the Decision Maker, Champion, Blocker, and End Users are — but ONLY based on evidence in the notes. If unclear, label "UNCONFIRMED" and say what to ask next.
- For each person, note their stated goal AND their unstated fear (infer from what they emphasized or avoided).
- Flag any person whose goal conflicts with the champion's goal.
Output: A stakeholder table: Name | Role | Classification (DM/Champion/Blocker/User) | Stated goal | Inferred fear | Confidence (High/Med/Low) | Next action.
Why it works: The "inferred fear" column is the one CSMs actually use. Renewal risk usually comes from an unspoken fear, not a stated objection.
3. The QBR narrative (not a feature recap)
A QBR that recaps features is a QBR that gets rescheduled forever. This prompt forces a business-outcome narrative.
Role: You are a Customer Success Director preparing a Quarterly Business Review for an executive sponsor.
Context:
- Customer: {company}, industry {industry}, {N} seats.
- They bought to achieve {original_goal}.
- This quarter they achieved {results} (usage data: {usage_metrics}).
- They did NOT achieve {gaps}.
- Their renewal is in {months} months.
- The exec sponsor cares most about {exec_priority}.
Constraints:
- Structure: 1) Where we started (baseline), 2) Where we are (with data), 3) What worked (2-3 specific wins tied to their goal), 4) What didn't (honest, with a plan), 5) Next quarter's bet (ONE priority, not five).
- Open with the single most important number. Not a slide title — a number.
- The "what didn't work" section must be 1/3 the length of "what worked" — honesty without dwelling.
- End with ONE ask of the exec sponsor (a decision, not "thoughts?").
Output: A QBR narrative script (what to say, slide by slide), 8-10 slides max. Include the opening line verbatim.
Why it works: The "one ask" constraint forces the CSM to know what they actually need from the exec — an introduction, a budget sign-off, a mandate. Most QBRs die because they end with "any questions?" instead of a decision request.
4. The churn-rescue email that doesn't grovel
When an account is at risk, the instinct is to over-apologize and offer a discount. That signals weakness. This prompt writes a rescue message that leads with a plan.
Role: You are a Customer Success Manager writing to an at-risk customer.
Context: The customer {company} has shown {risk_signal} — {specific_evidence}. Their champion {name} has gone quiet for {N} weeks. Their last known goal was {goal}. They raised this concern on {date}: {concern}. We have done {actions_taken}.
Constraints:
- Subject line: ≤6 words, lowercase, no urgency words ("urgent", "important", "checking in"). Reference their specific situation.
- First line: acknowledge the specific gap WITHOUT apologizing. Name what's broken.
- Second block: the fix — 3 concrete steps, each with a date. Not "we're committed to" — actual steps with dates.
- Third block: one question that requires a real answer (not "how are things?").
- No discounts. No "I'd love to hop on a call." The call is offered only if they answer the question.
- Max 120 words.
Output: The email, ready to send.
Why it works: The "no discount" and "no checking in" constraints are the two things that separate a CSM who saves the account from one who accelerates the exit. Discounts train customers to threaten churn.
5. The expansion conversation opener (not a sales pitch)
Expansion done badly feels like an upsell. Done well, it feels like a CSM who noticed something first. This prompt drafts the conversation opener for a usage-based expansion.
Role: You are a Customer Success Manager preparing to propose an expansion.
Context: Customer {company} currently has {current_plan}. In the last 90 days, {usage_evidence} shows they're hitting the limits of {limit_type}. Their team grew from {old_N} to {new_N}. The next plan tier adds {new_capability} which maps to their original goal of {goal}.
Constraints:
- Frame the expansion as "I noticed something" not "you should upgrade."
- Lead with the observation (the data), then the implication (what it means for their goal), then the question (whether they want to solve it now).
- Do NOT mention price. The goal of this message is a conversation, not a close.
- Reference their original goal explicitly — tie the expansion to why they bought, not to features.
Output: A Slack message or email (≤100 words) that opens the expansion conversation. Plus a 3-bullet "talking points if they say yes" prep for the CSM.
Why it works: Expansion messages that lead with price get forwarded to procurement. Messages that lead with "I noticed your team hit 47 seats and you're hitting API rate limits — here's what that means for your Q3 goal" get a reply from the champion.
6. The health-score narrative for internal review
CSMs maintain health scores, but the number is useless without a narrative. This prompt turns a health score into an executive-readable account story.
Role: You are a Customer Success Manager writing an internal account-health summary for your weekly CS team review.
Context:
- Account: {company}, ARR {value}, renewal date {date}.
- Health score: {score}/100, trend {up/down/flat over N weeks}.
- Product usage: {usage_summary}.
- Support tickets: {N} open, {theme}.
- Champion engagement: {engagement_level}.
- Last executive touchpoint: {date}.
Constraints:
- One sentence per category (usage, support, champion, exec relationship). No paragraphs.
- End with: Green/Yellow/Red verdict + the ONE thing that would move it up a color.
- If Yellow or Red, name the specific risk (champion left, usage dropped, competitor evaluated) — not vague "engagement concerns."
- Max 150 words total.
Output: The account-health summary, formatted for a Slack thread or CRM note.
Why it works: CS leaders don't read health scores — they read the "one thing that would move it up a color." That's the line that triggers a manager to assign help or escalate.
7. The customer feedback synthesis (themes, not quotes)
After a batch of customer interviews, you have 40 pages of transcripts. This prompt synthesizes them into actionable themes without losing the signal.
Role: You are a Customer Success Operations analyst.
Context: I conducted {N} customer interviews this month. Here are the transcripts/notes:
{paste_notes}
Constraints:
- Group feedback into themes. A theme needs at least {N} independent mentions to qualify.
- For each theme: the pattern, the severity (how many mentioned it), and one representative quote (verbatim, not paraphrased).
- Separate "product feedback" (something engineering should hear) from "success feedback" (something CS/process should fix) from "praise" (keep doing this).
- Rank themes by frequency × severity, not by how interesting they sound.
- Flag any feedback that contradicts another piece of feedback — contradictions are where the real insight is.
Output: A themed feedback report. One table per category (product / success / praise). Then a "contradictions" section.
Why it works: The "contradictions" section is the hidden value. When two customers want opposite things, that's a segmentation insight — not a bug.
8. The renewal forecast narrative
Renewal forecasts are usually a spreadsheet. This prompt adds the narrative that explains why each account will or won't renew.
Role: You are a Customer Success Manager preparing your monthly renewal forecast.
Context: Here are my accounts up for renewal in the next 90 days:
{account_list_with_ARR_champion_health_last_touchpoint}
Constraints:
- For each account, classify: COMMITTED, AT RISK, or RESCUE NEEDED. No "likely" or "probably" — force a call.
- For each AT RISK or RESCUE account, name the single dominant risk factor (champion departure, low adoption, budget freeze, competitor, unresolved ticket, exec sponsor change).
- For each, state the ONE action that would move it up a category, with a deadline this week.
- Total the ARR at risk. Put that number at the top.
Output: A renewal forecast table + the total at-risk ARR called out at the top.
Why it works: Forcing a three-bucket classification (no "probably") is uncomfortable — and that's the point. "At risk" accounts that stay "at risk" for three consecutive forecasts are the ones that churn. The prompt surfaces them early.
9. The executive sponsor update (written for someone who reads in 20 seconds)
Executive sponsors don't read CSM updates. They skim. This prompt writes an update that survives the skim.
Role: You are a Customer Success Manager writing a monthly update to an executive sponsor (VP/C-level at the customer).
Context:
- Customer: {company}. Exec sponsor: {name}, {title}.
- This month's headline result: {result}.
- Adoption metric: {metric} ({trend}).
- One risk or open item: {risk}.
- One ask or decision needed: {ask}.
Constraints:
- Subject line: the single most important sentence. Not "Monthly update" — the actual news.
- First line: "On track" or "Needs attention" — nothing else. Then the one number that matters.
- Body: 3 bullets max. Each bullet is a complete thought (the exec should understand it without context).
- The ask is the last line. Make it a yes/no question or a specific request, not "thoughts?"
- Max 100 words including subject.
Output: The email.
Why it works: The "On track / Needs attention" opener is borrowed from incident communication. It respects the exec's time and forces the CSM to know their own answer before asking.
10. The handoff document (when a CSM leaves an account)
Account handoffs lose more customers than any other CS process. This prompt forces a handoff doc that a new CSM can act on in week one.
Role: You are a Customer Success Manager writing an account handoff document for the CSM taking over.
Context: I am transitioning account {company} to {new_csm_name}. Here is what I know:
{account_details_champion_history_open_issues_goals_renewal_date}
Constraints:
- Structure: 1) Why they bought (the original goal, in their words), 2) Where they are now (adoption, sentiment, health), 3) The 3 people who matter (name, role, what they care about, how to reach them), 4) The landmines (open tickets, past promises, sensitive history, things never to say), 5) The next 30 days (3 specific actions with dates).
- The "landmines" section is the most important. Be specific. If you once promised a feature and it didn't ship, say so.
- No generic advice ("build rapport"). Only specifics.
- Include the renewal date and the current risk level at the top.
Output: A handoff document, structured as above. Max 500 words.
Why it works: The "landmines" section is what every incoming CSM actually needs and almost never gets. A new CSM who doesn't know about a broken promise will repeat the mistake that caused it.
How to use these prompts
Each prompt is designed to be adapted, not copy-pasted blindly. Here's the testing methodology I use:
- Run it 3 times with the same inputs. If the output varies wildly, your constraints are too loose. Tighten them.
- Generalize across accounts. After you've used a prompt on 5 accounts, look at the common failures. Those failures tell you which constraint to add.
- Read the output aloud. If it sounds like a template, the customer will hear it too. Add a constraint that forces specificity (a number, a name, a date).
- Cut anything generic. If a line could apply to any customer, delete the line and replace it with a constraint that forces a customer-specific detail.
The difference between a prompt that saves you 20 minutes and a prompt that gets a customer to renew is the constraints. The role and context set the scene; the constraints do the work.
Want the full system?
These 10 prompts are a sample. I've built larger prompt systems for SaaS teams covering customer success, sales, marketing, product, and operations — tested across real accounts.
- Developer Productivity Prompt Library — 30 prompts for dev teams ($49)
- SaaS Marketing Copy Prompt Pack — 25 prompts for marketing teams ($49)
- AI Startup Operations Prompt System — 50+ prompts + 10 workflows for the whole company ($199)
- AI Business Transformation Playbook — 100+ prompts + 12 workflows, the flagship ($999)
- Developer Product-Launch Prompt Pack — 7 prompts for launch day ($9)
Browse the full store at innovate01.gumroad.com.
If you want a custom prompt system built for your specific CS workflow — your onboarding flow, your health score model, your renewal motion — reach out. I build those for teams that need prompts tuned to their product, not generic templates.
Top comments (0)