Pricing a software product sounds like a business problem but it’s really a philosophy problem. What do you believe the thing is worth, who are you building it for, and what does the money need to do?

For Flow, I’m working through those questions in public, with no company entity yet, no runway, and infrastructure that currently costs me almost nothing because I’ve kept the stack deliberately small. That context shapes every option I consider.

The actual constraints

Before I can think about price, I have to be honest about the situation. Flow runs on free-tier infrastructure and a personal card. There is no company. I looked at activating an Estonia e-Residency OÜ early on, but a company costs money to maintain when it isn’t generating revenue, and I’d rather not carry that overhead prematurely. The threshold that makes sense to me is somewhere around 50 paying subscribers. That’s the point where the fixed costs of a legal entity are proportional to what’s coming in.

Until then, I’m a solo founder with a product in early beta. The constraints are real: no refunds at scale, no support SLAs, and no legal entity to absorb liability the way a registered company would. Any pricing decision has to be honest about that, not paper over it.

What this means practically: the first monetization has to be simple, low-overhead, and tied to people who genuinely believe in the direction of the product. Not a growth funnel. More like a mutual bet.

The models I looked at

I went through the usual options.

Starting with free and no monetization: that’s only sustainable if I have another income source indefinitely and don’t care about Flow ever becoming self-funding. That’s not the goal. I want the product to pay for itself so I can build it full-time eventually.

Freemium with a paid tier is the classic SaaS move. The problem is that freemium requires volume. You need thousands of free users to convert even a few hundred. That’s a marketing and distribution challenge I don’t have the resources for right now. Freemium also creates a product design tension where you’re always asking “is this feature free or paid?”, which fragments decisions. For a small product, that friction adds up.

A one-time purchase or lifetime deal is tempting because it generates immediate revenue without ongoing billing infrastructure. The downside is that it misaligns incentives over time. If I’ve sold lifetime access, the financial pressure to keep improving the product drops. I also can’t predict what Flow’s long-term hosting or API costs will look like, and locking in lifetime revenue now could mean losing money on every lifetime user if AI inference costs increase.

A subscription makes sense for ongoing software with ongoing costs. Recurring revenue is what funds ongoing development. The challenge is earning it. People are subscription-fatigued, and a productivity app has to deliver consistent value to survive renewal cycles.

A founding-member tier with a discounted subscription is where I’ve landed for now. It’s a hybrid: early supporters get a lower rate locked in permanently, in exchange for joining before the product is fully proven. They take on some risk. In return, I commit to those members as the first priority for feedback, features, and support.

Why a founding tier makes sense first

The first people who pay for an unfinished product are doing something different from buying a product. They’re funding a direction. They’ve seen enough to believe it’s worth betting on, and they’re willing to do that before the app is polished or well-known.

That deserves recognition, not just a receipt.

A founding tier acknowledges the asymmetry. The price should be lower than what I’d charge at launch, not as a discount promotion but as an honest reflection of what you’re getting: early access, fewer features, more rough edges, but also a direct line to the person building it. Your feedback actually shapes what gets built next. That’s a different product than what someone buys at version 1.0.

The number I’m thinking around is somewhere in the range of a few euros per month, locked permanently for founding members, while a standard subscription later would be higher. Those aren’t committed numbers. The infrastructure costs and the exchange rate between effort and value will influence where I land. But the logic holds regardless of the exact figure: early supporters pay less and get more influence, which is a fair trade.

This also avoids launching into silence. If I wait until the product is “ready” to think about monetization, I’ll have optimized for a user who doesn’t exist yet. The founding tier lets me build with real paying users in the loop from early on.

Value framing: what Flow actually costs people

Productivity apps occupy a weird position in software pricing. Tools like Figma or Linear are enterprise-adjacent. Companies pay for them, so the price scales with team size and business value. Consumer apps live and die on $10/month thresholds because people are paying personally and comparing against everything else they subscribe to.

Flow sits somewhere in between. It’s a personal tool, but the person using it is often losing real money to distraction. An hour of deep work lost to fragmented attention is an hour of output not produced. For freelancers, consultants, or anyone billing their time, that has a direct cost.

I’m not going to do the “it pays for itself in 12 minutes” math, because that’s the kind of framing people rightly distrust. The honest case is simpler: if Flow helps you reliably get into deep work faster and stay there longer, the value of that is not comparable to what a monthly subscription costs. The question isn’t whether the value is there. It’s whether the product is good enough to deliver it consistently.

That’s the actual work, and pricing follows from it.

What triggers the company

Around 50 paying subscribers is where the math shifts for the OÜ. At that point, the monthly revenue covers the cost of maintaining a proper entity, handling VAT, and having a legal home for the product. Before that, the overhead outweighs the benefit.

The stack decisions I’ve made reflect this same logic: keep costs close to zero until there’s real revenue to justify them. I wrote about the specific infrastructure choices in Building Flow on a zero-budget stack, which covers what’s actually free vs. what costs money as you scale. The short version: free tiers get you further than most people expect, but they have failure modes that a growing product eventually hits.

The founding-member tier is what bridges that gap. If enough people join early, the OÜ gets activated, proper billing infrastructure goes in, and Flow becomes a real business with a legal identity. If not, I keep building and the entity waits.

Where this lands

I don’t have a published price yet. What I have is a framework: founding tier first, subscription later, company when the numbers justify it. The product has to earn each step.

If you’re reading this and thinking about whether Flow is something you’d pay for, the most useful thing you can do right now is get on the early access list. That’s where founding-member details will land first, before anything goes public.

Join the early access list at flowdeep.app

No pressure, no countdown timer. Just a list of people who want to know when the founding tier opens.