# Territories built on who actually buys

> Calven ranks CRM accounts by ICP fit with the reason for each rank, finds win-backs worth a second try, and cuts win rates by segment, competitor and persona, in the AI tool RevOps already uses.

- Source: https://calven.ai/solutions/revenue-operations
- Last updated: 2026-10-05

---

## What can revenue operations teams use Calven for?

Ranked target lists, territory plans, win-rate cuts and forecast risk reads that start from the approved ICP and why deals are won or lost. Calven is the approved context your AI workflows need to scale across the team and still be trusted.

### Target account ranking

Every CRM account scored against the current ICP with the reason, for routing and prioritisation.

Ask it:
- Rank our [segment] accounts by ICP fit and give the reason for each rank.
- Split the strong fits in [segment] into never worked, open and lost [6]+ months ago, with who to contact.
- Score this account list against our ICP: [paste the list]
- Check this target list against our ICP and the CRM before we work it: [paste the list]
- Backtest our ICP fit score on last year's closed deals and show whether high scores actually win more.
- Rank my [segment] accounts by expected pipeline: fit times odds of winning times deal size, in a live spreadsheet.
- Have a veteran AE tear apart my top 20 target accounts, then keep, caveat or swap each one.
- Which Tier 1 accounts have no deal recorded?
- What is our win rate in profile versus out of profile this year?
- Why is [account] Tier 2?

Advanced prompts: Backtest the fit score on closed deals, Rank accounts by expected pipeline value, Red-team the top 20 as a veteran AE. Workflow prompts: Rank accounts by ICP fit, with reasons, Split strong fits by status and contact, Score an account list outside the CRM, Check a target list someone else built. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/target-account-ranking.md

### Pipeline health

How much of the quarter is in profile, multi-threaded and against which competitors.

Ask it:
- Give me the pipeline health read for this week's review.
- Match deals closing [this quarter] to the patterns we lost on most.
- List the open deals missing an amount, close date or competitor, by owner.
- Simulate this quarter's pipeline 10,000 times and tell me the odds of hitting [target] and which deals swing it.
- Run a survival analysis on closed deals and flag every open deal that's already outlived its odds of winning.
- Put every open deal on a fit versus momentum two-by-two and give each quadrant its own play.
- How much of the open pipeline is Tier 1?
- Which late-stage deals have only one contact?
- Which open deals face [competitor], and what is our win rate against them?
- Which open deals have been open longer than our average won sales cycle?

Advanced prompts: Simulate where the quarter lands, Flag deals that outlived their odds, Map the pipeline on fit and momentum. Workflow prompts: Build the weekly pipeline health read, Match open deals to past loss patterns, List open deals with data gaps. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/pipeline-health.md

### Win-backs

Closed-lost accounts whose loss reason may no longer apply, and whether the champion is still there.

Ask it:
- Find the deals we lost in the [last 12 months] whose loss reason no longer applies.
- Rank these win-backs by fit and whether the champion is still there: [paste the deals]
- Write the re-engagement angle for each account on this list: [paste the ranked list]
- Replay last year's lost deals against what we've shipped since and estimate which ones would flip.
- Rank closed-lost accounts by win-back odds, starting from a base rate and updating on each signal, Bayesian style.
- Design my win-back campaign as an experiment with a control group and a sample size that can detect real lift.
- Which deals did we lose on "Missing feature" in the last year, and which feature?
- What did we ship since [date] that answers a recorded loss reason?
- Is the champion from [lost deal] still listed at [account]?
- Which lost deals had a champion who's still listed and a loss reason we've since addressed?

Advanced prompts: Replay lost deals against what we shipped, Rank win-backs by updating the odds, Design the win-back test with a control group. Workflow prompts: Find lost deals worth another try, Rank win-backs by who's still there, Write the re-engagement angle per account. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/win-backs.md

### Forecast inputs

Deal-level risk from competitor, persona coverage and loss patterns, for the forecast call.

