Student founders: the questions to settle before you start

This article is general information, not legal or financial advice. It was written on October 10, 2026. It describes two universities’ published policies as examples, not the rules of your school. Ask your own counsel what applies to you.

Starting a company while you are enrolled has real advantages: time to experiment, people to talk to and a low cost of being wrong. It also has a question that founders who are not students rarely face. Your school may have a published policy about who owns what you create while you are a student, and that policy may apply to the thing you are about to build.

This article does not tell you what your school’s policy says. It shows how two schools’ policies read, so that you can see what kind of question you are looking for, and it lists the questions to settle before you put months into a product.

Why two examples, and not a rule

There is no single rule for student-created work in the United States. Each school writes its own policy, and the policies differ in who is covered, what they cover and what counts as using the school’s resources. The two below were read in full on the date above. They were chosen because they are public and clearly written. Neither stands for schools in general, and neither should be read as a ranking.

An invention policy keyed to resources and role

Stanford’s Research Policy Handbook says potentially patentable inventions made by members of the university community, including “student employees”, in the course of their university responsibilities “or with more than incidental use of University resources”, are to be disclosed to the university, and that title to them “shall be assigned to the University”. The policy also extends to other individuals who take part in research projects at the school, students among them.

Two features matter for a founder. First, the trigger is not enrollment alone. It depends on your role (employee, research participant) and on what you used. Second, the page describes a waiver process: the Vice Provost and Dean of Research may grant waivers “on a case-by-case basis”. Whether a waiver is available to you is a question for the school and for counsel.

A copyright policy that mostly leaves student work with the student

Stanford’s copyright chapter takes a different approach to writing and similar work. It says the university “does not claim ownership to pedagogical, scholarly, or artistic works, regardless of their form of expression”, and that such works “include those of students created in the course of their education, such as dissertations, papers and articles.” The same chapter lists exceptions, including work that “makes significant use of University resources or personnel”, and it sends patentable software to the invention policy above. The page shows its current version as March 18, 2018, which is a reminder that policies are revised and that you should read the one in force today.

A policy that lists what the school does and does not own

MIT’s policy is organized as two lists. The first begins “MIT owns IP generated by one or more of the following” and includes “Using MIT Funds” and work done in the performance of a covered person’s MIT employment. The second begins “MIT does not own the following IP, unless otherwise stated below” and includes coursework generated by students, IP from MIT-sponsored hackathons and IP from the use of MIT maker spaces. Each of those has stated limits. For instance, the policy says that while copyright in a student thesis is not owned by MIT, the “patentable inventions, software, and Materials described in the student thesis” are, subject to a separate exception, owned by MIT. The maker space entry has its own exception for projects that build on MIT-owned IP.

The policy also ends its list with this sentence: “This list may not cover every circumstance.” And it says that “Any questions concerning ownership of IP should be directed to the TLO”, its technology licensing office.

What the two have in common

Both examples treat different kinds of work differently, and both turn on what you used and what role you held. Written work and coursework are handled one way, and patentable inventions and software another. That is why the questions below start with your own facts and not with a conclusion.

Six questions to settle before you start

1. Which policy applies to me? Find your school’s intellectual property policy, and any separate policy for research, employment or student conduct. Note your own status: student, student employee, research participant, or several at once.
2. What am I using? List the school’s funds, labs, equipment, maker spaces, software licenses, staff time and course materials that touch the project. The examples above use phrases like “more than incidental use”, “significant use” and “using MIT Funds”. Your school’s phrasing may differ, and so may the point where use becomes ownership.
3. What kind of thing am I making? A patentable invention, software, a written work and a class project may each be treated differently. If the product started as a course assignment or a thesis topic, say so to counsel.
4. Who else contributed? Classmates, a supervising professor, a research lab and a team project each add a person whose rights or obligations matter. Write down who did what and when.
5. Does anything need to be in writing? Some policies provide a waiver or a release process. Whether you need one, and how to ask, is a question for counsel before you contact the school, because what you say to the school can have consequences.
6. What changes when I graduate, leave or take a leave of absence? Policies that depend on your status may apply differently once it changes. Ask what happens to work begun while you were enrolled.

