Know when your side project is asking to become a company

The question usually arrives after a stranger asks for a fix, a feature, or a status update. Your weekend AI tool has started using your time. Can Celik was the sole person operating Herdr in August 2026. Herdr had raised a $6 million seed, led by Bessemer Venture Partners with Y Combinator and e2vc participating. Shopify chief executive Tobi Lütke was named among the angels. Usage plus maintenance cost, not revenue, drives the decision.

Most side projects stay side projects, and that is fine. The problem begins when demand outpaces the hours you can give it. A side project can survive loose edges. A company cannot. Then you need a clear decision: keep it as a project, or make it a company. The decision should come from what the tool is doing, not from how impressive the repo looks.

Usage, not stars, is the first alarm

Start with the people who actually use the thing. Are they strangers? Are they returning? Are they asking for reliability, not just novelty? If the answer is yes, the project has moved from your personal tool into someone else’s workflow. That is the moment the question of becoming a company stops being abstract.

Herdr is a useful example. The August YC post listed 25,000 GitHub stars, 340,000 downloads, and more than 500 community plugins. Herdr's code is released under Apache 2.0, and Can Celik said the runtime would stay open after the financing. A project can attract serious funding when the tool is already doing real work. The funding did not create the demand. The demand made the company possible. That order matters for any builder watching strangers show up.

Stars are a threshold, not a customer

Stars are easy to count and easy to misread. A GitHub star is a low-effort bookmark-like signal of interest, not proof of usage, scale, or payment. Runa Capital’s ROSS Index counts stars as developer interest rather than production usage. Significant customer adoption usually takes more than one year. The index also sets a minimum of 1,000 GitHub stars before a repository can be included.

The baseline marks a threshold, not a business model. A project can pass it and still need a long runway to become a company. Open source can be commercially powerful. But the value shows up in adoption, governance, and operations, not in a star count. Ubuntu’s 2025 global open source report found that 83% of organizations view open source as important to their future, and 46% said it delivered more business value than the year before, even as adoption is moving faster than governance and operational maturity. The Linux Foundation’s 2025 commercial open source report found that commercial open source firms tend to beat closed-source rivals on valuation, fundraising speed, and liquidity, with the gap sharpest in infrastructure software. Moving from stars to revenue takes work.

A side project started in 2004 to manage data better than phpMyAdmin reached 30k GitHub stars, and its creator went from coding alone to running a 50-person company. The timeline runs long. It is not a shortcut. Usage can compound, but only if the builder keeps the project alive.

Run the checklist before you incorporate

Use this list when the demand feels real. Each item below is meant to be checked in a short sitting, not debated for long.

• Count recent active users or completed jobs, and note whether strangers are doing the work. Strangers mean demand is external.
• Estimate the maintenance hours it now costs you, including support, bugs, docs, and updates. Hours beyond your weekend budget mean the project is asking for more than a side project can give.
• Name what becoming a company would require: legal setup, a bank account, payroll, insurance, or a paid role. Plain terms make the decision concrete.
• Check whether the usage trend is steady or spiking. A steady pattern is easier to plan around than a one-off burst.
• Ask what you would stop doing to protect the tool. A job, a relationship, or your health makes the cost visible.

Keep the rule: measure organic usage, estimate the maintenance hours it now costs, and name what becoming a company would require. When usage and hours exceed your weekend budget, formalize the decision. Otherwise, keep the project where it belongs: in your evenings, with a set limit.

Formalizing is a cost, not a trophy

Becoming a company changes the work. You start answering to users, investors, vendors, and yourself in a different way. You may need to hire, set prices, write terms, and keep the runtime reliable. Herdr planned to use its seed funds to build a small team, connect machines running Herdr, and make the runtime faster, more robust, and more extensible. Stay a side project, and say so out loud. Incorporate, and name the first obligation you are willing to accept.