Closed-Lost Revival

The workflow

Play 11

Closed-Lost Revival

1Pull closed-lost deals

Closed-lost dealsWhy they said no

Loss reasonClose dateChampionBlocker

Accounts that became customers since, or have another open deal, are left out.

From

HubSpotSalesforce

2Wait a window set by the loss reason

Lost becauseCheck again

Timing→Next quarter

Budget→Next budget cycle

Went with a competitor→Ahead of their renewal

Missing feature→When it ships

3Check what changed, and who is still there

What changed?

New decision makerFundingTech stack changeLoss reason resolved

Find

ClayExplorium

Why now

Claude

Still there?Freshness check

Every contact from the old deal. A champion who left goes to champion tracking at the new company.

Check

LinkedIn

New

ProspeoFindymail

Verify

BounceBanon send day

4Re-score the account

Gate1

Something real changed

More changes and a resolved loss reason score highest. Nothing new means no outreach.

× No changeBack to the window

5Re-engage on what changed

“What changed since we spoke”

Old championDay 0

First touch, from the rep who ran the deal, naming the change.

DM

HeyReach

Call

Nooks

Text

WhatsAppTwilioif they texted before

New peopleDay 2

The new buying committee hears the same angle by email.

Send

Smartlead

2-day delay

Deal reopened, linked to the old one

The stackHubSpotSalesforceClayExploriumClaudeLinkedInProspeoFindymailBounceBanHeyReachNooksWhatsAppTwilioSmartleadSlack

Oriel · GTM plays library

Open full size

The diagram as text

1. 1

   Pull closed-lost deals

   Closed-lost deals (why they said no): Loss reason, Close date, Champion and Blocker. Accounts that became customers since, or have another open deal, are left out. From: HubSpot and Salesforce. Tool: HubSpot.

2. 2

   Wait a window set by the loss reason

   Lost because → Check again

   • Timing → Next quarter
   • Budget → Next budget cycle
   • Went with a competitor → Ahead of their renewal
   • Missing feature → When it ships
3. 3

   Check what changed, and who is still there

   What changed?: New decision maker, Funding, Tech stack change and Loss reason resolved. Find: Clay and Explorium. Why now: Claude.

   Still there? (freshness check): Every contact from the old deal. A champion who left goes to champion tracking at the new company. Check: LinkedIn. New: Prospeo and Findymail. Verify: BounceBan and on send day.

4. 4

   Re-score the account

   Gate 1: Something real changed. More changes and a resolved loss reason score highest. Nothing new means no outreach. Rejected: No change, Back to the window. Tools: Clay and Claude.

5. 5

   Re-engage on what changed

   “What changed since we spoke”: Tool: Claude.

   Old champion (day 0): First touch, from the rep who ran the deal, naming the change. Dm: HeyReach. Call: Nooks. Text: WhatsApp, Twilio and if they texted before. Tool: HeyReach.

   New people (day 2): The new buying committee hears the same angle by email. Send: Smartlead. Tool: Smartlead.

   Labeled connection: 2-day delay.

   Outcome: Deal reopened, linked to the old one. Tools: HubSpot, Salesforce and Slack.

Feedback loop: No change found: the deal goes back to wait for its next window.

The stack: HubSpot, Salesforce, Clay, Explorium, Claude, LinkedIn, Prospeo, Findymail, BounceBan, HeyReach, Nooks, WhatsApp, Twilio, Smartlead and Slack.

Open the diagram full size (1180 px wide)

The play in seven steps

1. 01

   Step 1: Pull closed-lost deals

   These accounts already know you, and the CRM already holds the reason they said no.

   • Export closed-lost deals from HubSpot or Salesforce with the loss reason, the close date and every contact on the deal.
   • Mark who championed the deal and who blocked it.
   • Leave out accounts that became customers since, or that have another open deal.
   • Deals with a blank loss reason go back to a rep to fill in first. The reason is the angle later.
