Competitor Price Monitoring: What a Real Increase Looks Like

On August 10 our pricing tracker read UptimeRobot’s Team plan at $38 a month. Seven days later the same page said $46. The Solo plan, the one a first-time buyer lands on, did not move at all.

That gap is the whole lesson. Competitor price monitoring is not valuable because it tells you a number went up. It is valuable because it tells you which number went up, and which one the vendor deliberately left alone. One of those facts is trivia. The other tells you where a competitor thinks its pricing power actually lives.

Here is the full read, from three consecutive weekly captures of the same page.

What UptimeRobot actually changed

Our directory captured uptimerobot.com/pricing on August 3, August 10, and August 17. Between the second and third capture, two tiers moved and three did not.

Tier	Aug 10 monthly	Aug 17 monthly	Change
Free (50 monitors)	$0	$0	flat
Solo (10 monitors)	$13	$13	flat
Team (100 monitors)	$38	$46	+21.1%
Scale (200 monitors)	$82	$98	+19.5%
Enterprise	contact sales	contact sales	n/a

These are current prices as of the directory’s last fetch on August 17, 2026. UptimeRobot’s live pricing page shows the same numbers today, which matters for reasons I will get to. You can see the tracked view on our UptimeRobot pricing page.

There is a second piece of context in the August 3 capture. At that point the $82, 200-monitor tier was relabeled from Enterprise to Scale, and a new contact-sales Enterprise tier appeared above it with SOC 2 documentation, a dedicated CSM, SLAs, and custom invoicing. Two weeks later, that newly renamed Scale tier went up 19.5%.

Build the ceiling first, then raise the floor underneath it. That is a sequence, not a coincidence, and it is the kind of thing you only see if you are holding more than one snapshot.

The entry price is the one they did not touch

Solo held at $13 through both weeks. That is the number that appears in comparison posts, in “best uptime monitoring tools” listicles, in the SERP snippet, and in every competitor’s battlecard. It is the price the market has memorized.

Raising it costs top-of-funnel traffic and makes every third-party page that quotes you go stale in a way that reads as expensive. Raising the Team plan costs almost none of that, because nobody encounters $46 until they have already decided the free plan is not enough and Solo is too small. By then the comparison is over and the switching cost is real: monitors configured, status pages branded, alert routing wired into Slack and PagerDuty.

Note also which tier carries the “most popular” flag. It is Team, the one that went up 21.1%. Vendors put that badge on the tier they want volume in, so raising the price of the plan you are actively steering people toward is a confidence signal rather than a hedge.

If a competitor does this to you, the useful question is not “should we match?” It is “which of our tiers is the equivalent of their Team plan, and have we ever tested it?” Most early-stage teams have repriced their entry tier three times and never touched the middle.

The value metric is the interval, not the monitor count

Read the free plan next to the paid entry plan and something looks broken. Free gives you 50 monitors. Solo, at $13 a month, gives you 10 by default, with a 50-monitor option available at a higher price. The free plan ships five times more monitors than the cheapest paid one.

That only reads as a mistake until you look at the second line of each tier. Free checks every 5 minutes. Solo checks every 60 seconds. Team every 30 seconds. Scale every 15 seconds.

They are not selling monitors. They are selling detection latency. Monitor count is a capacity limit, generous precisely because it is not the thing being charged for. The interval is the value metric, and it maps cleanly onto willingness to pay: a hobby project does not care about four minutes of undetected downtime, and a payments API cares enormously.

This is why headline-price competitor price monitoring is thin on its own. If all you captured was “$38 became $46,” you would file it as a monitoring tool getting 21% more expensive. What actually happened is a vendor taking price on the one axis its buyers already agreed was worth paying for. That distinction changes the response, and the same logic sits underneath most packaging changes worth reacting to, which is the argument in Seat-Based Pricing Isn’t Dead. It Just Lost Default Status.

The change that was not in the price field

One more thing moved, and it is the one most tracking misses entirely.

Our August 10 capture recorded the annual billing banner as “Save ~20% with annual billing.” The August 17 capture, and the live page today, read “Save ~15% with annual billing.” UptimeRobot’s own comparison table now prices Team at $39 a month billed annually, which is $468 a year.

So the annual buyer absorbed two increases at once: the list price went up, and the discount that offsets it got shallower. The monthly headline understates what happened to the yearly invoice.

Discount depth is a real price lever and it is almost always written in marketing copy rather than a structured price field. Percentage-off banners, first-year promotions, nonprofit and startup programs, multi-year terms: none of them live where a naive scraper looks. That is the practical difference between watching a number and reading a pricing page, which is the distinction I drew in Price Intelligence vs Price Monitoring.

