# The Closed-Lost Revival Playbook: Loss Reasons to a Ranked Reopen Queue

*Turn a raw closed-lost export into a ranked reopen queue where every row has a dated reopen reason, a named current contact, a send date, and a stop rule.*

- Canonical URL: https://www.refolk.ai/guides/closed-lost-revival-playbook
- Pillar: Sales and go-to-market
- Format: Playbook
- Published: 2026-11-04
- Last reviewed: 2026-11-04
- Reading time: 23 min
- Keywords: how to re-engage closed lost deals, closed lost reactivation playbook, when to reopen a lost opportunity, closed lost loss reason re-engagement timing, revive closed lost pipeline signals, closed lost deal recovery process

## Key takeaways

- In the JOLT research across 2.5 million sales conversations, 40 to 60 percent of lost deals were lost to no decision, and 56% of those were indecision, which a new-feature trigger does not fix.
- A competitor loss against a 12-month contract with a 60-day notice window has its first useful touch about 6 months after the loss, so a 90-day check-in lands while the incumbent is still onboarding.
- At the most conservative published decay rate of 2.1% per month, an 18-month-old lost deal has a 78.3% chance that at least one of four buying-group contacts has changed.
- In Refolk's index, 39,303 people in the United States hold VP of Sales titles against 529 in the United Kingdom, a 74.3x gap that mostly reflects title convention, so single-title searches miss new budget holders.
- A profile that still shows the old employer does not prove a blocker is still there, because people update profiles weeks to months after a move and some never do.
- No published, method-transparent revival rate by loss reason exists, so tracking the share of worked closed-lost accounts that re-enter an active stage, split by constraint type, is the only reliable benchmark.

This playbook is for founders selling their own product, account executives, SDR leads, and partnerships teams. It assumes you hold a few hundred closed-lost opportunities and need to decide which have really changed, who to contact at each one now, and in what order. It turns a raw CRM export into a ranked reopen queue where every row has a reopen reason, a named current contact, a send date, and a stop rule. It never produces a "just checking in" email.

## What makes a closed-lost deal worth reopening?

A closed-lost deal is worth reopening only when two things are true: the specific constraint that killed it has expired, and you can name the person at the account who should hear about it today. A funding round or a website revisit is a reason to look at the account. It is not a reason to send.

In this playbook, closed-lost means a qualified opportunity that went through a real evaluation and did not end in a purchase. Deals that were never qualified are not lost deals. They are noise in the export, and step 2 of the procedure removes them.

Most advice about loss reasons comes back to one primary source: Dixon and McKenna's JOLT research, published as The JOLT Effect, which analysed 2.5 million recorded sales conversations. Four of its findings shape the queue:

- **No decision is the biggest bucket.** Depending on the organisation, 40 to 60 percent of lost deals were lost to "no decision".
- **No decision splits in two.** 44% of no-decision losses were status quo, meaning the buyer judged that doing nothing was cheaper. 56% were indecision, meaning the buyer wanted to act but was afraid of getting it wrong.
- **Indecision is everywhere.** Medium to high levels of indecision showed up in 87% of all deals, won or lost.
- **Competitor losses are unmeasured.** Nobody has published a clean share of deals lost to a named competitor. It is whatever is left over, mixed in with price and disqualification.

In practice, this means one closed-lost list is really two queues. A competitor loss waits on the incumbent's contract dates, so it gets a calendar date. A no-decision loss waits on a change inside the account, so it gets a trigger and no date. A single fixed cadence runs on the wrong clock for both.

#### From closed-lost export to reopen queue

1. **Reconstruct** - One row per lost deal with last stage, amount, contacts, and last activities
2. **Re-code** - Each loss becomes a constraint that can expire
3. **Date and prove** - Earliest-valid date plus dated public evidence of expiry
4. **Re-map** - Champion, blocker, and budget seat checked against today
5. **Clear and rank** - Suppression and collision checks, then reason, contact, date, stop rule

*A lost deal reaches the queue only after its loss is re-coded, dated, proven expired, and matched to a current contact.*

## How do I reconstruct a closed-lost export I can trust?

For every deal closed-lost in the last 24 months, pull the opportunity record, its stage history, and its contact roles, then flatten them into one row per deal. You need to know how far each deal really got and who was really in it, and the loss-reason field alone will tell you neither.

In Salesforce, each object answers one question and has one way of misleading you:

