Competitor Switch Campaign Template
Four documents and four sheets built on the complaints a named competitor's customers publish, with a provable fix behind every angle.
Free download · No account needed
Message Angle by Complaint
[Competitor] — one row per candidate theme
A complaint theme only becomes a message angle after clearing two gates in order: enough customers say it, and there is a specific, checkable fix behind it.
| Theme | Share of themed complaints | Gate 1: frequency | Gate 2: provable fix | Status |
|---|---|---|---|---|
| — | required | required | required | — |
| — | required | required | required | — |
| — | required | required | required | — |
| — | required | required | required | — |
A theme can clear gate one and still die at gate two. The fix has to be something a reader can check, not a claim that the product is generally better.
Most switch-campaign advice is a sequencing playbook: which trigger to use, how many touches, and a warning not to bash the competitor by name. None of it says which complaints are real enough to build a message on, which is why so many switch emails read as a generic "we're better" pitch wearing a trigger. This pack starts from complaints the competitor's own customers already published, the same evidence a comparison page sources its claims from, and turns them into message angles only when two conditions both hold.
The first condition is frequency: a complaint theme has to clear a stated floor of the logged complaints before it counts as a pattern instead of one loud customer. The second is a provable fix, a specific and checkable answer the sending company actually has, not a claim of being generally better. On the worked campaign in this pack, five candidate themes cleared the frequency floor and two still died at the second gate, because the sending company had no real advantage on either one.
The remaining documents exist because the objection that ends a switch conversation is the cost of migrating, not a feature gap. Switch Guide lays out the real export mechanics and a timeline drawn from completed migrations rather than an estimate. Target Account List tags an account to an angle only where a public signal supports the tag. Performance then checks whether the tagged angles actually outperform a generic send, the way lost deal pattern analysis checks a hypothesis against real records instead of a hunch.
What you get
Campaign Scope
The one competitor this campaign runs against, which review platforms count as evidence, the sending identity for every message, and who signs off a comparative claim before it ships.
Complaint Source Log
One row per complaint pulled from public reviews, carrying the platform, the URL, the date, the reviewer's segment when disclosed, and the exact wording, so a theme can be traced back to real evidence.
Message Angle by Complaint
Every candidate theme run through both gates: a frequency floor, then a provable fix. The sheet keeps the kill reason for a dead angle so it never resurfaces on the same evidence.
Target Account List
Accounts identified from public signals and scored against your ICP, tagged to a specific angle only when a reviewer at a matching segment raised that exact complaint. Everything else runs a default sequence.
Campaign Brief
The objective, the shipped angles pulled straight from the gate results, the sequence cadence, and the checkpoint for pausing an angle that underperforms.
Switch Guide
The real migration mechanics: what the competitor's export contains field by field, the cutover sequence, and a timeline drawn from completed migrations instead of an estimate.
Migration FAQ
Answers to the questions that come up once the conversation reaches switching cost: historical data, downtime, the rollback plan, and how much of the work falls on the prospect's own team.
Performance
Sent, replied and reply rate per angle, with the untagged default sequence kept alongside so you can see whether a complaint-grounded angle actually converts better, rather than assuming it does.
How it works
- 1
Name the competitor and the sources
Open in River or download the blank pack, then set the one competitor this campaign runs against and where their customers complain in public: G2, Capterra, TrustRadius, or a community forum.
- 2
Log complaints, then gate the themes
Every complaint gets logged with its source before it becomes a theme. Each theme then has to clear a frequency floor and a provable-fix gate before it becomes a message angle.
- 3
Tag accounts, don't guess
Accounts get tagged to a shipped angle only when a public reviewer at a matching segment raised that exact complaint. Everything else runs the default sequence, on purpose.
- 4
Send, then compare tagged against default
Launch the sequence, log replies by angle, and check whether the complaint-grounded angles actually outperform the generic send rather than assuming the theory holds.
Frequently asked questions
Is it risky to name a competitor in the campaign?
Naming them is not the risk. The FTC's own comparative-advertising policy encourages naming competitors and supports brand comparisons where the basis is clearly identified. The risk is a claim with no basis, which is exactly what the provable-fix gate exists to stop before a message ships.
Does this apply CAN-SPAM rules to a cold sequence aimed at non-customers?
Yes, deliberately. The CAN-SPAM Act covers commercial email with no exception for business-to-business messages. Campaign Scope sets the sending identity, and Launch and Track the Sequence checks every message against it before it goes out.
What if none of our complaint themes survive both gates?
Then the honest output is fewer angles, not a weaker angle shipped anyway. The worked campaign in this pack shipped three of five candidate themes; the other two cleared the frequency floor and still had no provable fix behind them, so they were killed rather than softened into a claim nobody could check.
What format are the downloaded files?
The four documents come as .docx and the four sheets as .csv, opening natively in Word, Pages, Google Docs, Excel, Numbers and Sheets. The download needs no account, and the sheets arrive carrying the worked campaign rather than empty.
How is this different from a general competitor teardown?
A competitor teardown or review mining analysis finds and ranks the complaint themes. This pack assumes a theme is already known or gets logged fresh, then turns it into a target list, a gated message angle, and a migration guide built to remove the switching-cost objection specifically.
What does Edit with AI actually do?
It installs the pack as a private space and primes River to fill it in from what you send. The first useful output is usually the Complaint Source Log, built from the competitor's public reviews inside the window you set.
Build a switch campaign on complaints their customers already published
Name the competitor and where their customers complain in public. The first pass logs the complaints, gates the themes, and shows you what has a provable fix behind it.
Edit with AI