Keep the answers, with dates and copies of the policies you read, in one folder. The IP, contracts and access article describes the kind of record that later helps when you work with other people or ask for funding.

Before the first line of code. Students can settle most of the ownership questions in a short, written pass.

1. 1

   Read the policy

   Find the school invention and copyright policies and read the parts about students.

2. 2

   List your resources

   Write down which school labs, funds, networks and software you used or will use.

3. 3

   Ask in writing

   Ask the school office that handles these questions, and keep the reply.

4. 4

   Record the answer

   Save the policy text and the reply with the date in the company folder.

The questions that are not legal

Ownership is the question with the most lasting effect, and it is not the only one.

Who is the customer? If the people you know best are other students, the easiest customers to reach may not be the ones with the problem. Write down who feels the problem most, and whether you can reach them. The validate the problem playbook and the customer interview guide show how to find out without relying on friends.

What is the smallest version you can show? A semester has fixed deadlines and a limited number of available hours. A one-page statement of the problem is a better first deliverable than a half-built product. The one-page problem brief is a template for it.

How will the work fit with school? Name the weeks when coursework will leave you no time for the company, and decide in advance what you will pause. A separate article in this desk covers the decision to move from part-time to full-time.

Where this fits in a long effort

A student company can run long past graduation, so the ownership record made now is the record future partners will ask for. Student founders have public resources too: the SBA resource partners article describes small business development centers, many of which work with students, and the program decision guide covers independent programs and communities. Join them. WE works alongside, for the long run.

University and research programs, incubators and founder communities open to students are listed in the ecosystem directory. Student research teams with a faculty partner should also read the SBIR and STTR guide, since STTR pairs a small company with a research institution.

What this article cannot tell you

This article reads three public university policy pages and does not describe any other school’s rules. Your school’s policy may be more or less generous than either example, and a policy can differ from what a school does in practice, which you can only learn by asking. It is not a statement about how often schools claim student work, and it does not say that either school will claim anything you build. It does not describe visas or immigration status, funding, taxes, or the founders’ agreements among classmates, which need their own advice. It cannot tell you whether your project falls under a policy. Read your own school’s current text, and ask counsel before you ask the school.

In the data

These figures describe U.S. businesses in general, not WE’s results. Each one names its source.

Show the data as a table

Average founder age by growth tier, startups founded 2007 to 2009

Group	Mean	Standard deviation	Mean minus 1 SD	Mean plus 1 SD	Founders in the group
All startups	41.8 years	11.9 years	29.9 years	53.7 years	1,079,000
Fastest-growing 10%	41.6 years	11.5 years	30.1 years	53.1 years	126,000
Fastest-growing 5%	42.1 years	11.5 years	30.6 years	53.6 years	62,000
Fastest-growing 1%	43.7 years	11.1 years	32.6 years	54.8 years	13,000
Fastest-growing 1 in 1,000	45 years	10.7 years	34.3 years	55.7 years	1,700
Successful exit (IPO or acquisition)	46.7 years	10.6 years	36.1 years	57.3 years	4,000

Source: Azoulay, Jones, Kim and Miranda, Age and High-Growth Entrepreneurship (NBER WP 24489; AER: Insights 2020) , April 2018 (working paper); March 2020 (AER: Insights)

Retrieved 2026-10-15. Means, standard deviations and founder counts are copied from Table 5 as printed; growth is employment five years after founding.

Sources

1. Research Policy Handbook: Inventions, Patents and Licensing, Stanford University . Accessed October 10, 2026.
2. Research Policy Handbook: Copyright Policy, Stanford University . Accessed October 10, 2026.
3. MIT Policies and Procedures 13.1, Intellectual Property, Massachusetts Institute of Technology . Accessed October 10, 2026.

Spotted an error? Read how we handle corrections in our editorial policy.