| Object | What it gives you | Where it misleads |
|---|---|---|
| Opportunity | Amount, close date, LastStageChangeDate | Loss reason is not a standard field |
| OpportunityHistory | A record per change to Amount, Probability, Stage, or Close Date | Returns nothing if none of those changed |
| OpportunityFieldHistory | Changes to tracked fields | Silent for fields nobody switched on |
| OpportunityContactRole | Contacts with Role and IsPrimary | Can return deleted contacts |

Three details matter more than they look:

- **Stage history can be empty.** OpportunityHistory is read-only. It writes a record only when Amount, Probability, Stage, or Close Date changes. A deal that jumped straight to Closed Lost leaves almost nothing behind. LastStageChangeDate and LastStageChangeInDays on the Opportunity at least tell you when the last move happened.
- **One primary contact is not a buying group.** An opportunity can have at most one Primary Contact Role. Many teams add a validation rule that stops a deal from moving past Discovery without one. That rule guarantees one named contact. It does not mean anyone mapped the buying group.
- **Your loss-reason field may not mean what you think.** I have not seen a standard loss-reason field established. Check how yours was built, when it was added, and whether it was ever required.

To recover the real buying group, compare the meeting attendees in the activity log with the contact roles. Keep each deal's last two activities in its row. You will read them in step 3, when the loss code says "timing".

The work is done when you have one row per opportunity with the last stage reached, close date, amount, every contact who had a role or attended a meeting, and the last two activities. I budget about a day of RevOps time for this. That is my estimate, not a documented benchmark. If you are not on Salesforce, the same four questions apply: what stage, what amount, who attended, and what happened last.

Next, remove the disqualified deals: anything that never reached a real evaluation. Store them separately. They may be prospects, but they are not revivals.

## How do I re-code a loss reason into a constraint that can expire?

Replace each loss reason with one constraint type that can expire, and write down the dated public evidence that would prove it has. If you cannot name the evidence, the row is not ready for the queue.

| Constraint type | Proof it has expired | Clock |
|---|---|---|
| Competitor contract | Incumbent term nearing its notice window | Calendar |
| Budget cycle | Dated funding or earnings release | Trigger |
| Feature gap | Your dated changelog entry closing the gap | Trigger |
| Blocker person | Dated evidence the blocker left | Trigger |
| Status quo | Dated event that raised the cost of doing nothing | Trigger |
| Indecision | A risk reducer you can now offer | Trigger |

Be suspicious of "timing" and "budget". Reps often put competitor losses they would rather not report under those codes. A competitor loss coded as timing gets a trigger instead of a renewal date, so it either never fires or fires in the middle of the contract. Before you accept either code, read the last two activities and the notes from the last stage the deal reached.

The two no-decision codes need different treatment:

- **Status quo** buyers (44% of no-decision losses in the JOLT data) need evidence that doing nothing now costs more. Examples are a new mandate, a missed target, or growth that breaks their current process.
- **Indecision** buyers (56%) already wanted to move and stopped because they were afraid of making a mistake. News that something has changed does nothing for them. Their reopen reason has to reduce risk: a reference customer that looks like them, or a smaller first scope.

> A buyer who stalled out of fear does not come back because you shipped a feature.

On timing: one practitioner summary suggests spending the first two weeks classifying twelve months of closed-lost deals into competitive, disqualified, and no-decision buckets before any outreach. This playbook uses finer codes and covers 24 months, so plan for at least that much time and scale it by deal count, not by the calendar.

**Loss re-coding rubric (one row per opportunity)**

```
opp_id:
last_stage_reached:        from stage history, not the final stage
original_loss_code:
evidence_read:             last two activities + last-stage notes (Y/N)
constraint_type:           COMPETITOR_CONTRACT | BUDGET_CYCLE | FEATURE_GAP | BLOCKER_PERSON | STATUS_QUO | INDECISION
expiry_evidence_needed:    the one dated public item that would prove it expired
clock:                     CALENDAR (competitor only) | TRIGGER
incumbent_term:            CONFIRMED (n months) | ASSUMED 12, ask in first message
earliest_valid_date:       computed date, or blank until evidence appears
expiry_evidence_found:     link + date, or blank
```

*Use these as column headers in your working sheet; drop constraint types you never sell against.*

## When to reopen a lost opportunity: dating each constraint

Only competitor losses get a calendar date: the close date, plus the incumbent's contract term, minus the notice window, minus your evaluation lead time. Every other constraint is trigger-only. Its earliest-valid date is the date of the evidence that proves it expired.

Here is what is known about the competitor clock:

