Individual skill
won-deal-icp-finder
Use this skill when someone wants to know who actually pays them — auditing closed-won deals to derive a proven ideal customer profile instead of an aspirational one, then building a look-alike target list from it. Produces a revenue-ranked deal table, two to four named ICP archetypes with searchable criteria, and a ranking of the acquisition sources that produced the money. Trigger phrasings: "audit my biggest deals", "which customers made us the most money", "analyse my closed-won", "what's my real ICP", "find more customers like my best ones", "look-alike accounts", "revenue by account", "which channel produced our best deals", "ICP refresh before planning".
skills/erwann-lefevre/won-deal-icp-finder/SKILL.md
Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 237
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,090 bytesSKILL.mdcore · 7,090 bytesSKILL.mdcore · 7,090 bytesSKILL.mdcore · 7,090 bytesSKILL.mdcore · 7,090 bytesexamples/sample-deals.jsonasset · 3,105 bytesreferences/analysis-engine.mddoc · 4,446 bytesreferences/archetype-clustering.mddoc · 5,384 bytesreferences/deal-data-extraction.mddoc · 4,440 bytesscripts/analyze.pyruns · 27,262 bytes
Read excerpt
Applies when the ICP on the slide was written before the revenue arrived. Produces a proven profile, derived from deals that closed, plus the search criteria to find more of them.
## Most stated ICPs are aspirational
Teams write their ICP at the start, from the market they want. Then they close deals, and the deals quietly disagree — smaller, in an adjacent vertical, in a country nobody targeted. Nobody rewrites the slide, so prospecting keeps aiming at the market that never paid. This skill re-derives the profile from the ledger instead of the plan.
## Select on money, not on stage names
The first move is picking which deals count, and it is where this play usually breaks.
The obvious approach — filter on a "Closed Won" stage — assumes a stage that a surprising number of pipelines don't have, or don't use consistently, or spell in another language. When it silently matches nothing, the fallback is worse: pull the most recent deals instead, which are the newest and emptiest ones, and the analysis runs on rows with no value in them.
Select on **deal value being populated**, over the last twelve months. A won signal, where one genuinely exists, is a filter you add on top — not the thing you rely on. Read the CRM's own conventions before pulling anything: which field actually holds value (the standard amount field is often abandoned in favour of a custom ARR or ACV one), and whether a won status exists at all. If you can't tell, ask one specific question and stop. Guessing here doesn't produce a slightly-off answer, it produces a confident answer about empty rows. See `references/deal-data-extraction.md` for the field-discovery sequence, the CSV fallback, and how to keep the pull bounded.