Price Is a Hypothesis: Stop Treating Your Revenue Model as Though the Market Already Agreed to It

At some point in the early life of nearly every business, a founder sits down and decides what to charge. The process varies—some founders spend weeks on it, others arrive at a number in an afternoon—but the underlying logic is remarkably consistent: calculate the cost to deliver the product or service, add a margin that feels reasonable, check whether the resulting number is in the vicinity of what competitors are charging, and proceed.

This approach is so common that it is rarely questioned. It is also, in most cases, a significant strategic error.

What Pricing Actually Is

Cost-plus pricing—the method described above—treats price as an output. You know your costs, you apply a markup, and you arrive at a number. The logic is clean and the math is straightforward. The problem is that it addresses the wrong question.

The question cost-plus pricing answers is: what do I need to charge to cover my costs and generate a margin? That is a question about internal operations. It has nothing to do with what customers are willing to pay, what they believe the product is worth, or whether the margin you have targeted is achievable in the market you are entering.

Pricing is not an accounting exercise. It is a hypothesis about the relationship between your offering and the people you are trying to serve. Every price you set is an implicit prediction: I believe that customers who need this product will find this number acceptable given what they expect to receive in return. That prediction can be tested. Most founders never test it.

The Competitor Benchmark Trap

The alternative most founders reach for—benchmarking against competitor pricing—solves one problem while creating several others.

On the surface, it seems rational. If your competitors are charging $299 per month for a software subscription, pricing yours at $249 or $349 positions you relative to an established market expectation. You are not guessing; you are calibrating.

But competitor pricing reflects their cost structure, their customer acquisition strategy, their historical decisions, and their specific positioning—none of which may have anything to do with yours. A competitor who has been in the market for seven years and has amortized their development costs across tens of thousands of customers can sustain a price that would be destructive for a founder who built the same product last year and is still carrying the full weight of that investment.

More importantly, competitor pricing tells you nothing about the ceiling. It tells you where the market has been priced, not where it could be priced. Founders who anchor to competitor rates systematically underprice when their product delivers meaningfully superior value—and they never know it, because they never asked.

Starting From the Other Direction

The more productive framework inverts the conventional process. Rather than beginning with costs and moving toward a price, it begins with two questions that are harder to answer but far more strategically important.

The first question is: what is this actually worth to the customer? Not in the abstract, but in measurable terms. If your software saves a mid-sized accounting firm twelve hours of manual work per week, and that firm bills at $150 per hour, the economic value of your product to that firm is approximately $1,800 per week. That number—not your cost structure—is the ceiling of what the market can bear. Most founders set their price at a small fraction of delivered value because they have never calculated delivered value. They have only calculated their own costs.

The second question is: what do I actually need to sustain and grow this business? This is distinct from what your current cost structure requires. It encompasses the investment needed to improve the product, the margin required to weather periods of lower revenue, and the economics that would allow you to hire the people the business eventually needs. A price that covers today's costs but leaves no room for any of those things is a price that will eventually fail you, even if customers accept it readily.

The Operational Implications of Pricing Backwards

When founders start with what the market will bear and what the business genuinely requires, something important happens: the cost structure becomes a variable rather than a given.

If the market will support $500 per month for your service and you need $350 per month to build a sustainable business, you have $150 of operating room. You can choose to use that room to acquire customers more aggressively, to invest in product quality, or to build a financial reserve. The decision is yours to make.

If, on the other hand, your cost structure requires $480 per month and you have priced at $500 because that is what competitors charge, you have almost no operating room. Every unexpected expense, every slow month, every necessary investment is a crisis. You are not running a business—you are running a margin management problem.

Founders who discover this gap after years of operation often describe the realization as clarifying and frustrating in equal measure. The pricing decision that felt conservative and responsible turns out to have been a slow constraint on everything that followed.

Testing the Hypothesis

The practical implication of treating price as a hypothesis is that it becomes something you test rather than something you set and defend.

This does not require elaborate market research. It requires willingness. Offer your product at a higher price to a segment of new prospects and observe whether conversion rates change meaningfully. Ask existing customers—directly and without apologizing for the question—what they would pay for a version of your product that solved their problem more completely. Identify the customers who never push back on your price and ask yourself whether you are undercharging them.

None of this is comfortable. Founders who have anchored their identity to a particular price point often experience price testing as an existential challenge rather than a strategic exercise. That discomfort is worth examining, because it usually reflects a belief that the current price is correct—and that belief, in most cases, is the hypothesis that most needs testing.

The market has an opinion about what your product is worth. The only question is whether you are willing to find out what it is before you build your entire operation around a number you invented.