LocalBridge

Research template - 2 to 6 tabs

Compare pricing pages prompt template

Pricing pages are designed to resist comparison. Different units, different tiers, and the real constraint in a footnote. This template normalises them.

The prompt

Compare these pricing pages for me. They use different structures on purpose, so normalise before you compare.

Produce:
1. A table with one row per vendor: entry price, unit the price is per, what the cheapest usable tier includes, and the first hard limit you hit.
2. Everything charged as an add-on rather than included, per vendor.
3. Every limit stated below the main table on the page: seats, usage caps, retention, support response, overage rates.
4. Annual versus monthly difference, and whether annual is required for the advertised price.
5. What is not stated on the page at all and would need a sales conversation.

Rules:
- Quote the exact figures and units. Do not convert or estimate.
- Write "not stated" rather than inferring. Absence is the finding.
- Ignore marketing labels. Compare what is included, not what the tier is called.

My situation: [TEAM SIZE AND WHAT YOU ACTUALLY NEED]

Why this prompt is written this way

Section 3 is the point of the whole template. The comparison people get wrong is not the headline price, it is the usage cap in small print that makes the cheap tier unusable.

Requiring 'not stated' rather than inference matters here more than anywhere else, because a plausible inferred price is indistinguishable from a quoted one once it is in a table.

Ignoring tier names stops the comparison being organised by each vendor's marketing rather than by what you get.

Getting more out of it

  • Give your team size and real usage. Entry prices are meaningless without the volume you will actually hit.
  • Include the docs or limits page as well as the pricing page. The binding constraint is often only documented there.
  • Ask which vendor becomes cheapest at double your usage. That is usually the decision, not today's price.
  • Check the two figures the recommendation rests on against the pages yourself before deciding.

Works best with

2 to 6 tabs open at once. Send them together rather than one at a time, so the assistant can compare them instead of forgetting the first by the time it reads the last. Sending tabs to Claude explains the options.

Common questions

Will the prices be current?
They come from the pages you have open, so they are as current as those pages. That is the main advantage over asking from memory, where prices are often a year or two stale.
Can it handle usage-based and seat-based pricing together?
Yes, and that is where normalising helps most. Give it your expected volume so it can express both models in the same terms.
Does it work for enterprise tiers with no public price?
It will list them under section 5 as requiring a sales conversation, which is the honest answer. What it can still compare is the included features and limits.

Other templates

Stop pasting tabs one by one

LocalBridge sends the pages you have open into Claude or ChatGPT in one click, so this template gets the sources it needs.

See how it works