When a Side Project Should Become a One-Person Business

Your AI side project is running, and the decision is whether to keep it casual or give it the structure of a company. In 2023, 117,060 U.S. nonemployer firms, businesses with no paid employees, reported $1 million or more in annual gross receipts. That is the scale of the prize, not the plan. A one-person business is a bigger commitment than a side project: it asks for reliability, a support channel, a payment path, and a plan for the week you are sick. The Stay-Solo Test runs four checks before you add that structure: repeat revenue, maintenance load, solo leverage, and durability.

Most side projects should stay side projects

Solo work is the normal shape of the market. U.S. nonemployer businesses rose 65% between 2000 and 2019, from 16 million to nearly 27 million. U.S. nonemployer establishments reached 30,427,808 in 2023, up from 29,811,495 in 2022 and roughly 24 million in 2015, with nearly $1.8 trillion in receipts. That is a large pool of solo work, but most of it is small enough that the owner is the whole operation. Your weekend app is not automatically in the top group, and that is fine.

The outlier is not the plan

It is tempting to point to a solo founder who built a large solo business and assume the path is repeatable. Maor Shlomo's Base44 had 300,000 users, $3.5 million in annual recurring revenue, and one employee when it was sold to Wix for $80 million in cash. That outcome is rare enough to treat as an exception, not a forecast.

A sale to a platform is an exit, not a maintenance plan. The useful lesson is the narrowness of the product and the speed of the build. For a weekend builder, the more useful comparison is the maintenance cost after launch. Solo-led firms made up 30% of 2024 startups and captured 14.7% of priced equity rounds, the rounds where investors pay a set price for a share. That visibility can make a side project feel ready for a company.

Among Indie Hackers products, the hit rate at $10,000 in monthly recurring revenue or above is about 5%. Most projects do not clear that bar, and the ones that do still need a maintenance plan.

The Stay-Solo Test decides whether it wants a company

Run the project through the checks before you treat it as a company. The test is deliberately unglamorous: it asks whether the project can support a small business without taking all your time.

• Repeat revenue: Does money arrive without you chasing it? Customers who return, upgrade, or renew show a stable revenue pattern.
• Maintenance load: Can you keep it alive on weekends? Outages, support threads, and fixes that take the evening make it a job.
• Solo leverage: Does AI or automation remove enough work that one person can run it? If not, the project is asking for a team.
• Durability: Would it still be useful if the current AI trend cooled? A durable project can handle a slower month.

In 2026, 74% of solo business owners used AI, and automation gave back 10% to 40% of a founder's daily working time. That range matters because a weekend builder does not have a team to absorb the leftover work. Automation that saves only a small amount leaves the rest as your weekend work. A project that can use those tools to shrink the weekly load may be ready for a company structure. When it cannot, keep the project small enough that it can handle a bad month without becoming a second job.

The hours tell you when to stop

If your project passes the test, treat it as a one-person business: set a price, keep support narrow, and protect the hours that made it possible. Write down the smallest set of promises you can keep: a price, a support window, a maintenance routine, and a stop rule for when the hours stop working. When it fails, keep it a side project and use the saved hours on the next idea.