AI Side Project Money Checklist: Weekend Thing or Company?

A side project becomes a company when it has recurring revenue, a real margin, and a named platform risk. The builder then chooses whether to protect the weekend or scale the business.

Most AI side projects stay side projects, and that is fine. The uncomfortable moment is when the dashboard stops being a toy and starts looking like a full-time job. You need a test that does not flatter you. It should be quick enough to run before the next idea arrives.

SEOBOT, a product with public revenue readings, is a useful benchmark because its recurring income shows what a small tool can look like once customers keep paying. SEOBOT's MRR was $45,000 in August 2026, with readings since June 16, 2026. SEOBOT had $43,858 in monthly recurring revenue and 604 active subscriptions on August 31, 2026. Cumulative revenue reached $1,844,734 as of August 31, 2026.

The implied average subscription price was about $72.60, above the $49 entry tier. TrustMRR, a revenue tracker, showed verified recurring revenue of $41,805 and 577 active subscriptions. The founder had already operated 11 SaaS products and 20 directories before building the tool. It was not a solo-founder operation, and the founder already had a portfolio of products.

Money is a signal, not a verdict

Revenue answers a question: are people paying again? It does not answer whether you can keep building without losing the life that made the project possible. A weekend builder can have a small income stream and still be a weekend builder. The difference is whether the income starts demanding a schedule, a support queue, a refund policy, and a growth plan.

If the product is an AI content tool, the platform risk is often the model provider, the search engine, or the app store that carries the traffic. You do not need a legal memo. You need a name you can say out loud. If you cannot name the risk, you are probably still in the early stage. If you can, the project has a platform-risk question attached to it.

These questions separate a weekend from a company

1. Recurring revenue: Do repeat customers pay again without you chasing them? Single sales can feel like a business while still being a project.
2. Real margin: Do you know what each paying customer costs you to serve? AI tools can hide compute, support, and maintenance costs that eat the weekend.
3. Named platform risk: Can you name the platform, model, or channel whose change would hurt you? A side project can survive a policy shift, but a company needs a plan.
4. Available hours: Can you say how many hours you can give without resentment? Scaling without protected time turns a weekend project into a constant obligation.
5. Desire at small scale: Would you still build it if it stayed small? The best side projects are work you would choose again, even when the income stays small.

The answers tell you what to protect

If you answer yes to the revenue, margin, and platform-risk questions, and no to the hours and desire questions, the honest move is to protect the weekend. Keep the product small, keep the support load light, and treat the revenue as a signal that the idea is worth keeping alive. You can still improve it, but you do not owe it a growth engine.

If you answer yes to every question, the project has crossed into company territory. That does not mean you must quit your day job. It means you should make a deliberate choice: add a part-time operator, raise prices, narrow the feature set, or stop accepting new customers. The cost is your time, and you should price it like a job.

The checklist is a way to keep the weekend intact while the project earns. Run it before the next feature idea arrives, and again after the next support ticket does. If you are unsure, write the answer down and revisit it after the next billing cycle.