Positions and story with three competitors

Applies when your homepage explains what the product does before it names the problem, your positioning is interchangeable with three competitors, or nobody feels urgency to act now. Produces a hero-and-villain story and a differentiation level you can actually defend.

Get the roles right

Developers do not buy features; they hire a tool to defeat something making their work worse. Assign the roles:

• Hero — the developer. Never the vendor, never the product.
• Villain — the undeniable trend making the pain worse every day.
• Wise advisor — you, arriving with a gift (the product).
• Inciting event — the change in the world that forces the hero to act now.

No villain, no urgency, no story, no conversion.

The three-part story

1. Inciting event — introduce the hero and the villain; the world changed and the hero cannot stay put.
2. Obstacles — specific challenges, each solved with your help, told as mini before-and-afters: "Before, we had [problem]. Now, [measured result]."
3. Resolution — villain defeated for now, specific results, and the hero shares the wisdom. That is your testimonial.

A benchmark shape, three lines: "Slow builds waste your time. Standard build tools can't handle today's codebases. Speed up builds now to keep engineers in flow." Pain, villain, hero, urgency.

Good villains are trends, not competitors: cloud-cost sprawl, tool fragmentation, compounding tech debt, flaky pipelines, observability gaps, manual deploys, agents you cannot trust in production.

The four levels of differentiation

Compete as high up this ladder as you can. Feature wars are a race to the bottom.

1. Feature — "we have X, they don't." Weakest.
2. Benefit — "we save you time." Every competitor says it.
3. Segment — "for teams under release pressure with compliance." Stronger.
4. Problem — "the only fix for a problem no one else has named." Strongest, and the road to owning a category.

To reach level four, talk to enough real users to surface a problem competitors have not named, then name it so precisely your product is the obvious answer. When rivals adopt your vocabulary, they have already lost the position.

Decide where you stand

• Can you state a problem only you solve, in the user's own words? → Level 4. Lead with the problem and name the category.
• If not, can you name a specific segment with a compelling reason to care? → Level 3. Lead with the segment and their trigger.
• If neither → you are stuck at feature or benefit. Go talk to users until a problem or a segment surfaces.

What good looks like

• The developer is the subject of the sentence, and the problem comes before the product.
• There is a named villain (a real trend), so the story carries urgency instead of listing features.
• You are competing at the problem or segment level, not trading feature checklists.
• The story could not be pasted onto a competitor's site unchanged.
• Wins are shown as before-and-after with a real number and a named user, not adjectives.

Rules

• MUST make the developer the hero and the product the tool, never the reverse.
• MUST name a villain (a real trend) so the story has urgency.
• NEVER lead with "platform," "powerful," or "pleased to announce"; a feature is not a story, a customer win is.
• NEVER position on a feature checklist; it keeps you at the bottom of the differentiation ladder forever.