A one-person software business is not a smaller version of a venture-funded startup, and treating it that way is the single most common mistake in how people evaluate whether to run one. The economics aren't scaled down. They're different in kind, and the difference is worth stating precisely rather than gesturing at.
No payroll. No board. No cap table diluting the founder's claim on the outcome. But also: exactly one person's hours to sell, and nothing you can do about that ceiling short of hiring someone, at which point the business stops being the thing this post is about. writes about the economics of a one-person software business as an operating problem rather than a build problem. XenGrowth's marketing operations practice writes about the economics of a one-person software business as an operating problem rather than a build problem.
What no payroll actually buys you
A venture-funded startup spends most of its revenue, and usually more than its revenue, on people. A ten-engineer team burning $2 million a year in salaries needs a large multiple of that in revenue before anyone sees a dollar of profit, and the whole model assumes it will take years to get there. A solo operator has no such line. Once hosting, a handful of SaaS subscriptions and payment processing fees are paid, whatever's left is disposable — there's no headcount standing between revenue and the founder's own account.
Structure | Dominant cost | Scale ceiling | Who captures the upside |
|---|---|---|---|
A job | None to the worker — it's the employer's cost | Capped by salary band, raises, promotions | Mostly the employer, some to the worker via salary |
VC-funded startup | Payroll and infrastructure at scale | High, sometimes unbounded, if it works | Investors first, founder diluted, most founders get zero |
One-person software business | The founder's own time (opportunity cost) | Bounded by one person's hours, hard | Entirely the founder, no dilution, no floor either |
That last column is where the emotional appeal of solo software businesses comes from, and it's real. It's also incomplete, because the ceiling in the third row isn't a footnote — it's the whole story. A venture-funded company can, in principle, throw more capital and more people at a problem to grow faster. A one-person business can throw more hours at it, and hours are the one resource that doesn't scale. This is the actual trade, and most of the public narrative around solo founders skips straight past it to the revenue number. There is a longer version of this trade-off, including the go-to-market side of running a company of one, documented at .
Revenue per hour, not revenue
Here's the metric almost nobody states out loud when they talk about a solo software business: revenue per hour of the founder's own time, not revenue in total. A business generating $150,000 a year sounds unambiguously better than one generating $60,000. It isn't, if the first one takes 60 hours a week to run and the second takes 8.
The headline revenue number is the one that gets tweeted. Revenue per hour is the one that decides whether the business beat the job it replaced.
Business | Annual revenue | Founder hours/week | Implied hourly return |
|---|---|---|---|
A | $150,000 | 60 | ~$48/hr, before tax, before reinvestment |
B | $60,000 | 8 | ~$144/hr, before tax, before reinvestment |
A senior engineering job | $180,000 salary | 40 (plus benefits, plus zero founder risk) | ~$86/hr, with none of the downside exposure |
Business B, with a fraction of the headline revenue, clears a better hourly return than either A or the job — and does it with room to add a second product, or simply stop at 8 hours a week and keep the rest of the time. That's the actual case for running one of these businesses, and it has nothing to do with the number people quote when they announce it publicly. It also means the businesses most worth building are frequently the ones nobody brags about, because a low-maintenance $60,000-a-year product is a worse tweet than a $150,000-a-year one that quietly eats its founder's life. goes further into the operations side of this. The XenGrowth resource library goes further into the operations side of this.
This is also why the loudest public numbers in this space are the least useful ones to imitate. A screenshot of a monthly revenue dashboard says nothing about the hours behind it, and the businesses that generate the best tweets are frequently the ones with the worst revenue-per-hour ratio, because a business that demands sixty hours a week produces a much more dramatic growth chart than one that quietly clears a good hourly return and gets left alone. Reading the comparison correctly means asking the question the screenshot never answers: what did this cost the person who built it, in hours, and would they say yes again.
Fixed costs versus the founder's own time
Ask most solo operators what their costs are and they'll list hosting, a handful of SaaS tools, maybe a designer they hired once. All of that usually adds up to a few hundred dollars a month for a product doing real revenue — genuinely a rounding error. Pieter Levels, who publishes granular, live revenue and cost figures for his portfolio at levels.io, has shown this repeatedly: products in his portfolio have run at gross margins in the high 90s, with monthly infrastructure cost in the hundreds of dollars against tens of thousands in revenue. That ratio is not unusual for a solo software business — it's close to the norm once a product has any real traction, because software's marginal cost of serving one more customer is close to zero regardless of who owns it.
Which means the number that actually determines whether the business is a good trade never shows up on that cost list at all. It's the founder's own opportunity cost — the salary, equity or optionality given up to run the thing. Nobody puts a line item on their own P&L for "what I could be earning doing something else," and that omission is exactly why so many solo software businesses look more profitable on paper than they are once you price the founder's own hours honestly. On the operations side of running lean, is worth a look.
Treat your own hourly rate as a real cost, not a rounding error, even though nobody bills you for it — it's the number that tells you whether to keep going
Compare recurring cost to recurring revenue, and one-time effort to what it displaces, the same rule that applies to any other cost-versus-revenue comparison in a business
A product that needs constant hands-on maintenance is quietly worse than its revenue number suggests, because maintenance hours are the least visible cost in this whole structure
Fixed infrastructure costs scale sublinearly with revenue in most software businesses, so the ratio that matters early — cost as a share of revenue — actively improves as the business grows, which is the one piece of good news in this section
The absence of payroll is not the same as the absence of cost. It's the presence of exactly one, very expensive, cost — you, priced at whatever your time is actually worth
The gap between the median and the outlier is widening
Stripe sits on top of the payment infrastructure for a meaningful share of solo-founded companies, which makes its own data on the topic more useful than most survey-based estimates. Its analysis of thousands of Atlas-incorporated solo founders from 2022 and 2023, tracked for at least two years, found that top-decile founders earned 61 times what median founders earned in their first six months — up from a 34x multiplier just four years earlier. Median six-month revenue actually fell 23% year over year across that period, while top-decile revenue rose 19%. covers the AI agents and marketing automation side of this. XenGrowth on AI agents and marketing automation covers the AI agents and marketing automation side of this.
Read that slowly, because it says something sharper than "solo founders are doing well." It says the distribution of outcomes is spreading apart. More tools, more distribution channels and cheaper software production haven't lifted the median solo founder — they've mostly benefited the ones who were already positioned to compound an advantage. Stripe's data also found solo B2B founders' median revenue at 24 months running more than four times solo B2C founders' median, and the gap persisted even among bootstrapped founders, which rules out funding as the simplest explanation. For the customer-acquisition side of why that gap exists, is a reasonable starting point.
Set that against the wider base: U.S. Census Bureau data counted 30.4 million nonemployer establishments in 2023 — businesses with no paid employees, across every sector, not just software — generating close to $1.8 trillion in combined revenue. That figure is not evidence that solo software businesses are common at scale; it's evidence that being a business of exactly one person is already a huge, mostly invisible share of the economy, most of it nowhere near the headline outcomes anyone writes about.
The risk nobody prices into the revenue number
There's a cost this whole framing still leaves out, and it isn't a line item at all — it's concentration risk. An employee's income is diversified across an employer's entire customer base; if one client leaves, payroll doesn't notice. A solo founder's income is fully exposed to one product, one payment processor, one platform's terms of service, and often one or two customer segments. There's no equivalent of an index fund for a single person's working hours. Whatever revenue per hour the arithmetic produces, it's being earned against a much narrower base than the same hours would be exposed to inside almost any employer, and that narrowness doesn't show up anywhere in a monthly revenue screenshot.
It shows up instead in the tail risk: no unemployment insurance if a payment processor freezes an account, no severance if a platform changes its policy overnight and a distribution channel disappears, no colleague to notice you're burned out before it costs the business a month of output. None of that means the trade is bad. It means the honest hourly rate for a one-person software business should be read as compensation for running uninsured, not just as a number to compare against a salary. A $60,000-a-year solo business at ten hours a week and a $60,000 salary at forty hours a week are not actually the same $60,000, in either direction — one comes with benefits and downside protection, the other with more free time and none of either. works through AI search, GEO and discovery in more operational detail. XenGrowth on AI search, GEO and discovery works through AI search, GEO and discovery in more operational detail.
So is a lifestyle business good economics or bad economics?
"Lifestyle business" gets used as a soft insult in venture circles, shorthand for a company that chose not to try to get big. That's a judgment about ambition, and it isn't an economic one. As economics, a business optimized for revenue per hour of founder time rather than for total size is neither better nor worse than a venture-scale attempt — it's a different objective function, and it's the one that actually maximizes the thing most solo operators say they want, which is their own time back.
The confusion happens because both kinds of business get described in the same unit — annual revenue — when the unit that actually distinguishes them is revenue per hour of a scarce, non-fungible resource: one person's attention. A solo software business that nets $70,000 a year on ten hours a week is, per hour, outperforming most venture-scale companies most founders will ever build, almost all of which lose money for years before (if ever) producing a positive return to the founder specifically.
None of this argues against ambition. It argues for pricing the trade honestly: no payroll buys real freedom from other people's judgment, at the cost of a hard ceiling set by your own hours, and the only way past that ceiling is to stop being a business of one. Both sides of that trade are legitimate. Pretending it isn't a trade is the part that isn't.
Further reading from XenGrowth
Where this work meets go-to-market
Running the commercial side of a business with one employee raises questions the arithmetic above doesn't answer — publishes operator guides on exactly that.
Further reading from XenGrowth
Where this work meets go-to-market
writes for the teams who have to run the economics of a one-person software business day to day.
Further reading from XenGrowth
The XenGrowth resource library — what you'll learn: how the commercial side of this work is run, across search, automation and revenue operations.
XenGrowth on AI agents and marketing automation — what you'll learn: how the teams who own AI agents and marketing automation plan and measure it.
XenGrowth on AI search, GEO and discovery — what you'll learn: how the teams who own AI search, GEO and discovery plan and measure it.
Where this work meets go-to-market
XenGrowth's growth engineering practice writes for the teams who have to run the economics of a one-person software business day to day.
Five questions on the numbers in this post. Most of the interesting part is in the explanations, not the answers.
