Competitive Positioning Matrix

Every founder thinks they know their competitive landscape. They know the feature differences. What they almost never know is the positioning landscape: the specific mental territory each competitor has claimed, what they're deliberately avoiding, and what space is sitting there unclaimed. Paste this prompt into a browsing-enabled AI (Claude, ChatGPT, or Perplexity with web access). Give it your product description and 3–5 competitor URLs. It visits each site, extracts their positioning language verbatim, builds a full competitive matrix, identifies the unclaimed gap, and drafts 3 H1 options that claim it — with one clear recommendation. Takes 20–30 minutes. The output is the foundational input to any SaaS marketing strategy — it comes before the homepage, the pitch, and the messaging guide.

1. Click "Copy prompt" above and paste it into Claude, ChatGPT, or Perplexity — ideally with web browsing enabled.
2. Give the AI your product description (one sentence), your target audience, and 3–5 competitor website URLs.
3. With browsing enabled, the AI visits each competitor site, extracts their exact headline and positioning language, and proceeds to analysis automatically.
4. Without browsing, the AI asks you to paste each competitor's homepage headline and subheadline — takes about 10 minutes to gather manually.
5. You'll receive the full matrix, an unclaimed gap analysis, and three H1 options with one clear recommendation.
6. Use the "what to do next" guidance at the end — the matrix is the input to your homepage rewrite, not the final deliverable.

From a real matrix for a project management tool entering a crowded category:

THE LANDSCAPE:
Five homepages, four distinct strategies. Linear owns engineering identity and speed. Jira owns enterprise scale. Asana and Monday.com are fighting over identical ground (visual, cross-functional, any team). ClickUp is playing all-in-one. What's missing: any explicit voice for early-stage or small engineering teams.

UNCLAIMED ANGLES FOUND:
· Stage specificity: no competitor speaks to where you are in your journey
· Team size: nobody says "for teams of X"
· "Right amount of process": everyone is either "simple" or "powerful"; nobody owns the tension between them

THE OPEN TERRITORY:
No project management tool explicitly owns the early-stage engineering team. The space between "GitHub Issues is enough" and "we need Jira" (typically 5-30 engineers, Series A or pre-PMF) is completely unaddressed. Linear gets close but positions on craft and identity, not stage or team size.

RECOMMENDED H1:
"Project management for engineering teams that want structure without the overhead."
Names the category, signals the audience, owns a differentiation angle no competitor has claimed.