# SaaS alternatives page comparison brief

Blank template and worked fictional comparison

Use the blank brief to plan a SaaS alternatives page and the worked fictional comparison to see how one buyer scenario changes the recommendation. Replace the example details before sharing. This manual file does not collect data or approve conclusions.

Pack version 1.0 · 15 September 2026. Template version 1.0.

Guide: https://rankecho.io/resources/fix/alternatives-page

## Part 1 — Blank template

# SaaS alternatives-page comparison brief

Manual template - version 1.0. Complete the required fields before drafting. Keep unresolved facts visible; do not turn a missing answer into a product limitation.

## 1. Page control
- Working title [required]:
- Canonical URL [required]:
- Incumbent or category being compared [required]:
- Publisher and commercial relationship to every option [required]:
- Market, currency, language, and buyer region [required]:
- Product, pricing, security, or legal facts that require specialist verification:
- Comparison checked through [YYYY-MM-DD, required]:
- Next scheduled review and event-based triggers:

## 2. Buyer decision
- Primary buyer and team size [required]:
- Trigger for evaluating alternatives [required]:
- Job the buyer needs to complete [required]:
- Must-have requirements [required]:
- Preferences:
- Disqualifiers [required]:
- Switching constraints: contract / migration / data / integrations / retraining / security / procurement
- Budget basis: first month / first year / three years / quote comparison
- Direct answer the page owes [required]:

## 3. Missing-coverage diagnosis
- Evidence of demand: sales question / support request / on-site search / win-loss note / documented query research / other
- Existing canonical page:
- What the current page answers:
- Material decision questions it leaves unanswered:
- Why refresh the existing page or create a distinct page [required]:
- Sampled search or AI observations, if any, with query, surface, date, and limits:
- Competing explanations besides missing comparison content:

## 4. Candidate-selection rule
- Candidate universe [required]:
- Inclusion rule chosen before evaluation [required]:
- Exclusion rule and excluded candidates with reasons [required]:
- Direct alternatives included:
- Adjacent, build, self-host, or stay-with-current options included when useful:
- Paid placement, affiliate, partner, or publisher interest disclosed:

## 5. Shared decision criteria
| Criterion | Why it matters to this buyer | Exact question asked of every option | Evidence needed | Disqualifying result | Weight, if used |
| --- | --- | --- | --- | --- | --- |
| [Criterion] | [Buyer consequence] | [Same question] | [Source or test] | [Rule] | [Optional] |

Rules:
- Choose criteria from the buyer's decision, not from the publisher's strongest feature list.
- Ask every candidate the same material question and apply the same pass, fail, and unknown rules.
- Keep a criterion unweighted unless the weighting rule is explained and applied consistently.

## 6. Claim and evidence register
| Candidate | Exact claim | Evidence state | Source or test record | Checked | Plan/version/region | What it supports | What remains unknown | Refresh trigger |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| [Option] | [Claim] | Verified present / Verified absent / Not found / Untested / Conflicting / Not applicable | [Exact URL or test] | [YYYY-MM-DD] | [Scope] | [Narrow support] | [Unknown] | [Event/date] |

Source rules:
- Prefer the source that governs the fact: current pricing, product documentation, support, security, legal terms, or a recorded direct test.
- Record the exact page, checked date, plan, version, region, billing basis, and test conditions that qualify a claim.
- Attribute third-party experience to that source; do not silently convert it into a product specification.
- Use Verified absent only when the narrow absence is explicitly documented or demonstrated by a defined test.
- Use Not found in reviewed sources when documentation is silent. List the sources checked and ask the vendor.
- Use Untested when no recorded hands-on test supports an experience claim.

## 7. Comparison table
| Buyer criterion | Incumbent | Publisher's product | Alternative A | Alternative B | Decision note |
| --- | --- | --- | --- | --- | --- |
| [Same criterion] | [Fact + state] | [Fact + state] | [Fact + state] | [Fact + state] | [Why it matters] |

## 8. Fit, no-fit, and switching guidance
For every candidate:
- Strong fit when:
- Do not choose when:
- Verified strengths:
- Material trade-offs:
- Switching work and risk:
- Price basis and excluded costs:
- Unknowns to resolve before purchase:
- Exact next verification step:

## 9. Public methodology
- Buyer scenario and date:
- Candidate inclusion and exclusion rule:
- Shared criteria and any weighting:
- Source hierarchy:
- Hands-on tests completed and conditions:
- Meaning of every evidence state:
- Publisher interest, compensation, or affiliate relationship:
- Limits: what was not tested, unavailable, private, quote-only, or likely to change:

## 10. Publish and refresh check
- Opening answer names fit and decisive trade-offs: Yes / No
- Candidate set and publisher interest disclosed: Yes / No
- Same criteria and evidence states applied to every option: Yes / No
- Material claims have dated sources and scope: Yes / No
- Unknown, untested, conflicting, and quote-only facts remain visible: Yes / No
- Pricing includes currency, unit, interval, minimum, and checked date: Yes / No / Not applicable
- Comparison table is understandable in visible page text: Yes / No
- Canonical, indexability, crawler policy, internal links, and schema checked: Yes / No
- Product, legal, security, or compliance verification completed where needed: Yes / No / Not needed
- Next review date and event triggers recorded: Yes / No