Where competitor price monitoring usually goes wrong

This is the step most setups skip. Automated capture produces false positives, and if you act on one you will publish something wrong or walk into a deal with a bad claim. The good news is that artifacts have recognizable shapes.

A change that reverts to exactly the old numbers within days. Prices rarely go up and come back to the cent a week later. That pattern almost always means the page was captured in two different billing-toggle states, monthly one week and annual the next.

Every tier moving by an identical percentage. Real repricing is uneven, because the vendor is making a different judgment about each segment. A uniform move across all tiers usually means a currency, region, or promotional-banner difference rather than a decision.

A tier’s entire feature list disappearing at once. Vendors trim features one or two at a time and usually explain it. A whole list vanishing in one capture is a parse failure, not a repackaging.

A change with no corresponding edit on the live page. If the vendor’s page still shows the thing your alert says was removed, your alert is wrong. This one takes thirty seconds to check and it settles the question completely.

The UptimeRobot move passes all four. It is monotonic across three captures rather than a round trip. It is uneven across tiers, with Solo flat, Team up 21.1%, and Scale up 19.5%. Feature lists are intact on every tier. And the live page carries the new numbers right now.

Treat every alert as a lead, not a fact. The verification step is cheap and it is the only thing standing between a useful signal and a confidently wrong one.

What to do with this, depending on who you are

If you compete with UptimeRobot: the opening is not price, it is the $13-to-$46 gap. Anyone who has outgrown 10 monitors but does not need 100 now faces a 3.5x jump. A plan that sits in that gap is a more interesting response than undercutting $46.

If you are a customer: your renewal quote is the number to check, not the public page. Existing customers are frequently grandfathered through the first cycle, and the annual discount change means the sticker difference and the invoice difference are not the same.

If you are pricing your own product: copy the sequence, not the numbers. Add a tier above before you raise the tier below, hold the entry price the market has memorized, and take the increase where switching costs are already sunk.

The one move worth making this week

Open your two closest competitors’ pricing pages and write down three numbers each: the entry price, the price of whichever tier carries their “most popular” badge, and the annual discount percentage. Then ask which of the three you would actually notice changing next month.

For most teams the honest answer is only the first, because the entry price is the one that shows up in comparisons and the other two live in places nobody rereads. Set up competitor pricing monitoring that captures all three, and make sure it keeps history rather than just overwriting the current state. The increase you need to hear about is the one on the tier your shared customers are already sitting on, and you can only see it by comparing two captures. If you want the manual version first, How to Track Competitor Pricing Without Hiring an Analyst walks through it.

This post came out of Outmano’s own pricing data: three weekly captures of one page, diffed and analyzed automatically. That is what Outmano does across pricing, positioning, SEO, content, and roadmaps, with the analysis attached to every change rather than a raw alert you have to interpret yourself.

Frequently Asked Questions

How often should competitor price monitoring run?

Weekly is the right default for most B2B SaaS. Pricing pages change on the order of months, and daily checks mostly generate noise from A/B tests and billing-toggle states rather than real decisions. The exception is a live repricing or a competitor’s launch window, where daily capture for a couple of weeks is worth the extra noise.

What should I track besides the headline price?

Annual discount depth, which tier carries the “most popular” or “recommended” badge, seat and usage limits, free plan caps, trial length, and whether the top tier has a published price at all. Those fields change more often than list prices and they signal packaging strategy earlier. The UptimeRobot change above was visible in three of them at once.

How do I know a detected price change is real and not a scraping error?

Check whether the change reverts within days, whether every tier moved by the same percentage, whether feature lists vanished wholesale, and whether the vendor’s live page confirms it. Any one of the first three is a strong artifact signal. The last check is definitive and takes under a minute, so do it before you act on anything.

Is it legal to monitor a competitor’s pricing page?

Reading a public pricing page is ordinary competitive research and is what every buyer does before purchasing. The considerations that do apply are the site’s terms of service around automated access, request rate, and not circumventing authentication or paywalls. Public, published pricing accessed at a reasonable rate is standard practice.

Why do vendors raise middle-tier prices instead of entry prices?

The entry price is the number the market has memorized and the one quoted in every comparison page, so raising it damages top-of-funnel and makes third-party listings look unfavorable. Middle tiers are encountered after the buying decision, where switching costs are real and price sensitivity is lower. UptimeRobot raising Team 21.1% while holding Solo at $13 is a clean example of that logic.

How much history do I need before price monitoring is useful?

At least two captures, because a single snapshot cannot show a change. The real value starts around three or four, when you can distinguish a one-off correction from a direction. The UptimeRobot read only works because there were three consecutive weekly captures showing a monotonic move rather than a round trip.