TL;DR: Your unit price determines whether your SaaS is sustainable. Here's how to calculate it — and what to do when the number doesn't look good.
Pricing isn't just about picking a number that "feels right." For SaaS businesses, it's about understanding the costs and value behind each unit of your service. That's where unit price comes in. Indie founders, listen up — because I got this wrong for the first 18 months of building SEOJuice and it nearly killed the business.
When we launched, I priced our plans based on what competitors charged. $29/month felt right because other tools were at $29. No cost analysis, no margin calculation, just vibes. Three months in, I ran the numbers and realized we were losing about $4 per customer per month after accounting for API costs, hosting, and support time. At 80 customers, that's $320/month going the wrong direction. Not catastrophic, but not exactly the business model you want to scale.
Unit price is the cost per unit of your service, whether that's a single subscription, user, or seat. It represents the financial foundation of your business model. Think of it like this: If your SaaS has 100 customers paying $30 each, your unit price determines:
Profitability
Your unit price ensures you're covering all costs — both fixed (like development and salaries) and variable (like hosting fees or customer support). Without this clarity, you risk underpricing and losing money on every new customer. We learned this the hard way: our variable cost per customer was higher than expected because our AI processing costs scaled non-linearly. Every new customer with a large site cost us more than a customer with a small site, but we charged them the same.
Scaling
Growth is exciting, but it's only sustainable if your pricing scales with you. By calculating your unit price, you can determine how many customers you need to break even, and the revenue needed to achieve your profit goals.
Strategic Pricing Decisions
A clear unit price informs everything from marketing to sales strategies. It helps you set competitive prices that align with customer value and identify when it's time to raise prices to match increasing costs or added features.
When you understand your unit price, every decision becomes clearer. Let's walk through how to calculate it.
Unit price refers to the cost per individual unit of your service, typically measured as one user or one subscription for SaaS businesses, or the smallest billable portion of your product offering.
For example: if you run a project management SaaS, the unit price might be the cost for one user per month. For a subscription-based SaaS, it could be the price of one plan.
It's easy to confuse unit price with total pricing or overall revenue, but they're distinct:
By zeroing in on unit price, you can answer whether you're charging enough to cover costs and generate profit, and how your pricing scales as you gain more users.
Here's the formula we eventually settled on at SEOJuice, after burning through two pricing models that didn't work. The math itself is straightforward — the hard part is being honest about all your costs.
Begin by listing all the expenses associated with running your SaaS. Divide them into two categories:
(Side note: "customer support" is the cost most founders underestimate. We budgeted $1/user/month for support and the real number was closer to $3. Every "quick question" email costs time, and time costs money.)
Spreadsheet Example for Cost Breakdown:
| Expense Category | Cost Type | Monthly Cost |
|---|---|---|
| Developer Salaries | Fixed | $3,000 |
| Marketing Campaigns | Fixed | $2,000 |
| Hosting | Variable ($5/user) | $1,000 (200 users) |
| Payment Processing | Variable ($1/user) | $200 (200 users) |
| Customer Support | Variable ($2/user) | $400 (200 users) |
| Total Costs | - | $6,600 |
Predict how your user base will grow over time. Use conservative estimates — I cannot stress this enough. Our first forecast assumed we'd hit 500 customers in 6 months. We hit 300 in 12 months. The optimistic forecast would have had us pricing too low to survive the slow months.
Spreadsheet Example for Customer Growth Forecast:
| Time Frame | Expected Users | Variable Costs (@ $8/user) |
|---|---|---|
| Current | 200 | $1,600 |
| 6 Months | 300 | $2,400 |
| 12 Months | 500 | $4,000 |
Add a profit margin to your calculation. This could be a flat dollar amount or a percentage of your costs. For example, desired profit: 20% of total costs.
Spreadsheet Example for Profit Margin:
| Metric | Value |
|---|---|
| Total Costs | $6,600 |
| Desired Profit (20%) | $1,320 |
| Revenue Target | $7,920 |
| Users (Current) | 200 |
| Unit Price | $39.60/user |
Costs and user numbers change as your business grows. Reassess your unit price every 3-6 months. We do this quarterly now, and we've adjusted pricing three times since launch — twice up, once down when we found a cheaper API provider.
One of the biggest mistakes is failing to account for all the expenses associated with running your SaaS. It's easy to focus on obvious costs like hosting and development, but hidden costs can eat into your margins.
Solution: Create a detailed breakdown of fixed and variable costs, including potential hidden expenses. Regularly update this list as your business evolves.
Setting a high price can alienate customers if it's not aligned with the perceived value of your service. I've seen this happen to competitors who jumped from $49 to $99 overnight without adding features. Their churn rate tripled in two months.
Solution: Focus on value-based pricing. Highlight your unique features and outcomes. Communicate the ROI your customers get from your product. Regularly survey users to understand their willingness to pay.
Your pricing exists within a competitive market. Pricing too low compared to competitors can signal inferior quality. Pricing too high without differentiation can push potential customers away.
Solution: Perform regular competitive pricing analysis. Compare features, pricing tiers, and target audiences. Identify what makes your SaaS unique and position your pricing as competitive but reflective of your added value.
Setting your unit price is a balance between costs, value, and competition. Pricing isn't static — it evolves with your product, market, and customers. The founders who get pricing right are the ones who revisit the numbers regularly, talk to their customers about value, and aren't afraid to change course when the math tells them to.
Related reading:
Unit price ≠ value.
tbh the article explains break-even well, but avg unit price hid problems for us — support-heavy customers blew up margins even though hosting costs were tiny; we switched to cohort contribution-margin models and priced by feature set instead. Anyone else model per-cohort break-even rather than a single avg unit price?
Love the unit-price breakdown — really clear on fixed vs variable costs 👍 But IMO focusing only on per-unit cost can be misleading for SaaS since marginal hosting is often near-zero; a tutorial on folding LTV/CAC and churn into the unit-price calc would be 🔥🙏
no credit card required
