# Every renewal starts from why they bought

> Calven gives customer success the reasons each account bought, what they have said since, who matters and how to answer a competitor, for QBRs, renewals and expansion. In the AI tool CS already uses.

- Source: https://calven.ai/solutions/customer-success
- Last updated: 2026-10-05

---

## What can customer success teams use Calven for?

Renewal briefs, QBR decks, success plans and customer replies that start from why each account bought and what they have said since. Calven is the approved context your AI workflows need to scale across the team and still be trusted.

### Renewal prep

The renewal case, risks and talking points from the original deal and the year's conversations.

Ask it:
- List the renewals closing in the next [90] days, with the risk signals for each.
- Build the renewal brief for [account], renewing on [renewal date].
- Read renewal risk across my book over the [last six months]: [paste the accounts]
- [Competitor] is in the [account] renewal. What will they claim, and how do I answer?
- Tell me why we lost the [account] renewal, and what the signals were.
- Start from your base renewal rate and update [account]'s odds one piece of evidence at a time, so the forecast is defensible.
- Model the renewal negotiation as a game: their walk-away, yours, and the price uplift both sides can live with.
- Play a price ladder to [account]'s buying group and find the uplift where the economic buyer starts looking elsewhere.
- Why did [account] buy from us originally? Quote them.
- Is the champion from the [account] deal still a contact?

Advanced prompts: Update the renewal odds evidence by evidence, Map the renewal negotiation as a game, Test the price uplift on a persona ladder. Workflow prompts: List the renewals coming up and their risk signals, Build the renewal brief for one account, Read renewal risk across your book, Prepare for the competitor in the renewal, Learn from a lost renewal. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/renewal-prep.md

### QBR and EBR prep

The business review from what the customer said they wanted, what changed, and what is next.

Ask it:
- Outline the [Q3] QBR deck for [account], with evidence for each slide.
- Prepare the EBR for [sponsor] at [account], tied to what they are measured on.
- Summarise what [account] said since [the start of the quarter], good and bad.
- Review this QBR deck as [persona] would read it: [paste the deck]
- Estimate the counterfactual: what [account]'s year would have looked like without you, with ranges the sponsor can't wave away.
- Rank every ask you could make at the QBR by expected value, and walk in with the one most likely to land.
- Hand the EBR deck to a hostile CFO who wants to cut the line item, and fix every slide that wouldn't survive.
- What did [account] say they wanted from us when they bought?
- What has [account] said on calls this quarter?
- Which product use cases is [account] not using that fit their outcomes?

Advanced prompts: Estimate their year without us, Rank the QBR asks by expected value, Stress-test the EBR as their CFO. Workflow prompts: Outline the QBR deck, Prepare the EBR for the sponsor, Summarise what they said this quarter, Review your QBR deck. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/qbr-and-ebr-prep.md

### Account briefing and handoff

Everything Calven knows about an account before the first CS call.

Ask it:
- Brief me on [account] before my first call as their CSM.
- Check what our rep promised [account] against the product brief.
- Map the people at [account] to our personas, and tell me who is missing.
- Write the questions I should ask [rep] before taking over [account].
- Backtest which signals in the original deal predicted a lost renewal, then score [account] on them before the first call.
- Run a three-round Delphi panel of the AE, SE, CSM and sponsor on [account]'s renewal odds before you set the success plan.
- Turn the deal record into a promise ledger, then red-team it as the sponsor who'll hold you to every line.
- Why did [account] choose us? Quote the buyer.
- Did our rep promise anything to [account] that is not in the product brief?
- What objections did [account] raise during the sale?

Advanced prompts: Backtest which handoff signals predict churn, Run a Delphi panel on the account, Red-team the handoff as their sponsor. Workflow prompts: Build a one-page account brief, Check rep promises against the brief, Map the account's people to personas, Write the rep handoff checklist. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/account-briefing-and-handoff.md

### Risk review

Which accounts show churn signals in their own words, and what buyers like them left over.

Ask it:
- Run the risk read on my accounts for the [last 30 days]: [paste the accounts]
- [Account] renews on [date] and [lost its champion]. Propose a save play.
- Which of my accounts have gone quiet for [60] days? [paste the accounts]
- Run a survival analysis on your book with Calven's voice signals as covariates, and see which ones really shorten customer life.
- Rank every at-risk account by expected ARR lost and the odds a save play works, so the team spends its week where it pays.
- Which of my accounts said something negative this month?
- Which accounts no longer have a champion contact?
- What did customers who churned for [reason] say before they left?
- Which accounts mentioned a competitor and lost a contact in the same quarter?
- What did customers who renewed after a rough patch say turned it round?

Advanced prompts: Run a survival curve on your book, Rank risk by expected ARR lost. Workflow prompts: Run the weekly voice-risk read, Propose a save play for one account, List accounts that have gone quiet. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/risk-review.md

### Competitive displacement defense

What to say when a customer is evaluating a rival.