Ask it:
- Give me the risk read on deals over [amount] closing [this quarter], for [Monday]'s forecast call.
- What could sink [deal]? Give me the risks and what past wins had that it has.
- List the deals closing [this quarter] that are missing forecast data.
- Forecast each commit deal from its closest closed lookalikes, then compare that outside view with the rep's call.
- Have a sceptical CFO interrogate every deal in this week's commit, then defend, haircut or cut each one.
- Which deals closing this quarter are single-threaded?
- Which committed deals face a competitor we lose to more than we win?
- Is [deal] in profile, and what is the win rate for its tier?
- Which commit deals have a contact marked as Blocker?
- How long do won deals in [segment] usually sit at the negotiation stage?

Advanced prompts: Forecast each commit deal from its reference class, Stress-test the commit as the CFO. Workflow prompts: Build the risk read for the forecast call, Find what could sink a committed deal, List deals missing forecast data. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/forecast-inputs.md

### Segment win rates

Win rates by segment, competitor and persona you can cut, with n.

Ask it:
- Cut win rates for [last quarter] by segment, competitor and persona for the [board] pack.
- Explain why our win rate against [competitor] in [segment] moved from [48%] to [31%].
- Reconcile this win-rate table with Calven and tell me why the numbers differ: [paste the table]
- Rank segments by win rate without being fooled by tiny samples, using empirical Bayes shrinkage and credible intervals.
- Tell me whether our win rate moved because we got better or just sold to easier segments.
- Stage a debate between doubling down on our best segment and fixing our worst, judged by the CRO.
- What is our competitive win rate this quarter versus last, with n?
- What is our win rate against [competitor] this year?
- Do we win more when a technical buyer is on the deal?
- Which segment's win rate rose while its deal count fell?

Advanced prompts: Shrink small-sample win rates before ranking, Split the win-rate change into mix and rate, Debate where to double down. Workflow prompts: Cut win rates and show what moved, Explain one win-rate shift, Reconcile a win-rate table from another deck. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/segment-win-rates.md

### Lost deal analysis

Why deals were lost, by reason, competitor and segment, in the buyer's words.

Ask it:
- Build the lost deal readout for [last quarter], by reason, competitor and segment.
- Compare the CRM loss reasons for [last quarter] with what the buyers said.
- Turn this loss readout into actions for each team: [paste the readout]
- Build a causal map of why we lose, separating root causes from the symptoms reps put in the CRM.
- Rank the fixes for our top loss drivers by pipeline recovered per dollar, with break-even effectiveness for each.
- Grow a small decision tree from closed deals that predicts losses, and turn it into a rep checklist.
- s words?", 
- , "How often does the rep
- Which losses had a champion but no economic buyer on the deal?
- What do buyers say about us in deals we lost at the final stage?

Advanced prompts: Separate root causes from symptoms, Rank loss fixes by pipeline recovered, Grow a decision tree that predicts losses. Workflow prompts: Build the quarterly loss readout, Compare rep loss reasons with buyer reasons, Turn the loss readout into team actions. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/lost-deal-analysis.md

### Territory planning

Territories built on who actually buys: fit, segment, win predictors.

Ask it:
- Score and segment the account pool for [next year] territory planning.
- Show how Tier 1 potential splits across territories: [paste the mapping]
- Explain the [East] territory to its rep: the ten accounts to work first and why.
- Solve territories as an optimisation problem so every rep gets roughly equal expected bookings, not equal account counts.
- Stress my territory plan by shifting ICP weights and win rates, and show which territories break.
- War-game my territory rules against reps chasing commission, and close the loopholes before launch.
- How many Tier 1 accounts are in [region]?
- Which territory has the fewest strong-fit accounts?
- Which accounts in [territory] are disqualified by the ICP?
- Which region has the highest share of Tier 1 accounts with a recent trigger?

Advanced prompts: Balance territories with an optimisation model, Test how fragile the carve is, War-game how reps will game the rules. Workflow prompts: Score and segment the account pool, Show how potential splits across territories, Explain a territory to its rep. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/territory-planning.md

### ICP refreshes

What actually predicts a win, where to expand, what to disqualify.