2. 02

   Step 2: Wait a set window

   Reaching back a week after a no just reopens the same argument. Something has to have changed first.

   • Set a revival window per loss reason, not one date for everyone. Timing and budget losses come back sooner than competitor losses.
   • Lost to a competitor: line the window up with their likely renewal date.
   • Lost on a missing feature: the window opens the day it ships.
   • Each deal enters the check queue in Clay when its window opens.
3. 03

   Step 3: Check what changed

   A revival only works with a real, dated reason to come back.

   • A new decision maker in the buying function, found with Explorium and LinkedIn.
   • A funding round since the loss.
   • A tech stack change, for example dropping the tool they picked instead of you.
   • The loss reason itself resolved: the feature shipped, the budget cycle reset.
   • Claude reads the loss reason against the change and writes one line on why now.
4. 04

   Step 4: Check the contacts are still there

   Deal contacts are the oldest data in the CRM. Half the value is knowing who is left from the last conversation.

   • Run a job-change check on LinkedIn for every contact on the old deal.
   • Champion still there: they get the first touch.
   • Champion gone: send them to champion tracking at their new company and find their replacement.
   • Find verified emails for anyone new with Prospeo and Findymail, and re-verify every address, old ones included, with BounceBan on send day.
5. 05

   Step 5: Re-score the account

   Not every lost deal deserves a second run, and the score decides which ones get worked.

   • Score on how many changes stacked up and how strong each one is.
   • Weight the loss reason: a resolved reason scores highest.
   • No change found: the deal goes back to wait for its next window, not to outreach.
6. 06

   Step 6: Re-engage on what changed

   The opener is never a check-in. It names the change and ties it to why they said no.

   • Claude drafts a 'what changed since we spoke' message from the loss reason and the change.
   • The old champion gets a LinkedIn message first through HeyReach, then a call from the original rep through Nooks.
   • If the champion texted the rep during the deal, a short WhatsApp or SMS through Twilio from that rep is fair. Never text someone who only ever emailed.
   • Two days later, new people on the buying committee get an email through Smartlead with the same angle.
7. 07

   Step 7: Reopen the deal

   A revived account goes back into pipeline with its history, so nobody re-asks what was already answered.

   • On a positive reply, reopen the deal in HubSpot or Salesforce, linked to the old one.
   • Log what changed and the reply on the deal.
   • Alert the original owner in Slack.
   • Track which loss reasons revive, and tune the windows from that.

Tools used

The fifteen tools this play names. Each links to the other plays that use it.

HubSpotSalesforceClayExploriumClaudeLinkedInProspeoFindymailBounceBanHeyReachNooksWhatsAppTwilioSmartleadSlack

Related plays

Play 12

Contact Data Refresh Before Every Send

1Pull everyone about to be contacted

Contacts queued for next week's sendsLists and sequences

What can have gone stale

JobCompanyWork emailMobileLinkedIn URLTitle

2Check each field against a live source

Still at the company?Job change

Compare the current LinkedIn role with the CRM record.

Check

LinkedInApify

Email still delivers?Verify

Re-verify on send week, not on the day it was found.

Verify

BounceBanZeroBounce

Number still live?Line type

Look up carrier and line type, drop disconnected numbers.

Check

Twilio

3Decide what each record needs

FindingAction

Left the company→Find the replacement, follow the person

Email risky or invalid→Find a new email, else LinkedIn only

Title changed→Re-score, maybe a new angle

Number dead→Remove it from call lists

All still true→Send as planned

4Fill the gaps

Replacement at the account

The new person in the same seat inherits the account context.

Find

ApolloClay

Email

FindymailProspeo

The mover at the new company

A past champion who moved is often the warmest lead you have.

Track

LinkedIn

Mobile

FullEnrich

Gate1

Only verified records go out

Anything still unverified is held for the next cycle.

× Unverifiedheld, rechecked next week

Every send goes to a real person in the right seat

