Competitor pricing monitoring: the complete evidence-first guide

Competitor pricing monitoring is the repeated comparison of the full commercial offer—not just the headline price. A reliable record tracks prices, billing periods, value metrics, tiers, included usage, entitlements, trials, regional terms, and calls to action, then preserves the source and old/new states for review.

What this guide covers

• the commercial fields worth monitoring;
• how to create a stable pricing baseline;
• how to distinguish a price move from a package move;
• review rules that stop layout churn from becoming an alert;
• a copyable pricing-change record.

EXVIV corpus snapshot, August 4, 2026: 93 public pricing sources were in the reviewed public source map. That count describes coverage, not 93 fully comparable price lists; calculators, quote-led pages, regional variants, and incomplete public terms still require field-level review.

Pricing and packaging are different

Price is what the buyer pays. Packaging is the collection of value, limits, and access conditions attached to that payment.

A plan can hold at $20 per month while becoming materially more expensive because included usage falls, an essential feature moves up a tier, overages appear, or annual billing becomes mandatory. It can also become more generous without a price cut.

Stripe's pricing and packaging guide makes the same important distinction at the strategy level: the value metric and tier structure shape acquisition, conversion, expansion, and retention. Monitoring only the currency field removes most of that context.

Build a commercial field map

Use a structured record for each visible plan.

Different categories require additional fields. Cursor's pricing page requires model/access and usage interpretation. Lovable's pricing page requires credit, build, hosting, and team context. Intercom's pricing FAQ requires a precise understanding of what counts as a resolution and which base plan or external helpdesk is involved.

Establish a comparable baseline

Save more than a screenshot. A screenshot is useful evidence, but it is a poor database.

For each capture, store:

• observed time and timezone;
• requested URL and final URL;
• locale, currency, billing toggle, and audience selection;
• visible plan rows and structured fields;
• source excerpt or evidence reference;
• capture health and any missing region or interaction;
• content and schema revision.

If the page defaults to annual billing while showing a monthly equivalent, record both. If a calculator changes the rate based on volume, save the selected workload. If the price requires login or a sales quote, write “not public” rather than estimating it.

Compare stable fields before raw page text

A redesigned pricing page can produce thousands of markup changes while leaving the offer untouched. A one-line limit change can alter the economics while producing a tiny visual difference.

Compare in this order:

1. plan additions and removals;
2. value metric and unit;
3. base and marginal price;
4. included usage and limits;
5. feature entitlements;
6. trial/free access conditions;
7. billing term, currency, and region;
8. CTA and sales motion.

Raw text and screenshots remain evidence. They should not determine severity by themselves.

Classify the commercial movement

Use labels that describe the offer, not the webpage edit:

• price: visible base or marginal amount changed;
• package: tier composition or entitlement changed;
• allowance: included quantity or limit changed;
• metric: the billable unit changed;
• term: billing period, commitment, or contract condition changed;
• entry: free plan, trial, card, demo, or self-serve condition changed;
• region: localized plan, currency, or geographic availability changed;
• presentation only: layout or language changed without a supported commercial movement.

One event may contain several movements. Keep the exact fields so another reviewer can reproduce the conclusion.

Set review thresholds

Not every commercial change deserves an interruption.

Fast review

• public price or unit change;
• plan introduced or retired;
• material allowance contraction;
• free plan or trial boundary changed;
• important feature moved between tiers;
• existing self-serve path moved behind sales.

Weekly review

• CTA or discount language;
• small entitlement additions;
• regional packaging not tied to the current market;
• enterprise proof or policy language.

Reject as noise

• visual redesign with stable fields;
• reordered feature lists;
• tax wording without a commercial change;
• toggles captured in different states;
• incomplete or blocked capture.

Separate fact, implication, and response

Suppose a competitor lowers included usage. The fact is the old and new allowance. “They are under margin pressure” is one possible explanation, not a fact. They may be segmenting heavy users, preparing an add-on, correcting abuse, or running a regional test.

A useful review item says:

• Fact: allowance changed from X to Y on plan Z.
• Evidence: page, region, and two capture dates.
• Possible consequence: heavy users now cross the paid boundary sooner.
• Alternatives: experiment, localization, or page error not yet ruled out.
• Decision: pricing owner reviews our comparison and affected segment.

Copyable pricing-change record

# Pricing change: [Company] — [short movement]

Observed: [timestamp and locale]
Source: [primary URL]
Reviewer: [name]

## Before
- Plan:
- Price and period:
- Value metric:
- Included usage:
- Relevant entitlements:
- Entry/CTA:

## After
- Plan:
- Price and period:
- Value metric:
- Included usage:
- Relevant entitlements:
- Entry/CTA:

## Supported conclusion
[One sentence limited to the evidence.]

## Plausible commercial consequence
[Clearly labeled interpretation.]

## Decision to review
- Owner:
- Due:
- Decision:
- Outcome:

What good monitoring produces

The output is not a screenshot archive. It is a dated ledger that lets a team answer:

• what changed;
• what did not change;
• when the new state first appeared;
• which segment or workload is affected;
• how confident the comparison is;
• who needs to review a decision.

EXVIV's competitor-pricing monitoring page describes the product boundary, while Evidence Compare shows the role of structured, source-backed comparison. The broader competitor-monitoring guide covers non-pricing sources.

Sources and further reading

• Stripe: SaaS pricing and packaging strategy
• Cursor pricing
• Lovable pricing
• Intercom pricing FAQ

Method note

Prices and packaging can vary by date, region, volume, billing selection, or negotiated agreement. This guide teaches the comparison method. Any current vendor amount must be rechecked on the linked primary page before a decision or publication.