- Non-renewal notice windows are usually drafted at 30, 60, or 90 days. In standardised SaaS agreements, 30 days is the most common.
- One source reports that 69% of software contracts auto-renew and have a cancellation notice period of 30 to 90 days.
- The usual term is one year.
- Buyer-side guidance says to start reviewing 90 to 120 days before renewal. One contract glossary recommends reminders at 120, 90, and 60 days before the non-renewal deadline.
- No one has published a breakdown of notice windows by software category. One vendor-specific table circulates, but its method is undisclosed, so do not treat it as a norm.

Combining those, and assuming a 12-month incumbent term:

| Notice window | First touch, days before renewal | Months after loss |
|---|---|---|
| 30 days | 150 | ~7 |
| 60 days | 180 | ~6 |
| 90 days | 210 | ~5 |

The first-touch figure is the notice window plus the 120-day reminder. Read the last column as the earliest point your message is useful, not as a deadline. The buyer has to decide before the notice window closes and starts thinking about it about 120 days before that. If you touch a competitor loss 90 days after losing it, the incumbent is still onboarding, and nobody in that seat is ready to admit a mistake.

Sources disagree on the clock for everything else. One agency recommends re-working every deal 90, 180, and 365 days after the loss. A vendor recommends acting on signals, such as a lost account revisiting your site. My position: use the calendar only for competitor rows and compute it for each deal. Use triggers for everything else, but only triggers that match the row's constraint. A website revisit shows interest. It does not prove that a budget cycle turned or that a blocker left.

These are the earliest-valid dates for trigger-only rows:

- **Budget cycle:** the date of a funding announcement or earnings release.
- **Feature gap:** the date of your own changelog entry that closes the gap.
- **Blocker person:** the date of the evidence that the blocker left.
- **Status quo:** the date of the event that raised the cost of doing nothing.
- **Indecision:** the date you have a matching reference or a smaller scope ready to offer.

> **Tip:** Flag every assumed contract term
>
> A 12-month assumption makes the reopen fire mid-term on a multi-year deal. Mark the term as assumed, check for a dated case study the competitor published about the account, and ask about the term directly in the first message.

## Re-mapping the buying group: who left, who stayed, who arrived

Assume every buying group on an old lost deal has changed until you prove it hasn't. On an 18-month-old deal, even the most conservative published decay rate gives a 78.3% chance that at least one of four contacts has moved or changed role.

| Annual rate assumption | Per-contact stale at 18 months | At least 1 of 4 changed |
|---|---|---|
| 2.1%/month (HubSpot) | 31.7% | 78.3% |
| 29.6%/yr change company | 40.9% | 87.8% |
| 70.8%/yr any field change | 84.2% | 99.9% |

The rates come from two sources. HubSpot's Database Decay Simulation, built on MarketingSherpa research, uses 2.1% a month, which compounds to 22.5% a year. A survey published on b2bmarketing.com found that 29.6% of people changed companies in a year and that 70.8% of records had at least one field change. Title or job-function changes made up 65.8% of those changes, so a contact who stays at the account may still have left the buying group. Every value in the table comes from compounding over 18 months, and it assumes contacts change independently of each other. A reorganisation moves several people at once, so use the table as an order of magnitude, not a forecast. You will also see a figure of about 70% annual decay attributed to Gartner. I could not trace it to a Gartner primary source, so leave it out of your planning.

Senior seats change hands more slowly than average. The BLS tenure release puts median tenure at 4.1 years overall and 6.1 years for management occupations. BLS publishes the series every two years, so check the current value there. My inference is that the 2.1% row is the better guide for VP-level buyers, and the 29.6% row for practitioner-level champions.

Each row needs answers to three questions.

### Is the blocker still there?

You can confirm the blocker has gone only with positive, dated evidence. A stale profile does not count. Each of these counts:

- A new role at another company, with a date.
- Removal from the company's leadership page.
- A company announcement of the change.
- For US public-company officers, an SEC Form 8-K Item 5.02 filing. Search the SEC's own filings rather than relying on summaries.

To show the blocker is still there, you need dated activity from the last 90 days at the same company.

> **Watch out:** An unchanged profile proves nothing
>
> Career guidance says most people wait one to four weeks after starting a job to update their profile, others say up to two months, and some never update. A profile that still shows the old employer is not proof that the blocker is still in the seat.

### Where did the champion go?

When a champion leaves, you learn two things: there is a gap at the lost account, and you have a warm contact at a new company. Log the new company as a separate prospect row. Keep it out of this queue, and don't let it inherit the old deal's loss reason. At the lost account, the champion's replacement becomes the contact to identify.

