Join our community of websites already using SEOJuice to automate the boring SEO work.
See what our customers say and learn about sustainable SEO that drives long-term growth.
Explore the blog →TL;DR: I priced SEOJuice at $29/month on vibes for 18 months. We lost about $4 per customer per month after API and support costs. At 80 customers that was $320/month going the wrong direction. This is how to calculate your SaaS unit price so you don't do the same. Pricing models, LTV/CAC, the math, the mistakes, and the FAQ at the end.
Updated: May 2026.
Pricing isn't about picking a number that "feels right." For SaaS businesses, it's about understanding the costs and the 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 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 (development and salaries, roughly 65% of our monthly burn at the time) and variable (hosting fees, payment processing, customer support). Without this clarity, you risk underpricing and losing money on every new customer. We learned this the hard way: variable cost per customer was higher than expected because AI processing cost 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 unit price, you can determine how many customers you need to break even and the revenue needed to hit your profit goals.
Strategic pricing decisions. A clear unit price informs marketing budget, sales discounting limits, and when to raise prices. It also tells you which customer segments quietly destroy margin (in our case: large-site customers on the entry plan).
When you understand your unit price, every decision gets clearer. Let's walk through how to calculate it.
In SEOJuice's case, unit price equals revenue per active subscription per month, not per seat, because we sell per-domain not per-user. I confused these two for a year. Total revenue looked great while unit economics were underwater, because growth was masking the per-unit loss. If your billing model is per-domain, per-workspace, per-API-call, or per-event, define your unit before you do anything else. (Honestly, this is the step most founders skip because it feels obvious. It isn't.)
For a project management SaaS, the unit might be one seat per month. For a usage-based product like an SMS API, the unit is one message. For a per-domain product like ours, the unit is one tracked site. The math doesn't change. The denominator does.
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.
Before you calculate a unit price, you have to choose a pricing model, because the model decides what a "unit" even is. Five models cover roughly 95% of SaaS, and most teams end up on a hybrid of two.
| Model | What a "unit" is | Real-world examples | Best for |
|---|---|---|---|
| Flat-rate | One plan, one price, all features | Basecamp ($299/mo unlimited users) | Simple products, small audiences, founders who hate pricing pages |
| Per-seat | One paying user / month | Slack, Notion, Linear | Collaboration tools where value scales with team size |
| Usage-based | One unit of consumption (API call, MB, message) | AWS, Twilio, OpenAI API | Infrastructure, AI, anything where cost-to-serve varies wildly |
| Tiered | One plan tier per month (Starter / Pro / Business) | HubSpot, Mailchimp, ConvertKit | Self-serve SaaS with clear feature ladders |
| Hybrid | Tier + usage overage, or seat + feature gate | Stripe (% + fixed), Vercel (seat + bandwidth) | Mature SaaS with both small and large customers on one product |
Remember the $4-per-customer loss I mentioned at the top? That was a pricing-model bug, not a number bug. Flat-rate pricing was wrong for an AI-heavy product because the variable cost per customer wasn't proportional to seats, it was proportional to pages crawled. We were charging by the wrong unit. The number could have been $29 or $59 or $89, the model itself was leaking margin. We eventually moved to a tiered model with a usage overage on pages, which is the hybrid row in the table above. (For what it's worth, OpenView's 2024 SaaS Pricing Benchmark report found that usage-based pricing adoption nearly tripled between 2018 and 2023, and that it correlates with stronger net revenue retention. We arrived there the slow way.)
If your unit economics look bad, change the model before you change the number. I learned this two pricing migrations too late.
Here's the formula we 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.
List every expense 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. I'm still not sure $3 is the right number, it's the number we hit in trailing-12-month data, but I'd hedge it to anywhere between $2 and $4 depending on plan mix.)
Spreadsheet example for cost breakdown (numbers below mirror SEOJuice's actual monthly profile at the 200-customer stage, rounded):
| Expense Category | Cost Type | Monthly Cost |
|---|---|---|
| Developer Salaries | Fixed | $3,000 |
| Marketing Campaigns | Fixed | $2,000 |
| Hosting + AI processing | 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 |
Variable costs dominate at 200+ users in this table. That's the pattern you want to look for, because it's the point where flat per-seat pricing breaks down for AI-heavy products. (It's also the moment to seriously consider a usage component, see the hybrid row in the pricing-models table above.)
Predict how your user base will grow. 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. This could be a flat dollar amount or a percentage of costs. The 20% used below is illustrative, not canonical. The widely cited SaaS benchmark is 70-80% gross margin at scale (see ProfitWell's analysis of SaaS gross margin benchmarks); early-stage indie SaaS often runs lower while the variable-cost mix matures.
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 the business grows. Reassess your unit price every 3-6 months. We do this quarterly, and we've adjusted pricing three times since launch: twice up, once down when we found a cheaper API provider.
Unit price is one number. To know whether that number actually works, you need three more. These are the canonical SaaS unit-economics metrics, and every serious SaaS investor and operator anchors decisions on them.
SEOJuice's numbers (rough, Q1 2026 snapshot): ARPU ~$32, monthly churn ~4%, so LTV roughly $800. CAC is hard to pin precisely because most of our growth is content/SEO with delayed attribution, but our marketing spend per paying signup runs around $90-120 depending on the quarter. That's a 6-9x LTV:CAC ratio, which sounds great until you remember it includes the period when we were underpricing by $4/customer. Once we fixed the unit price, the same ratio looks materially healthier in dollar terms, not just ratio terms.
(I'm still figuring out one thing: how to attribute the long tail of content marketing fairly to CAC. The $90-120 number assumes the SEO content is "free" once written. It isn't. The honest answer is probably 30-40% higher.)
The mistake I made at SEOJuice for 18 months: I treated unit price as a marketing decision instead of an accounting one. Pricing pages are a marketing surface, but the number on them is a P&L decision. If I'd separated those two jobs from day one, the $320/month bleed wouldn't have happened. Specifically: I assumed support cost was negligible, hosting cost was flat, and AI cost would track linearly with seats. All three were wrong by 2-3x.
Solution: create a detailed breakdown of fixed and variable costs, including potential hidden expenses. Regularly update this list. Sanity-check against external benchmarks (OpenView and ChartMogul both publish annual reports referenced above).
Setting a high price can alienate customers if it isn't aligned with perceived value. I watched a competitor (won't name them, they're still around) jump from $49 to $99 without adding meaningful features. Their public reviews shifted noticeably toward price complaints within two months, and their G2 rating dropped about a full star. I don't have their internal churn number, so I won't claim it tripled, but the public signal was unambiguous.
Solution: focus on value-based pricing. Highlight unique features and outcomes. Communicate ROI. Regularly survey users to understand their willingness to pay.
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.
"Pricing is the most important lever you have, and the one most founders touch the least. Most teams revisit pricing once a year. The teams that grow fastest revisit it every quarter."
— Patrick Campbell, founder of ProfitWell (ProfitWell on SaaS pricing)
Solution: run a competitive pricing analysis at least twice a year. 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.
Honestly, three things, in order of impact:
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.
Unit price is the revenue your SaaS earns per single unit of service per billing cycle, where the unit can be a seat, a subscription, a domain, an API call, or whatever you bill on. It's the smallest revenue-bearing slice of your product. Calculating it is the only way to know if growth is making you money or losing it.
Three steps. (1) Add fixed and variable costs at your current customer count. (2) Decide a target profit margin (20% of costs is a starting point; the SaaS benchmark for gross margin is 70-80%). (3) Divide the total revenue target by your current user count. The result is your minimum sustainable unit price. Run the same math at 2x and 5x current users to see if the price still works at scale.
There isn't one. Flat-rate is simplest, per-seat works for collaboration tools, usage-based works for infrastructure and AI, tiered works for self-serve SaaS, and hybrid works for most mature companies. The right answer depends on what drives your variable cost. If cost scales with seats, charge per seat. If cost scales with usage, charge for usage. If cost scales with both, hybrid.
3:1 is the widely cited target. Below 1:1 you're paying to acquire customers who lose you money. Above 5:1 you may be leaving growth on the table by underinvesting in acquisition. Pair this with CAC payback period: under 12 months is top-quartile, 12-18 months is median for B2B SaaS (per ChartMogul's benchmark report).
Quarterly at minimum, especially in your first three years. OpenView's pricing benchmark data shows top-performing SaaS companies revise pricing meaningfully on a 6-12 month cadence; the median company touches it once a year or less. We do a full review every quarter and a light cost check every month at SEOJuice.
Eventually, yes, but with caveats. Grandfather your earliest believers for 6-12 months. Communicate the change with reasoning, not just a notice. Tie the increase to a visible improvement when possible. We've raised prices twice and grandfathered both times; total churn from the increase was under 2% in both cases.
Want to see how your current pricing compares to your variable cost-to-serve? Run a free SEOJuice audit to surface the high-cost / low-margin pages that are quietly eating your unit economics, before you set your next price.
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