agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/closed-lost-reactivation/SKILL.md

closed-lost-reactivation

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when you want to revive closed-lost deals and old opportunities: \"re-engage lost deals\", \"win back closed lost opportunities\", \"reactivation campaign\", \"which lost deals should we try again\". Filters lost deals by reason and time since loss, checks for new triggers, picks the ones worth reopening, and writes reactivation messages that reference what changed (on their side or yours) instead of repeating the old pitch. Often the cheapest pipeline a team can create.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Use this when pipeline is thin or each quarter.

    line 16
  2. Distinctive:

    Every message names a specific change.

    line 50
  3. Distinctive:

    MUST name what changed in every reactivation message.

    line 56
  4. Distinctive:

    MUST check contacts are still in role and have not opted out.

    line 57
  5. Distinctive:

    NEVER disparage the competitor they chose.

    line 58
  6. Distinctive:

    NEVER misstate the reason they gave for saying no.

    line 59

≈ “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

Use this when pipeline is thin or each quarter. Lost deals already know you, already have the problem and often lost on timing; reopening them costs far less than finding new ones.

Inputs

  • Closed-lost deals from the last 3-24 months: reason, stage lost, contacts, notes, competitor chosen.
  • What changed on your side since: product releases, new pricing or packages, new proof.
  • Current triggers at those accounts: new leaders, funding, hiring, the competitor's contract term ending.

The play

1. Filter by reason and timing

Lost reasonReopen whenAngle
Timing / no priority3-6 months later, or a trigger fires"Is it a priority now?"
BudgetNew fiscal year or fundingNew budget, phasing options
Chose a competitor9-12 months later, before their renewalCheck-in on how it's going
Product gapWhen the gap ships"You asked for X; it's live"
No decision / went dark3-4 months laterNew proof, fresh angle
Bad fitOnly if their situation changedUsually leave it

2. Score each deal

Priority = how far it got (later stage = higher) + new trigger present + the lost reason has been resolved + contacts still in role.

3. Lead with what changed

The message must answer "why talk again now?". Something changed: their situation (new leader, growth), your product (the missing feature), or the market (a new requirement).

4. Pick the contact

The original champion if still there; if they left, the new person in the role (and run a job-change play on the champion).

5. Write short and honest

Hi Priya, when we spoke in March, multi-entity support was the deal-breaker. It went live last month, and Contoso is running four entities on it. Worth a fresh look, or has the team moved on?

What good looks like

  • Every message names a specific change.
  • Deals lost to a competitor are approached near the end of the competitor's likely contract term, not a month after signing.
  • The common mistake is re-sending the original pitch with "circling back" on top, which reminds the buyer why they said no.

Rules

  • MUST name what changed in every reactivation message.
  • MUST check contacts are still in role and have not opted out.
  • NEVER disparage the competitor they chose.
  • NEVER misstate the reason they gave for saying no.

Example prompts

  • "Here are 120 closed-lost deals from the last 18 months. Which should we reopen and with what?"
  • "We just shipped SSO. Write messages to every deal we lost because of it."
  • "Plan a quarterly closed-lost reactivation play."

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.

Check your setup, free