The unit you charge for is harder to reverse than the price. Four tests for choosing it, and why per-seat pricing quietly caps most solo products.
A SaaS value metric is the unit you charge for — the "per" in your pricing. Per seat, per project, per run, per contact, or nothing at all for flat pricing. It is a harder decision to reverse than the price itself, and most solo founders make it by accident.
If your customers are individuals, flat pricing with a usage ceiling beats per-seat every time.
The default is per-seat, inherited from software built for teams. If you sell to solo operators, per-seat means every customer sits on one seat forever and your revenue never expands.
Two things get confused here. The pricing model is how customers pay — subscription, usage-based, tiered, freemium. The value metric is what they are paying for.
"$29 per user per month" contains both: subscription model, per-user metric. Founders spend weeks on the model and minutes on the metric, which is backwards. The metric determines whether revenue grows as customers succeed.
It also determines whether your pricing feels fair. A metric disconnected from value turns your invoice into a tax, and customers who feel taxed leave — see the churn reduction framework for what that looks like in the data.
Run every candidate metric through these four. A metric that fails any one of them will cause problems within a year.
Test 1 — Does it rise with customer value? As the customer gets more out of the product, does the number go up? Per-invoice-processed passes: more invoices means more time saved. Per-gigabyte-stored usually fails, because storage tracks your cost, not their benefit.
Test 2 — Can the buyer count it before paying? A prospect should be able to look at your pricing page and work out their own bill. "Per contact" passes — they know roughly how many contacts they have. "Per API call" often fails, because nobody knows their call volume until they are already using you.
Test 3 — Can they game it without losing the value? If customers can consolidate five projects into one to pay less, and lose nothing by doing so, the metric is broken. Per-project fails this constantly. Per-seat fails it too: teams share logins.
Test 4 — Can you actually measure and bill it? A metric you cannot instrument is not a metric. This is the one that quietly kills clever ideas, because outcome-based metrics are usually unmeasurable by a solo founder.
| Metric | Works when | Breaks when |
|---|---|---|
| Per seat | Value grows with team adoption | Your customers are individuals — the common solo SaaS case |
| Flat | One user, one workflow, predictable use | Heavy users cost you more than they pay |
| Per unit of work | Volume tracks value clearly | Volume is unpredictable and buyers fear the bill |
| Per contact or record | The stored set is the asset | Customers delete records to cut costs |
| Tiered by capability | Segments want visibly different things | You invent tiers before knowing the segments |
For most solo subscription products the answer is flat pricing with a generous usage ceiling. It passes tests two and four cleanly, is trivial to explain, and removes the expansion problem by moving customers between tiers rather than counting units.
Standard advice says to analyse usage data across cohorts. With eleven customers there is no cohort, so use the qualitative version instead.
Ask every customer one question: what would have to change about your business for this to become more valuable? The answer names your value metric. If four customers say "when we take on more clients", your metric is clients. If they say "when the team grows", per-seat is defensible after all.
Five answers beat a dashboard here. The customer interview guide covers how to ask without leading the witness.
Do not change your value metric more than once. Changing the price is routine; changing the unit forces every existing customer to re-evaluate the whole relationship. Get it right the second time at the latest.
Once a solo product passes roughly $5k MRR, growth comes from two places: new customers and existing customers paying more. The second one is entirely determined by your value metric.
Flat pricing with no tiers has zero expansion built in. Every customer pays the same on day 700 as on day 1, no matter how much value they extract. That is the structural reason many solo products stall at a plateau — the model has no way for success to show up as revenue.
Fixing this is usually the single biggest change available at the plateau. Breaking the MRR plateau covers the wider diagnosis, and retention vs acquisition covers where to spend the effort.
A value metric is the unit you charge for — the 'per' in your pricing. Per seat, per project, per run, per contact, or nothing for flat pricing. The pricing model describes how customers pay; the value metric describes what they are paying for.
It rises as the customer gets more value, the buyer can count it before paying, it cannot be gamed without giving up the value, and you can measure and bill it reliably. A metric failing any of those four tests causes problems within a year.
Usually not. Per-seat is inherited from software built for teams. If your customers are individuals or one-person businesses, every customer sits on a single seat forever and revenue never expands. Flat pricing with a usage ceiling is normally the better fit.
Ask every customer what would have to change about their business for the product to become more valuable. The answer names the metric. Five direct answers are more reliable than usage analytics on a sample too small to segment.
You can, but not repeatedly. Changing price is routine; changing the unit forces every existing customer to re-evaluate the relationship. Treat it as a decision you get to make at most twice.
Tell Marcus what you charge for and who buys it. You get a specific answer on whether the unit is capping your revenue.
Try GhostCoach free →14-day free trial · cancel anytime · 30-day money-back on Lifetime