Competitor pricing analysis: compare the cost of the same job

Competitor pricing analysis compares what the same customer would pay for the same job across competing offers. Start with a customer scenario, calculate the cost of the package that actually fits it, then ask recent buyers what mattered in their decision. A list of starting prices is not enough to decide whether you should charge less.

Pick a buying situation before collecting prices

Write down the customer, the task, the number of users, expected usage and essential features. For example: a small sales team needs five people to host meetings and distribute incoming bookings between them. This is a hypothetical buying situation, not a customer result.

Compare products those buyers would seriously consider. Keep a separate row for staying with their current process. If you mix an individual freelancer, a five-person team and an enterprise security department in one average, the number will describe nobody's purchase.

Record the offer, not just the headline number

Stripe's pricing guidance recommends collecting list prices, discounts and contract terms alongside what the offer includes. Put a source URL and observation date next to each row so another person can check it.

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. Do not turn an unknown into zero or assume a price recalled by one customer applies to everyone.

A real pricing page shows why the unit matters

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.

Applying those published prices to our hypothetical five-host team gives:

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

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. Use the same customer scenario across your shortlist, and repeat it at a plausible smaller and larger workload.

Keep subscription cost separate from migration work. One is a vendor charge; the other depends on the customer's situation. Record the time estimate and who supplied it instead of hiding an assumed salary calculation in the price column.

The result should let you say something specific: “At five hosts, this package costs this much for the required features.” It should not say “our competitor is expensive” without saying for whom and for what.

Ask buyers what the price comparison misses

A spreadsheet can show the available packages. It cannot tell you whether the buyer trusted the product, could obtain approval, or wanted to migrate. Interview people who recently compared the options, including those who chose differently from what your team expected.

Use questions 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 information the person can share; a confidential proposal is not required to understand their buying process. Our lost-deal interview guide covers the fuller timeline.

Choose the next test

If buyers misunderstood the unit, improve how you explain the price. If they needed one feature locked in a larger package, investigate the package. If switching work dominated the discussion, test a clearer migration offer. A price cut addresses only one of these possibilities.

Before changing your price, check whether the proposed offer can cover your own delivery costs. Then use the willingness-to-pay guide to test a concrete offer rather than averaging hypothetical price guesses.

If you need experience outside 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. Bring the comparison and ask which assumptions need checking; their experience helps explain a decision, not establish everybody's willingness to pay.