A request such as “please research our competitors” is too open to price or evaluate fairly. One provider may review five websites, another may analyze paid ads, and a third may deliver a market report. Each can satisfy the sentence while answering a different question.
A useful brief makes the purchase comparable. It tells a researcher what decision is pending, whose expectations matter, which evidence is in scope, what the final document must help someone do, and what the research cannot establish. This guide is for a founder, marketer, or operator preparing to buy an external report. It is different from a competitor website analysis checklist, which explains how to inspect sites once the research question is defined.
Write the decision before the research request
Complete this sentence before listing competitors:
We need to decide [action] for [buyer or market] before [date, launch, or spend], and the uncertainty is [specific question].
For example: “We need to decide whether to publish a starting price for our three core services before the September website revision, and the uncertainty is how nearby competitors explain scope, exclusions, and the next step.” That question tells the researcher what to compare and gives the business a way to accept the result.
Do not turn the brief into a disguised request for a guaranteed outcome. Public research can describe visible positioning, pages, offers, ads, proof, and paths. It usually cannot reveal a competitor’s conversion rate, profitability, internal costs, or private test results. The brief should preserve that boundary from the first conversation.
Define the buyer, market, and comparison roles
State where the decision applies: geography, language, customer segment, service category, price context, device context, and research date. “Our competitors” is not a stable set without those qualifiers.
Then define why each comparison belongs:
- Direct competitor: sells a similar solution to the same buyer.
- Search competitor: appears for an important query even if its business model differs.
- Substitute: solves the same problem through software, DIY, a marketplace, or another route.
- Expectation setter: shapes what buyers now consider clear, safe, fast, or convenient.
Ask for the selection rule as well as the names. If a researcher proposes a different set, the brief should require an explanation of what each addition contributes and which original role it replaces. The Ahrefs competitive-analysis guide is a useful first-party reference for separating direct competitors from sites that share search visibility; the role labels here are a practical adaptation for buying a report, not an industry standard.
Set the evidence standard
Specify what counts as an observation. A strong brief asks for the source URL, page or channel, review date, market context, and a short capture or excerpt for material findings. It also asks the researcher to separate what was seen from what is inferred.
Use a simple record:
- Observation: what is visibly present, such as a “book now” button above the first service section.
- Interpretation: what that pattern may make easier or harder for the buyer.
- Confidence: high, medium, or low, with the reason.
- Action: the smallest change or test worth considering.
Do not ask a vendor to report estimated competitor traffic as if it were a private analytics export. Semrush explains that its Traffic & Market data uses external clickstream and modeled sources, while Google Analytics uses data collected directly from the site owner’s implementation. That distinction is a useful requirement for any brief that mentions traffic, audience, or demand estimates.
Define freshness in a way the decision can use: “review public pages during the two weeks before the launch brief is delivered” is more useful than “use current data.” If a page changes during the work, require the researcher to note the change instead of silently mixing review dates.
Score whether the brief is ready to send
Use this 20-point scorecard before requesting proposals. Give each check 0, 1, or 2 points: 0 means missing, 1 means partly defined, and 2 means specific enough for two providers to scope the same work. This is a buying aid created for this guide, not a market benchmark.
| Check | 0 points | 1 point | 2 points |
|---|---|---|---|
| Decision | “Research competitors” | A broad goal with no deadline or choice | One action, audience, uncertainty, and decision date |
| Comparison fit | No market or selection rule | Names a few brands without roles | Market context, roles, and inclusion rule are stated |
| Evidence plan | No sources or freshness requirement | Requests screenshots or links without context | Requires dated sources, observations, confidence, and limits |
| Usable output | “Send a report” | Format is named but use is unclear | Sections, action order, owners, and acceptance test are defined |
| Boundaries | Access and claims are unrestricted | Some exclusions are implied | Public-only boundaries, privacy limits, unknowns, and claim rules are explicit |
A score of 16 to 20 means the brief is likely ready for comparable proposals. A score of 10 to 15 means fix the missing fields before buying the broadest package. A score below 10 usually means the business is still choosing the question; run an internal review or a small discovery step first. Those cutoffs are deliberately practical, not a guarantee of report quality.
Specify the deliverable someone can use
Ask for an output that survives the handoff. A compact brief can require:
- a one-page answer to the decision;
- a comparison table with evidence links and review dates;
- the strongest patterns and meaningful counterexamples;
- a ranked action order with confidence, effort, dependencies, and owner;
- an assumptions and unknowns section;
- a source register your team can retain and revisit.
Define acceptance before work starts. For example, the report is accepted when it covers the agreed competitor roles, includes a source for every material observation, answers the stated question, labels estimates and unknowns, and gives the implementation owner a first action. “A polished deck” is not an acceptance test.
Readable structure is part of usability. WCAG 2.2 Success Criterion 2.4.6 states that headings and labels describe topic or purpose. Apply that principle to the deliverable: headings should name the decision or finding, tables should label their dimensions, and links should make their destination clear. A report that cannot be navigated is harder to implement even when its research is sound.
Add claim and access guardrails
State what the researcher may inspect and what they must not do. Public pages, public ads, public listings, and publicly available reviews may be in scope. Logging into an account, submitting another business’s form, placing a test order, scraping restricted content, or collecting unnecessary personal data should be out of scope unless there is a separately documented and lawful reason.
Ask for claims that are accurate enough to reuse. The FTC’s Advertising FAQ for Small Business explains that advertising must be truthful and non-deceptive and that advertisers need evidence to support their claims. Your brief does not turn a competitor observation into proof of performance. It should instead require language such as “the page states,” “we observed,” “this may reduce uncertainty,” or “this remains unverified.”
Also state who owns the report, source register, captures, and working files, how long the research window lasts, what happens when scope changes, and who can approve the final answer. These details keep a useful report from becoming an inaccessible vendor artifact.
Worked example: repair a weak brief
Imagine a home-services company that wants to improve quote requests. Its first brief says: “Analyze the top competitors and tell us how to get more leads.” That scores 2 out of 10 on the five checks because it has a broad goal but no market, evidence, output, or boundary.
The repaired brief says: “We need to decide which changes to test on our residential HVAC quote page before the October campaign in our service area. Review two nearby direct competitors, one search competitor, and one substitute. Compare service-area clarity, emergency versus replacement paths, proof near the request action, price or financing explanation, fields required, stated response expectation, mobile behavior, and confirmation language. Record dated public URLs and separate observations from inferences. Deliver a two-page summary, evidence table, ranked three-step action order, unknowns, and owner handoff. Do not infer conversion rate, lead quality, or revenue.”
That revised version scores 10 out of 10 on the readiness checks and gives two providers a much better chance of pricing the same job. It still does not promise that the recommended page changes will increase leads. The business must test its own customer path and measure qualified requests after implementation.
Choose the smallest useful buying path
- Is the decision specific? If no, interview customers or review internal evidence before commissioning external research.
- Can the team answer most of it internally? If yes, buy outside judgment only for the blind spot that remains.
- Does the brief score at least 16? If no, repair the scope or request a smaller proof step.
- Does the proposal match the brief? If no, ask for a written change or remove the proposal from comparison.
- Is the action already clear and recurring visibility is the real need? If yes, compare a one-time competitor report with competitor monitoring instead of buying another broad diagnosis.
Use the free competitor scan when you need a lower-friction signal that a meaningful gap exists. Use a paid report when the decision is real and the team needs a source-backed priority order. The agency-selection scorecard is the next step when several providers can answer the same brief.
Primary and first-party sources used in this guide
- Google Search Central, Creating Helpful, Reliable, People-First Content, for original analysis, clear authorship, and adding value beyond rewriting other sources.
- Google Search Essentials, for descriptive, crawlable, people-first site content and honest search expectations.
- Semrush, Using Traffic Analytics Data for Competitive Research, for the difference between external competitive estimates and a site owner’s analytics.
- W3C Web Content Accessibility Guidelines 2.2, for headings and labels that describe topic or purpose in a usable deliverable.
- Federal Trade Commission, Advertising FAQ’s: A Guide for Small Business, for truthful, non-deceptive, evidence-backed claims.
- Ahrefs, Competitive Analysis: The Lean Guide, for separating direct competitors from search competitors and documenting comparison-set rationale.
A good competitor research brief does not make the market certain. It makes the purchase and the remaining uncertainty visible. If the document names the decision, evidence, limits, output, and owner, proposals become easier to compare and the final report has a better chance of changing what the team does next.