The competitive pricing stack: tools and workflows for pricing teams
Three jobs, in order: aggregate, analyse, track. Most teams tool the second one and skip the first and third.
The manual stack, and where it stops
Nearly every company starts with the same three tools: a spreadsheet, a screenshot folder, and a recurring calendar invite for a quarterly review. It is a reasonable stack. It costs nothing, everyone can read it, and for three competitors in one segment it is genuinely sufficient.
It stops working for structural reasons rather than lazy ones. Competitors reprice on their own schedule, so a refresh is either complete and expensive or partial and misleading. Feature names drift, and the same capability accumulates three rows. Nobody diffs versions, so the history — the most valuable part — is never captured. And the review cadence sets your reaction time: a quarterly rhythm means a competitor’s March increase reaches your pricing conversation in June.
The manual stack
- A spreadsheet per market
- Screenshots in a folder
- A quarterly review
Three separate steps
- 1AggregateCollect every page, dated
- 2AnalyseOne structure: segments, plans, features
- 3FollowA diff on every reading, not a memory
Job 1 — aggregate
Collecting the data. The output is a dated, structured record of every competitor’s plans, prices and features, in one shape.
Two properties matter more than they sound. Dated: every value carries the moment it was observed, so you never compare a March price to a September one by accident. Structured: prices normalised to one currency, period and unit, and features mapped to a controlled vocabulary you define once. Without normalisation there is nothing to analyse, only text.
This is the job teams most often skip, because it is the least interesting and the most laborious. It is also the one that determines whether the other two are possible.
Job 2 — analyse
Turning the record into a position. Three outputs cover most decisions: where you sit on price within each segment, which features are table stakes and which carry a premium, and a short list of the weaknesses and opportunities that follow.
The failure mode here is a dashboard that reports numbers without a claim. “Median €15.20” is data. “You are the third cheapest of seven in the small-team segment while including two features four competitors bill separately” is analysis, because it implies an action. Ask of any analysis output: could someone disagree with it? If not, it is a metric, not a finding.
Job 3 — track
Detecting change. Re-scan on a schedule, diff against the previous version, and route what moved to whoever cares: a price change, a new or removed plan, a feature that shifted tier, a billing model change.
Two details make the difference between a useful feed and noise. Alerts should be typed rather than generic — a price increase and a repackaging deserve different urgency. And the history has to be queryable, because “how has this market moved over eighteen months” is a better input to a pricing decision than any single snapshot.
Time before a price change is seen
What to look for in a tool
Four questions, in order of how much they will affect you:
Does it extract, or do you? If setup means typing competitor plans into forms, you have bought a spreadsheet with a login. Extraction from a pricing page URL is the difference between minutes and days.
Can you define your own market structure? Your segments, capacity lanes and qualifiers are specific to you. A tool with fixed categories will misclassify half your market.
Is monitoring scheduled and typed? Automatic re-scans, diffs, and alerts that distinguish a price change from a packaging change.
Can the output leave the tool? Pricing decisions get made in meetings and proposals. If a comparison cannot become a shared report or an export, it will be retyped into slides, and it will go stale there.
Where Market Sonar sits
Market Sonar is the data layer for the three jobs, not a replacement for your pricing strategy. It aggregates — pricing pages are found from each competitor’s website, and every plan, price and feature is extracted and classified into the market structure you defined. It analyses — the features rival plans charge more for, a competitive SWOT, and pricing suggestions that name the competitors and medians behind each number. It tracks — scheduled re-scans, typed change alerts, and a history you can read over time.
What it does not do is decide. Whether to follow a competitor’s increase, hold and defend on value, or reprice a segment entirely is a judgement about your customers, your margins and your roadmap. The point of the stack is that you make that judgement with the market in front of you rather than from memory.
From reading to your own market.
Or request a demo.