# Walk into every deal knowing how you win it

> Calven gives account executives deal prep, competitor landmines and objection handling backed by deals you won, in the AI tool they already use. Approved by product marketing, with sources.

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

---

## What can sales teams use Calven for?

Call briefs, talk tracks, objection answers and recaps that start from the approved story and the deals you won. Calven is the approved context your AI workflows need to scale across the team and still be trusted.

### Deal prep

The brief before a call: where the deal stands, who is on it, what sank similar deals, what to ask first.

Ask it:
- Build my call brief for [deal] at [time]. [Competitor] is in the deal.
- Find what decides deals like [deal] against [competitor] in [segment].
- Pick the proof point for a [persona] worried about [concern].
- Check my call plan for [deal] against what wins: [paste your plan]
- Start from our real base rate and update the win odds on [deal] fact by fact, Bayesian style, for the forecast call.
- Replay three to five lost deals like [deal] and test which one change would have saved them.
- Turn my next call on [deal] into an if-they-say, I-ask decision tree, three levels deep, as a clickable page.
- Where does [deal] stand and who is on it?
- Why did we lose the last three deals to [competitor]? Quote the buyers.
- Which contact roles are missing from [deal] compared with the deals we won?

Advanced prompts: Update the odds as the deal facts come in, Replay the deals we lost that looked like this one, Build the call as an if-they-say tree. Workflow prompts: Build a one-page call brief, Find what decides deals like this one, Pick the proof point for this buyer, Check your own call plan. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/deal-prep.md

### Objection handling

A response to a live objection, drawn from deals we won and the approved objection handling.

Ask it:
- The [persona] on [deal] said "[objection]". How did we answer that in deals we won?
- Draft a written answer to "[objection]" that [contact] can forward to [stakeholder].
- Find the objections from [last quarter] that our talk track does not answer.
- Check my answer to "[objection]" before I send it: [paste your answer]
- Have two answers to "[objection]" debate each other, let the [persona] judge, then write the answer that beats both.
- Backtest how our reps answer "[objection]" against deal outcomes and show which approach actually wins.
- Build an HTML flashcard drill of real buyer objections that resurfaces the ones I fumble until they stick.
- How do we answer "we already use [competitor]"?
- Show me a buyer who said "[objection]" and then bought. What changed their mind?
- Is "[objection]" usually a brush-off or a real concern in our deals?

Advanced prompts: Debate two answers and let the buyer judge, Backtest which answers show up on won deals, Build a spaced-repetition drill for objections. Workflow prompts: Answer one objection with evidence, Draft a written answer they can forward, Find objections the talk track misses, Check your answer before you use it. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/objection-handling.md

### Competitive talk tracks

How to position against the rival in the deal, with landmines and proof.

Ask it:
- Build my talk track against [competitor] for [deal]. The buyer liked [their demo].
- What has [competitor] changed since [the last time I pitched against them]?
- Play a [persona] who prefers [competitor] so I can rehearse.
- Check the [competitor] battle card against our calls from [last quarter].
- War-game [deal] against [competitor] in four move and counter-move rounds and find the move they can't answer.
- Build a payoff matrix for [deal] from our real win rates against [competitor]: fight, reframe or walk away?
- Role-play a [persona] leaning to [competitor], three rounds harder each time, and score every answer I give.
- Where do we lose to [competitor], honestly?
- What trap should I set against [competitor] on a first call with a [persona]?
- A buyer says [competitor] has [feature] and we do not. What do we say?

Advanced prompts: War-game the deal against them, Decide whether to fight, reframe or walk, Run a scored role-play against their best rep. Workflow prompts: Build a talk track for this deal, See what the competitor changed recently, Rehearse against a buyer who prefers them, Check the battlecard against recent calls. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/competitive-talk-tracks.md

### Discovery questions

The questions to ask this persona in this deal, built on their pains and our qualification criteria.

Ask it:
- Write my discovery questions for a first call with a [persona] at [account].
- Give me the two questions that test the risk on [deal] against [competitor].
- What did my discovery on [deal] miss? [paste your notes]
- How well do we really know the [persona]? Show me the gaps.
- Build a discovery guide on push, pull, anxiety and habit to learn whether a [persona] will actually switch.
- Rank my discovery questions by how much each answer would move the forecast, and cut the rest to fit the call.
- Write a rubric from our best reps' discovery and grade my own call transcripts against it, line by line.
- What does a [persona] care about most, and what are they measured on?
- What question exposes where [competitor] loses?
- How do buyers describe the problem we solve? Give me their phrases.

