agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/competitor-teardown/SKILL.md

competitor-teardown

Skill13 starsChanged 23 days agoMITView on GitHub

Use this skill when you need to understand a competitor well enough to beat them: a deal is going head to head, a new competitor appeared, positioning needs a refresh, or reps keep losing on the same objection. Tears down the competitor's positioning, ideal customer, pricing and packaging, product strengths and gaps, customer complaints, sales motion and recent moves, and produces a teardown with where to compete, where to avoid, and the talk track that wins. Built from public sources and your own win-loss notes.

13 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

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 7

    Distinctive

    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 a competitor shows up in deals often enough to matter.

    line 16
  2. Distinctive:

    Read reviews (lowest ratings first), community threads and public support forums.

    line 33
  3. Distinctive:

    Use the matrix in references/teardown-template.md: segments where you win, where you tie and where you lose.

    line 42
  4. Distinctive:

    MUST use public sources or your own deal notes, and cite them.

    line 68
  5. Distinctive:

    MUST date pricing; pricing pages change often.

    line 69
  6. Distinctive:

    NEVER disparage the competitor in rep-facing copy.

    line 70
  7. Distinctive:

    NEVER use confidential material obtained from a competitor's employees or customers under NDA.

    line 71

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “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 a competitor shows up in deals often enough to matter. It produces a teardown that tells sales where to fight, where to walk away and what to say.

Inputs

  • Competitor name and site.
  • Your own positioning, product scope and pricing.
  • Win-loss notes or rep anecdotes involving this competitor. Even five are useful.

The play

1. Read their story

Homepage headline, category they claim, the customer logos they lead with, the use cases on their navigation. Write their positioning in one sentence as they would: "For <who>, <product> is the <category> that <benefit>."

2. Map pricing and packaging

Plans, price points, what is gated to higher tiers, contract terms, free trial or not. Packaging choices reveal who they want and who they tolerate.

3. Mine customer complaints

Read reviews (lowest ratings first), community threads and public support forums. Cluster complaints into themes and count them. Recurring themes with 5+ mentions are real weaknesses; single rants are not.

4. Map their sales motion

Self-serve or sales-led, demo gating, typical discount behaviour, implementation time, who they target in the buying committee.

5. Read recent moves

Launches, pricing changes, leadership hires, funding, layoffs from the last 12 months. Direction of travel matters more than today's feature list.

6. Decide where to compete

Use the matrix in references/teardown-template.md: segments where you win, where you tie and where you lose. Losing segments are as valuable as winning ones; they tell reps when to qualify out early.

Output format

Competitor: <name>  |  Their positioning: <one sentence>
Who they win: <segments>         Who they struggle with: <segments>
Pricing: <summary>               Packaging traps: <what is gated>
Strengths (be honest): <3>
Weaknesses (evidence): <3, with count of mentions and source>
Recent moves: <dated>
Where we compete: <segments + win theme>
Where we avoid: <segments + early qualify-out question>
Talk track: <3 lines a rep can say, no trash talk>
Landmines: <questions that expose their weak spots, asked neutrally>

What good looks like

  • Honest strengths. A teardown that says the competitor is bad at everything gets ignored by reps who just lost to them.
  • Weaknesses come with evidence and counts.
  • Landmine questions are neutral and fair: "How long did implementation take for teams your size?" not "Did you know they're terrible at onboarding?"
  • It answers when to walk away. The best teams lose fewer deals by qualifying out of the wrong ones faster.

Rules

  • MUST use public sources or your own deal notes, and cite them.
  • MUST date pricing; pricing pages change often.
  • NEVER disparage the competitor in rep-facing copy.
  • NEVER use confidential material obtained from a competitor's employees or customers under NDA.

Example prompts

  • "Do a teardown of Northbeam versus us. We lose to them in mid-market."
  • "A new competitor just launched. Tear them down from their site and reviews."
  • "Turn these 14 loss notes against Acme into a teardown and talk track."

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.