Do founding-user price locks make sense?

From the SoleOS answers series — written about our own product space; grounded in published definitions and documented behavior, never invented numbers.

Founding-user price locks make sense when you're trading predictable near-term revenue for lower churn and real word-of-mouth from people who feel like they got in early. They make less sense if your product or pricing model is still changing fast, because you'll end up locking people into a price for a product that doesn't exist yet. The honest way to decide is to model the lock as a cost — a discount you pay for retention and trust — and check whether that cost is smaller than what you'd otherwise spend acquiring and re-convincing customers.

What a price lock actually is

A founding-user lock is a promise: "the price you pay today is the price you'll pay for as long as you stay subscribed, even if list price goes up later." It's different from a lifetime deal (no recurring revenue at all) and different from a plain early-bird discount that expires after a date. The lock ties the discount to the customer's continued subscription, not to a calendar.

That distinction matters because it changes the economics. A time-limited early-bird discount just pulls revenue forward — you get paid sooner, then everyone's on list price. A founding lock is a standing liability: every month that customer stays, you're collecting less than a customer who joined later. You're underwriting their loyalty with your own margin.

SoleOS uses this model — early-access pricing is locked for founding users for as long as their subscription stays active — so this post is partly us explaining our own reasoning. Take the framework, not the conclusion; your numbers will differ.

The math: what you're actually trading

Three things determine whether a lock is worth it:

1. The discount size. How far below your eventual list price is the founding price? A lock at 20% off is a very different bet than one at 50% off.
2. The churn delta. Do locked-in founding users actually churn less? This is the whole bet. If they churn at the same rate as regular customers, you've just given away margin for nothing.
3. The word-of-mouth and feedback value. Founding users who feel ownership over your roadmap tend to report bugs, suggest features, and refer other solo founders. That's real, but it's also the easiest number to overestimate because you can't track it cleanly.

Here's a rough way to frame it without inventing numbers you don't have: take your current monthly churn rate (pull it straight from Stripe or RevenueCat — don't estimate it). Model two cohorts over 24 months: one at full list price with your current churn rate, one at the discounted lock price with a hypothesized lower churn rate. Multiply out total revenue per customer in each case. The lock is worth it only if the churn improvement more than offsets the discount — and you need enough history to check whether that improvement is actually happening, not just assumed.

This is the same kind of cohort math people use for LTV, just segmented by acquisition price. If you're already tracking LTV by plan, add "founding" as a plan-equivalent segment and watch it for a few billing cycles before concluding anything.

When a price lock makes sense

• You expect to raise prices meaningfully within 12–18 months and want a clean story for why early supporters get to keep the old number.
• Your product is validated enough that the current feature set won't change wildly, so you're not locking people into a price for a product you're about to pivot away from.
• You're a solo founder without a sales team, and the lock itself is doing marketing work — "founding member pricing" is a stronger hook in a launch post than "10% off."
• Support cost per customer is low and fairly fixed, so a slightly lower ARPU from early cohorts doesn't blow up your unit economics once you're supporting 500 customers instead of 50.

When it doesn't

• You're still finding product-market fit. If you expect to rework plans, merge tiers, or change what's included within six months, a lock written against today's plan structure will cause support headaches later ("my locked price doesn't match what's in the plan now").
• Your margins are thin and your discount is steep. A 40% founding discount on a product with 30% margins isn't a growth lever, it's a slow leak.
• You have no mechanism to track whether it's working. If you can't segment founding users from regular ones in your billing and retention data, you can't tell if the lock earned its keep — you're just trusting a hunch.
• You run many small products rather than one. Across a handful of apps, founding-lock bookkeeping (who's locked, at what price, since when, on which plan) adds coordination overhead that a single-product founder doesn't have. If you're already juggling tracking Stripe and RevenueCat together across several apps, a per-product patchwork of grandfathered prices is one more thing to reconcile by hand.

A practical structure if you do it

Keep it simple enough to honor without a spreadsheet of exceptions:

• Lock the price, not the feature set. You can add features to a plan without breaking the lock; removing features from under a locked customer breaks trust.
• Put a real cap on it — first N customers, or a hard date — not an indefinite "early access" that never ends. Open-ended locks get awkward in year three when you can't remember who qualifies.
• Decide up front what happens on downgrade/upgrade. Does moving from Maker to Portfolio keep the founding discount proportionally, or reset it? Write this down before your first founding customer asks.
• Track founding vs. non-founding as a first-class segment in whatever tool you use to watch MRR, so the churn-delta question above is answerable with real numbers instead of vibes. If you're comparing options for that, see SoleOS vs Baremetrics or SoleOS vs a spreadsheet for what cohort segmentation actually requires.

How to check if it's paying off

Three months after your founding cohort closes, pull churn and LTV by cohort and compare. If founding users are churning at a visibly lower rate and you can point to unsolicited referrals or testimonials from that group, the lock is earning its discount. If churn looks the same as everyone else, the lock was just a discount with extra paperwork — fine if you needed the early revenue, but stop telling yourself a retention story that isn't true. This is the same discipline as checking a healthy MRR growth rate against your own history rather than a borrowed benchmark: measure your own cohort, don't assume the mechanism works just because it's common.

You don't need a portfolio dashboard to run this check with one product and a spreadsheet. Where it gets harder is once you're running several apps with different founding-cohort cutoffs, different discount depths, and different billing providers — that's a lot of manual segmentation to keep straight by hand across tools.

Frequently asked questions

Does a founding price lock hurt my ability to raise prices later?

No — it's specifically designed so you can raise prices for new customers without having an awkward conversation with your earliest supporters. The risk is the opposite: if you raise prices often, your founding cohort becomes an increasingly large discount relative to list price, so revisit the cap periodically.

Should the lock apply to annual as well as monthly plans?

Yes, and it should probably be the stronger pitch for annual, since you're already asking for a bigger upfront commitment. Just be explicit that the lock applies to the annual rate, not to switching between monthly and annual freely at the locked monthly number.

What if a founding user stops paying and comes back later?

Decide this before it happens. Most founders treat a lapsed subscription as forfeiting the lock — once it's canceled, they re-subscribe at current list price. That's the simplest rule to communicate and the easiest to actually enforce in Stripe or RevenueCat.

Is a founding price lock the same as a lifetime deal?

No. A lifetime deal is a one-time payment for permanent access, with no recurring revenue at all — it's a cash-now, margin-later trade that many solo founders have regretted once support costs stack up. A price lock keeps the subscription recurring; you're discounting the rate, not giving away the product.

How do I know if the discount is too deep?

Check it against your margin, not your gut. If your all-in cost to serve a customer (infrastructure, support time, payment processing) is close to your discounted founding price, you're not running a loyalty program — you're running near break-even for an indefinite period. Model it against your actual costs before you set the number, not after you've sold fifty of them.