agentleFS
teodstrteodstr/garage/skills/competitor-teardown/SKILL.md

competitor-teardown

Skill0 starsChanged 2 days agoMITView on GitHub

Map every alternative a customer has (direct competitors, indirect solutions, workarounds, doing nothing), take apart the strongest ones (offer, price, promise, channels, customer reviews), and find the gaps a new entrant can use. Use for a startup's competitive analysis, before positioning or pricing a product, or for the competition slide of a pitch deck. Triggers: "competitors", "competitive analysis", "competitor teardown", "alternatives", "concurrents", "analyse concurrentielle", "benchmark concurrentiel", "veille concurrentielle", "competidores", "análisis de la competencia", "benchmark competitivo".

14 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

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before positioning, pricing or building the MVP.

    line 20
  2. Very specific:

    Not to judge how attractive a whole industry is: use porter-five-forces from boardroom if it is installed.

    line 22
  3. Distinctive:

    Be fair: write down what each competitor does better than the founder's project.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 12 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

Competitor teardown

"We have no competitors" worries investors more than a crowded market: customers always solve their problem somehow. This skill lists those alternatives, studies the strongest ones closely, and turns what their customers complain about into openings.

When to use

  • Before positioning, pricing or building the MVP.
  • For the competition slide of a pitch-deck.
  • Not to judge how attractive a whole industry is: use porter-five-forces from boardroom if it is installed.

Inputs

  1. The problem and the target customer.
  2. The competitors the founder already knows.
  3. The geography.

Method

  1. List every alternative, in four groups: direct competitors (same solution, same customer), indirect solutions (a different product doing the same job), workarounds (spreadsheets, freelancers, doing it by hand), and doing nothing. Ask the jobs-to-be-done question: what do customers "hire" today to get this done?
  2. Pick three to five to take apart: the ones customers actually use, not the ones that look most similar.
  3. Take each one apart: target customer, promise (the headline of its website), offer and features, price and pricing model, channels (how it finds customers), size or funding if public, and what its customers say.
  4. Mine the reviews: app stores, Google reviews, software review sites, Trustpilot, Reddit, forums. Group complaints and praise by theme, count them, and quote a few with the link and the date.
  5. Compare on what customers value, not on the founder's feature list: a table, or a positioning map on two axes that matter to customers.
  6. Find the gaps: underserved segments, complaints nobody fixes, offers that are too expensive or too complex, missing channels. For each gap, say why incumbents leave it open, or how easily they could close it.
  7. Be fair: write down what each competitor does better than the founder's project.

Output

### Alternatives map
| Alternative | Type (direct, indirect, workaround, nothing) | Who uses it | Why |
|---|---|---|---|

### Teardown
| | Competitor A | Competitor B | Our project |
|---|---|---|---|
| Target | | | |
| Promise | | | |
| Price | | | |
| Channels | | | |
| Top complaints (count) | | | |

### Gaps we can use
1. <gap>: evidence, why incumbents leave it open, how we use it

Quality bar

  • Indirect solutions and "doing nothing" are included; the answer is never "no competitors".
  • Prices, features and figures come from the competitors' own pages or filings, with the link and the date accessed; review counts are real counts.
  • Each gap is backed by evidence and considers how incumbents could react.
  • The comparison says where competitors are stronger.
  • Written in the user's language, with the terms below.

Terminology

EnglishFrançaisEspañol
CompetitorConcurrentCompetidor
Direct, indirect competitionConcurrence directe, indirecteCompetencia directa, indirecta
SubstituteProduit de substitutionProducto sustitutivo
WorkaroundSolution de contournementSolución alternativa
Positioning mapCarte de positionnementMapa de posicionamiento
Competitive intelligenceVeille concurrentielleInteligencia competitiva

Sources

  • Porter, M. E. (1980). Competitive Strategy: Techniques for Analyzing Industries and Competitors. Free Press.
  • Christensen, C. M., Hall, T., Dillon, K., & Duncan, D. S. (2016). Competing Against Luck: The Story of Innovation and Customer Choice. HarperBusiness.

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.