Advanced prompts: Build a switch interview on the four forces, Rank questions by what the answer is worth, Write a rubric to grade your own discovery calls. Workflow prompts: Write the question set for a first call, Find the two questions that test the risk, Spot what your discovery notes missed, Check how well we know this persona. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/discovery-questions.md

### Follow-up recaps

The email after the call, in the buyer's words, with the next step and the proof they asked for.

Ask it:
- Write the recap for my call with [contact] that they can forward: [paste your notes]
- Check this recap for [account] before I send it: [paste the recap]
- Which proof points do I keep lacking? [paste what buyers asked you to prove]
- Build a scoring rubric for a forwardable recap and grade my last five against it, so I see the habit that weakens them.
- Map the mutual action plan's critical path and estimate, PERT-style, the real odds we close by the date the buyer gave.
- How do customers describe [pain] in their own words?
- Do we do [thing they asked about]? Give me the honest answer.
- What proof do we have on time to value?
- Which phrase do [persona] buyers use for [pain] that our messaging never does?
- What's the proof point closest to the metric [account] gave me?

Advanced prompts: Grade your last recaps against a rubric, Find the critical path to the close date. Workflow prompts: Write a forwardable follow-up recap, Check the recap before you send it, Find the proof points you keep lacking. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/follow-up-recaps.md

### Technical questions

A straight answer to a product, integration or architecture question, including what we do not do.

Ask it:
- [Contact] at [account] asked "[question]". Answer from the approved product brief.
- Does what I tell buyers about [topic] still hold? [paste your answer]
- Find the buyer questions from [last quarter] the product brief can't answer.
- Red-team what we've told [deal] as their architect and security lead, and find the answer that would stall it.
- Turn the buyer's RFP into a risk-weighted fit spreadsheet against the product brief, with a bid or no-bid call.
- Write 20 trick technical questions with golden answers from the product brief to test any draft before it goes out.
- Does the product do [capability]? Say no if we do not.
- What does the brief say about hosting, data residency and SSO?
- Is this a question for the solutions engineer?
- Which product feedback category shows up most on deals we lost?

Advanced prompts: Red-team our answers as their architect, Score the RFP against the brief, weighted by risk, Write a test set of hard technical questions. Workflow prompts: Answer a buyer's technical question, Check whether your product answer still holds, Find questions the product brief can't answer. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/technical-questions.md

### Pricing objections

Handling "too expensive" and "cheaper elsewhere" with the approved packaging and win/loss evidence.

Ask it:
- The buyer on [deal] says [competitor] is cheaper. Answer with evidence, not a discount.
- How often did price really decide our deals in [segment] over [the last two quarters]?
- Check my pricing response to [account] before I send it: [paste your response]
- Run a Van Westendorp price ladder with the buying committee's personas and find where our price reads as too expensive, and to whom.
- Build a give-get matrix with both sides' walk-away options and the zone of agreement before procurement asks for a discount.
- Find the break-even: how much does a discount have to lift my win probability before it's worth giving?
- How often is price the reason we lose, and how often did it really decide the deal?
- Which buyers said we were pricier and bought anyway? What did they say?
- What is the approved answer to "it's too expensive"?
- On deals lost to price, what did the buyer actually rank first in win/loss?

Advanced prompts: Run a price ladder with the buying committee, Build the give-get matrix before you negotiate, Find the discount that pays for itself. Workflow prompts: Answer a pricing objection with evidence, See how often price decides our deals, Check your pricing response before sending. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/pricing-objections.md

### Account plans

The plan for a named account: fit, buying group, whitespace, angle, next 90 days.

Ask it:
- Build a one-page plan for [account] in [segment] for [Q1].
- Which roles are we missing at [account] compared with the deals we win in [segment]?
- Challenge my plan for [account] the way my manager would: [paste your plan]
- Rank which of these accounts deserve a plan this quarter: [paste the list]
- Rank the whitespace plays at [account] by expected value per hour, using our real win rates and deal sizes for each play.
- Map the buying group at [account] on a power and interest grid and find the shortest path to the economic buyer.
- Find the won accounts most like [account] and replay how we won them as a 90-day path to copy.
- Is [account] in our ICP? Which tier, and why?
- What deals have we had at [account] and what happened?
- Which accounts in my territory have a trigger and no open deal?

Advanced prompts: Price each whitespace play by expected value, Map who moves the decision and how to reach them, Replay how lookalike accounts were won. Workflow prompts: Build a one-page account plan, Find the roles you're missing, Challenge your plan as your manager, Rank which accounts deserve a plan. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/account-plans.md

