We scored every category for how buildable it is by one person, then checked what those businesses actually earn. The gap between the two is where most solo founders get stuck.
Most one-person business lists are written by people who have never had to answer support tickets at 11pm. They optimise for what sounds appealing rather than what one human can sustainably operate.
We approached it from the data instead. We score categories on buildability, which estimates how feasible a product is for a very small team, and we track what products in those categories actually earn. Putting the two together produces a much less romantic picture, and a far more useful one.
Everything below was queried live on 5 August 2026.
The best one-person businesses in 2026 sit in categories scoring 7.0 or above for buildability where existing supply is thin. Newsletters and publishing tops the list at 7.5. Avoid scheduling and booking: it scores lowest at 6.6 and already holds 100+ small competitors. Expect $500 to $5,000 MRR, not more.
Before the ideas, the arithmetic. These are the revenue bands across the products we track, and the shape of the distribution matters more than any single number.
| Band | Products | Median MRR | Average MRR | Still one person? |
|---|---|---|---|---|
| Under $500 | 2,500+ | ~$50 | ~$105 | Yes, and usually a side project |
| $500 to $5,000 | 800+ | ~$1,265 | ~$1,698 | Yes. This is the realistic target |
| $5,000 to $20,000 | 250+ | ~$8,962 | ~$9,965 | Possible, with deliberate low-touch design |
| $20,000+ | 130+ | ~$35,562 | ~$92,782 | Rarely. Most have hired by here |
The biggest group by a wide margin is the bottom one, and its median is $50 a month. That is the base rate. Any plan that assumes you skip that tier is a plan built on the exception.
The band worth aiming at is the second one. For one person with low costs, $1,000 to $5,000 MRR is a genuine income with no boss, and it is achievable in a year or two of consistent work. We collected worked examples in solo developer revenue examples and tracked the wider picture in the state of indie SaaS revenue.
Buildability estimates how feasible a product in a category is for a very small team, based on integration surface, operational burden, and how much of the value is software rather than service. Higher is easier for one person.
| Category | Small products | Buildability | AI-native |
|---|---|---|---|
| Newsletters and publishing | 22 | 7.5 | 0 |
| Consulting tooling | 13 | 7.4 | 1 |
| Project management | 38 | 7.3 | 0 |
| Design studio tooling | 15 | 7.3 | 0 |
| No-code and internal tools | 25 | 7.2 | 0 |
| Marketing automation | 32 | 7.1 | 2 |
| Membership communities | 46 | 7.0 | 0 |
| Forms and surveys | 37 | 7.0 | 2 |
| Events and ticketing | 33 | 7.0 | 0 |
| Invoicing and billing | 67 | 6.7 | 5 |
| Scheduling and booking | 104 | 6.6 | 8 |
Read the first and last rows together. The easiest category to build in has 22 small products. The hardest has 104. Difficulty and competition are moving in opposite directions, which is the single most useful thing on this page.
Scheduling and booking is the most common first idea for a solo founder, and our data says it is close to the worst available choice. It carries the lowest buildability score in the set and the highest number of existing small competitors by a factor of nearly five over the top-scoring category.
The reason is structural. Scheduling looks simple and is not. Calendar synchronisation, timezone handling, cancellation policies, payment capture, and reminder delivery are each individually fiddly and collectively a full-time job. Meanwhile every founder has personally experienced scheduling friction, so everybody has the idea.
The general rule: the categories worth entering are ones you had to research, not the ones you thought of in the shower. We map crowding across the whole market in SaaS market saturation and low competition SaaS ideas.
The highest buildability score in the set, and the lowest operational burden. Publish for one trade nobody covers, and sell sponsorship to the vendors who need to reach it.
Why it suits one person. No support tickets, no uptime obligation, no integrations. The work is entirely research and writing, which scales with your hours rather than your customer count.
The catch. It never stops needing you. Revenue is also worth less at exit than software. We covered the full economics in newsletter business ideas.
Buildability 7.4, and only 13 small products in the category. Consultants need proposals, scoped statements of work, time tracking against retainers, and client reporting, and they mostly assemble this from four disconnected tools.
Why it suits one person. Your customer is a solo operator like you, so you understand the workflow natively and can sell without a sales team.
The wedge. Pick one discipline. Tooling for independent management consultants is a different product from tooling for freelance engineers, and the generic version loses to both.
Buildability 7.2, 25 small products, and zero AI-native entrants. Companies build internal tools badly because nobody owns them. An opinionated product for one recurring internal workflow sells on time-to-value rather than flexibility.
Why it suits one person. Narrow scope by definition, and buyers accept a small vendor for internal-only tools far more readily than for customer-facing systems.
Not a category so much as a discipline. Take one feature that large platforms do badly, build only that, and charge for it. Several of the highest-revenue solo products we track are exactly this, including a browser extension doing one AI task well and reporting figures in the top revenue band.
Why it suits one person. The surface area is small enough to hold in your head, which is what makes solo maintenance sustainable across years.
We collected the pattern in single-feature micro SaaS ideas and micro SaaS examples.
Buildability 7.0 with 46 small products. The software is commodity, which means your product is curation and access, not code.
Why it suits one person. Revenue arrives immediately and predictably, and members do much of the retention work for you once the group reaches critical mass.
The catch. Below that mass it is entirely on you, and churn in small communities is brutal. This is the highest-effort option here in year one.
Buildability 7.0, 37 small products. Generic form builders are a solved commodity, but regulated verticals need retention rules, audit trails, consent capture, and specific export formats that generic tools will never prioritise.
Why it suits one person. The core engine is simple. The value is entirely in the vertical rules, which is knowledge work rather than engineering scale.
Buildability 7.0, 33 small products, no AI-native entrants. General ticketing platforms handle general events. Recurring classes, multi-day workshops with sessions, and membership-gated events all break their assumptions.
Why it suits one person. Transaction fees mean revenue scales with customer volume rather than seat count, so a handful of active organisers can carry the business.
The pragmatic option, and the fastest to revenue. Fixed scope, fixed price, repeatable delivery. Not software, but it funds software and it teaches you the niche faster than any research process.
Why it suits one person. You can start this week and charge real money immediately, which buys you the runway to build something with better economics later.
The honest trade. Service businesses sell at roughly a 3x profit multiple against about 10.6x for SaaS in our acquisition data. Treat this as a funding mechanism, not a destination.
The constraint that actually ends most one-person businesses is not engineering capacity. It is the number of human conversations the product generates per paying customer per month. Everything else is downstream of that number.
Work the arithmetic. If each customer generates one support interaction a month and each takes fifteen minutes including context switching, then 100 customers costs you 25 hours. At 200 customers you have lost a full working week every month before writing a line of code. This is why solo businesses tend to stall in a band rather than at a number: they hit the point where support consumes the hours that used to produce growth.
Three design decisions move that ceiling, and all of them are far cheaper to make early than to retrofit.
Reduce the interactions per customer. Most support volume comes from a small number of confusing moments, usually in onboarding and billing. Instrument where people actually get stuck rather than guessing, then fix the top two. A single confusing setup step can account for a large share of your total ticket volume.
Make the product self-evident rather than documented. Documentation is a tax you pay forever, because it has to be maintained alongside the feature it describes. An interface that does not need explaining is cheaper across years than a well-documented one that does.
Price so that high-touch customers are worth the touch. The worst position is a low price point with an enterprise-shaped support burden. If a segment needs hand-holding, either charge for it properly or decline it. Solo founders lose more time to underpriced demanding customers than to any technical problem.
This is also the difference between the third and fourth revenue tiers in the table above. Businesses that stay solo past $10,000 MRR almost always made these choices deliberately rather than discovering them under pressure.
Pricing is the fastest lever a solo founder has, and the one most consistently set too low. The arithmetic is unforgiving: at $10 a month you need 500 customers to reach $5,000 MRR, and 500 customers is well past the support ceiling described above. At $100 a month you need 50, which one person can genuinely serve.
| Price per month | Customers for $2,000 MRR | Customers for $5,000 MRR | Solo-viable? |
|---|---|---|---|
| $9 | 222 | 556 | Rarely. Support volume dominates |
| $29 | 69 | 172 | Workable with low-touch design |
| $79 | 26 | 64 | Comfortable |
| $199 | 11 | 26 | Comfortable, but concentration risk |
The sweet spot for one person is usually the $29 to $99 range against a business buyer. Below that you need consumer-scale volume you cannot support. Far above it you are down to a handful of accounts, and losing two of them is a bad quarter. Note the last row: at $199 you only need 26 customers, which sounds wonderful until one of them is a fifth of your revenue.
Charge in the customer's currency of value, not your cost. A tool that saves a consultant four billable hours a month is worth a fraction of those hours, and that fraction is almost always more than $29. See how to price a micro SaaS for the full treatment.
The thing nobody warns solo founders about is that the constraint moves as you grow, and the skill that got you to one tier is not the one that gets you to the next.
Zero to $500. The constraint is distribution. You have a product and nobody knows. Almost all effort should go into being found by the specific people who have the problem.
$500 to $5,000. The constraint is retention. You now have customers and some are leaving. This is where onboarding and activation earn their keep, and where most solo businesses quietly stall.
$5,000 to $20,000. The constraint is you. Support and sales conversations start eating the hours that used to go into product. Businesses that stay solo past here made deliberate choices about self-serve onboarding early.
Above $20,000. Most have hired. If staying solo matters more than growing, this is the point to decide that consciously rather than drift into a team by accident.
For the practical next steps see getting your first 100 users, reaching $1K MRR, and how to price a micro SaaS.
Every score here came from a dataset you can search. Check any category for how many small products already compete and what problems their users still complain about.
Search the complaint database free →The gap between picking an idea and having a business is where most solo attempts die, usually because the first month is spent building instead of selling. Here is a sequence that inverts that.
Days 1 to 14: pick the niche, not the product. Choose a group of people before choosing what to make for them. Write down where two hundred of them can be found: an association, a subreddit, a conference list, a directory. If you cannot fill that page, the niche is not reachable and no product will fix it. Cross-check the category against the buildability table above so you are not walking into scheduling and booking by accident.
Days 15 to 30: find the documented complaint. Collect at least ten independent people describing the same problem in the last year, in their own words. Not paraphrased, not inferred. This is the single highest-value fortnight in the whole plan, because it is the only point where changing your mind is free. Our guide to finding problems worth solving covers the search patterns.
Days 31 to 45: sell it before it exists. Describe the solution to ten of those people and ask for money. A deposit, a pre-order, a letter of intent. Almost everyone skips this because it is uncomfortable and because building is more pleasant than being told no. It is also the only step that cannot be fooled by your own enthusiasm.
Days 46 to 75: build the smallest thing that closes the loop. Not an MVP in the vague sense, but the narrowest thing that takes a customer from problem to resolved. Deliberately leave out settings, integrations, and anything with the word "manage" in it. Every feature you ship is one you maintain alone for years.
Days 76 to 90: onboard by hand, then remove yourself. Walk your first customers through personally, and write down every question they ask. That list is your onboarding roadmap and, per the support ceiling above, it is also the thing that determines your revenue ceiling. Fix the top two questions in the product rather than answering them again.
At day 90 you should have paying customers and a short list of known friction, not a finished product. That is the correct outcome. See launching a micro SaaS quickly and how to build a SaaS for the execution detail.
All figures queried live on 5 August 2026. Here is what sits behind each and where it falls short.
| Source | Scale | Used for | Limitation |
|---|---|---|---|
| Category buildability scoring | Tens of thousands of companies | Buildability and competitor counts | Model-generated from company descriptions, not audited. Small product counts reflect one payment provider only |
| Revenue cluster tracking | 3,700+ products | Revenue bands | Self-reported and skewed toward founders willing to publish, which biases every figure upward |
| Founder success stories | 1,700+ with revenue | Named high-revenue examples | Public posts, not audited. Severe survivorship bias: failures do not post revenue screenshots |
| Acquisition listings | 290+ SaaS, 69 agency | Exit multiples | Asking prices, not closed sales |
| Complaint corpus | 1M+ documented | Unmet-need signal per category | Skews to categories with review volume; thin verticals are under-represented |
The strongest caveat is survivorship. Every named revenue figure comes from someone who chose to publish it, and people publish good numbers far more often than bad ones. The band table is the more honest guide, and even that skews high for the same reason.
Underlying datasets are documented at the Stripe Index database, TrustMRR revenue benchmarks, and the complaint database.
The one in a category you already understand, built in a niche with high buildability and low existing supply. Our category scoring puts newsletters and publishing, consulting tooling, project management, and no-code internal tools at the top for solo buildability, all scoring 7.2 or above out of 10. Scheduling and booking scores lowest at 6.6 and already contains 100+ small independent products, which makes it the most common mistake rather than the best pick.
Across 2,500+ tracked micro products the median is around $50 MRR, which is the honest starting reality. The realistic target band for a competent solo operator is $500 to $5,000 MRR, where 800+ tracked products average roughly $1,700. Above $20,000 MRR you are in a group of about 130 products, and most have stopped being one-person businesses by then.
Yes, up to a ceiling set by support load rather than engineering. Solo operators tend to stall not because they cannot build features but because support, billing issues, and sales conversations consume the hours that used to go into product. The businesses that stay solo past $10,000 MRR are almost always ones with self-serve onboarding and low-touch support by design, not by accident.
Choosing a category by familiarity rather than by supply. Scheduling and booking tools are the clearest example: it is an obvious problem every founder understands, which is exactly why 100+ small products already compete there. The categories worth entering are the ones you had to research, not the ones you thought of immediately.
Not necessarily, and the data is interesting here. Several of the highest-buildability solo categories contain zero AI-native companies among the ones we track, including newsletters and publishing and project management. That is either an opening or a signal that AI adds little in those workflows. Treat AI as a way to reduce your own operating hours first, and as a product feature only where it changes the outcome for the customer.
Next steps: simple SaaS ideas for solo developers, micro SaaS ideas, niche SaaS ideas, and unique business ideas backed by real complaints. To validate before building, read how to validate a startup idea and validating before you code. For tooling, the solopreneur SaaS toolkit and what to build as a solo developer.
BigIdeasDB Research. (2026). One-Person Business Ideas 2026: What a Solo Founder Can Actually Run. BigIdeasDB. Retrieved from https://bigideasdb.com/one-person-business-ideas-2026