### Who holds the budget seat now?

Search for the seat by function and seniority, not by one exact title. Title conventions vary so much between countries that a single-title search will miss many of the people who now hold the budget.

| Segment | Count | Ratio |
|---|---|---|
| VP Sales, US | 39,303 | 1.0x |
| VP Sales, UK | 529 | US is 74.3x UK |
| Director/Sales Director, US | 77,740 | 1.98x US VP |

**74.3x - More people titled VP of Sales in the US than in the UK, in Refolk's index**

The gap mostly reflects title convention, since the UK more often uses Sales Director for the same seat, and a UK Director count was not queried.

Counts come from Refolk's index of professional profiles, and the ratios are derived. Even inside the US, Sales Directors outnumber VPs of Sales almost two to one, so the title that holds budget varies by company as well as by country. That is the search [Refolk](/) is built for: describe the seat in plain English by function, seniority, market, company size, and how recently the person started, instead of guessing every title variant. The same approach finds people who left a role and shows where they work now, which covers both the blocker check and the champion trail.

I ran this search: `VPs of Sales or Sales Directors who started a new role in the last 6 months at UK SaaS companies with 200 to 1,000 employees` - [see the full result list](https://www.refolk.ai/s/py3j4vq4ky).

*Returns named people who recently filled a UK sales leadership seat, with their current company and role, ready to match against your lost UK accounts.*

The work is done when each row has a named current contact or is marked unresolvable. Unresolvable is a valid outcome. Sending to a guessed contact is not.

## The closed-lost revival procedure, step by step

Run these nine steps in order. Each one has a defined finished state, and a row that fails any step leaves the queue rather than being patched by guesswork.

#### Closed-lost export to ranked reopen queue

1. **Export and reconstruct the lost deals** - Pull Opportunity, OpportunityHistory or OpportunityFieldHistory, and OpportunityContactRole for every opportunity closed-lost in the last 24 months. Done when there is one row per opportunity with last stage reached, close date, amount, contacts with roles, and the last two activities.
2. **Remove deals that were never qualified** - Separate opportunities that never had a meaningful evaluation from genuine losses. Done when the disqualified rows are out of the queue and stored separately.
3. **Re-code each loss to an expiring constraint** - Assign each row one constraint type: competitor contract, budget cycle, feature gap, blocker person, status quo, or indecision. Done when every row has a constraint type and names the dated evidence that would prove it expired.
4. **Date the constraint** - For competitor losses, compute close date plus contract term, minus the notice window, minus evaluation lead time. Every other row is trigger-only. Done when each row has an earliest-valid date or a trigger-only flag.
5. **Collect dated public evidence of expiry** - Find the dated item that shows each constraint has expired, such as a changelog entry, a funding or earnings release, or a leadership change. Done when the evidence and its date sit in the row, or the row is parked.
6. **Re-map the buying group** - Check whether the champion and the blocker are still at the account and who now holds the budget seat, searching by function and seniority rather than one title. Done when the row has a named current contact or is marked unresolvable.
7. **Run collision and suppression checks** - Remove opt-outs, accounts with an open opportunity or active partner engagement, and unresolvable contacts. Done when every surviving row has cleared all three checks.
8. **Rank, schedule, and set stop rules** - Order rows by strength of evidence and certainty of contact, then give each a reopen reason, a named contact, a send date, and a stop rule. Done when no row is missing any of the four.
9. **Measure revival rate by loss-reason segment** - Track the percentage of worked closed-lost accounts that re-enter an active sales stage, split by constraint type. Done when the first segment report exists and is compared against your net-new win rates.

How long each step takes:

- **Step 1:** about a day of RevOps time (my estimate).
- **Steps 2 and 3:** the practitioner guidance is two weeks for twelve months of deals. Scale it to your volume.
- **Step 4:** quick once step 3 is clean, because it is arithmetic on the competitor rows only.
- **Steps 5 and 6:** no one has published a per-account time. Time your first twenty rows and use that figure to plan the rest.
- **Steps 7 to 9:** mechanical once the earlier steps are done, but do not skip step 7 to save an afternoon.

## How closed-lost revival goes wrong

Most failed revivals come from trusting a record that has gone stale: a loss code, a contact role, a profile, or a contract assumption. Each failure mode below shows what the mistake looks like and the check that catches it.

1. **"Timing" or "budget" used as a catch-all code.**
   Looks like: a competitor loss gets a trigger instead of a renewal date and never fires, or fires mid-contract.
   Check: read the last two activities and the notes from the last stage before you accept the code.
2. **Empty stage history.**
   Looks like: the stage jumped straight to Closed Lost, so the history shows nothing about how far the deal got, and a late-stage loss gets treated as an early one.
   Check: confirm that field history tracking was switched on before the close date. If it wasn't, rebuild the stage from the activity log.
3. **Phantom contact roles.**
   Looks like: OpportunityContactRole returns contacts that have been deleted, or the deal lists only its one primary contact.
   Check: query the Contact table and compare meeting attendees in the activity log with the contact roles.
4. **"Blocker still there" false positive.**
   Looks like: the profile shows the old employer, but the person left weeks or years ago, so you park a row that is actually open.
   Check: look for dated activity from the last 90 days or confirm on the company's leadership page.
5. **New-seat false negative.**
   Looks like: a search for one title comes back empty, so the row is marked unresolvable while someone with a different title holds the budget.
   Check: search by function and seniority. Table A shows how much titles for the same seat vary between countries.
6. **Multi-year incumbent contract.**
   Looks like: the 12-month assumption fires the reopen halfway through a three-year term.
   Check: look for a dated case study the competitor published about the account, and ask about the term in the first message.
7. **Collision.**
   Looks like: another rep has an open opportunity at the account, or a partner is already working it, and the buyer gets two uncoordinated messages from one vendor.
   Check: before setting any send date, dedupe by account against open opportunities and partner engagements.
8. **Vendor benchmarks treated as norms.**
   Looks like: you judge the program against an agency's "1 to 4% closed-won" and kill it, or celebrate it, for the wrong reason.
   Check: that figure is one agency's self-report with no stated sample. Track your own revival rate by loss-reason segment.

The two that cost the most are 1 and 4. Both make a row look settled when it isn't, so the error never shows up in later steps.

## How do I rank the queue and set stop rules?

Rank by two things: how strong the dated evidence of expiry is, and how certain you are that the contact is current. Every row that ships carries four fields, and a row missing any one of them does not ship.

#### Which lost deals to work first

Horizontal axis runs from No dated proof of expiry to Dated proof of expiry. Vertical axis runs from No current contact to Named current contact.

| Quadrant | What it means |
| --- | --- |
| Watching | Hold and monitor for the matching trigger; send nothing |
| Reopen now | Queue first and send on the earliest-valid date |
| Parked | Archive and re-check at the next queue refresh |
| Window open, nobody to tell | Re-map the buying group before the window closes |

*Rows with both dated proof of expiry and a named current contact go first; proof without a contact means re-map before anything else.*

Within the "Reopen now" quadrant, I order rows like this:

1. Competitor rows whose computed first-touch date is today or within the next few weeks. The window closes on a fixed date.
2. Feature-gap rows where your changelog closes the exact gap named in the loss.
3. Blocker-gone rows backed by positive evidence of the departure.
4. Budget-cycle and status-quo rows with a dated external event.
5. Indecision rows where you now have a matching reference or a smaller first scope.

One agency reports that competitor-renewal and feature-gap segments usually outperform pure timing, but it publishes no figures. My order follows the same logic: rows whose evidence is hardest to argue with go first.

> **Rule:** Four fields or it does not ship
>
> Every row needs a reopen reason backed by dated evidence, a named current contact, a send date on or after its earliest-valid date, and a stop rule written before the first send.

Write stop rules before the first send, not after a silence. Each row should have:

- **Opt-out:** stop immediately and suppress the person and the account address everywhere you send from.
- **Collision found later:** stop and hand the row, with its evidence, to the owner of the open opportunity.
- **Contact unresolvable or bounced:** stop and park the row. Do not guess a replacement.
- **No reply:** I default to two touches per evidence event. Then the row goes back to Watching until a new, dated piece of evidence appears.
- **Reply says "not now" with a date:** stop and set that date as the new earliest-valid date.

**First reopen message**

```
Subject: {the specific gap} at {company}

Hi {first name},

{Previous contact or "your team"} and I looked at {problem} together about {n} months ago, and you went with {incumbent or "staying as you were"}.

I'm writing now for one reason: {dated evidence, for example "on {date} we shipped {feature}, which was the gap that decided it last time"}.

If your {incumbent} agreement is on an annual term, the renewal decision usually has to be made 30 to 90 days before it renews. Is yours annual, or did you sign for longer? If it's longer, I'll hold off until it matters.

{signature}
```

*Replace the evidence line with this row's own dated item; for indecision rows, replace it with the reference customer or the smaller first scope.*

## How do I measure revival and keep the queue current?

Measure revival rate: the percentage of worked closed-lost accounts that re-enter an active sales stage, tracked separately for each loss-reason segment. No published, method-transparent revival rate by loss reason exists, so your own segmented numbers are the only benchmark you can trust.

What the public figures do and don't tell you:

- One agency reports 5 to 12% reply and 1 to 4% conversion to closed-won from its own campaigns, with no stated sample.
- A claim that a quarter of dead leads revive within 12 months is cited second-hand and could not be verified.
- One vendor says outright that the numbers vary and that teams should measure their own.

To judge whether revived deals are worth the effort, compare their win rate with your net-new win rates by source. ICONIQ's State of GTM report gives one reference point:

| Opportunity source | Win rate |
|---|---|
| Customer-success-sourced | 52% |
| Sales-sourced | 43% |
| Channel and partner | 39% |
| Marketing-sourced | 27% |

If revived deals win below your marketing-sourced rate, the queue is costing more than it returns. Tighten the evidence bar before you add more rows. If they win near or above your sales-sourced rate, widen the export window.

To keep the queue current:

- Tag every send with its constraint type from day one, so the segment report builds itself.
- Recompute competitor dates whenever a buyer confirms or corrects the contract term.
- Refresh trigger-only rows on a fixed schedule, checking for new dated evidence and new seat holders. Over 18 months, most buying groups change.
- Add newly lost deals to the queue at close, while the last two activities are still fresh. Code them properly then, and you won't have to reconstruct them later.

#### Before the first send

- [ ] Every disqualified deal is out of the queue and stored separately.
- [ ] Every row has exactly one constraint type, and no row is coded timing or budget without its last two activities read.
- [ ] Every competitor row has an incumbent term marked confirmed or assumed.
- [ ] Every send date is on or after the row's earliest-valid date.
- [ ] Every reopen reason cites a dated public item, with its date recorded in the row.
- [ ] Every contact is confirmed current by positive, dated evidence, not by an unchanged profile.
- [ ] No account in the queue has an open opportunity or an active partner engagement.
- [ ] No contact or account appears on the opt-out list.
- [ ] Every row has a written stop rule.
- [ ] Every send is tagged with its constraint type for revival-rate reporting.

## Frequently asked questions

### How long should I wait before re-engaging a closed-lost deal?

It depends on why you lost. A competitor loss waits on the incumbent's contract: assuming a 12-month term, the first useful touch falls about 5 to 7 months after the loss, depending on whether the notice window is 90, 60, or 30 days. No-decision, budget, feature-gap, and blocker losses get no waiting period. They reopen when dated evidence shows the constraint has expired, whether that is two weeks or two years after the loss.

### Should I re-engage closed-lost deals at 90, 180, and 365 days?

Not as a blanket cadence. One agency recommends those fixed intervals, but they fire too early for competitor losses, where day 90 lands while the incumbent is still onboarding, and they ignore no-decision losses, which change only when something inside the account changes. Use a computed calendar date for competitor rows and evidence-based triggers for everything else.

### What reply and win rates should I expect from closed-lost outreach?

There is no reliable public benchmark. The figures in circulation, such as 5 to 12% reply and 1 to 4% closed-won, are one agency's self-report with no stated sample. One agency says competitor-renewal and feature-gap segments outperform timing segments but gives no numbers. Measure your own revival rate by loss-reason segment and compare it against your net-new win rates by source.

### What do I do when the CRM loss reason just says timing or budget?

Don't trust it until you have read the last two activities and the notes from the last stage the deal reached. Reps often use timing and budget for competitor losses they would rather not report. If a competitor shows up anywhere in those notes, recode the row as a competitor-contract loss and give it a renewal-based date instead of a trigger.

### How do I confirm the person who blocked the deal has actually left?

Look for positive, dated evidence: a new role at another company, removal from the company's leadership page, a company announcement, or for US public-company officers, an SEC Form 8-K Item 5.02 filing. A profile that still shows the old employer proves nothing, because people often update weeks to months after moving and some never update at all.

### Can I reopen a lost deal if another rep is already working the account?

No, not on your own. Before setting any send date, dedupe your queue by account against open opportunities and active partner engagements. If there is a collision, the row stops and goes to the current owner, along with your reopen reason and evidence. Two people from one vendor writing to the same account undermines both of them.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/closed-lost-revival-playbook*