### Multi-threading

Which personas are missing from the deal and how to open them.

Ask it:
- Show me the threading gap on [deal] and how to close it through [champion].
- Find my single-threaded deals in [segment].
- Check my opener to the [persona] on [deal]: [paste the message]
- Map the buying group as a network and find who really holds influence, not just who's on the org chart.
- Backtest how many roles we threaded against how closed deals actually ended, and find the threading threshold that predicts a win.
- Build a decision tree for which missing contact to open first, weighing the win-rate gain against the risk of upsetting my champion.
- Which personas are on the deals we win in [segment]?
- Which role, when missing, costs us deals most often?
- Give me a three-line note to a [persona] from their champion's point of view.
- Which persona appears on our won deals but almost never on lost ones?

Advanced prompts: Map who holds influence in the buying group, Backtest threading depth against closed deals, Decide which contact to open first. Workflow prompts: Map the threading gap and how to close it, Find single-threaded deals in your pipeline, Check your opener to a new contact. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/multi-threading.md

### Exec briefings

The one-page briefing for the economic buyer or an executive sponsor.

Ask it:
- Build my briefing for [contact], [title] at [account], and a version my champion can forward.
- Play the [CFO] on [deal] so I can rehearse the meeting.
- Read my briefing as a [CFO] and tell me what they skip: [paste the briefing]
- Put my business case through a Delphi panel of executive personas and let them converge, over rounds, on what would make them sign.
- Have the CFO stress-test my business case: which assumption breaks it, and how far can it fall before the deal doesn't pay back?
- What does a [executive persona] care about and distrust?
- What objections do economic buyers raise that kill our deals?
- Where does our win rate drop when the economic buyer is not engaged?
- Which outcome do executives in our won-deal quotes cite most?
- What does the economic buyer persona's canvas say counts as proof?

Advanced prompts: Converge an executive panel on the case, Stress-test the business case as the CFO. Workflow prompts: Build the exec briefing and a forwardable version, Rehearse the meeting with the economic buyer, Read your briefing as the executive. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/exec-briefings.md

### Demo storylines

The narrative the demo follows for this buying group, built with the SE.

Ask it:
- Build the demo storyline for [deal], with [attendees] in the room and [competitor] in play.
- Debrief the [deal] demo against the record: [paste your notes]
- Read this demo storyline as a [persona]: [paste the storyline]
- Run my demo past a synthetic panel of the buying group and chart each persona's attention beat by beat.
- Make the trade-off: which features earn a place in my demo's time, given what each buyer values and what the competitor shows?
- What does a [persona] need to see in a demo?
- What should I show that [competitor]'s demo cannot?
- Which customer quote fits the [capability] moment?
- Which capability do buyers in [segment] mention most in won-deal drivers?
- What did lost buyers say they wanted to see that we didn't show?

Advanced prompts: Chart each persona's attention beat by beat, Pick the features to show in your time. Workflow prompts: Build the demo storyline for this buying group, Debrief the demo against the record, Read the storyline as the buyer. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/demo-storylines.md

### Proposal drafts

The proposal narrative: problem, approach, proof, packaging.

Ask it:
- Draft the proposal for [deal] around the problem they stated: [problem].
- Fact-check every claim in this proposal: [paste the proposal]
- Read this proposal as the [CFO] and tell me what they push back on: [paste]
- Have their procurement lead red-team my proposal line by line and tell me what they'll strike, question or use against me.
- Build a working ROI spreadsheet for my proposal with low, expected and high ranges the buyer can edit.
- Frame my proposal as good-better-best options and test with the personas which one they pick, and whether a decoy shifts them.
- What are our unique attributes against [competitor]?
- Which quote shows a measurable outcome for [segment]?
- Does the brief say we integrate with [system]?
- Which proof point do won deals against [competitor] cite most?

Advanced prompts: Red-team the proposal as their procurement lead, Build the value model behind the proposal, Test good-better-best options on the personas. Workflow prompts: Draft the proposal narrative, Fact-check every claim in the proposal, Read the proposal as the economic buyer. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/proposal-drafts.md

### Deal reviews

The deal card for the weekly review, scored against the qualification framework with evidence.

Ask it:
- Build the deal card for [deal] for tomorrow's pipeline review.
- Which of my open deals in [segment] look weakest, and why?
- Challenge my commit on [deal] for [date] the way my manager would: [paste reasons]
- Score my past commit calls against what actually closed with a Brier score, and show where my forecast bias lives.
- Simulate my quarter a thousand times from my open deals and tell me the real odds of hitting my number.
- Grade every MEDDICC letter on my deal by the strength of its evidence, with a confidence score, not a colour.
- Do we have an economic buyer on [deal]?
- Why do deals like [deal] slip past their close date?
- Which of my open deals is out of ICP profile?
- Which stage do deals in [segment] most often stall at, and for how long?

