SaaS Pricing for Founders: A Cost to Build to Sell Framework
SaaS pricing is the decision about how much to charge customers for access to the product and how to structure that pricing (per seat, per usage, per feature tier, or some combination). The cost to build to sell framework connects pricing to the cost structure of the product: the infrastructure cost per customer, the customer acquisition cost, the support cost per customer, and the gross margin required to build a sustainable business. Pricing that does not account for these costs produces a product that grows in users but shrinks in profitability.
What you need to know
- SaaS gross margin should be 70 to 85 percent. Infrastructure and support costs that exceed 15 to 30 percent of revenue indicate a pricing or cost structure problem.
- Calculate the minimum viable price from actual COGS before pricing based on market comparison or intuition.
- Customer acquisition cost payback should be under 18 months. Prices that produce longer payback require continuous capital to fund growth.
- AI features with LLM API costs require specific per feature cost analysis. LLM costs that scale with usage can produce negative gross margin for heavy users if the pricing is flat.
- Value based pricing produces better margins than cost plus pricing but requires genuine customer research to calibrate correctly.
The core argument
Most founders set prices by looking at competitors and slightly undercutting them, or by guessing what the market will bear, without doing the cost analysis that would tell them whether the price is profitable. The result is products that have users and growth but do not have a viable business model, because the infrastructure and support costs consume the gross margin before any overhead or profit remains.
The framework that works: start with the unit economics. What does it cost the company to serve one customer for one month? This includes hosting, third party APIs that scale with usage, customer support time allocated to support volume, and payment processing. This is the COGS floor. From there, work backward from the target gross margin to the minimum price. Then work upward from value based analysis to understand the maximum price the market will support. The pricing decision lives in the range between the minimum (the cost based floor) and the maximum (the value based ceiling).
The insight that most early stage founders miss is that the pricing decision is also a positioning decision. A $29 per month price attracts self serve customers with price sensitivity. A $299 per month price attracts buyers who are solving a business problem and have budget. A $2,999 per month price attracts enterprise buyers with procurement processes. The same product can be positioned at any of these price points with different packaging, but the strategy for reaching the market and the customer success model are completely different at each level.
Common mistakes
Not tracking infrastructure costs per customer. Many founders know total AWS costs but not the cost per customer, which makes it impossible to calculate gross margin accurately. Implement per customer cost tagging in AWS or use a cost allocation tool that breaks costs down by product tier or customer segment.
Underpricing to win early customers, without a plan to raise prices. A product priced at $9 per month to attract early adopters faces significant challenges raising to $49 per month when the cost structure requires it. Early customers who agreed to $9 per month expect grandfather pricing, and raising prices risks churn. Price based on the sustainable unit economics from the start, even if it means slower early growth.
Ignoring support costs in the pricing model. Support is a real COGS item for SaaS products. A product that requires two hours of onboarding support per customer at $50 per hour has $100 of support COGS per customer acquisition, not counting ongoing support. Include support costs in the unit economics calculation.
Treating AI feature costs as negligible. LLM API costs (OpenAI, Anthropic) are not negligible at scale. A feature that calls GPT-4 three times per user session at $0.01 per call costs $0.03 per session. A user with 100 sessions per month generates $3 in LLM costs. At $29 per month, this is 10 percent of revenue from a single customer's AI feature usage before any other costs. Model the LLM cost per user per month before including AI features in a flat subscription price.
Setting prices without testing willingness to pay. Willingness to pay testing does not require selling at the higher price; it requires asking potential customers whether they would buy at specific price points. The Van Westendorp pricing model (asking about price acceptance ranges) produces useful data about the price range the market considers reasonable. This research takes a week and prevents pricing mistakes that take months to correct.
Where to start
Calculate the current COGS per customer. Pull the AWS bill, third party API invoices, and support hours for the last month. Divide by the number of active customers to get the monthly COGS per customer. This number is the cost floor for pricing.
Calculate the current gross margin. Monthly revenue minus monthly COGS, divided by monthly revenue. Compare to the 70 to 85 percent target range. If below 70 percent, identify which cost line is disproportionate and either reduce it or adjust pricing.
Run a value based pricing analysis for one customer segment. Interview five customers from the segment. Ask: what was the most expensive alternative to solving this problem? What would it cost if this product disappeared tomorrow and they had to solve the problem another way? What would they pay for the product if they had to justify it to a procurement team? The answers calibrate the value based ceiling for pricing.
- Software Costs That Founders Underestimate
- Plan Upgrades and Downgrades: A Billing Architecture Story
FAQ
Frequently asked
- What is gross margin for a SaaS product and what is a healthy range?
- How do you calculate the minimum viable price for a SaaS product?
- What is customer acquisition cost and how does it relate to pricing?
- What is value based pricing and how does it differ from cost plus pricing?
- How does per seat vs per usage pricing affect the cost structure?
Author
The engineering bet behind Yashveer Labs
The bet I am running with Yashveer Labs is simple. Most software is built by people who treat it as a job. I treat it as a craft. I am Yashveer Singh, founder, with five production systems on the board so far, and the arc points toward machine learning, AI engineering, and cybersecurity. If your project sits in any of those orbits, you are reading the right page.