Ask it:
- [Contact] at [account] asked how we compare to [competitor] on [topic]. Draft my answer.
- How serious is [account] about [competitor]? Give me the signals for and against.
- Build the defence plan for [account] against [competitor] before [renewal date].
- What did [competitor] change in the [last 90 days], and what do I say if asked?
- War-game three rounds of [competitor]'s attempt to take [account], move by move, before their SE gets the meeting.
- Build a switching-cost calculator for [account] that shows, in their numbers, what leaving for [competitor] would really cost.
- Replay the accounts you lost to [competitor] and find the moment each was still saveable, and what would have saved it.
- How do we compare to [competitor] on [capability]?
- What do customers who left for [competitor] say was the reason?
- What questions should my customer ask [competitor] about [topic]?

Advanced prompts: War-game the rival's run at the account, Build the switching-cost calculator, Replay the accounts they took from us. Workflow prompts: Answer a customer's competitor comparison, Gauge how serious the evaluation is, Build the defence plan, Find what the rival changed recently. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/competitive-displacement-defence.md

### Expansion plays

Upsell and cross-sell spotted and framed from what the account owns and what its people ask for.

Ask it:
- Find expansion opportunities in my book, ranked by evidence: [paste the accounts]
- Write the case for [product] at [account], for [sponsor].
- Give me a talk track for raising [product] with [contact] at [account].
- Review how our expansion deals went this year, won and lost.
- Backtest an expansion propensity score on past expansion deals, then use it to rank your book.
- Find the expansion offer [account]'s buyers would pick by running a conjoint-style trade-off across scope, price and term.
- Allocate your CSM hours across the book by expected expansion value, like a portfolio manager, not by who shouts loudest.
- Has [account] asked for anything [product] does?
- What does [persona] object to when offered more?
- Which expansion deals did we lose this year and why?

Advanced prompts: Backtest an expansion propensity score, Find the offer by trade-off, Allocate your hours by expected value. Workflow prompts: Find expansion opportunities in your book, Write the expansion case for one account, Get a talk track for the check-in, Review how past expansions went. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/expansion-plays.md

### Onboarding kickoff and success plan

Kickoff agenda and success plan built on why they bought and what they expect.

Ask it:
- Draft the success plan for [account] from what they said during the sale.
- Write the kickoff agenda for [account], with [attendees] in the room.
- Build the 30-60-90 day plan for [account] on [product].
- Check this success plan against what [account] told us: [paste the plan]
- Run a Monte Carlo on your onboarding milestones and get the real odds of first value inside 30 days.
- Map the push, pull, anxiety and habit forces on each [account] user group, and find what really stalls adoption.
- Rehearse the kickoff against a skeptical stakeholder played from real quotes, then get scored on how you handled them.
- What outcome did [account] say they want from [product]?
- Did the rep promise a go-live date to [account]?
- Write the definition of done for [account] in their words.

Advanced prompts: Simulate the date of first value, Map the forces that stall adoption, Rehearse the kickoff against a skeptic. Workflow prompts: Draft the success plan from their words, Write the kickoff agenda, Build the 30-60-90 day plan, Check a success plan against the record. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/onboarding-kickoff-and-success-plan.md

### Customer questions

Straight answers on product, integrations, security and pricing from the approved brief.

Ask it:
- Answer [contact] at [account] from the product brief: [paste the question]
- Which of these customer questions does the brief not answer? [paste the questions]
- Check this reply to [account] about [topic] against the brief: [paste the draft]
- Measure how much of your question load the product brief could answer, and what that frees up in CSM hours.
- Write an eval set of hard customer questions with graded answers from the brief, so you can test any assistant or new CSM against it.
- Do we support [integration]?
- Is [feature] included in the [tier] plan?
- What is the approved answer to "[objection]"?
- Which questions do customers ask that our known weaknesses section already answers honestly?
- What's the most common question about [integration], and is the brief's answer still current?

Advanced prompts: Model the questions you could deflect, Write an eval set for answer accuracy. Workflow prompts: Answer a customer question from the brief, Find questions the brief can't answer, Check a colleague's draft reply. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/customer-questions.md

### Escalation handling

A response grounded in what the customer bought for, what the product does, and what changed.

Ask it:
- Draft my reply to [contact] at [account] about [topic]: [paste the complaint]
- Write the internal brief on the [account] escalation about [topic].
- Write a four-sentence note to [sponsor] at [account] about the escalation.
- Build a fault tree for the escalation and find whether it's a product gap, a broken promise or a missed onboarding step.
- Lay out every remedy for the escalation as a decision tree and pick the one with the best expected outcome for the renewal.
- Did our rep promise [account] anything about [topic]?
- Have other customers complained about [topic]? Quote them.
- Write an honest two-line acknowledgement of a problem with [feature].
- Which customers raised the same issue as [account], and did they renew?
- Did any lost renewal list [topic] as a deciding driver?

Advanced prompts: Build a fault tree of the escalation, Choose the remedy with a decision tree. Workflow prompts: Draft the escalation reply, Write the internal escalation brief, Write the note to the sponsor. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/escalation-handling.md

### Stakeholder mapping