Ask it:
- Build the evidence pack for the ICP review of [last quarter].
- Show me why [segment] buys from us, in their own words.
- Check this proposed ICP edit against our win data: [add payments as a priority vertical]
- Fit a regression on closed deals and show where our ICP scorecard weights disagree with what actually predicts wins.
- Run a three-round Delphi panel of sales, PMM, CS and finance on my proposed [ICP change].
- Map push, pull, anxiety and habit for [segment] from buyer quotes, and tell me if they'll actually switch.
- Does the ICP still predict wins? Give me the four KPIs with the prior period.
- Which attribute predicts a win most?
- Which out-of-profile segment wins most often?
- Which out-of-profile wins share an attribute the ICP doesn't mention?

Advanced prompts: Fit a win model against the scorecard, Run a Delphi round on the ICP change, Map the forces that make a segment switch. Workflow prompts: Build the ICP review evidence pack, Show why a segment buys, in their words, Check a proposed ICP edit against the data. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/icp-refreshes.md

### Lead routing rules

Scoring and routing inputs from ICP fit, win predictors and persona coverage.

Ask it:
- Check our lead scoring against the ICP and what predicts a win: [paste the scoring sheet]
- Write the inbound routing spec by persona, with the titles that map to each.
- Audit the leads we routed in [last quarter] against the ICP and the win predictors.
- Replay my proposed routing rules on last year's leads and show which won deals they'd have misrouted.
- Model the queue my new routing rules create and find the volume where the response SLA breaks.
- Which ICP attributes should carry the most points?
- Which persona converts best, and what titles map to it?
- Does company size predict a win in our data?
- Which job titles show up on won deals but aren't mapped to any persona?
- How many contacts at Tier 1 accounts are still Lead after 90 days?

Advanced prompts: Replay new routing rules on last year's leads, Size the sales queue the rules will create. Workflow prompts: Check lead scoring against the win predictors, Write the inbound routing spec by persona, Audit last quarter's routed leads. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/lead-routing-rules.md

### Persona coverage

Which personas are on each deal, the multi-threading payoff, where coverage is thin.

Ask it:
- Give me the persona coverage read for deals over [amount] in [last quarter].
- Brief the rep on [deal] on who to add, given these contacts: [paste the contacts]
- Which personas show up on our wins but never reach the pipeline in [last quarter]?
- Estimate the pipeline each missing persona is worth on every open deal, controlling for deal size.
- Let a rep role-play the missing [persona] on their deal, played from our canvas, and score the conversation.
- What is the win rate for multi-threaded versus single-threaded deals?
- Which open deals over [amount] have no economic buyer?
- Which deals have a blocker and no champion?
- Which persona appears on won deals but almost never on lost ones?
- Which open deals have an end user but no buyer persona?

Advanced prompts: Price each missing persona in pipeline, Rehearse the missing stakeholder before the rep meets them. Workflow prompts: Build the persona coverage read, Brief a rep on who to add, Find personas the pipeline never reaches. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/persona-coverage.md

### QBR metrics pack

The quarter's GTM numbers from one source, with n and the prior period.

Ask it:
- Build the GTM metrics pack for [Q3], with the prior quarter and n.
- Explain the five biggest movers this quarter, with the evidence: [paste the movers]
- Write the one-page QBR narrative from this pack and [our bookings numbers].
- Red-team my QBR narrative for cherry-picked windows, missing sample sizes and moves that are only noise.
- Build a driver tree for pipeline won and show which lever explains the change from last quarter.
- s headline KPIs for last quarter, with the prior period?", 
- , 
- Which KPI moved against the trend of the last two quarters?
- Which dashboard's sample is too small to report this quarter?
- How did the ICP share of wins change while pipeline won changed?

Advanced prompts: Red-team the QBR story for cherry-picking, Trace pipeline won through a driver tree. Workflow prompts: Build the quarter's GTM metrics pack, Explain the five biggest movers, Write the one-page QBR narrative. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/qbr-metrics-pack.md

### CRM data quality

Deals missing size or close date, accounts without industry, stages without history.

