DocsUse CasesSales & Deals

Sales & Deals

Use Cases by Department · Beginner Friendly

Win More Deals with AI-Powered Proposals

Run in Prompt Architect
salesproposal

The Problem: Sales teams spend 30+ hours per RFP response, often losing deals because of slow turnarounds.

1

RFP Ingestion

Upload the RFP document — AI extracts every requirement into a structured checklist.

2

Vault Matching

AI maps RFP requirements to your proven capabilities stored in the Vault.

3

Analyzer Prompt

AI maps RFP requirements to specific Vault capabilities to find the 'Win Theme'.

Best Practices

Start win more deals with ai-powered proposals with a small live pilot and one owner per review lane.

Track rerun rate per opportunity and reply rate from day one.

Bake this control into your checklist: claims and numbers are source-backed

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: competitive claims without proof source.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Win More Deals with AI-Powered Proposals Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Track where reps overwrite generated messaging and turn that into new constraints.

Personalized Outreach at Scale

Run in Prompt Architect
salesemail

The Problem: Generic outreach gets <2% response rates. Personalization at scale is impossible manually.

1

Prospect Research

AI analyzes the prospect's LinkedIn profile, company news, and 10-K filings.

2

Sequence Gen

Generate 5-step personalized sequences that reference the prospect's actual LinkedIn news.

Best Practices

Start personalized outreach at scale with a small live pilot and one owner per review lane.

Track rerun rate per opportunity and reply rate from day one.

Bake this control into your checklist: claims and numbers are source-backed

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: outreach that sounds polished but could apply to any account.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Personalized Outreach at Scale Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Track where reps overwrite generated messaging and turn that into new constraints.

Build Instant Competitive Battle Cards

Run in Prompt Architect
salescompetitive

The Problem: Competitive intelligence is outdated within weeks and reps don't use static PDFs.

1

Competitor Scan

AI monitors competitor websites, G2 reviews, and job postings for feature signals.

2

Battle Card Gen

AI generates objection handlers and 'Killer Questions' to ask the prospect.

Best Practices

Start build instant competitive battle cards with a small live pilot and one owner per review lane.

Track reply rate and proposal turnaround from day one.

Bake this control into your checklist: account context appears in first paragraph

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: outreach that sounds polished but could apply to any account.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Build Instant Competitive Battle Cards Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

AI-Powered Deal Scoring

Run in Prompt Architect
salesforecast

The Problem: Sales forecasts are based on gut feeling, leading to 30-40% inaccuracy.

1

CRM Data Pull

AI ingests deal data: stage, age, engagement metrics, and stakeholder mapping.

2

Scoring Model

AI identifies 'stagnant' deals and scores closing probability based on objective MEDDIC criteria.

Best Practices

Start ai-powered deal scoring with a small live pilot and one owner per review lane.

Track stage conversion and rerun rate per opportunity from day one.

Bake this control into your checklist: next-step CTA is explicit and dated

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: handoff to post-sales without decision context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: AI-Powered Deal Scoring Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

Train with Real-World Rebuttals

Run in Prompt Architect
salestraining

The Problem: Reps freeze on tough objections and miss quota because they can't handle 'We're going with CompetitorX'.

1

Objection Catalog

Build a library of every objection from win/loss reviews.

2

Simulate & Grade

AI role-plays as the prospect; rep practices live. AI evaluates the response quality.

3

Grading Loop

AI scores the rebuttal on: Technical Accuracy, Tone, and Empathy.

Best Practices

Start train with real-world rebuttals with a small live pilot and one owner per review lane.

Track reply rate and rerun rate per opportunity from day one.

Bake this control into your checklist: next-step CTA is explicit and dated

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: outreach that sounds polished but could apply to any account.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Train with Real-World Rebuttals Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

Empower Resellers with Instant Specs

Run in Prompt Architect
salespartner

The Problem: Channel partners can't answer technical questions on the spot, losing deals at the last mile.

1

Knowledge Base Build

Upload product specs, pricing matrices, and competitive positioning into the Vault.

2

Q&A Assistant

Provide partners with a 24/7 technical bot for answering customer edge cases.

Best Practices

Start empower resellers with instant specs with a small live pilot and one owner per review lane.

Track rerun rate per opportunity and reply rate from day one.

Bake this control into your checklist: next-step CTA is explicit and dated

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: outreach that sounds polished but could apply to any account.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Empower Resellers with Instant Specs Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Track where reps overwrite generated messaging and turn that into new constraints.

Equitable Patch Alignment

Run in Prompt Architect
salesops

Problem: Unbalanced territories cause top reps to leave and underperforming territories to be neglected.

1

Data Collection

Ingest CRM data: accounts, ARR, whitespace opportunity, and win rates by region.

2

Patch Balancing

Suggest boundary shifts that ensure every rep has a 'Fair Share' of high-intent accounts.

Best Practices

Start equitable patch alignment with a small live pilot and one owner per review lane.

Track proposal turnaround and reply rate from day one.

Bake this control into your checklist: account context appears in first paragraph

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: handoff to post-sales without decision context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Equitable Patch Alignment Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

Deep Research for Whale Accounts

Run in Prompt Architect
salesabs

Problem: Enterprise deals require deep account research that takes days per prospect.

1

10-K Analysis

AI ingests the target company's 10-K filing and extracts strategic priorities.

2

Exec-Level Pitch

Generate a '1-Pager' that translates your product into a direct solution for those 10-K goals.

Best Practices

Start deep research for whale accounts with a small live pilot and one owner per review lane.

Track proposal turnaround and stage conversion from day one.

Bake this control into your checklist: claims and numbers are source-backed

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: handoff to post-sales without decision context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Deep Research for Whale Accounts Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

Scale Referrals with AI Matchmaking

Run in Prompt Architect
salesreferral

Problem: Referrals convert at 3-5x the rate of cold outreach, but most companies get them accidentally.

1

NPS Analysis

AI identifies your top promoters from NPS and CSAT scores.

2

Network Match

Cross-reference promoters' LinkedIn connections against your ICP to find warm intros.

3

Intro Drafting

Generate a pre-written intro email for the customer to send to their peers in seconds.

Best Practices

Start scale referrals with ai matchmaking with a small live pilot and one owner per review lane.

Track reply rate and rerun rate per opportunity from day one.

Bake this control into your checklist: claims and numbers are source-backed

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: competitive claims without proof source.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Scale Referrals with AI Matchmaking Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Add a ‘why now’ line tied to an account event in every first-touch output.

Structure Complex Multi-Product Deals

Run in Prompt Architect
salesfinance

Problem: Complex enterprise deals with multiple products, ramp schedules, and discount tiers are error-prone.

1

Deal Config

Input products, quantities, ramp schedule, and discount requests.

2

Margin Analysis

AI calculates blended margin and flags deals below the floor.

3

Incentive Gen

Suggest 'Non-Cash' concessions (e.g. Free Training) to preserve the deal ARR.

Best Practices

Start structure complex multi-product deals with a small live pilot and one owner per review lane.

Track rerun rate per opportunity and stage conversion from day one.

Bake this control into your checklist: next-step CTA is explicit and dated

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: handoff to post-sales without decision context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Structure Complex Multi-Product Deals Owner: Revenue Operations Manager Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Track where reps overwrite generated messaging and turn that into new constraints.

Academy v4.0 · Interactive Documentation · Beginner Mode