competitive-displacement
Skill2 starsChanged 25 days agoMITView on GitHub
Build the narrative and the plan to unseat an incumbent or beat a competitor in a live deal. Use this skill whenever a seller says "we're up against [competitor]", "displace the incumbent", "how do I unseat [vendor]", "they're already using [tool]", "competitive deal", "compete against [X]", "win against the incumbent", or is in an evaluation where another provider is the default. It pulls context from Loop first (falling back to CRM, call transcripts, and email), reads the incumbent's strengths and gaps, builds a differentiation narrative based on approach and outcome (not a feature war), writes the switching story, and gives you trap-setting questions that surface the incumbent's gaps without badmouthing. Prefer this over a feature-comparison battlecard any time a deal is competitive.
In this repository10 other files it gives its agents.
- account-planningSkill
- call-follow-upSkill
- call-prepSkill
- champion-enablementSkill
- deal-advancementSkill
- manage-upSkill
- multithreadSkill
- one-page-business-caseSkill
- qbr-prepSkill
- sales-playsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
When you are up against an incumbent, the feature war is the losing game.
- Very specific: line 36
Loop first: If the Loop MCP (https://mcp.fluint.io/mcp) is connected, use it first.
- Distinctive: line 40
No Loop? Detect what is live and fall back: Do not assume a vendor. In parallel:
- Distinctive: line 42
Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies.
- Very specific: line 54
Read references/frameworks.md (Read the incumbent).
- Very specific: line 61
Read references/frameworks.md (Be different, not better).
- Very specific: line 68
Read references/frameworks.md (The switching story).
- Very specific: line 75
Read references/output-templates.md.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Competitive Displacement
What this does
When you are up against an incumbent, the feature war is the losing game. The buyer already owns the incumbent, switching feels risky, and a battlecard turns the conversation into a checklist you may not win. This skill builds the other approach: change the criteria, make the status quo feel riskier than the switch, and let the buyer surface the incumbent's gaps themselves.
- Reads the incumbent: what they are strong at, and where they fall short for this buyer.
- Builds differentiation on approach and outcome, not features.
- Writes the switching story: why now is the right time to move.
- Gives you trap-setting questions that expose the gaps without badmouthing anyone.
The deliverable is a displacement plan you can run in the next conversation.
Step 1: Lock the deal and pull context
Loop first. If the Loop MCP (https://mcp.fluint.io/mcp) is connected, use it first. Pull the
deal, the meeting history, and any notes on the incumbent or competitor. Loop already
fuses CRM, calls, and emails, so start there.
No Loop? Detect what is live and fall back. Do not assume a vendor. In parallel:
- CRM (HubSpot, Salesforce, Attio, Pipedrive) = the deal, the named competitor, notes.
- Call transcripts (Salesloft, Gong, Clari, Chorus, Fathom, Fireflies; or via Clay / Deepline) = what the buyer has said about their current solution and its frustrations.
- Email (Superhuman, Gmail, Outlook) = recent signals.
Confirm who the incumbent or competitor is. If it is unknown, that is the first thing to find.
Missing a source? Flag it, and make the gap a move. Mark it inline as [MISSING: ...] and continue. Every gap gets the single highest-leverage way to close it: the one question, to the one person, at the next touchpoint. Not "get more data."
Who can actually say yes? Name the people with the power to approve this, or to block it, and mark whether they are engaged yet. Power is often not in the room. If the deciders are absent or untouched, that is the headline, not a footnote.
Step 2: Read the incumbent
Read references/frameworks.md (Read the incumbent). Name who you are up against, what they
are genuinely strong at (respect it, do not pretend it away), and where they fall short for
this specific buyer. Note what a switch would cost the buyer, because that cost is the real
opponent, not the competitor.
Step 3: Build the differentiation
Read references/frameworks.md (Be different, not better). Write the 2 to 3 ways you are
meaningfully different in approach or outcome, tied to what this buyer cares about. Not a
feature list. Then name the villain: the status-quo problem the incumbent structurally cannot
solve. Different beats better, because better invites a comparison and different reframes it.
Step 4: Write the switching story
Read references/frameworks.md (The switching story). Tell the story of why now is the right
time to move: what has changed in their business or market that makes the status quo the risky
choice. Frame it with the change equation: dissatisfaction with today, a vision of the after,
and an easy first step have to outweigh the resistance to switching.
Step 5: Set the traps
Read references/output-templates.md. Write 3 discovery questions that surface the gaps and
frustrations with the current solution, without badmouthing the competitor. The best of these
is the "what must be true of a solution for this to work" question, which gets the buyer to
name the requirements the incumbent cannot meet.
The deliverable
Produce the displacement plan using the skeleton in references/output-templates.md:
- Incumbent read (strengths, gaps for this buyer, the cost of switching)
- Differentiation (2 to 3 differences in approach/outcome + the named villain)
- Switching story (why now, framed as status-quo risk)
- Trap-setting questions (3 questions that surface the gaps, no badmouthing)
The operator's read
Before you hand it over, add the part a summary cannot: the one thing an experienced operator would notice that the data does not show on its own. The non-obvious risk. The stakeholder who matters more than their title. The deal that is not what it looks like. The strength that is quietly a trap. One or two sentences of judgment, called out plainly. Anyone can produce the map. This is the read.
Operating principles
- Be different, not better. Better invites a feature war. Different reframes the criteria.
- Sell the approach before the product. Win "what must be true" and the search narrows to you.
- The real opponent is the switching cost, not the competitor. Make the status quo the risk.
- Never badmouth. Let the buyer surface the gaps. Their conclusion beats your accusation.
- Voice guard. Anything the buyer will read opens with their words, from the call or their own materials, in the first line. Banned openers: "Great connecting," "As discussed," "I wanted to follow up," "Hope this finds you well," "Circling back." If a sentence would survive being pasted into a different deal, it is too generic. Cut it.
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
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.

