Competitor pricing analysis: compare the job, not the $10 headline price

Competitor pricing analysis compares what one customer pays for one job: the plan that fits, the billing unit and terms, then what recent buyers say mattered.

Instant Expert EditorialPublished Updated 4 min read

Competitor pricing analysis should compare what the same customer would pay for the same job across competing offers. A list of starting prices compares nothing. Price the package that fits one customer scenario, then ask recent buyers what mattered before deciding whether to charge less.

1. Write down one buying situation first

Name the customer, the task, the number of users, expected usage and essential features. Here is a hypothetical one: a small sales team needs five people to host meetings and distribute incoming bookings between them.

Compare the products those buyers would seriously consider, plus a row for staying with their current process. Average a freelancer, a five-person team and an enterprise security department together and the number describes nobody's purchase.

2. Record the whole offer, with a source and a date

Stripe's pricing guidance recommends collecting list prices, discounts and contract terms alongside what the offer includes. Put a source URL and observation date beside each row. For each option, capture:

  • The plan that meets the customer's requirements.
  • The billing unit: account, seat, project or unit of usage.
  • Monthly versus annual billing and any minimum commitment.
  • Included usage, required add-ons and one-time charges.
  • Which important requirements remain unconfirmed.

Label unpublished prices quote needed. Don't turn an unknown into zero, and don't assume a price one customer remembers applies to everyone.

3. Check the billing unit, because it changes the answer

On September 30, 2026, Calendly's public pricing page displayed Standard at $10 per seat per month and Teams at $16 per seat per month under yearly billing. The page lists round-robin scheduling in Teams. Meeting invitees do not require paid seats.

For the hypothetical five-host team:

PlanCalculation under yearly billingAnnual subscription amountFits the stated round-robin requirement?
Standard5 × $10 × 12$600No; the pricing page lists it in Teams
Teams5 × $16 × 12$960Yes, according to the pricing page

These are subscription calculations before taxes or optional add-ons, not checkout quotes; we read the pricing page and did not test the product. Comparing a rival's team package with the $10 headline would use the wrong plan. Recheck the page when making a purchase.

4. Put every competitor on the same basis

SurveyMonkey's competitive pricing guide explains why a flat monthly price and a usage fee need a common usage assumption. Run one scenario across your shortlist, then at a plausible smaller and larger workload.

Keep subscription cost separate from migration work, which depends on the customer's situation. Record the time estimate and who supplied it, instead of hiding a salary guess in the price column.

The result should support a sentence like "At five hosts, this package costs this much for the required features," never a bare "our competitor is expensive."

5. Ask buyers what the spreadsheet misses

Your spreadsheet can't tell you whether the buyer trusted the product or could get approval. Interview people who recently compared the options, including some who chose differently than your team expected. Ask about the actual decision:

  • Which plan did you evaluate, and which requirement put you on that plan?
  • Who needed access, and who only needed to receive the output?
  • What work would changing products have created?
  • When did price become part of the discussion?
  • What settled the decision after you had the prices?

These prompts apply GOV.UK's guidance on specific experiences and neutral questions. Ask only about what the person can share; a buying process makes sense without the confidential proposal. Our lost-deal interview guide covers the fuller timeline.

6. Pick the test that matches what you heard

  • If buyers misunderstood the unit, explain the price more clearly.
  • If they needed one feature locked in a larger package, investigate the package.
  • If switching work dominated, test a clearer migration offer.

A price cut addresses only one of these. Before changing your price, check that the new offer covers your own delivery costs. Then use the willingness-to-pay guide to test a concrete offer rather than averaging hypothetical price guesses.

To hear from buyers beyond your current customers, search Instant Expert for professionals who have bought the kind of software or service you sell. Review their experience before inviting them to a paid conversation, and bring your comparison for them to check. One buyer explains a decision; it doesn't establish everybody's willingness to pay.