1. Start with the decision
“Review competitor pricing” is not an acceptable scope. An executable question names the decision, subjects, and time boundary: Should we keep a free tier? Which plan should include team permissions? Is our annual discount outside the market range?
A precise question keeps collection stable. Without one, a five-competitor review can expand into twenty companies and move from public prices into private sales quotes—producing a long document that still cannot support a decision.
- Decision: what should this analysis change or confirm?
- Subjects: which products are direct competitors, substitutes, or reference brands?
- Time: which access date or observation window applies?
- Boundary: are regional prices, taxes, promotions, and sales quotes included?
2. Freeze a comparable field contract
Prices are comparable only when their billing units align. Per-seat monthly pricing, annual contracts expressed as a monthly average, workspace pricing, and usage pricing cannot share one column without context. Plan names are not equivalents either: one product’s Pro may map more closely to another product’s Business tier.
Define the field table before collecting pages. Give every field allowed values, a missing-value convention, and a normalization rule. That limits ad hoc judgment during execution and lets reviewers inspect why a value changed.
| Dimension | Frozen rule | Failure signal |
|---|---|---|
| Price | Keep original currency, period, and tax context | A number survives but its billing context disappears |
| Unit | Label seats, workspaces, and usage separately | Different units are ranked directly |
| Plan | Map by target user and key capabilities | Plans align only by name |
| Source | Store original URL, access time, and page location | A screenshot exists without a visitable link |
| Unknown | Mark unpublished, quote-only, or unconfirmed values | Guesses fill every blank |
3. Capture evidence context, not just numbers
Each price record should include the original URL, access time, original page wording, and a necessary screenshot. If a regional redirect, login wall, dynamic toggle, or promotion affects the page, capture that access condition too.
A screenshot shows what was visible at the time; a URL lets a reviewer return to the source. Neither replaces the other. Pages change, so the delivery must keep access dates and avoid presenting an older screenshot as a current price.
- Prefer the company’s pricing page, help center, or public contract documentation.
- Use secondary aggregators to discover leads, not to override a primary source.
- When several pages support one claim, state the role of each source.
- Record access failures and conflicting statements as exceptions.
4. Normalize without flattening meaningful differences
Normalization should make comparison possible, not force every product into the same business model. You may calculate a monthly equivalent for an annual plan, but retain the original annual total and formula. You may map plans to small-team or enterprise tiers, but show the mapping criteria.
Treat usage tiers and custom quotes as business-model differences rather than empty cells. For the decision, that structural difference may matter more than whether one visible price is higher than another.
5. Deliver facts, inferences, and unknowns separately
“The Business plan displays this annual price” can be a page fact. “The company uses permission controls to drive upgrades” is an inference from packaging differences. “The final Enterprise contract price” may remain unknown. Writing all three in the same voice hides their reliability.
A recommendation should cite the facts that support it and name its assumptions. If you recommend placing team permissions in a higher plan, show which competitors use a similar boundary, whether the sample is sufficient, and whether your own customer evidence supports the move. Competitor evidence reduces uncertainty; it does not replace customer evidence.
6. Check these eight items before delivery
A review-ready pricing brief lets someone who did not collect the data verify key figures and understand how the recommendation was formed.
- The competitor set and selection rationale are confirmed.
- Region, currency, tax, billing period, and team size are explicit.
- Every key number has an original URL and access time.
- Original wording and normalized values both remain visible.
- Plan mapping has explicit criteria.
- Conflicts, missing data, quote-only fields, and access failures are separate.
- Facts, inferences, and unknowns use distinct labels.
- Recommendations return to evidence and state the remaining internal validation.