Pricing Your First Product

Pricing is the decision about what to charge, how to charge it, and to whom. For a first SaaS product it is a hypothesis backed by little data, not a permanent setting. The aim early on is not to find the perfect number. It is to pick a defensible starting point, capture a fair share of the value you deliver, and create room to learn and adjust.

Price is also positioning. It tells buyers who the product is for and how serious it is. A number set too low signals a toy and starves the business; a number set without understanding value leaves money on the table or scares off the customers you want. Treat the first price as the start of a process, not the end of one.

Three decisions inside “pricing”

Value metric, the unit you charge by (per seat, per usage, per workspace, flat). It should track the value the customer gets.
Model, how those units turn into a recurring charge (subscription tiers, usage-based, hybrid, freemium, one-time).
Price point, the actual numbers on the page, and the gaps between tiers.

Getting the value metric right matters more than getting the number exactly right. A good metric scales revenue with the customer’s success and feels fair as they grow.

Pricing approaches

Value-based, anchor on the economic value the product creates (time saved, revenue gained, cost avoided) and capture a fraction of it. The strongest basis, but it requires understanding the customer’s economics.
Competitor-based, position relative to known alternatives. Useful for orientation, dangerous as the only input because it ignores your differentiation and costs.
Cost-plus, add a margin to your cost to serve. Simple, but for software the marginal cost is near zero, so it usually underprices value. Use it as a floor, not a target.

In practice, start from value, sanity-check against competitors, and confirm the price clears your cost to serve.

Common SaaS pricing models

Per-seat, charge per user. Predictable and easy to understand; can discourage adding users, which may limit adoption.
Usage-based, charge by consumption (API calls, events, storage, compute). Aligns cost with value and lowers the entry barrier, but makes bills less predictable.
Flat / tiered subscription, a fixed monthly price per plan. Simplest to buy and forecast; needs well-chosen tier boundaries.
Hybrid, a base subscription plus usage above an included allowance. Common for infrastructure and API products.
Freemium, a free tier to drive adoption, with paid upgrades for capacity or features. Works only when the free tier is cheap to serve and there is a clear reason to upgrade.
Free trial, full or limited access for a fixed window, then conversion to paid. Lower long-term cost than freemium but less viral reach.

Choosing a value metric

A good value metric is:

Aligned with value, the customer pays more as they get more out of the product.
Easy to understand, the buyer can predict roughly what they will pay.
Easy to measure, you can meter it accurately and bill on it.
Hard to game, customers cannot get the value while avoiding the metric.

Ask: what grows as the customer succeeds with the product? If revenue tracks that, pricing feels fair as accounts expand. If it tracks something incidental (logins, clicks), it will feel arbitrary.

Guidelines

Price on value delivered, not on hours spent building or marginal cost to serve.
Launch with one simple tier, or at most a small ladder. Complex matrices can wait until you understand segments.
Raising prices for new customers is far easier than retrofitting existing ones, so do not anchor too low out of fear.
Use annual billing (often with a discount) to improve cash flow and retention once monthly demand is proven.
Make sure the price clears your cost to serve plus the cost to acquire the customer, with margin to spare.
Talk to buyers about budget and authority, not only feature wish lists. In B2B the user and the payer are often different people.
Avoid pricing so low that it signals low quality or makes the unit economics impossible to fix later.

Tactics for setting the first number

Estimate the value, what does the customer save or earn by using the product? Use ranges from interviews, not guesses.
Capture a fraction, aim to charge a portion of that value (commonly a small slice), leaving the customer clearly ahead.
Check against alternatives, what do they pay today for the workaround or competitor? Your price should be justifiable against that anchor.
Confirm the floor, the price must exceed cost to serve plus acquisition cost over a reasonable customer lifetime.
Round to a credible number, clean, confident prices read as deliberate.
Pick a default tier, design the page so most buyers land on the plan you want to sell.

When uncertain, it is usually safer to start higher than instinct suggests. A high price can be discounted; a low price is hard to raise.

Talking to customers about price

Ask what they pay today and what budget the problem comes out of.
Ask “at what price would this be so expensive you would not consider it?” and “at what price would it be so cheap you would doubt its quality?” to bracket a range.
Watch reactions to a concrete number rather than asking for a number in the abstract.
In B2B, identify the economic buyer and frame price against the cost of the status quo.

Treat these as directional signals. Stated willingness to pay overstates real willingness, so weight actual purchases and commitments far more heavily.

Tier design

Order plans so the recommended tier is visually emphasized and most buyers choose it.
Differentiate tiers by the value metric (capacity, seats, usage) and a few meaningful capabilities, not a long checklist.
Keep an obvious entry point for the smallest viable customer and a path to expand as they grow.
For sizable or complex customers, a “contact us” enterprise tier lets you price by negotiation while you learn.
Avoid more than three or four public tiers early; choice overload reduces conversion.

Iterating after launch

Pricing is a living system. Revisit it as you learn.

Monitor: conversion rate, average revenue per account, expansion and churn, discount frequency, and where deals stall.
Run experiments carefully: test new prices on new customers or cohorts, and change one variable at a time.
Grandfather existing customers when raising prices, or give generous notice. Trust is worth more than the short-term gain.
Expand the ladder only when segments are clear enough to justify more tiers.
Expect to raise prices as the product matures and proves value; early underpricing is common and correctable.

Common pitfalls

Pricing on cost or build effort instead of customer value.
Anchoring permanently low out of fear, then being unable to raise it.
Choosing a value metric that does not track customer success, so growth feels like a penalty.
Launching with a complex matrix of tiers before understanding segments.
Treating competitor prices as a ceiling while ignoring your own differentiation.
A freemium tier that is expensive to serve with no clear reason to upgrade.
Discounting reflexively, which trains buyers to wait and erodes the anchor.
Forgetting acquisition cost, so each customer is unprofitable over their lifetime.

Relationship to validation

Pricing and validating a SaaS idea are tightly linked. The strongest validation signal is someone paying, so price shows up in early experiments through pre-sales and letters of intent. Conversations about budget and willingness to pay during validation feed directly into the first price point.