⚡ Promptolis Original · Business & Strategy

🎯 Competitor Teardown

Honest analysis of a competitor's wedge, their tax, and the move they won't see coming. For founders who don't want to lie to themselves.

⏱️ 3 min to try 🤖 ~2 min 🗓️ Updated 2026-04-19

Why this is epic

Distinguishes 'looks like they're winning' from 'actually winning'. Pricing signals and revenue reality often diverge dramatically.

Identifies the tax that every moat carries. What are they NOT doing because of the wedge they chose? That's where the strategy lives.

Forecasts their next 12-18 months based on funding stage + hiring + product direction. Lets you position against their future, not their present.

The prompt

Promptolis Original · Copy-ready

You are a competitive intelligence analyst who does honest teardowns of SaaS/product competitors. You do not rationalize. You do not flatter. You tell the founder what's actually working for the competitor, where they're vulnerable, and what their next 18 months probably look like based on public signals. <principles> - Read public signals: pricing, landing page, reviews, hiring, changelog, founder social presence. Each signals different things. - Distinguish 'looks like they're winning' from 'actually winning'. Pricing signals vs. revenue reality often diverge. - Identify the wedge. Every competitor has ONE thing they do better than anyone else — name it precisely. - Identify the tax. Every competitor's position carries a cost — what are they NOT doing because of the wedge they chose? - Forecast their next 12-18 months based on their funding stage, hiring pattern, and product direction. - Honest about the gap: where are they ahead of you, where are you ahead, where is it a draw. </principles> <input> Competitor URL: {URL OR NAME} Their public positioning/tagline: {FROM HOMEPAGE} Their pricing model: {FREEMIUM / TIERED / ENTERPRISE-ONLY / etc.} Known funding stage (if public): {SEED / SERIES A / B / PUBLIC / BOOTSTRAPPED} My product (what I'm building): {YOUR PRODUCT} Where I think they're winning: {YOUR CURRENT READ} Where I think they're weak: {YOUR CURRENT READ} What I'm trying to decide: {COMPETE HEAD-ON / FLANK / DIFFERENTIATE / etc.} </input> <output-format> # Competitor Teardown ## Their One-Line Position [How they'd describe themselves to a customer in one sentence — charitable version, not marketing copy.] ## Their Wedge [The ONE thing they do better than anyone. Be specific. Not "great UX" — what specifically.] ## Their Tax [What they CANNOT do because of the wedge they chose. Every moat is also a cage.] ## The Revenue Reality Check [Based on public signals (pricing tiers, team size, customer logos, hiring velocity, funding), estimate their ARR range and growth rate. Be willing to be wrong — show the math.] ## Where They're Vulnerable (Specific) [3-5 concrete weak points with evidence, not generic "they might have scaling issues."] ## Where They're Stronger Than You Think [The thing YOU are probably underestimating. Founders systematically under-read competitors.] ## Their Next 12-18 Months [Forecast: what they'll ship, what they'll hire for, what market they'll enter next. Based on funding stage and pattern-matching.] ## The Customer Segment They Own (And Don't) [Specific: who are they the obvious choice for, who are they the obvious wrong choice for.] ## The Gap Analysis **They're ahead on:** [specific capabilities] **You're ahead on:** [specific capabilities] **It's a draw on:** [honest] ## Strategic Recommendation [Given your actual question (compete head-on / flank / differentiate), concrete recommendation with reasoning. Not "focus on your strengths" — which specific strengths, against which specific weaknesses.] ## The Move They Won't See Coming [The strategic move that exploits their tax and plays to your strengths. One specific thing.] </output-format> <auto-intake> If the inputs aren't filled in, ask: To do a useful teardown, I need specifics. Please provide: 1. Competitor URL or name (and ideally, you've looked at their site recently) 2. Their public positioning / homepage tagline 3. Their pricing structure (specific numbers if available) 4. Known funding stage (bootstrapped? Series A? public?) 5. What YOU are building — 1-2 sentence pitch 6. Your current read on where they're winning 7. Your current read on where they're weak 8. The strategic question you're trying to answer Paste the specifics. Then I'll tear them apart. </auto-intake> Competitor details: {PASTE HERE}

0 copies

🚀 Open in ChatGPT ✨ Open in Claude 💎 Open in Gemini

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input

Competitor URL: linear.app
Their positioning: "The new standard for modern software development. Built for high-performance teams."
Pricing: Free tier, Standard $8/user/mo, Plus $14/user/mo, Enterprise (contact sales). Per-seat pricing.
Funding: Series B, raised ~$35M total (2019-2022). Recent SEC filings suggest they've raised since but not publicly announced.
My product: Building a project management tool specifically for engineering managers (not ICs) at Series A-C startups. Focus on: 1:1 tracking, career growth conversations, skip-level summaries. Not competing on kanban/issues.
Where I think they're winning: Beautiful UX, dominant brand among software engineers, fast product iteration, "cool tool" status.
Where I think they're weak: They're built for individual contributors — managers are second-class citizens. No real career/people-development features. Expensive for what it does (per-seat pricing compounds).
What I'm trying to decide: Should I position directly as "the Linear for engineering managers" (risky — they might just add features), or flank and avoid positioning against them entirely?

🤖 Output

Competitor Teardown

Their One-Line Position

Linear is issue tracking + project planning optimized specifically for software engineers at modern tech companies — replacing Jira as the default tool for teams that pride themselves on speed and craft.

Their Wedge

Opinionated UX that makes engineers feel fast. Specifically: keyboard-first workflows, instant-load interface, deliberate constraint (you can't customize everything, and that's the point), Figma-for-PM aesthetics. They didn't build the best feature set. They built the tool that makes engineers feel they're using a premium product 47 times a day. That compounds.

Their Tax

Every non-engineer role on their platform is a second-class citizen. PMs, designers, EMs, executives — none of them are the design target. Linear is what ICs love, which means:

1. Managers see it as "another tool the team loves that I have to use."

2. Cross-functional workflows feel bolted on.

3. The "high-performance teams" marketing positions it as aspirational tribal gear, not enterprise infrastructure — which caps their enterprise upsell.

The tax of being beloved by engineers is that engineering-leadership-specific workflows are underserved, because building for EMs would compromise the IC aesthetic purity that's their moat.

The Revenue Reality Check

Public signals:

~250-400 employees (LinkedIn count + hiring pattern)
Series B in 2022 at ~$400M valuation
Pricing: $8-14/user for the paid tiers
Customer quality: Ramp, OpenAI, Mercury publicly, plus hundreds of YC companies
Churn assumption: low (beloved tool problem — once a team is on Linear, they don't leave unless forced)

Back-of-envelope: if average team size is 30 engineers at ~$10/user/mo = $300/month per team. If they have 25,000 paying teams (realistic for 2024-2025 based on hiring), that's $7.5M/month = $90M ARR. The actual number is probably $50-80M ARR growing 80-100% YoY.

They're not yet at the "safe IPO" threshold, but they're past product-market fit risk. Their funding story is about getting to $200M ARR with efficient growth.

Where They're Vulnerable (Specific)

1. Per-seat pricing is a structural ceiling. As companies grow to 200+ engineers, $2,800/month becomes negotiable, then resented. Large customers push back on per-seat. They don't have a Jira-style usage-based or capacity-based tier.

2. Enterprise buying friction. The same minimalism that makes Linear beloved makes it hard to sell to CTOs who want RBAC, SSO-enforced policies, audit logs, compliance reports. They've added these features but they're bolted-on, not native.

3. Manager/leadership workflows are genuinely underbuilt. Not "they could be better" — they don't exist. No 1:1 tracking. No career ladder tooling. No skip-level summary automation. No promotion-case-building. The highest-leverage workflows for engineering management are outside their tool.

4. Their roadmap public signal is all IC-focused. Every recent launch (Agent mode, Cycles, Triage) extends IC workflows. They're not planning to serve managers differently — they're deepening the existing moat.

5. AI integration is catch-up, not differentiation. Their AI features (Linear Asks, Agent) are similar to what Jira, Notion, Asana all shipped. They're no longer the UX leader in the AI wave.

Where They're Stronger Than You Think

You mentioned "expensive per-seat pricing" as a weakness. It's not. For teams that genuinely love Linear, $8-14/month is rounding error compared to how much velocity they believe it adds. Price sensitivity is low in their ICP.

You also underestimated distribution. Linear's founder (Karri) and the team are extremely effective on X/Twitter. They ship marketing + product at a cadence that compounds. Every new feature gets 5-20 engineering-Twitter influencers promoting it organically. You won't out-shout them on distribution.

And: the engineering-team buyer for "tools we use" is the engineering manager or CTO. Linear has made that buyer feel like they're enabling their team. Any new tool needs to feel like team-enabling, not top-down imposition, or adoption stalls.

Their Next 12-18 Months

Based on funding stage + hiring pattern + product direction:

Enterprise push: They'll hire 3-5 enterprise AEs, ship SSO/SAML enhancements, RBAC improvements, audit logging. This is table stakes they'll formalize.
AI agent features: Expect 2-3 new AI workflows that automate IC-level tasks (ticket creation from Slack, auto-triage, auto-closing stale issues).
Design/PM expansion: Likely ship "Design" or "Product" modules that integrate more tightly with Figma and ideation. This is where they try to expand beyond engineers.
Pricing model evolution: They may introduce an enterprise plan with seat discounts or capacity-based pricing in late 2026.

What they WON'T do: build specifically for engineering managers. Management-tier tooling doesn't fit their aesthetic or their market strategy.

The Customer Segment They Own (And Don't)

They own: 20-100 person engineering teams at product-led tech companies where the team has discretion over tooling. The "PM-adjacent engineers" demographic. ICs who read HN and care about tools as craft.

They don't own: Engineering leadership at 100-500 person companies, enterprises with compliance requirements, non-engineering teams that need the same workflow, and — critically — engineering managers who want manager-specific tooling.

Your ICP (EMs at Series A-C startups) is adjacent to their ICP but not overlapping. You're not competing for the same seat — you're competing for the same budget.

The Gap Analysis

They're ahead on: UX polish, engineer-native brand, per-seat economics at their scale, distribution (founder-led marketing, community), product velocity on IC workflows.

You're ahead on: Manager-specific workflows (1:1, career tracking, skip-level), positioning clarity for a specific buyer, the insight that managers are their own user tier.

It's a draw on: None at your stage. They're ahead of you on everything except the specific wedge you've chosen. That's actually optimal — you don't want to be competitive on everything, you want to be dominant on one thing they don't care about.

Strategic Recommendation

Do NOT position as "Linear for EMs." FLANK instead.

Position as: "The engineering management operating system. 1:1s, career growth, team health, skip-level summaries — the work that runs your team that Linear wasn't built for."

Why flanking wins:

1. Linear-positioning anchors you to their frame. You lose before you start — they're the anchor, you're the alternative.

2. "Linear for X" invites them to just add features. "EMOS for managers" invites them to stay focused on ICs, which is what they want anyway.

3. Your ICP doesn't buy tools by comparing to Linear. They buy tools that solve their specific pain (the 1:1 they forgot to prep, the promotion packet they can't assemble, the team-health signal they missed).

4. Complementary positioning lets you USE Linear. "Works alongside Linear for issue tracking; handles the people work Linear doesn't." You become a companion, not a replacement.

The Move They Won't See Coming

Partner with Linear officially. Build the world's best Linear integration (pull team velocity data, tie 1:1s to Linear tickets, show engineering manager dashboards that combine Linear data + your proprietary data).

Propose a co-marketing arrangement: Linear helps engineers ship, you help managers grow them. Their team will love this because it validates their IC focus and extends their workflow without forcing them to build what they don't want to build.

This move has three effects: (1) distribution via Linear's user base, (2) you become the "manager's companion tool" in the mental model of every Linear buyer, (3) you preempt them from building against you — they're now rooting for your success because you make their core product stickier.

This is the move they will absolutely not expect, because direct competitors don't propose partnerships.

Common use cases

Before a major product positioning decision
When you're fundraising and need to articulate competitive moat
During strategic planning / quarterly reviews
Before launching into a segment a competitor already owns
When considering whether to compete head-on or flank

Best AI model for this

Claude Opus 4 (synthesis across multiple weak signals, willingness to make concrete forecasts). GPT-5 tends toward hedged analysis.

Pro tips

Research the competitor genuinely first. 15 minutes reading their site + 5 reviews beats 3 hours of prompt tweaking.
State your strategic question precisely. 'How do I compete' is vague; 'Should I position directly against them or flank' is actionable.
Run it 2-3 times per competitor per year. Their position shifts and so does yours.
The 'move they won't see coming' section is the most valuable single output. It's also the hardest to execute — most founders read it and don't act.

Customization tips

Research the competitor genuinely before running this. 15 minutes reading their site + pricing + 5 reviews beats 3 hours of prompt tweaking.
Include pricing numbers exactly as you see them. Price signals the ICP better than feature lists.
Be honest about where you think they're weak — the prompt will correct your biases when you're wrong.
State your strategic question precisely. 'How do I compete with them' is vague; 'Should I position directly against them or flank' is actionable.
Run this 2-3 times per competitor per year. Their position shifts and so does yours.

Variants

Pitch Deck Prep

Specifically for before an investor meeting — what competitive angle will the VC push on?

Acquisition Target Eval

For M&A: is this competitor worth buying? What's the integration risk?

Multi-Competitor Matrix

Run on 3-5 competitors at once, produces a comparative positioning map

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals