agentleFS
NEON-RutgerNEON-Rutger/B2B-revops-skills/closed-lost-revival/SKILL.md

closed-lost-revival

Skill58 starsChanged 38 days agoMITView on GitHub

Run a quarterly revival sweep over pipeline you already paid for: closed-lost deals, proposals that went quiet, champions who changed jobs, and engaged contacts who went silent. Triggers on 'closed-lost', 'win-back', 'revive dead deals', 'they ghosted us', 'gone quiet', 'lost the deal, what now', 'reactivation campaign', 're-engage old pipeline', 'proposal never answered', 'dormant accounts', or a team buying new leads while once-interested accounts sit untouched. Gates hard: it revives accounts that engaged and then went quiet, never cold contacts that ignored you from day one. BOUNDARY: turning wins into lookalikes is a separate play; job-change monitoring is a standing signal, and this skill only uses verified moves inside the quarterly campaign; live threads under 60 days of silence are patience, not revival.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈11

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every sweep audits three lanes.

    line 29
  2. Distinctive:

    Never "just checking in," never "touching base," and no reassurance hedges ("no pressure," "no agenda," "either way").

    line 47
  3. Distinctive:

    Ask for a specific outcome, not permission: "Worth 15 minutes to see if the landscape changed?" beats "Would you be open to reconnecting?"

    line 48
  4. Distinctive:

    No diagnosis in the first message ("I bet you're dealing with...") and no stock congratulations.

    line 68
  5. Distinctive:

    If it matches, pull the revival play that already worked for that category.

    line 91
  6. Distinctive:

    If it matches nothing, create a new category, define its play, and file this account as the first worked example.

    line 92
  7. Distinctive:

    Cap at 5-15 accounts: If 20+ survive, take the top 15.

    line 105
  8. Distinctive:

    Every account carries a one-line premise anchored in dated evidence: "Closed-lost Nov 2024, objection was integration depth.

    line 106
  9. Distinctive:

    Every draft goes to a human review queue with its lane, premise, evidence, and a NEXT-TOUCH date.

    line 118
  10. Distinctive:

    Run these before the first sweep.

    line 126
  11. Distinctive:

    When someone re-engages a dead account today, do they know the original objection, or are they opening cold with worse odds?

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Closed-Lost Revival: The Pipeline You Already Paid For

The 2025 Ebsta x Pavilion benchmark measured a 19% B2B new-logo win rate across roughly 655,000 opportunities, down from 29% the year before. Read that from the other side: roughly four of five opportunities you worked end closed-lost. That pool compounds every year, it already knows you, and in most CRMs nobody owns it. Revival is not a heroic save. It is working an asset you already paid to create.

One practitioner data point for what disciplined revival produces: Swan AI publicly documented $250K of pipeline in seven days from a pool of 566 closed-lost deals, after adding one step, loss categorization, to a re-engagement agent (public LinkedIn post, August 2026). The step that made the difference is built into this skill as the loss-pattern library.

The prime rule: revive engaged-then-quiet, never cold-never-replied. A contact who never engaged is not dormant pipeline, they are a stranger with your logo in their inbox. Revival applies only to accounts that showed real interest and then disengaged. Everything else routes back to normal prospecting.


The Three Revival Lanes

Every sweep audits three lanes. Each lane has hard gates (skip immediately), evidence requirements (before any draft), and an opener posture.

Lane A: Closed-Lost Deals and Proposal-Gone-Quiet

The highest-value lane. Post-proposal win rates run 31-50% (Norwest, 2024): a buyer who reached proposal stage was more likely to buy than not. When that thread dies silently, more value evaporates than anywhere else in the funnel.

Hard gates:

  • Marked Do Not Contact or equivalent: skip entirely.
  • Peers, advisors, partners, or friendly industry contacts: skip. They never ride a sales cadence.
  • Cold-never-replied: not revival material. Dead is dead.
  • Lost to a fundamental mismatch (wrong ICP, product genuinely cannot do the job): skip. Revival cannot fix a fit problem.

Evidence required before drafting:

  • Closed-lost: the deal closed 6-18 months ago (the reactivation sweet spot; objections resolve, budgets reset, sponsors rotate). Pull the original objection, the last contact date, and who owned the relationship.
  • Proposal-gone-quiet: demo or proposal sent 60-120 days ago, no response, contact still at the same company. Pull the exact date and what the proposal promised.

Opener posture:

  • Lead with the specific objection from the first cycle, never generic win-back language: "When we last spoke, you flagged [exact objection]. Since then, [concrete change]."
  • Never "just checking in," never "touching base," and no reassurance hedges ("no pressure," "no agenda," "either way"). Sophisticated buyers know you are selling; hedging reads as weakness.
  • Ask for a specific outcome, not permission: "Worth 15 minutes to see if the landscape changed?" beats "Would you be open to reconnecting?"

Lane B: Champion Job Changes

Roughly 20% of your past champions change jobs in any given year (industry estimates from job-change tracking vendors; Swan AI cites the same rate in production, 2026). Each verified move is a warm door into an account you have never touched.

Hard gates:

  • The champion must have realized value at the origin account: the deal closed won, or they were a materially active user who drove workflows. A named contact on a lost deal is warm familiarity, not a champion. Skip.
  • Origin company declined you within the last 90 days: the champion is leaving a company that just said no. Not a buying signal. Skip.
  • New company is a competitor or a standing exclusion: log it, no outreach.
  • New company is below your minimum viable size: a personal note from the old relationship owner at most, never a sales motion.
  • Moved into advisor, fractional, or board roles: classify as a partner conversation, not a deal.