Publication decision: Ready / Not ready
Decision date:
Unresolved blockers:

## Part 2 — Worked fictional comparison

### What does a fair filled comparison look like?

Everything in this example is fictional. AtlasDesk, RelayBoard, CaseNest, and OpenQueue are invented products; the buyer, plans, features, prices, documentation, contract timing, test, and implementation estimates are synthetic. They do not describe RankEcho, a customer, a real vendor, a market benchmark, or field research.

Fictional scenario, checked September 11, 2026: a 40-agent B2B support team needs email and chat, SAML SSO, EU data hosting, exports that preserve ticket IDs and timestamps, a go-live within 30 days, and a first-year ceiling of USD $30,000. RelayBoard is the fictional publisher. Candidates were included because they were the incumbent or met the first three requirements in the synthetic discovery record. The same seven criteria are applied below.

| Buyer criterion | AtlasDesk (fictional incumbent) | RelayBoard (fictional publisher) | CaseNest (fictional alternative) | OpenQueue (fictional alternative) |
| --- | --- | --- | --- | --- |
| Required channels: email and chat | Documented on current plan | Documented on Team plan | Documented on Managed plan | Documented in core package |
| SAML SSO for 40 agents | Enterprise quote required | Included on Team plan | Included on Managed plan | Community plug-in documented; no support commitment found |
| EU data hosting | Documented for the current contract | Documented on Team plan | Documented on Managed plan | Possible through self-hosting; buyer owns configuration |
| Export preserves ticket IDs and timestamps | Documented CSV export | Verified in a synthetic migration test of 500 tickets | Documented export; no scoped test completed | Not found in the reviewed fictional documentation |
| Go live within 30 days | Already live; no migration | Fictional scoped plan: 21 days | Fictional implementation guide: 8-12 weeks | No documented estimate; untested by the buyer |
| First-year cost for 40 agents | Current total is confidential and excluded from the public comparison | Synthetic price: USD $24,000 billed annually; tax excluded | Quote required; amount unknown | USD $0 synthetic license price; hosting, support, labor, and migration unknown |
| Material switching constraint | Staying avoids migration; renewal notice is due in 45 days | Legacy internal-note migration remains unverified | Timeline misses the buyer's 30-day requirement | Requires internal infrastructure and on-call ownership |

### Who fits, who does not, and what remains unknown in the example?

On the synthetic evidence, RelayBoard is the strongest fit for this one buyer because it meets the stated requirements, synthetic budget, and 30-day deadline. That conclusion is conditional on a migration test for legacy internal notes. CaseNest misses the required timeline; OpenQueue has unresolved export, timing, and total-cost questions; staying with AtlasDesk remains credible if avoiding migration matters more than the enterprise-only SSO route.

The example does not declare a universal winner. A buyer that requires private-cloud controls and accepts a longer project could prefer CaseNest. A buyer with infrastructure staff and a self-hosting requirement could prefer OpenQueue. The conclusion changes when the buyer, rule, facts, or unknowns change.

| Option | Strong fit when | Do not choose when | Unknowns before decision |
| --- | --- | --- | --- |
| AtlasDesk (fictional incumbent) | The current workflow is acceptable and avoiding retraining or migration is worth more than changing tools. | The enterprise-only SSO route or current contract no longer fits the team's constraints. | The current first-year renewal total is confidential, so no public price comparison is possible. |
| RelayBoard (fictional publisher) | A 40-agent cloud team needs the stated channels, SSO, EU hosting, a tested core export, and a scoped sub-30-day migration within the synthetic budget. | The buyer needs self-hosting, a voice contact center, or proof that legacy internal notes migrate intact. | Legacy internal-note migration is unverified; the buyer must test it before signing. |
| CaseNest (fictional alternative) | A team values managed enterprise controls and can accept an 8-12-week implementation. | The 30-day deadline is firm or the team needs a public self-serve price before evaluation. | The quote amount and untested export behavior remain unresolved. |
| OpenQueue (fictional alternative) | The buyer requires self-hosting and has staff to operate, secure, update, and support the system. | The team wants a managed service, a bounded implementation date, or a known first-year total. | Export preservation, implementation time, support cost, hosting cost, and migration labor remain unresolved. |

## Use this pack

1. Save a copy and complete Part 1 with your own buyer, candidate rule and evidence.
2. Use Part 2 as a teaching example, preserving missing data and unresolved review states.
3. Duplicate a criterion, evidence or option record for additional entries. Check sources, comparisons and approvals before sharing your completed version.

Next workflow: [Evaluate the Fix Engine](https://rankecho.io/product/fix-engine). Inspect a [sample fix](https://rankecho.io/sample-fix) first. Full-page writing or refreshing is a separate [content add-on](https://rankecho.io/pricing/content), not included with the visibility subscription.