Pricing is the most powerful, least-used lever a founder has. A 10 percent price increase, if customers stick, flows almost entirely to gross profit -- no new headcount, no new pipeline, no product to build. And yet most startups underprice for years, anchored to a number they picked before they had a single customer and never revisited. The reason is simple: pricing feels risky, the data feels thin, and "we'll fix it later" is the easiest decision in the building.
This guide is the framework we use with founders to set a price, measure what customers will actually pay, and model a change before shipping it -- including the one calculation that tells you whether a price increase is safe.
The Short Answer
Price to the value you create for the customer, not to your costs or to a competitor's number. Set the price high enough that a meaningful share of prospects hesitate -- if no one ever pushes back on price, you are leaving money on the table. Then revisit it on a schedule, because your product gets more valuable over time while your price usually does not.
Before you change anything, model it. A price change moves five things at once -- revenue, gross margin, churn, LTV:CAC, and payback -- and intuition is bad at holding all five in your head. Our Pricing Sensitivity Calculator does it in about two minutes: enter your current numbers and a price elasticity assumption, and it shows you the profit-maximizing price and how many customers you could afford to lose.
Why Underpricing Is the Default -- and the Most Expensive Mistake
Founders underprice for predictable reasons. The product felt unfinished when they set the price. The first customers were friends. A competitor published a low number. Raising prices feels like it will cost deals. So the price gets set low and stays low while the product matures past it.
The cost is enormous and invisible. Price is the single highest-leverage variable in your model because it has no marginal cost. Winning a new customer costs you CAC; building a new feature costs engineering time; raising the price costs you nothing and lands almost entirely in gross profit. A company stuck 30 percent below its value-justified price is not 30 percent behind on revenue -- after fixed costs, it can be giving away the majority of its profit.
Underpricing also poisons everything downstream. It depresses the LTV in your LTV:CAC ratio, which makes paid acquisition look unprofitable and starves growth. It lowers your ceiling on what you can spend to acquire a customer. And it attracts the most price-sensitive, highest-churn customers -- the exact segment you least want. Cheap pricing is not a growth strategy; it is a slow tax on the whole business.
The Three Ways to Price (Only One Is Right)
Cost-plus pricing takes your cost to serve and adds a margin. It is the most common instinct and almost always wrong for software, where marginal cost is near zero. Cost-plus systematically underprices anything valuable, because it ignores the only thing that matters to the buyer: the value they receive.
Competitor-based pricing anchors to what similar products charge. It is a useful sanity check and a terrible strategy. It assumes your competitor priced correctly (they probably did not), and it commoditizes you -- if your only pricing logic is "a bit cheaper than them," you have told the market you are a substitute, not a category.
Value-based pricing sets the price as a fraction of the economic value you create for the customer. If your product saves a customer $100,000 a year in labor, or makes them $500,000 in new revenue, the question is what slice of that value you can capture -- typically 10 to 25 percent. Value-based pricing is the only approach that scales with how good your product actually is, and it is the only one worth building your strategy around. The other two are inputs, not answers.
How to Find Willingness to Pay
"Price to value" raises the obvious question: how do you know what customers will pay? You measure willingness to pay, and you do not do it by asking "how much would you pay for this?" (people are terrible at answering hypothetically). Better methods:
- Watch the deals. If nearly every prospect accepts your price without flinching, your price is too low -- a healthy price gets pushback from a meaningful minority. If almost everyone balks, it is too high. The win rate at each price point is real willingness-to-pay data hiding in your sales notes.
- Test price points with real prospects. Quote different prices to comparable segments and measure conversion, not opinions. A pricing page A/B test or different quotes across similar deals reveals elasticity directly.
- Anchor to the value metric. Identify what your price should scale with -- seats, usage, revenue influenced, transactions processed. The right value metric grows the bill as the customer gets more value, which aligns your revenue with their success and makes increases feel fair.
- Use the Van Westendorp questions for early, pre-revenue signal: at what price is it too expensive, expensive-but-worth-it, a bargain, and so cheap you'd doubt the quality? The overlap brackets an acceptable range.
The output you want is not a single number but a sense of the demand curve: how quantity sold changes as price moves. That curve is what the pricing calculator turns into a profit projection.
Price Elasticity: The Number That Decides Everything
Price elasticity is how much demand changes when price changes. In practical founder terms: for every 1 percent you raise price, what percentage of customers do you lose?
- Inelastic (≈ 0.3–0.7). Sticky, mission-critical B2B products with high switching costs. A 10 percent price rise loses only 3–7 percent of customers. These products are almost always underpriced and should raise prices.
- Unit elastic (≈ 1.0). A 10 percent rise loses ~10 percent of customers. Revenue is roughly flat on a price change, but profit still rises, because you serve fewer customers at the same total revenue.
- Elastic (1.5+). Commodity or easily-substituted products. A price rise loses more revenue than it gains. Here the work is to differentiate first, then price.
The critical insight most founders miss: because your cost to serve a customer is roughly fixed in dollars, the profit-maximizing price is almost always higher than the revenue-maximizing price. You make more money serving fewer customers at a higher price, because each lost customer also takes their cost-to-serve with them. The Pricing Sensitivity Calculator shows this directly -- the profit-maximizing row is usually well above the revenue-maximizing one.
If you do not know your elasticity, assume 1.0 and test a range. Most B2B SaaS founders discover, once they actually measure it, that they are far more inelastic than they feared.
What a Price Change Actually Does to Your Unit Economics
A price increase is not one number moving; it is five:
| Metric | Effect of raising price (holding cost-to-serve fixed) |
|---|---|
| MRR / ARR | Up, unless elasticity is high enough that customer loss outweighs the increase |
| Gross margin % | Up -- fixed cost-to-serve is a smaller share of a higher price |
| LTV | Up -- higher revenue per customer over their lifetime |
| LTV:CAC | Up -- the same CAC now buys a more valuable customer |
| CAC payback | Down (faster) -- you recover acquisition cost in fewer months |
Every one of these moves in your favor on a price increase, provided the customer stays. That is why the entire decision collapses to one question: how many customers will you lose, and can you afford it? Which is exactly what the break-even figure answers.
For a refresher on the metrics a price change touches, see our guide to burn multiple, Rule of 40, and net new ARR, and pair the pricing calculator with the Unit Economics Calculator to see the LTV:CAC impact in full.
The One Calculation That Tells You a Price Increase Is Safe
Before raising prices, calculate your break-even churn cushion: the percentage of customers you could lose at the new, higher price and still hold today's total revenue.
The math is simple. If you raise prices 20 percent, you can lose up to 1 − (1 / 1.20) ≈ 16.7 percent of customers and keep the same MRR. Anything less than that, and the price increase is pure upside. If your measured elasticity says you'll lose only 6–8 percent, you have a large safety margin and the decision is easy.
This cushion is why price increases are far less risky than founders fear. You are not betting that no one leaves -- you are betting that fewer leave than your break-even, and the break-even is usually generous. The Pricing Sensitivity Calculator computes this break-even for every price point automatically, so you can see exactly how much room you have before a change costs you money.
How to Roll Out a Price Increase
Modeling says go. Execution is where price increases succeed or fail:
- Grandfather existing customers, at least for a window. Apply the new price to new customers immediately; give existing customers a runway (or a permanent legacy rate for your earliest, most loyal accounts). This removes most of the churn risk while capturing the upside on all new business right away.
- Tie the increase to added value. A price rise that lands alongside a real new capability reads as fair. A naked increase reads as a grab. Sequence them together when you can.
- Communicate early and directly. For existing customers, advance notice from a human beats a silent invoice change. Most B2B customers accept a well-justified increase; the resentment comes from surprise, not from the number.
- Start with new-customer pricing. The lowest-risk way to raise prices is to raise them only for new logos and watch win rates. If conversion holds, you have proven the market accepts the new price before touching a single existing relationship.
- Revisit on a schedule. Put a pricing review on the calendar at least annually. Your product gains value continuously; your price should not stand still for three years.
Common Mistakes
Setting price once and never revisiting it. The default failure. The price you set pre-product-market-fit is almost never the right price two years later.
Pricing on cost instead of value. Guarantees underpricing for anything genuinely valuable, because it ignores the buyer's economics entirely.
Competing on price. Tells the market you are a substitute. If price is your only differentiator, you have no differentiator.
Confusing the revenue-maximizing price with the profit-maximizing price. The profit-maximizing price is higher. Optimizing for revenue alone leaves profit on the table.
Changing price on a hunch instead of modeling it. A price change moves five interlocking metrics. Model it -- including the break-even cushion -- before you ship it, not after.
Discounting to close instead of fixing the price. Heavy discounting is underpricing with extra steps, and it trains your sales motion and your customers to expect it.
What We Recommend
- Price to value, not cost. Anchor your price to the economic value you create, and target capturing 10–25 percent of it.
- Measure willingness to pay from real deals, not hypothetical surveys -- your win rates already contain the answer.
- Find your elasticity, then push price toward the profit-maximizing point. Most B2B founders are more inelastic than they think and are underpriced.
- Always compute the break-even cushion before raising prices. It almost always shows the increase is safer than it feels.
- Model every change first. Run it through the Pricing Sensitivity Calculator, then validate with a real cohort before rolling it out broadly.
Pricing sits at the intersection of strategy, finance, and go-to-market, which is why it so often falls through the cracks -- no single function owns it. We help founders set and revisit pricing as a deliberate financial decision, modeled and de-risked rather than guessed. If you suspect you are underpriced, or you are weighing an increase and want the unit-economics impact modeled first, book a free consultation and we will run the numbers with you.
This article is general guidance, not financial advice. Pricing outcomes depend on your specific market, product, and customers; model and test before making changes.
