You Don't Own a Software Business. You Own a Math Problem
Johnny is a software developer. He wants to make money online but is not sure about the market potential of the software he wants to build. He estimates it will take 6 weeks of development work to build the service to the part it will be minimally useful to anyone in that field ( Minimally Viable Product). He assumes there are enough people that have money and are willing to spend it on solving this problem. So when can Johnny expect to see meaningful results on the 6 weeks of work. Please show your work.
One of the most important things to remember in any business venture is that you do not own a business, you own a math problem.
A difficult word problem to be specific.
So here is how you math problem actually looks in real like in real life ( as I understand it as of this moment, which changes constantly, so please take everything I say with a grain of salt)
Johnny is a software developer. He wants to make money online but is not sure about the market potential of the software he wants to build. He estimates it will take 6 weeks of development work to build the service to the point it will be minimally useful to anyone in that field ( Minimally Viable Product). He assumes there are enough people that have money and are willing to spend it on solving this problem.
- According to the Pareto distribution ( Power-Law) we know that 80% of our results come from 20% of our efforts.
- Search engines dont list your software immediately it takes anywhere from 3 months to a year to be fully visible
- Churn Rates vary wildly but average 8-15 % on average
So when can Johnny expect to see meaningful results on the 6 weeks of work. Please show your work.
So ..... when can Johnny expect meaningful results?
Let's do the math honestly.
Johnny finishes his MVP after 6 weeks. He launches, submits to Google Search Console, and waits. The search engine clock starts now — not when he had the idea, not when he started coding. Now.
Conservative estimate: 90 days before meaningful organic traffic arrives. Optimistic: 6 months before he's ranking for anything competitive.
Let's use 90 days and call it generous.
So we're at week 6 plus 13 weeks. Roughly month 5 before anyone organic finds him.
Now Pareto enters the picture. If Johnny is like most developers launching a product, he has one app. One shot. The Pareto principle doesn't help Johnny — it only helps people with enough attempts to let the distribution work in their favor. With one app, Johnny is gambling, not farming.
But let's say traffic arrives at month 5. Some percentage of visitors convert to a free trial. Some percentage of those convert to paid. Industry averages suggest roughly 2-5% of organic visitors become paying customers. Johnny needs to know his traffic numbers to work this part of the equation, and he won't know them until month 5 at the earliest.
Let's say he gets 10 paying customers by month 6. Good start.
Now churn enters. At 10% monthly churn — the low end of average — Johnny loses 1 customer per month while acquiring new ones. His subscriber base only grows if he acquires faster than he churns. At 10 customers and 10% churn that means he needs more than 1 new customer per month just to stay flat.
Steady state subscribers = new customers per month ÷ churn rate.
If Johnny acquires 5 new customers per month and churns at 10%, his business stabilizes at 50 subscribers. At $29/month that's $1,450 MRR. Not life-changing. Not nothing.
So when does Johnny see meaningful results?
Month 5 before he has any data. Month 8-9 before he has enough data to know if the math works. Month 12 before steady state gives him a reliable revenue number to plan around.
That's 12 months of work, waiting, and compounding uncertainty on 6 weeks of development.
The math isn't cruel. It's just honest. And most people don't do it before they start.
The developers who win are not necessarily the best coders. They're the ones who understood the word problem before they wrote the first line.
Here is where the math gets cruel.
Johnny gets impatient and starts buying keywords and ad space before he knows anything about organic demand.
He figures he'll shortcut the 90-day SEO wait. He opens Google Ads, sets a daily budget, and starts driving traffic to his landing page. It feels like progress. The dashboard shows impressions, clicks, sessions. Numbers going up. The dopamine hit of visible momentum after months of invisible work.
But Johnny has made a math error that will cost him more than money.
He has confused activity for information.
Paid traffic and organic traffic are not the same customer. The person who clicks an ad was interrupted. The person who finds you through search was looking. These two people convert differently, churn differently, and tell you completely different things about your product's viability. By mixing them together before he has any organic baseline, Johnny has contaminated his own dataset. He no longer knows what his numbers actually mean.
Let's run the math on what Johnny is actually buying.
A competitive keyword in a software niche costs $2-8 per click on the low end. Let's call it $4. Johnny sets a modest budget of $500/month. That buys him 125 clicks per month.
At a 3% conversion to trial that's 3-4 trial users per month.
At a 20% trial-to-paid conversion that's less than 1 paying customer per month.
At $29/month subscription price, Johnny is spending $500 to acquire a customer worth $29.
His payback period on that customer at 10% monthly churn — meaning an average customer lifetime of 10 months — is $290 in lifetime value against $500 in acquisition cost.
Johnny is paying $500 to lose $210. At scale.
And it gets worse. Because Johnny isn't looking at it this way. He's looking at his dashboard seeing traffic and telling himself the product is working. He extends the campaign. He tweaks the ads. He A/B tests headlines. He is now running an advertising business that happens to have a SaaS product attached to it, and the advertising business has negative unit economics.
Month 8. Johnny has spent $4,000 on ads. He has 11 paying subscribers generating $319 MRR. He has no idea whether any of them would have found him organically because he never gave organic a chance to breathe. I do get it though, nobody wants to waste weeks, or years, of work.
Month 10. He pauses the ads to save money. Traffic drops to near zero. Half his trials evaporate. His 11 subscribers feel less like a business and more like a coincidence. It feels that way, because that is what they were.
This is where most solo developers quit. Not because the product was wrong. Not because the market wasn't there. But because they ran out of patience and money simultaneously, in a math problem that required exactly one of those things to solve it: time.
The search engine was going to deliver Johnny customers at zero marginal cost. It just needed 90 days. He bought himself 4 months of expensive noise and called it traction.
The math was never the enemy. Johnny's relationship with uncertainty was the enemy. And Google Ads was the most expensive way he could have expressed that discomfort.
This is even assuming that Johnny won the lottery and happened upon the 2/10 that would have actually gotten traction to begin with, because some just die in obscurity.
So, things to remember. You are statistically wrong about someone wanting your idea real bad. 80% or so of all apps either get zero users or a minimal amount. Buying ads before establishing organic demand will pollute your dataset. Stop optimizing for too much traffic, you could probably handle the amount of 1st year traffic you are going to get on a 1990's laptop running period correct php. Dont get too excited about your idea until it is tested in a cold market. Market signals dont care about your feelings.
Remember, Everything is a math problem and variables. Even if you dont want to admit it. Fortune favors the undying persistent.