Andrea Reyes

Competitor messaging teardown from their pasted homepage copy

Compares your homepage copy with competitors' pasted copy: who each targets, what they promise, shared table stakes and the open ground left.

At a glance

Best for: Founders and marketers in a crowded category who suspect their homepage sounds like everyone else's and want evidence before rewriting.
Tested on: Claude · Opus 5.5
You fill in: competitor_countmarketcompetitor_copyour_copy
You get: Table Who it's for Main promise Proof Tone Repeated words A "teams" "Never take meeting notes again" "Trusted by 40,000 teams" simple, relieved,… (full result below)

Prompt

Here is homepage copy from {{competitor_count}} competitors in {{market}}, pasted as-is:

{{competitor_copy}}

And ours:
{{our_copy}}

Do a messaging teardown. Only use what's in the text above; don't guess at anyone's pricing, traction or features beyond it.

1. Table, one row per company including us: Who they say it's for | Main promise | Proof offered | Tone (3 words) | Words or phrases they repeat.

1. Shared claims: promises two or more companies make. These are table stakes and won't set anyone apart.

1. Open ground: a customer, problem or promise none of them claims clearly.

1. Our copy, honestly: where ours blends in, where it's stronger, and the line a visitor could swap onto a competitor's page without anyone noticing.

1. Three directions for our headline that take the open ground, each with the risk that comes with it.

Be specific, and quote the copy when you make a point.

Fill in

{{competitor_count}}: How many competitors you've pastede.g. 3
{{market}}: The category you compete ine.g. AI meeting note-takers for small teams
{{competitor_copy}}: Their above-the-fold copy, labeled by companye.g. Competitor A: Never take meeting notes again...
{{our_copy}}: Your own homepage copye.g. AI-powered meeting notes for modern teams...

Example input

competitor_count: 3
market: AI meeting note-takers for small teams
competitor_copy:
Competitor A: "Never take meeting notes again. A joins your Zoom, Meet and Teams calls, transcribes every word, and sends a summary to everyone in minutes. Trusted by 40,000 teams. Start free."
Competitor B: "Meetings that move work forward. B turns every conversation into action items, assigns them to owners and syncs them to Asana, Jira and Linear. Built for fast-moving teams. SOC 2 Type II."
Competitor C: "Your AI meeting assistant. C records, transcribes and summarizes your meetings with 99% accuracy in 30+ languages. Search every meeting you've ever had. Free forever plan."
our_copy: "Minutely: AI-powered meeting notes for modern teams. Automatically transcribe, summarize and share your meetings so your team can focus on what matters. Try it free."

1210

Generated Outputs (1)

3 hours ago

Claude

Opus 5.5

3 hours ago

Generated Output

1. Table

| | Who it's for | Main promise | Proof | Tone | Repeated words |
|---|---|---|---|---|---|
| A | "teams" | "Never take meeting notes again" | "Trusted by 40,000 teams" | simple, relieved, confident | "every," "minutes" |
| B | "fast-moving teams" | "Meetings that move work forward": action items with owners | Asana, Jira, Linear sync; "SOC 2 Type II" | brisk, operational, businesslike | "every," "work" |
| C | anyone ("your") | record, transcribe, summarize, search | "99% accuracy," "30+ languages" | technical, feature-list, broad | "every," "meetings" |
| Us | "modern teams" | transcribe, summarize, share; "focus on what matters" | none | generic, soft, familiar | "meetings," "team" |

2. Shared claims (table stakes)

• Transcription and summaries: A, C and us.

• "Teams" as the audience: A, B and us.

• Free to start: A ("Start free"), C ("Free forever plan"), us ("Try it free").

• "Every": A "every word," B "every conversation," C "every meeting." Completeness is assumed.

3. Open ground

• Decisions. Nobody uses the word. B covers action items; no one promises "know what was decided."

• A specific kind of meeting or team. No one names client calls, sales calls, 1:1s or standups.

• The people being recorded. Apart from B's "SOC 2 Type II," no one addresses guests' comfort or consent.

4. Our copy, honestly

• Blends in: entirely. "AI-powered meeting notes for modern teams" could head any of the three pages.

• Stronger: nowhere yet. We're the only one of the four with no proof at all: no customer count, integration or accuracy claim.

• Swappable line: "so your team can focus on what matters." It would sit on A's page unnoticed, and on most SaaS pages.

5. Three headline directions

1. "Know what was decided, even in meetings you missed." Takes the decisions gap. Risk: the product must reliably pull out decisions; one missed decision in a summary breaks the promise.

1. "Meeting notes for client-facing teams: every call summary ready to send." Takes the specific-team gap. Risk: narrows the audience, and only works if the product really serves that team better.

1. "A note-taker your clients won't mind." Takes the consent gap. Risk: needs a concrete feature behind it (a clear notice to guests, say), or it's an empty claim, and it raises a worry some visitors didn't have.

Whatever you choose, add one real piece of proof under the headline. Right now we're the only page asking for trust without offering any.

Why it works

Working only from pasted copy keeps the analysis honest: the model compares what visitors actually read, not what it half-remembers about real companies. The fixed table columns make differences visible at a glance. Naming shared claims as table stakes is the key insight most teardowns miss: if everyone says "transcribe and summarize," saying it better won't help. The swappable line test is blunt and effective, and asking for the risk with each direction stops the model selling you a repositioning without the downside.

When not to use it

Homepage copy is only one signal. It won't show you pricing pages, onboarding or what customers say in reviews, so don't rewrite your positioning from this alone. If your market has one dominant player, compare against that player's customers' complaints instead. Always paste copy you've gathered yourself rather than asking a model to recall competitors' sites.

Comments (0)

No comments yet. Be the first to share your thoughts!