How to Price Your Product Without Guessing

Free Playbook · Product & Growth

How to Price Your Product
Without Guessing

Most startups set their pricing once, early, almost arbitrarily — and then never revisit it. Pricing is one of the highest-leverage levers you have. Here’s how to think about it properly, and the prompts to help you get there.

What’s in this playbook
  1. Why your first price is probably wrong — and that’s OK
  2. Value-based vs cost-based vs competitor-based pricing
  3. Choosing the right pricing metric
  4. How many tiers do you actually need
  5. The pricing page that converts
  6. How to raise prices without losing customers
  7. Using AI to test pricing assumptions

Why Your First Price Is Probably Wrong

Most founders set their initial price based on a mix of gut feeling, what a competitor charges, and what feels “fair.” This is normal — and it’s also almost always wrong, in one direction or another.

The good news: your first price doesn’t need to be right. It needs to be a starting point you’re willing to test and change. The founders who struggle with pricing are usually the ones who set a number once and then treat it as fixed, even as their product, market position, and customer base evolve dramatically.

If you’ve never had a customer push back on price, you’re probably underpriced. Some resistance is a healthy signal — it means you’re charging close to what the market will bear.

Value-Based vs Cost-Based vs Competitor-Based Pricing

Cost-based pricing — cost plus margin — is the easiest to calculate and the worst way to price software. Your costs have almost nothing to do with the value a customer gets. A tool that saves someone 10 hours a week might cost you almost nothing to run, but it’s worth a great deal to them.

Competitor-based pricing — matching or undercutting competitors — is a reasonable starting point but a bad long-term strategy. It anchors your pricing to someone else’s positioning, and it gives you no room to capture more value if your product is genuinely better.

Value-based pricing — pricing according to the value the customer receives — is the right long-term approach. It requires understanding what your product is actually worth to different customer segments, which is harder to calculate but far more powerful.

Prompt — Calculate the value you create

“My product is [description]. It helps customers by [specific outcome — time saved, revenue generated, cost avoided, risk reduced]. For a typical customer who is [describe their profile], help me estimate the dollar value this outcome is worth to them per month. Walk through the calculation: what would they otherwise spend in time, money, or risk to achieve the same outcome without my product? Based on this, what pricing range would represent good value for them while capturing a fair share of that value for me?”

Choosing the Right Pricing Metric

The pricing metric — the thing you charge based on — matters more than the price itself. The right metric scales naturally with the value the customer receives. The wrong metric either penalises growth (so customers resist expanding usage) or doesn’t capture value at all (so you leave money on the table as customers grow).

Common metrics: per seat (works when value scales with team size), usage-based (works when value scales with volume — API calls, transactions, data processed), flat fee (works for simple products where usage doesn’t vary much), and outcome-based (works when you can directly tie pricing to a measurable result, but is operationally complex).

The test for a good pricing metric: as the customer gets more value, does your revenue from them naturally increase? If not, you’re leaving expansion revenue on the table.

Prompt — Choose your pricing metric

“My product is [description]. Customers get value from it by [how they use it and what they get]. Help me evaluate different pricing metrics — per seat, usage-based, flat fee, tiered by feature access. For each one: how well does it scale with customer value, how easy is it for customers to understand and predict their costs, and what are the risks of each — for example, does it create incentives that work against adoption? Recommend the best metric and explain why.”

How Many Tiers Do You Actually Need

Most B2B SaaS products work well with 3 tiers. Fewer than that and you can’t capture the range of customer sizes and needs. More than that and you create decision paralysis — and most customers won’t engage with a pricing page that looks like a spreadsheet.

The structure that works: a starter tier priced to be an easy yes for small customers, a middle tier that’s the one you actually want most customers to choose — design it to be the obvious best value — and a top tier for your highest-value customers, often with custom pricing or “contact sales.”

The middle tier should be the one most customers pick. If your starter tier is the most popular, your pricing is probably too aggressive at the entry level, and you’re leaving money on the table from customers who would happily pay more.

The Pricing Page That Converts

A good pricing page does three things: makes the choice between tiers easy by clearly differentiating who each tier is for, removes friction by anticipating objections (what happens if I need to change plans, is there a free trial, what’s the cancellation policy), and creates urgency or confidence without being manipulative — social proof, guarantees, clear value statements.

Avoid pricing pages that list every feature in every tier as a wall of checkmarks. Most buyers don’t compare feature-by-feature — they’re trying to figure out “which one is for someone like me?” Help them answer that question fast.

Prompt — Write pricing tier descriptions

“I have 3 pricing tiers for [product]: [list tier names and what’s included in each]. Write a one-sentence description for each tier that helps a visitor quickly identify which tier is for them — based on company size, use case, or need, not just feature lists. Then suggest a label for the middle tier that signals it’s the recommended choice without being pushy.”

How to Raise Prices Without Losing Customers

Price increases are one of the most avoided decisions in early-stage companies — and one of the highest-leverage. A 10% price increase that costs you 5% of customers is still a net positive if those customers were marginal.

The key to raising prices without backlash: grandfather existing customers for a defined period, give advance notice — 30-60 days minimum, communicate the increase in terms of value added since they signed up, not just “costs have gone up,” and make the new pricing apply to new customers immediately, existing customers later.

Prompt — Write a price increase announcement

“I need to announce a price increase to existing customers of [product]. The increase is from [old price] to [new price], effective [date]. Since they signed up, we’ve added: [list improvements/features]. Write an email that: explains the change clearly without apologising excessively, frames it around the value added rather than just costs, gives them a grace period if applicable, and maintains trust rather than triggering a wave of cancellations. Direct and respectful, not defensive.”

Using AI to Test Pricing Assumptions

AI can’t tell you the “right” price — that requires real market testing. But it can help you stress-test your pricing logic before you commit to a change.

Prompt — Stress-test a pricing decision

“I’m considering this pricing structure: [describe your current or proposed pricing — tiers, prices, metric]. My target customer is [describe them] and my closest competitors charge [their pricing]. Stress-test this: (1) What objections will a buyer have when they see this pricing, and how would I respond? (2) Where might this pricing structure create the wrong incentives — for example, discouraging usage I want to encourage? (3) If I were a competitor trying to win a deal away from me on price, how would this pricing make me vulnerable?”


Get 50 more prompts for pricing, growth, and product strategy — free.

Leave a Comment