The Best Competitor Pricing Comparison Prompts

Most pricing comparisons go wrong before any arithmetic happens. Two vendors publish numbers, somebody puts them side by side, and the table implies both figures describe the same purchase. They rarely do. One assumes annual billing and the other monthly. One counts a platform fee that the other folds into the seat price. And one of them charges for onboarding in a line the table never reached.

So the first decision is not which prompt to use. It is what configuration you are pricing: how many seats, over what term, billed how, in which currency, and which features have to be included. Write that line down before you run anything. Every prompt below gives a different answer for a different configuration. A comparison that does not state its own cannot be reproduced by the colleague who questions it.

The word price hides two numbers

Almost every software pricing page carries a billing toggle. The two figures behind it are not close to each other, and the gap is widest exactly where buyers start. HubSpot’s Sales Hub page in September 2026 puts Starter at $7 per seat per month billed annually, and $20 billed monthly. That is one plan described by two numbers nearly three times apart.

A table with one price column has already made that choice and not recorded it. The prompts here will not let the model make it, which is why the first one spends a rule on the billing period rather than on tone or persona. Price intelligence as a discipline is largely the practice of keeping these distinctions straight at scale.

Run them in order. Each one uses the output of the one before. The table built first feeds the cost model and the tier analysis, instead of being rebuilt three times with small differences.

The fourth gets skipped more than the other three, and changes a decision more often than any of them. A buyer comparing two vendors is rarely stopped by a price. They are stopped by something neither page told them, and a list of those gaps is a better brief for a sales conversation than the comparison itself. Which capability sits on which tier is the other half of that list, and a feature comparison answers it from documentation rather than from the pricing page.

Pricing is the worst subject to ask a model about from memory. The answer is numeric, confident and checkable, and nothing about it signals its age. Three things belong in the context window first.

We ran the same question twice against one vendor whose prices are published openly: once with nothing supplied, once with the page saved that morning. Printing both matters because the ungrounded answer is not obviously bad. It is the kind of answer somebody checks, nods at, and puts in a deck.

Two numbers reported as one

Every tier name came back correct. The onboarding charges came back correct. The error was quieter. Each per-seat figure quoted was the monthly-billing price, given without saying so. Against an annual comparison, that overstates the entry tier by roughly 186 per cent. It goes the same way every time, so nothing inside the answer looks odd enough to query.

This is why “check the AI for hallucinations” is not a workable instruction for pricing work. Nobody is scanning for a made-up plan name. The thing to check is whether each figure knows which billing period it belongs to, and the only way to check that is to have the page open.

What a grounded answer still cannot fix

The second run is accurate, and its accuracy has a shelf life measured from the moment the page was captured. That is a real improvement: a dated claim can be re-checked and an undated one cannot. But be precise about what changed. The risk moved from being wrong to being old. Those need different fixes, and only one of them is a better prompt.

Three checks, in this order, because they are ranked by what a mistake costs you in the room.

Then give the output somewhere to live. A comparison that stays in a chat window gets re-derived by the next person who needs it, slightly differently. The competitive pricing matrix takes the table with its columns intact and exports it. That matters mainly because it gives every figure a cell to sit in, beside the date it was captured.

The comparison you just built is correct, and it has already started ageing. What makes pricing different from most competitive work is the shape of the decay. It is not gradual. It is a step, and it happens on a day nobody announces.

A price rise is the easy case, because it is visible the next time anybody looks. The expensive case is a repackaging. A vendor moves one feature from the middle tier to the top one, and every published figure on their page stays the same. A comparison built on those figures stays arithmetically perfect while describing a product that no longer exists at that price. Nothing in the output looks stale, which is exactly the problem.

Catching one means holding two dated copies of the page and comparing what each tier contains rather than what it costs. Detecting a pricing change is a different job from comparing prices, and most of it is separating a real change from a row somebody renamed.

Being late on that has a specific cost, and it is not embarrassment. It is a rep quoting a tier that was reorganised last quarter, to a buyer with the competitor’s page open on a second screen. The rep then loses the argument about everything else in the comparison too.

Watching for it is ordinary competitive monitoring rather than anything a prompt can do. Flares tracks competitor pricing pages and what each tier contains. A repackaging arrives as a notification rather than as a surprise in a deal, and the pages you paste into this prompt are the current ones.

What monitoring does not do is decide what the change means for your price. Whether a competitor moving a feature upmarket is an opening or a threat depends on your own packaging and your own buyers. That judgement is what this prompt was always there to support, not to make. Where the answer has to be said out loud, it lands on a competitor battlecard, and a price with no capture date on it should not make the trip.