The stackHubSpotLinkedInApifyBounceBanZeroBounceTwilioClayApolloFindymailProspeoFullEnrichSmartlead

Oriel · GTM plays library

Play 12Outbound · ABM

Contact Data Refresh Before Every Send

4 steps · Email, LinkedIn, Call, CRM

+6 more

Play 24

CRM Hygiene

1Audit, read-only

Snapshot and fill rates0 records written

TitleLinkedInCountryEmail validityPhone validitySegment

Export first, measure every field, and trace which integration created each record.

Export

HubSpotSalesforce

2Detect the dirty sets

Dirty setFix

Duplicate person or company→Merge, survivor picked by rule

Contact not linked to its account→Link to the account

Job changer→New contact, old one marked gone

Bounced email or dead number→Replace and verify

Missing fields→Fill blanks only

Lead with no account→Match on domain

3Match duplicates carefully

Gate1

Same company domain

A name match only counts when the domain matches too.

× Different people

Gate2

Not a shared key

A switchboard number or a common firm name is never the key.

× Shared line

Gate3

Not a role inbox

A person's name stamped on info@ is a field to fix, not a merge.

× Fix the field

4Approve, back up, then write

The change set

Saved as a list view or report the owner can open.

Backup export

Every record in the change set, before anything moves.

Then

Owner approves the exact listYes unlocks the write

Write unlocked

Every change is logged with its old value, so any field can be restored.

5Fill blanks, catch job changers

Enrichment waterfall

Only the misses move on. Fill blanks, never overwrite a value someone set on purpose.

Profile

Explorium

Email

ProspeoFindymail

Verify

BounceBan

Phone

Twiliolookup, dead numbers cleared

Job changers

Current-employer scan, customers first. The same company under another domain is not a move.

Scan

ClayLinkedIn

Create

New contact, history kept

6Keep it on

Same rules, every new record

New inboundRep-added recordsJob-change signalsWeekly sweep

Report

Slack

A CRM that stays clean, with every change undoable

The stackHubSpotSalesforceClayExploriumProspeoFindymailBounceBanTwilioLinkedInSlack

Oriel · GTM plays library

Play 24Outbound · Inbound

CRM Hygiene

7 steps · CRM

+4 more

Play 22

Signals in the CRM, with Decay

1Catch signals, each with a date

Signals on your target accountsDated or dropped

Job postsFundingTech stackExec movesSite visitsPost engagement

Every signal carries a date, a one-line summary and the source URL.

Detect

ClayClaude CodeTrigify

2One CRM record per signal

Signals custom objectLinked to the company

TypeDateSummarySource URLWeight

In

HubSpotSalesforce

Rollup

Count, last signal date, priority score

3Score it, then let it fade

Priority score

Each signal adds its weight, then decays on its own curve. A new signal lifts the score again.

Config

Weight and decay rate per type, kept in a table

Each signal hasIt controls

Decay window→Ranking and queue order

Copy window, shorter→Whether copy may name it

Hard hide, about 6 months→Whether it shows at all

Intent topics→The subject chosen, never stated

4Thresholds move accounts both ways

Warm

Watched, no outreach yet.

HotNow

The owner works it today.

Cold

Decayed out on its own.

5Hot account: committee, brief, alert

Buying committee

Every buyer at the account, checked and pushed to the CRM.

Source

AI Ark

Email

ProspeoFindymail

Job change

LinkedIn

Verify

BounceBan

Brief and alert

Why it is hot, written only from copy-safe signals, plus a task for the owner.

Brief

Claude

Task

HubSpot

Alert

Slack

A target list that re-ranks itself every morning

The stackClayClaude CodeTrigifyHubSpotSalesforceAI ArkProspeoFindymailLinkedInBounceBanSlackClaude

Oriel · GTM plays library

Play 22ABM · Outbound

Signals in the CRM, with Decay

6 steps · CRM, Email, LinkedIn

+6 more

All GTM plays