SourceFrame
ProductHow it WorksBrief TypesUse CasesFAQ

Brief typeCompare

Source Comparison Brief

Compares what your sources say — where they line up, and where they contradict each other.

The things being compared are the perspectives in your reading, not products. Use it when a vendor page, an independent review and a practitioner thread describe the same thing three different ways and you need to see the split.

Free plan · No card required

Source Comparison Brief

Comparing 4 sources

  • S1Vendor page
  • S2Independent review
  • S3Forum thread
  • S4Benchmark

Where sources agree

All four describe migration effort as the dominant switching cost source 1 source 2 source 3 source 4

Where sources differ

Both readings retained

The vendor page puts migration at days; the forum thread reports weeks source 1 source 3

Answers
“What do these sources agree and disagree about?”
Appears when
You choose Comparison mode and your wording points at the sources — with at least two usable sources.
Never does
Rank the sources, decide which one is right, or compare products against criteria. The disagreement is the finding.

Two kinds of comparison

Same evidence. Different thing being compared.

Look at what sits in the column headers. In a Source Comparison Brief the subjects are sources; in a Comparison Brief they are options.

Source Comparison Brief · this page

Compared subjects

  • S1 — Vendor page
  • S2 — Independent review
  • S3 — Forum thread
  • Where sources agree
  • Where sources differ
  • Tradeoffs
  • Open questions

No criteria, no matrix. The unit of comparison is a perspective.

Versus

Comparison Brief

Compared subjects

  • Linear
  • Jira
  • Shortcut
Evidence coverage for each option on each criterion
CriterionLinearJiraShortcut
Setup effortSupportedSupportedlimited — Limited evidence
Cost at scaleSupportedlimited — Limited evidencemissing — No source coverage
  • Tradeoffs
  • Open questions
Comparison Brief
Shared evidencesource 1source 2source 3source 4— one set of reading, two different questions about it

Inside the brief

Agreement, divergence, and what neither settles

Source Comparison BriefV1 · Primary

Overview

The four sources agree on what the switching cost is, and disagree by an order of magnitude on how large it is.

  • Migration effort, not licence cost, is the barrier every source names source 1 source 2 source 3 source 4
  • Timeline estimates range from days to weeks source 1 source 3

Where sources agree

Migration effort dominates the switching decision

All four sources treat data and workflow migration, not licence cost, as the real barrier source 1 source 2 source 3 source 4.

Small teams outgrow heavyweight configuration

Even the vendor page concedes that configuration depth is a cost below a certain team size source 1 source 2.

Where sources differ

Disputed:

How long migration actually takes

The vendor page says most teams are live in under three days, with no sample size given source 1; six practitioners in the forum thread report two to five weeks, mostly spent on historical tickets source 3.

Disputed:

Whether automation rules survive a move

The benchmark treats them as portable; the review says they are rebuilt by hand source 2 source 4.

Tradeoffs

A shorter plan or a safer one

Trusting the vendor timeline plans a shorter project; trusting the thread plans a safer one. Nothing in the set lets you price the difference source 1 source 3.

Open questions

  • Do the vendor and the thread describe teams of comparable size? Neither states it.
  • Is the benchmark measuring the same migration path?

Evidence gaps & caveats

2 OPEN
  • One of four sources is vendor-published advocacy.
  • The forum thread is assertion-only, and the only measured data comes from one benchmark.

Suggested next steps

  1. Add one measured migration case study to break the timeline disagreement.

What the sources are

  • source 1

    Vendor page

    Perspective · advocacy
  • source 2

    Independent review

    Perspective · balanced
  • source 3

    Forum thread

    Evidence · assertion-only
  • source 4

    Benchmark

    Evidence · data-heavy

Because the sources are the subject, what kind of source each one is becomes part of the reading.

Section order is fixed

  1. Overview
  2. Where sources agree
  3. Where sources differ
  4. Tradeoffs
  5. Open questions
  6. Evidence gaps & caveats
  7. Suggested next steps

How you get one

Point the comparison at your sources, and it routes here

Comparison mode covers both comparison types. Wording that points at the sources gives a Source Comparison Brief; wording that names options gives a Comparison Brief. It works from a web prompt or from tabs you captured yourself.

Capture path

Route in
  1. Capture 2+ sources
  2. Comparison mode
  3. Source Comparison Brief

Focus · wording that points at the sources

“Where do these pages agree and disagree about migration effort?”

Two or more usable sources are required — a comparison of one perspective isn’t a comparison.

If you get the other one

Source-pointing wording is read first, so “What do the Linear and Jira reviews say?” routes here even with products named. Wording that only names options routes to a Comparison Brief.

Comparison · “Compare Linear and Jira”
Comparison Brief
Comparison · “Where do these reviews disagree?”
Source Comparison Brief
Summary · “Summarize these”
Source Summary Brief

Evidence behavior

The brief never decides which source is right

Divergence is preserved

Conflicting readings sit side by side with their citations. Resolving them is your job — or the job of a source you add.

Source quality, by dimension

Each source shows what kind of source it is — vendor page, review, forum thread, benchmark — and, separately, its perspective and its evidence depth. Neither is a score.

AI chats don’t count as a voice

A captured conversation is cited as AI-generated context, never as an independent source.

Thin sets look thin

When only one source speaks to a point, that is recorded in Evidence gaps & caveats rather than read as consensus.

What you can do next

From this brief
  1. Source Comparison Brief
each move below starts here
    1. Add sources
    2. variant 2

    The most useful move here: add the source that could break a disagreement, and read the updated variant next to the original.

    1. Turn into…
    2. Recommendation Brief

    When you have to act despite the disagreement, the recommendation inherits it — and states its status accordingly.

    1. Ask · Sources only

    Interrogate one side of a disagreement without letting AI knowledge fill the gap.

From Source Comparison Brief

  • Different comparison

    Comparison Brief

    Same mode, but the subjects are named options assessed against criteria — not source perspectives.

  • If themes matter more

    Source Summary Brief

    Reports the same set as themes and tensions rather than a point-by-point agreement map.

  • Use it for

    Compare what sources say

    The job, worked through: capturing conflicting sources and reading the split.

See exactly where your sources stop agreeing.

Free plan · No card required