Advanced prompts: Score your past commit calls for calibration, Simulate the quarter from your open deals, Grade each qualification letter by its evidence. Workflow prompts: Build the deal card for pipeline review, Find the open deals that look weakest, Challenge your commit as your manager. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/deal-reviews.md

### CS handoff

The handoff note: what was promised, why they bought, what nearly stopped it, who matters.

Ask it:
- Write the handoff note for [account] so the CSM never has to re-ask me.
- List every promise we made to [account] and check each against the product brief.
- Check my handoff note for [account] against the record: [paste your note]
- Score the first 90 days at [account] on probability and impact, from what nearly stopped the deal.
- Trace every promise made to [account] on calls and paper to the product brief, and flag the ones we can't keep.
- Why did [account] buy, in their own words?
- What did our reps promise on calls with [account]?
- What does [account]'s champion say success looks like?
- What did customers in [segment] complain about most during onboarding?
- Which competitor did [account] evaluate, and what did they like about them?

Advanced prompts: Build a 90-day risk register for the account, Trace every promise to its proof. Workflow prompts: Write the customer success handoff note, List and check every promise we made, Review a handoff note written from memory. Full prompts: https://github.com/calven-ai/calven-mcp/blob/main/use-cases/account-executives/cs-handoff.md

### Renewal prep

What the customer bought and why, what they said since, and the expansion case.

Ask it:
- List the renewals in the next [90] days and the risk signals on each.
- Build the renewal brief for [account], renewing on [date], for [sponsor].
- [Competitor] is in the [account] renewal. Prepare me for it.
- We lost the [account] renewal. Tell me why and what it says about the rest.
- 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.
- Has anyone at [account] mentioned [competitor]?
- What should I propose as an expansion to [account], based on their asks?

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, 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

15 use cases, full prompts: https://github.com/calven-ai/calven-mcp/tree/main/use-cases/account-executives

## Example

Question: "Build my call brief for Helio Bank at 2:00. Northwind is in the deal."

Answer (illustrative example workspace): Biggest risk: hosting. 3 of your last 4 losses to Northwind needed on-premises, and 2 of those were banks. Nobody has asked Helio yet. Ask first: Tom Whitfield, Director of IT Security, is on the deal but has not been on a call. Ask him: "Where does this have to run, and who signs off on data leaving your environment?" Your proof: Kestrel Payments picked you over Northwind on time to value: "Live in six weeks, not five months."

Sources: Helio deal record, Northwind battle card, Win/loss, 31 deals vs Northwind, Kestrel interview.

## Where sales 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 sales teams' AI tools read from Calven?

Sales teams using AI without a shared source get confident answers built on old battle cards and guessed product facts. Connected to Calven, every brief, talk track and recap starts from the approved context and the deals you won.

| Pain point | Without Calven | With Calven |
| --- | --- | --- |
| Prep time | Thirty minutes in the CRM, Slack and old decks before every call | A one-page call brief from the deal record, battle card and win/loss in one prompt |
| Competitors | A comparison slide the competitor has already answered | Talk tracks from the deals you won against that rival, with the trap and the proof |
| Objections | Answered from a script, or from what the rep remembers | Answered with what changed the mind of a buyer who said the same thing |
| Accuracy | Ping product marketing before every technical call, or promise what does not ship | Answers from the approved product profile, including what you don't do |
| Follow-up | Recaps written from memory that repeat the pitch | Recaps in the buyer's words with the proof they asked for |
| Deal reviews | Pipeline review as opinion versus opinion | Deal cards with buyer evidence behind every criterion, and the risk named first |

## FAQ

### How does Calven help account executives prepare for a deal?

Ask your AI tool about the deal and Calven returns where it stands, who is on it, what sank similar deals against the same competitor, and the first question to ask, each point linked to the deal, interview or battle card behind it.

### Where do the objection responses come from?

From deals you won and the objection handling product marketing approved. Calven quotes the buyers who raised the same objection and how the deal was won, so reps answer with evidence instead of a script.

### Can reps see CRM deals through Calven?

Yes, where your workspace allows it. Calven mirrors CRM accounts, contacts and deals, and each rep sees only what their Calven role permits. Admins decide whether pipeline is readable over MCP.

### Do sales 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)