Alternatives Page Writing Brief Template

Alternatives Page Brief (fill-in)

When to use: One brief per incumbent product: fill it in, agree it with sales or product, then hand it to the writer.

Alternatives page writing brief

One brief, one incumbent. If buyers leave two different products, write two briefs.

Shortlist summary for the writer

Next action

• Owner: [name] - action: [confirm triggers with sales notes] by [date]
• Writer: [name] - action: [first draft] by [date]
• Reviewer: [name] - action: fact-check every competitor claim against its source

Completion check

• Each switching trigger names where it came from.
• Every shortlisted option has an inclusion reason and a dated source.
• Migration limits cover both data export and the contract.
• The "who should stay" section names real reader types, not a token line.
• The CTA matches the top trigger, and any disclosure sits before the first link.

Switching Triggers

When to use: Find and rank the real reasons readers leave the incumbent, so the page opens on their problem, not yours.

Where triggers come from

• Sales calls and CRM notes: the reason a prospect gave for looking at you.
• Lost and won deal notes: what tipped the decision.
• Support and onboarding tickets: what new customers say they could not do before.
• Public reviews of the incumbent: repeated complaints, quoted with a link, not paraphrased into something stronger.
• Search results: the questions and angles that already rank for the query.

Common trigger types

Rank them

Keep the top 3. Rank by how often each appears in your own notes, not by how well your product answers it. Write each as one sentence in the reader's words: [trigger], source: [where you saw it].

Check how the query is framed today with the SERP Analyzer, and pull the close variants with Keyword Research.

Shortlist and Inclusion Rules

When to use: Decide which options make the page, in what order, and why, before anyone writes a word of copy.

Inclusion rules (agree them first)

• The option solves at least one of your top 3 triggers.
• It serves the same reader type as the incumbent.
• It is actively sold today, with a public pricing or plans page.
• You can source every claim from public material and put a check date next to it.
• Buyers name it: it appears in your deal notes or ranks for the query.

Shortlist size and order

• Aim for [3 to 7] options. Fewer, better-matched options beat a long list.
• Order by reader type or trigger, not by who pays you.
• If you include your own product, say so plainly and give it the same fields as the others.

Exclusion log

The log answers the reviewer who asks "why isn't X on the page?" and stops the list growing every month.

Use Competitor Analysis to see which rivals compete with you in search. For a scored roundup of a whole category, use the best software roundup scoring rubric instead.

Migration Limits: Data Export and Contracts

When to use: Tell the reader what switching really costs: what data leaves, what stays behind, and what the contract allows.

Data export checklist

Contract checklist

• Term: [monthly / annual]. Notice period: [days before renewal].
• Auto-renewal: [yes / no], and where the setting lives.
• Data access after cancelling: [read-only period, deletion date].
• Overlap: plan [2 to 4 weeks] running both tools during the move.

Writing rules

• Only state what the vendor's public docs say, with the date you read them.
• Tell readers to check their own contract. You can't see it.
• Name what will be lost or rebuilt. Readers trust a page that admits the hard part.
• Don't promise a migration service you don't offer.

Who Should Stay With the Original

When to use: Write the honest section that tells some readers not to switch, which makes the rest of the page believable.

Why this section matters

An alternatives page that says everyone should leave reads like an ad. Naming who should stay shows you know the incumbent and the reader.

Fill in 2 to 3 reader types

• Stay if [you rely on feature X], because [no shortlisted option matches it yet].
• Stay if [you are mid-contract with N months left], because [the switching cost outweighs the saving now].
• Stay if [your team is deeply trained on it] and [the trigger is minor for you].

Good stay reasons

• A real strength of the incumbent, sourced like any other claim.
• A migration limit from the previous section that hits this reader hardest.
• Timing: a renewal date is the natural point to switch, so wait for it.

Suggested wording

"[Product] is still the better fit if [reason]. If that's you, [practical tip for staying, such as a cheaper plan or a setting]."

CTA and Page Outline

When to use: Turn the brief into a page outline with a CTA matched to each trigger and a disclosure in the right place.

Page outline for the writer

1. H1: [Product] alternatives, plus who it is for.
2. Short answer: the top pick per reader type, in 3 to 5 lines.
3. Why people switch: the top 3 triggers.
4. Shortlist: one block per option, same fields each time.
5. Comparison table across the shortlist.
6. Migration limits: export and contract.
7. Who should stay with [Product].
8. How we chose: inclusion rules, sources, check date.
9. CTA and FAQ.

Match the CTA to the trigger

Disclosure and links

• If you make one of the options or earn from links, say so before the first link, close to the recommendation.
• The FTC says readers might not understand "affiliate link" alone, while "Paid link" next to the link should be adequate.
• Mark paid links with rel="sponsored", which Google prefers for paid placements.

Draft the title with the Comparison Article Title Generator, then hand the outline to the Content Brief tool for headings and terms.

Worked Example (fictional scheduling software)

When to use: A filled-in brief for an invented field-service scheduling app writing a page about leaving an invented incumbent.

Worked example: Corvane Schedule alternatives (Brindlepath)

Example only. Brindlepath, Corvane Schedule, Hollowmere Rota, Tessaline, Arkwell Jobs and all people, figures and dates are invented.

Why this brief works

• Each trigger names its source, so the writer doesn't guess.
• The photo and notes gap is stated, even though it makes switching look harder.
• A real stay case is included, which makes the page fair.
• The CTA answers the price trigger and the migration fear together.

Need the head-to-head page too? Use the comparison and versus article template for Brindlepath vs Corvane.