The Snoop reference
From a signal to a sound decision.
A useful competitor brief separates what was observed, what it might mean, and what to test next. This is Snoop's intended evidence standard and a practical web and app research checklist—not a claim that every step is already automated.
01 / Start with a decision
Define the competitor, market, audience, and decision before collecting signals. A pricing decision needs comparable plans and billing terms; an app positioning decision may need store locale, version history, and recent review language. State the time window so old information is not presented as a new move.
02 / Keep the source attached
- Record the original public URL, publisher, capture date, and relevant excerpt or screenshot.
- Separate publication time from observation time. Record locale, region, currency, plan, app version, and other comparison conditions.
- To claim a change, preserve comparable before-and-after evidence. With only one snapshot, describe the current state—not a confirmed change.
- Use public sources that are permitted to be accessed. Mark unavailable, stale, or incomplete evidence instead of inventing a fact.
03 / Separate three kinds of statement
- Observation
- What a source directly supports.
- Interpretation
- A possible explanation, with alternatives and uncertainty.
- Recommendation
- A proposed next step for the user's context, not a fact or guaranteed outcome.
Two pages repeating one announcement are not independent confirmations. A confident recommendation cannot repair weak evidence. Explain what would change the interpretation.
04 / A worked example
Hypothetical example—not a real company or customer result: two saved pricing-page snapshots show a new team plan and admin-controls section. The observation is the page change, provided the region and billing terms match.
One interpretation is an increased focus on team buyers. Alternatives include a packaging test or clearer communication of an existing offer. The change alone does not prove higher revenue, adoption, or a successful strategy.
A reasonable next step is to check release notes and speak with relevant customers before changing your own packaging. Record the finding, uncertainty, and what would disconfirm the interpretation.
05 / Make the brief reviewable
Public data can be delayed, sampled, region-specific, edited, or removed. Reviews may not represent all customers; rankings do not establish revenue. Recheck consequential claims against the original source. This framework is a product principle, not a certification or service-level guarantee.
- Decision and scope: which question is this brief answering?
- Evidence: can a reviewer open the source and reproduce the comparison?
- Freshness and confidence: when was it checked, and what is missing?
- Implication: is reasoning labeled separately from facts?
- Next action: who will validate it, and what result would change the decision?
