RevOps playbook · AI Employee: Rev

Closed-Lost Cascade

Loss data captured 100%; nurture pipeline seeded

Install this playbookBack to marketplace
The problem

Closed-lost deals leave no trace. AE marks the opp lost with a two-word reason ("lost — competitor"), the prospect goes off the radar, and everyone moves on. Six months later, marketing runs the same campaign against the same account and calls them a fresh lead. The competitor won on price and the customer isn't happy, but nobody knows to re-approach at renewal. Post-mortem intelligence — why we lose, what changed the deal, what would have kept them — evaporates.

At a glance
Trigger
CRM event
Approvals
None
What it does
Writes to your systems
Systems
Salesforce · HubSpot · Marketing automation
How it feels in production

An hour-by-hour walkthrough.

AE marks DEAL-4842 Closed Lost with reason "Competitor — Notion." Rev picks up the closed-lost event and starts the cascade: First, Rev conducts a light-touch loss review. It reads the deal history (call transcripts, emails, timeline of stage progression, discount attempts, competitive mentions), and drafts a structured loss summary: - Primary reason: Competitor chosen (Notion) - Secondary factors: Prospect's champion left mid-deal (LinkedIn signal), 3-month decision delay after RFP, price mentioned as "tight" but not the deciding factor - Competitive intelligence: Notion mentioned in 4 of 7 calls; specific features cited: real-time collaboration, template library - Missed signals: our security packet arrived 2 weeks after prospect asked; prospect's timeline slipped 2 months - Recovery window: contract with Notion likely 1-year; re-engagement recommended in month 9 The summary lands in the AE's inbox for confirmation + edits. AE agrees, adjusts one thing. Rev writes back to the opportunity with the full loss record. Then the cascade fires: - Marketing: contact moved to "lost to competitor" segment, opted out of active demand campaigns for 6 months, enrolled in competitive-content nurture - Product: feature gaps mentioned in the loss (real-time collaboration) tagged to product feedback with the deal value - Competitive intelligence: loss added to the Notion battle card - CRM: re-engagement task scheduled for month 9, pointing to AE + CSM - Team learning: pattern-matching against recent losses surfaces trends for pipeline review The deal is lost but the intelligence isn't.
How it works

Step by step.

  1. 01

    Detect close + trigger loss review

    Closed-lost stage transition → Rev picks up. Detects the reason category (competitor, no-decision, budget, timing) and drives the review depth accordingly.

    Salesforce · HubSpot · CRM
  2. 02

    Assemble loss summary from deal history

    Reads all interactions: emails, call transcripts, cadence responses, competitive mentions, stage-progression timeline, discount history. Structured loss summary drafted with cited evidence.

    Gong · Chorus · Outreach · Email · CRM history
  3. 03

    AE review + edit

    AE receives draft; confirms or edits. Reason categorisation is standardised; qualitative context is AE's authorial space. Loss review completes in 10-15 minutes vs. 45 minutes from scratch.

    Slack · Teams · CRM notes
  4. 04

    Fire the cascade to downstream teams

    Marketing (contact segmentation + nurture), product (feature-request tagging with deal value), competitive intel (battle card update), CRM (re-engagement task).

    Marketing platform · Product feedback · Competitive intel · CRM tasks
  5. 05

    Pattern-matching for team learning

    Loss summaries aggregated for pattern detection. Recurring loss reasons, feature gaps, competitor wins by segment. Weekly digest to sales leader + product + competitive marketing.

    Analytics · Slack digest · Loss-pattern dashboard
Systems and wiring

What you connect to make this run.

Salesforce · HubSpot

read+write

Closed-lost event as trigger. Write structured loss summary, competitive intel, re-engagement task. Read full deal history for the review.

Gong · Chorus · Outreach

read

Call transcripts + email history for evidence gathering. Competitor mentions extracted with speaker attribution + timestamp. Feature-request quotes captured verbatim.

Marketing platform (HubSpot · Marketo · Iterable)

read+write

Contact segmentation update. Move to lost-to-competitor list, opt out of active demand, enrol in competitive-content nurture. Prevents cold re-approach that looks unaware.

Product feedback (Productboard · Aha! · Jira Product Discovery)

write

Feature requests from the loss tagged with deal value + competitor context. Product roadmap decisions informed by aggregate deal-value gap, not one-off asks.

What changes

Before and after, honestly.

Closed-lost deals with structured loss summary
Before
20-40%
After
95%+
Re-engagement of lost deals at strategic windows
Before
5-15%
After
40-60%
Win-back rate on re-engaged lost deals
Before
3-8%
After
12-22%
AE hours per lost-deal wrap-up
Before
30-60 minutes (skipped often)
After
10-15 minutes (review + confirm)
Related

Playbooks that pair with this one.

RevOps

Closed-Won Cascade

Mirror cascade — same mechanism for won deals; different downstream actions.

RevOps

Deal-at-Risk Detection

Loss patterns feed the at-risk model as leading indicators for active deals.

RevOps

Call Recording Lookup

Loss reasons queryable across deals via the same corpus and reasoning path.

Frequently asked

Answers about this playbook.

What if the AE's stated loss reason doesn't match what the recordings show?

Rev surfaces the discrepancy ("AE said 'no decision' but calls mention Notion in 4 of 7 conversations"). AE reviews and updates; loss reasoning becomes more honest over time, and pattern data becomes more actionable.

How does it handle deals that were never a good fit?

"Not-ICP" is a valid loss category. Feeds SDR + marketing targeting: consistent losses of a specific persona/industry indicate a targeting problem, not a sales problem.

What about re-engagement — how do we know when to re-approach?

Signals: competitor contract likely ending, champion changed role or company, product update fills the identified feature gap, prospect's company had a growth event. Rev watches for these and prompts the AE.

Can we exclude specific reasons from the cascade?

Yes — some losses (e.g., prospect went out of business) skip re-engagement scheduling. Config per reason. Sensible defaults; overrideable.

How does this coordinate with our marketing team?

Marketing sees the lost-deal segmentation live. Campaigns exclude these contacts for the opt-out window, then re-enrol at re-engagement date. Marketing decides campaign content; the timing is coordinated with sales.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks