In one sentence
Price is essential business design: the amount customers pay determines who buys, what they expect, how the product must be delivered, and which sales, support, marketing, and financing systems the company needs.
Overview
Cohen challenges the advice to avoid discussing price during customer-development interviews. Although price can distract from understanding a customer’s problems, it is also part of product/market fit: people may value a solution in principle but reject it at a particular price. Therefore, founders should investigate not only the problem but also the expected cost, budget owner, approval process, ROI expectations, and changes required to justify a higher price.
The essay’s central device is a ladder of order-of-magnitude price points. Lower prices favor self-service, simple products, word of mouth, viral growth, or venture funding. Higher prices require increasingly hands-on sales, implementation, proof of value, enterprise features, long sales cycles, and substantial cash reserves. The “right” price is not universally high or low; it is the price whose operational consequences match the company’s capabilities and strategy.
Core ideas
Pricing is a product feature
Price affects purchasing decisions as directly as functionality does. A product can solve a real problem and still fail to achieve fit because customers cannot—or will not—pay the asking price.
Each price band creates a different company
At roughly $0–$10 per month, the model depends on scale, low support costs, and organic distribution. Around $100 per month, a bootstrapped B2B company can often support sales and customer service with a manageable customer base. At $1,000 and above, procurement, demos, discounts, case studies, and formal sales become central.
Low price means operational constraint
Cheap products generally cannot afford human support, paid acquisition, or complex implementation. They must be simple, self-service, easy to spread, and inexpensive to operate. A low price is therefore not merely a customer benefit; it dictates product architecture and distribution.
High price means evidence and coordination
Enterprise pricing requires convincing organizations rather than individual users. Buyers may demand ROI analysis, approvals, pilots, integrations, references, implementation help, and on-site engagement. At very high prices, sales cycles can last many months and consume substantial capital.
The middle can suit bootstrapping
Cohen especially favors the approximate $100-per-month range for bootstrapped businesses: it can address a broad B2B market, produce meaningful revenue from a few hundred customers, and leave room to spend on acquisition and support.
Interview for economic reality
Customer research should ask who writes the check, who approves it, what the buyer expects to pay, whether an ROI case would help, and what would need to change to make a substantially higher price credible. This exposes the business model implied by the product.
Practical takeaways
- Choose a tentative price early, then design around its consequences rather than adding monetization after the product is built.
- For low-priced products, prioritize self-service, reliability, simplicity, low infrastructure costs, and distribution through sharing or passionate users.
- For mid-priced B2B products, ensure the economics can fund support, demos, sales material, and customer acquisition.
- For enterprise pricing, plan for procurement, integrations, implementation, references, pilots, discounts, and long sales cycles from the beginning.
- In interviews, test price expectations and buying mechanics—not just whether the problem sounds painful.
- Ask what would have to be true for the customer to pay twice as much; the answer may reveal a more valuable product direction.
Caveats and counterpoints
- The price bands are heuristics, not universal laws. Industry, customer segment, contract structure, usage-based pricing, geography, and product category can shift the expectations attached to a price.
- The article emphasizes business-model consequences more than willingness-to-pay research methods or detailed pricing experiments.
- Its examples and thresholds reflect a 2014 software-startup context; costs, market conventions, and SaaS expectations may differ today.
- Higher prices can improve economics but also narrow the market and increase sales complexity; lower prices can expand adoption but demand scale and disciplined cost control.
Questions worth revisiting
- What price point would support the company I actually want to build—self-service, sales-led, or enterprise?
- At my proposed price, who is the buyer, who approves the purchase, and what evidence do they need?
- Can the product create enough measurable value to justify a higher price?
- Which features, service levels, integrations, or implementation support are implied by the target price?
- Does the expected revenue per customer leave enough margin for acquisition and support?
Return to this when…
Return when setting or revisiting a SaaS or B2B product’s pricing. The price-point ladder is a quick reminder that monetization choices determine product scope, go-to-market motion, staffing, funding needs, and growth speed—not just revenue.