Deal qualification (MEDDICC)
You need to qualify a B2B deal or check its health.
You get MEDDICC scorecard · Confirmed vs assumed · Gap list
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.
Use it when you want to revive closed-lost deals and old opportunities.
“Here are 120 closed-lost deals from the last 18 months. Which should we reopen and with what?”
What happens when you ask your agent with this skill installed. Every step below comes straight from the skill.
Here are 120 closed-lost deals from the last 18 months. Which should we reopen and with what?
closed-lost-reactivationReady for your review. Nothing is sent or changed until you approve.
What good looks like
What you bring
What you get
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.
| Lost reason | Reopen when | Angle |
|---|---|---|
| Timing / no priority | 3-6 months later, or a trigger fires | "Is it a priority now?" |
| Budget | New fiscal year or funding | New budget, phasing options |
| Chose a competitor | 9-12 months later, before their renewal | Check-in on how it’s going |
| Product gap | When the gap ships | "You asked for X; it’s live" |
| No decision / went dark | 3-4 months later | New proof, fresh angle |
| Bad fit | Only if their situation changed | Usually leave it |
Priority = how far it got (later stage = higher) + new trigger present + the lost reason has been resolved + contacts still in role.
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).
The original champion if still there; if they left, the new person in the role (and run a job-change play on the champion).
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?
Once the skill is installed, plain requests like these load it automatically. Swap in your own company, buyer and numbers.
“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.”
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. You get: prioritised reactivation list, what changed per deal, reactivation messages.
Use it when you want to revive closed-lost deals and old opportunities.
Run /plugin marketplace add prosyo-ai/gtm-skill and then /plugin install gtm-skills@prosyo to add the whole library, or run npx skills add prosyo-ai/gtm-skill –skill closed-lost-reactivation for this skill alone. In Claude.ai, download the .zip from this page and upload it under Settings, Capabilities, Skills.
Have these ready: closed-lost deals with reasons and dates, what changed since, current triggers. If something is missing, the skill tells the agent to ask for it rather than guess.
Yes. The skill is a plain SKILL.md file with no vendor lock-in. Agents that load skills natively (Claude Code, Claude.ai, Codex, Cursor, Gemini CLI and others) pick it up automatically; anywhere else, paste the file into the conversation as instructions.
No. Every skill in the library drafts, researches and analyses, and waits for a person to approve anything that sends, schedules or changes records in bulk. Your inbox, CRM and accounts stay under your control.
Yes. It is free and MIT-licensed. Copy it, adapt it to your market and voice, and if you improve it, open a pull request so everyone gets the better version.
Paste this into Claude, Codex or any agent. It interviews you about your play, writes the skill in the house format, checks it and opens the pull request. Once it is merged, it shows up here with your name on it.
Fetch https://raw.githubusercontent.com/prosyo-ai/gtm-skill/main/AGENTS.md and follow its submission flow. Interview me about my GTM play (the real numbers, rubrics and examples), draft it in their format with reference pages, validate it and open the pull request.
The skill gives your agent the playbook. Penny, the Prosyo AI SDR, runs plays like this for you every day across LinkedIn and email.
Penny, the Prosyo AI SDR, finds your buyers, writes from what they actually posted, follows up on LinkedIn and email and lands every reply in one inbox with an answer ready. 7 days free, no card.