Who is on the account, which persona and buying role each maps to, and who is missing.

Ask it:
- Map the stakeholders at [account] and the roles we have no contact for.
- Nobody talks to the [persona] at [account]. Give me the angle and an intro.
- Which accounts in my book are single-threaded? [paste the accounts]
- Model [account] as an influence network and simulate what breaks when the champion leaves.
- Compare [account]'s contact coverage with the buying groups on deals that renewed and those that didn't, and close the gap.
- Who is the economic buyer at [account]?
- Which of my accounts have only one contact?
- Write an intro message to a [persona] that my champion can forward.
- Which buying role is most often missing on renewals we lost?
- Who at [account] attended the most calls, and what's their buying role?

Advanced prompts: Model the account as an influence network, Benchmark coverage against renewed accounts. Workflow prompts: Map the stakeholders on one account, Reach the role nobody talks to, Find single-threaded accounts in your book. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/stakeholder-mapping.md

### Customer education content

Training outlines and adoption guides per persona from the product brief and the jobs to be done.

Ask it:
- Write an adoption guide for [user persona] on [use case].
- Build an FAQ for [use case] from the questions customers actually asked.
- Which of our guides did this month's product changes make stale? [paste the guides]
- Pilot your training on synthetic learners built from each persona, then fix the lessons where they get lost.
- Design a proper A/B test for your adoption guide, with the sample size and run time you'd need to trust the result.
- What are the jobs to be done for [user persona]?
- What questions do users ask about [use case]?
- Write a five-step quick start for [user persona] on [use case].
- Which job to be done for [user persona] has no guide covering it?
- What do users say they wish someone had told them in week one?

Advanced prompts: Pilot the training on synthetic learners, Design an A/B test for the adoption guide. Workflow prompts: Write an adoption guide for one role, Build an FAQ from real questions, Find guides that need updating. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/customer-success/customer-education-content.md

11 use cases, full prompts: https://github.com/calven-ai/calven-mcp/tree/main/use-cases/customer-success

## Example

Question: "Build the renewal brief for Kestrel Payments, renewing in March."

Answer (illustrative example workspace): Why they bought: time to value. "Live in six weeks, not five months." Audit readiness was the second driver. What they have said since: two calls mention a new payments region in 2027 and audit scope growing with it. Where you can help: regional data residency and audit trails, both in the approved product brief. They also asked about dbt Cloud, which has no approved answer yet.

Sources: Kestrel won deal and survey, 2 account calls, Product brief.

## Where customer success teams use Calven

Calven works where your team already does: in Slack, where you ask @Calven in a thread or a DM, and in Claude, ChatGPT, Cursor, Copilot or any MCP client over Calven MCP: https://calven.ai/mcp

## What changes when customer success teams' AI tools read from Calven?

Customer success teams using AI without a shared source get fast prep built on the CRM notes field. Connected to Calven, every brief, QBR and renewal starts from why the customer bought and what they have said since.

| Pain point | Without Calven | With Calven |
| --- | --- | --- |
| Prep time | QBR and renewal prep rebuilt from CRM notes and last year's slides | The brief drafted in one prompt from why they bought and what they said since |
| Handoffs | What sales promised gets lost between the close and the kickoff | Promises, drivers and people in one brief, each promise checked against the product brief |
| Competitors | Competitor threats found on the renewal call | Competitor moves on renewing accounts flagged with the battle card that answers them |
| Risk | Risk read from a usage dashboard and a gut feeling | Risk read from what the account said, matched to how you usually lose |
| Expansion | Expansion pitched as a seat-count upsell at renewal | Expansion framed on needs the account named, in their words |
| Accuracy | Every CSM answers product questions a little differently | Answers from the approved product brief, caveats included |

## FAQ

### How does Calven help customer success teams?

It gives CSMs the context sales and product marketing hold: why each account bought, what was promised, quotes from their calls, who matters by buying role, and how to answer a competitor. CSMs use it for QBRs, renewals and expansion.

### Does Calven include product usage or health scores?

No. Usage, tickets, health scores and contracts stay in your CS tools. Calven covers the buying and market side: deal drivers, call quotes, personas, the product brief and battle cards.

### Can Calven warn us when a competitor targets a customer?

The competitive intelligence agent tracks competitor sites, docs and pricing. When a move touches a renewing account, the Slack app can post it with the battle card that answers it.

### Do customer success teams need to log into Calven?

No. Product marketing runs Calven. Everyone else reaches the same approved context from the AI tool they already use over Calven MCP, or in Slack. Professional and Enterprise include unlimited seats, so each person signs in as themselves.

### Which AI tools work with Calven?

Any client that supports remote MCP: Claude, ChatGPT, Cursor, VS Code with GitHub Copilot, Claude Code, Codex and others. Paste https://api.calven.ai/mcp, choose OAuth and sign in.

See also: [All teams](https://calven.ai/solutions.md) · [Calven MCP](https://calven.ai/mcp.md) · [Product marketing](https://calven.ai/solutions/product-marketing.md)