# From side project to company: the decision points When a side project starts to need a legal home, a bank account and written agreements, and the questions each moment raises for solo and student founders. Canonical URL: https://worldenterprise.org/insights/from-side-project-to-company-the-decision-points/ Last updated: 2026-10-10 Publisher: World Enterprise, run by World Enterprise Group Incorporated *As of 2026-10-10, this is general information, not legal or financial advice. Company formation, tax and school or employer policies differ by place. Ask a lawyer and an accountant licensed where you live, and read your own school or employer policy.* Most companies were once a side project. Someone built a tool in the evenings, put it online and found that other people used it. There was no moment of founding, only a slow drift from a personal project to a shared product. That drift is fine until something happens that the project was never set up to handle: a person pays, a friend contributes code, a school asks a question or a customer sends a contract. This article lists the decision points where a side project starts to need more structure. It is written for people working alone, and for students whose work may also touch a school's rules. It does not say when to form a company, because that depends on facts about you. It says when the question starts to matter and what to ask. ## The decision points at a glance | Trigger | The question it raises | Who to ask | |---|---|---| | Other people start using it | What do users agree to, and what do I do with their data? | A lawyer; the policies of any platform you use | | Money starts to change hands | Who receives it, how is it recorded, and what is owed on it? | An accountant | | Someone else writes code or content | Who owns what they made? | A lawyer | | You want liability to sit somewhere other than with you | Is a separate legal entity worth its cost and paperwork? | A lawyer and an accountant | | You want to hire or pay people | What tax registrations and agreements are needed? | An accountant and a lawyer | | A school, employer or funder has a claim | Do their policies reach what you built? | The policy itself, then a lawyer | | You want to put in more time or money | What is the limit, and what is the exit? | You, and someone you trust | Read the table as a list of prompts, not a schedule. Some projects meet several triggers in a week, and some meet none for years. ## Trigger one: other people use it When a stranger signs in, the project has stopped being private. Two questions arrive at once. The first is what you tell users: what the product does, what it does not promise and what you do with their information. The second is what the platforms you rely on require of you, such as app stores, payment processors, hosting providers and the sources of any open source code you ship. A plain page of terms and a plain page about data are not a legal safeguard by themselves, and this article does not say what they should contain. Ask a lawyer what applies where your users live. The [security baseline checklist](https://worldenterprise.org/library/security-baseline-checklist/) shows the basic protections that a product holding other people's data is usually asked about. ## Trigger two: money changes hands The first payment turns a hobby into something an accountant and a tax authority may care about. Ask: - Where does the money go: a personal account or a separate one? - Is it income to me, and when? - Do I need to register for any tax or collect any tax on sales? - How will I record it so that I can answer these questions later? Keeping business money apart from personal money is a common first step, and it makes every later question easier to answer. The reason is practical: a record that mixes the two is hard for anyone to read, including you. ## Trigger three: someone else contributes Help is welcome, and it creates ownership questions. A friend writes a module, a designer draws a logo, a classmate adds a feature. In United States copyright law, copyright in a work vests initially in the author or authors of the work, which means your project may contain code that you do not hold the rights to. The article on [intellectual property and access diligence](https://worldenterprise.org/insights/ip-contracts-and-access-diligence-for-small-engineering-teams/) shows what a later reviewer will look for. Ask a lawyer how a short written assignment from each contributor should look, and ask for it before the work is merged rather than after. ## Trigger four: you want a legal home for the project A company is a legal structure that can own the product, sign contracts and hold the money. The U.S. Small Business Administration says that the business structure you choose affects how much you pay in taxes, your ability to raise money, and the paperwork you need to file. It adds that you may convert to a different structure in the future, but that there may be restrictions based on your location, and that a conversion could result in tax consequences and unintended dissolution, among other complications. In other words, the first choice is not necessarily permanent, and it carries consequences of its own. Questions to take to counsel and an accountant: - Which structures exist where I live, and how do they differ in liability, tax and paperwork? - Which would an investor or a larger customer expect to see, if I may want either? - What does it cost to form and to keep, each year? - What must I do with the code and the brand: transfer them to the new company, and in what document? - What if I have co-founders? See [questions to ask your counsel before you sign](https://worldenterprise.org/insights/questions-to-ask-your-counsel-before-you-sign/). If you form a corporation or limited liability company in the United States, the IRS advises that you form your entity through the secretary of state before you apply for an employer identification number. The IRS also lists the situations in which you generally need such a number: to hire employees, to operate a partnership or corporation, and to pay sales and excise taxes, among others. If you are not in the United States, the equivalent registrations and their order differ, and a local adviser can say what they are. ## Trigger five: a school, an employer or a funder has a claim For solo founders with day jobs, the point is the one covered in the article on [spinning a product out of an employer](https://worldenterprise.org/insights/spinning-a-product-out-of-an-employer-what-to-settle-first/): your agreement may reach your side work. For students, the school's policy matters in the same way. Universities publish rules about who owns what students and researchers create. As one example, Stanford's research policy handbook says that inventions made with more than incidental use of University resources are to be disclosed on a timely basis to the University, and that title to such inventions is to be assigned to the University. That is one school's policy, written for patents. Yours may be broader, narrower or different, and it may treat software, coursework, a campus incubator space or a grant differently. Questions for a student founder: - What does my school's intellectual property policy say, and which office administers it? - Did I build this in a course, in a lab, on university equipment, with a faculty member or with a grant? - Does using the library, a computer lab, a startup space or a school-provided cloud account count as use of university resources? - Who at the school can confirm in writing that the school makes no claim, if that is the case? - Does my status change when I graduate, take leave or withdraw? Ask early and keep the answer. A written statement from the school is worth more than a recollection of a hallway conversation. ## Trigger six: you want to commit more At some point, you may want to put in more of your time and savings, or leave a course or a job. This is a personal decision with legal and financial parts that others can inform but cannot settle for you. A few questions you can write down: - What is the most I am willing to lose, in money and in time? - What would I need to see, and by when, to continue? - Who depends on me, and what do they need to know? - What will I do if the project does not become a company? A clear answer makes it easier to try. ## A short order of operations For a solo founder or student, a common order of work is: 1. Read any agreement or policy that could reach the project. 2. Write down who has contributed what, and collect written assignments. 3. Open a separate account for project money. 4. Decide, with advice, whether and when a company is the right container. 5. Move the assets into the company in writing, once it exists. This order is an illustration of one way to sequence the work, not a recommendation, and it will not fit every case. ## What this article cannot tell you It cannot say when your side project should become a company, or whether it should. The four sources cited are a U.S. Small Business Administration page on business structure, an IRS page on employer identification numbers, one university's patent policy and one section of the U.S. Copyright Act; they describe United States arrangements and one school, and they do not describe other countries, other schools, copyright policies, scholarship or visa conditions, or tax rules. The article names no incorporation service and gives no price, deadline or percentage. Employer, school and funder rules change from one place to the next, and a written policy is the only reliable guide to yours. Nothing here suggests that a side project will become a company or that forming one will help. ## Sources - Choose a business structure. U.S. Small Business Administration. - Get an employer identification number. Internal Revenue Service. - Research Policy Handbook, Inventions, Patents and Licensing. Stanford University, Office of the Vice Provost and Dean of Research. - 17 U.S. Code section 201, Ownership of copyright. Legal Information Institute, Cornell Law School.