Evidence required before drafting:

  • Live verification of current employment. Cached enrichment data lags exactly where movers happen. Read the full profile, not the headline.
  • Wrong-person guard (hard rule): the destination profile's own work history must contain the origin company. A name-and-company match alone is never sufficient.
  • Capture the move month. The outreach window is days 14-45 in the new role. Day 2 they are drowning; month 4 the "new broom" energy is spent.

Opener posture:

  • Reference the prior relationship in terms of what THEY did with your product, not what you did for them.
  • No diagnosis in the first message ("I bet you're dealing with...") and no stock congratulations. Name the specific reason their move makes this relevant.

Lane C: Engaged-Then-Quiet Threads

Hard gates:

  • Last real exchange 60+ days ago. Under 60 days is an active cadence problem, not revival (see stage-aware-follow-up).
  • Real engagement happened: a substantive reply, an attended meeting, a genuine conversation. One-way sends do not count.
  • Contact still at the same company (if moved, re-route to Lane B) and account still fits ICP.

Evidence required before drafting:

  • Pull the last message, its date, and the last open question in the thread.
  • Classify the silence: GHOSTED (interest then disappearance), OBJECTION-PENDING ("let us think" then nothing), TIMING-MISS ("circle back after [event]" that never happened), or CHANGED-LANDSCAPE (reorg, freeze, role change mid-conversation). The class determines the opener.

Opener posture:

  • Acknowledge the gap briefly, never apologize for it, and anchor on their last question: "You asked about [specific thing]. Here is what changed since."

The Loss-Pattern Library

The step that turns revival from a one-off campaign into a compounding system. Before drafting anything for a Lane A account, name the loss pattern:

  1. Match the account against your existing loss categories (examples that recur across B2B: budget-cycle timing, champion departed mid-deal, chose competitor on one capability, trial launched at the wrong moment, sponsor lacked authority, price-to-value gap at the proposed scope).
  2. If it matches, pull the revival play that already worked for that category.
  3. If it matches nothing, create a new category, define its play, and file this account as the first worked example.

Treating 500 losses as 500 unique investigations gives you zero leverage; account #10 learns nothing from the nine before it. With a library, most losses drop into a shape you have already solved, and only genuinely new patterns need original thought.


Campaign Compression Rules

A sweep produces ONE campaign package per quarter, not a drip of ad-hoc sends.

  1. Audit all three lanes with the hard gates. Only survivors advance.
  2. De-duplicate across lanes: the same human appearing twice (a champion mover from a closed-lost account) gets one thread, not two.
  3. Rank by signal strength and freshness: champion movers first, then proposal-gone-quiet, then engaged-then-quiet, then old closed-lost. Apply recency decay within each lane.
  4. Cap at 5-15 accounts. If 20+ survive, take the top 15. If fewer than 5 survive, ship fewer. Never pad with weak accounts: quality per touch is the entire economics of revival, because each account gets exactly one credible re-open per cycle.
  5. Every account carries a one-line premise anchored in dated evidence: "Closed-lost Nov 2024, objection was integration depth; they posted an integration-engineer opening last week." If the premise cannot cite a date, it does not ship.

The current-offer rule. Revival reaches people who went quiet months or years ago. Whatever they were offered then is often retired. Every draft converges on what you are CURRENTLY selling or sharing, and where the old asset was superseded, bridge it explicitly ("that assessment became something sharper") rather than re-pitching the dead version or pretending the first cycle never happened. The dated trigger opens the message; the current offer carries the ask.

Quarterly cadence is intentional. Monthly sweeps drain the pool and catch movers too early (the best movers have been in role long enough to hit a real problem). Quarterly spacing also lets budgets reset and objections age out. Resist the urge to accelerate just because candidates accumulate.


Human Approval Contract

Revival touches people with history, where a clumsy message burns the one re-open you get.

  • Every draft goes to a human review queue with its lane, premise, evidence, and a NEXT-TOUCH date. Nothing sends autonomously.
  • NEXT-TOUCH discipline: closed-lost 7 days, champion movers 10 days (they are busy, give them room), engaged-then-quiet 14 days. One follow-up. No reply by then: the account moves to passive nurture until a fresh signal fires. Revival is one knock, not a new cadence.
  • Log every shipped cohort and its outcomes. Quarter-over-quarter reply and conversion rates per lane are how you learn which lanes deserve more of the 15 slots.

Diagnostic Questions

Run these before the first sweep; they usually expose the opportunity in minutes.

  1. How many closed-lost deals sit in the CRM from 6-18 months ago, and does anyone own them today?
  2. What percentage of your proposals from the last two quarters received a final answer, even a no?
  3. Can you name the last three champions who left customer accounts, and where they work now?
  4. What are your top five loss reasons as WRITTEN IN THE CRM, and do you believe them? (Loss-reason fields are usually fiction; transcripts and email threads are the evidence.)
  5. When someone re-engages a dead account today, do they know the original objection, or are they opening cold with worse odds?

Benchmarks Referenced

Full provenance, vintages, and the list of practice-based rules: read references/revival-benchmarks.md.

  • B2B new-logo win rate 19% measured for 2025 across ~655,000 opportunities (Ebsta x Pavilion benchmark, 2025; prior year 29%). The complement is the size of the closed-lost pool.
  • Post-proposal win rates 31-50% (Norwest, 2024): the case for the proposal-gone-quiet lane.
  • ~20% of champions change jobs per year (job-change vendor estimates, 2023-2026, consistent with Swan AI's published production rate, 2026).
  • $250K pipeline in 7 days from 566 closed-lost deals once loss categorization was added (Swan AI, public post, August 2026). A practitioner anecdote, not a controlled benchmark; treat as an existence proof.

Built by Neon Triforce

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.