Ask it:
- List this week's CRM gaps by owner, with the analysis each one breaks.
- Check which of last week's CRM gaps closed: [paste last week's list]
- Map each CRM field to the analyses it feeds for [product], with today's gap count.
- Show how wrong our win rates could be because of missing CRM fields, with best and worst case bounds.
- Turn our stage definitions into exit rules a script can run, then show which deals fail which rule.
- How many open deals have no close date?
- Which late-stage deals have no competitor recorded?
- Which lost deals this quarter have no loss reason?
- Which lost deals have no loss reason and no survey response, so we'll never know why?
- Which accounts are missing a size, so they drop out of segment win rates?

Advanced prompts: Bound the error the gaps put in your win rates, Write stage exit rules as checks you can run. Workflow prompts: List this week's CRM gaps by owner, Check whether last week's gaps closed, Map fields to the analyses they feed. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/crm-data-quality.md

### Win/loss program health

Survey coverage, response funnel, timing and segment coverage of the win/loss program.

Ask it:
- Give me the win/loss program health read for [last month].
- List the deals decided in [last month] that have no survey.
- Check how far to trust the numbers in this win/loss readout: [paste the readout]
- Check whether survey respondents look like our decided deals, and reweight the loss readout if they don't.
- Tell me how many responses each segment and competitor cut needs before its findings mean anything, and how long that takes.
- What share of decided deals had a completed survey this quarter?
- What is the survey completion rate, and how did it change?
- Which segment has the lowest survey coverage?
- Do lost deals or won deals answer the survey more often?
- Which competitor's losses have the fewest completed responses?

Advanced prompts: Correct the readout for non-response bias, Find the response count each cut needs. Workflow prompts: Read the win/loss program's health, List decided deals with no survey, Check how far to trust the numbers. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/revenue-operations/win-loss-program-health.md

13 use cases, full prompts: https://github.com/calven-ai/calven-mcp/tree/main/use-cases/revenue-operations

## Example

Question: "Split the strong ICP fits in fintech into never worked and lost 6+ months ago, with who to contact."

Answer (illustrative example workspace): Fit matters: in-profile deals closed at 31% over the last four quarters, outside-profile at 9%. Route these first. Account Status Who to contact Ledgerline Never worked Marcus Lee, Head of Data Parcelwise Lost in February, on budget Jonas Albrecht, the champion, still listed Orbit Pay Never worked No data lead on record. Start with the CFO

Sources: CRM accounts, contacts and loss reasons, 412 CRM deals, ICP, last approved Sep 12.

## Where revenue operations 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 RevOps' AI tools read from Calven?

RevOps teams using AI without a shared source get fast answers from a CRM export that cannot say why deals are won. Connected to Calven, every ranking, win-rate cut and forecast read starts from the same approved ICP and loss evidence.

| Pain point | Without Calven | With Calven |
| --- | --- | --- |
| Account fit | Target lists sorted by headcount and region | Every account scored against the approved ICP, with the reason for its rank |
| Win rates | A pivot on a CRM export that changes every time someone reruns it | Win rates by segment, competitor and persona, with n and the window |
| Loss reasons | The rep's pick-list reason, taken at face value | The buyer's own words, and where they disagree with the CRM |
| Forecast risk | A commit built on rep confidence | Each committed deal checked against past loss patterns, threading and competitor |
| Win-backs | Every closed-lost deal older than six months | The losses whose reason no longer applies, and whether the champion is still there |
| QBR numbers | Rebuilt from exports every quarter, and they never reconcile | One source, the same window, the prior period and the movers explained |

## FAQ

### How does Calven help RevOps teams?

It adds the context the CRM lacks: ICP fit with the reason, segment tiers, loss reasons in the buyer's words, and win rates by competitor and persona with sample sizes. RevOps uses it to plan territories, rank target accounts and find win-backs.

### Does Calven write to our CRM?

Calven MCP is read-only, so nothing you ask in an AI tool changes the CRM. The Calven app can write ICP scores and competitive intel back to the records reps open. Routing, forecasts and other CRM edits stay with RevOps.

### How does Calven score accounts against the ICP?

The ICP agent learns which traits predict a win from the deals you won and lost: industry, size, tech stack and use case. Every account is scored against that profile with the reason for its rank.

### Do revenue operations 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)