Signals
Competitor pricing monitoring: track packaging, not just the number
A price can stay the same while the offer changes completely. Entitlements, limits, billing units and sales language belong in the same record.
Create a pricing schema before collecting
Define fields that can survive page redesigns: plan, public price, currency, billing interval, usage unit, included allowance, overage, user minimum, trial, contract cue and source URL. Preserve the raw page beside the structured values.
Mark “contact sales” as a commercial state, not missing data. A movement from public pricing to negotiated pricing is itself a signal.
Watch packaging and fences
Features moving between tiers can matter more than a small price adjustment. Record which capabilities are gated, whether security and support enter higher tiers, and whether the company is introducing consumption or platform fees.
Look for new minimums, annual-only language and calculator defaults. These details reveal who the offer is designed to serve.
Verify before escalating
Pricing pages are often localized or tested. Confirm currency, region, login state and billing interval. Recheck material changes and preserve the exact public URL before sending an alert.
Do not turn a price change directly into a strategy claim. Compare release notes, sales language and customer evidence, then state what the change could mean and what remains unknown.
Route the finding to a decision
Sales may need an updated objection response, finance may need a model refresh, and product marketing may need a packaging review. Name the affected artifact and its owner in the finding.
Working checklist
Use this in the next review.
- Track billing unit and interval beside the displayed price.
- Capture features, limits and contract cues for every tier.
- Confirm region and experiment state before alerting.
- Preserve the source and changed passage.
- Update the relevant battlecard or pricing model.