Simple founder agreement checklist for student teams (with a one-page template)
· buildtolaunch
You and two or three friends are about to build something together, and nobody has said who owns what. This checklist gives student teams a one-page founder agreement they can fill in over one coffee, plus the reasons behind each line. It is part of our guide to building with teammates.
Short answer
A simple founder agreement for a student team is a one-page written note that covers seven things: who does what, how much time each person gives, who owns the work, how ownership is split, what happens if someone leaves, how decisions are made, and when you review it. Write it before you earn anything, sign it with a date, and ask a lawyer before registering a company.
Why bother when you are just friends building a project?
Most student teams skip this because it feels awkward or too serious. The cost shows up later: two people did the work and one disappeared, someone wants to take the project to a competition alone, or a real offer arrives and nobody knows who can say yes.
A one-page agreement does not make you a company. It records what you all said out loud, so a month from now nobody has to rely on memory. If you do not have a company yet, this note is a statement of intent between friends. It is not a replacement for proper legal documents once real money, real users or a registered business are involved.
This article is general information, not legal advice. Rules on company registration, equity and intellectual property differ by country, and by your school's own policy. Check with a lawyer or the relevant authority for your case.
The one-page checklist
Copy this into a shared doc. Fill in every line, even if the answer is "not decided yet, we will decide by [date]".
1. Project and goal
- Project name and one-sentence description.
- What does success look like at the end of this semester or this competition?
- Is this a class or competition project, a side project, or the start of a company?
2. Who is in and what each person does
- Names and the role each person owns (for example product, build, design, users and marketing, pitch and operations).
- One owner per task area. Two owners means no owner.
- If you want a starting point, see the roles chart for 3 to 5 person student projects.
3. Time and commitment
- Hours per week each person can honestly give, and the weeks when exams make that lower.
- Weekly check-in day and time, and how you tell the team when you will miss it.
- What counts as "not pulling their weight"? Agree on this before it happens.
4. Ownership of the work
- Who owns the code, designs, brand name and domain? A safe default for a team project: the team owns it together, and no one uses it for another project without asking.
- Check your school and competition rules. Some competitions or class projects set their own rules about who owns what.
- Where is everything stored (repository, shared drive), and who has admin access to each account?
5. Ownership split
- Percentages, or "we will agree on the split by [date] once we see who does what". It is fine to defer, as long as you write down the date.
- Make the split based on contribution and future commitment, not only on who had the idea.
- If you register a company later, this line becomes a real document. Treat the note as a draft intention.
6. Vesting and leaving
- Vesting means ownership is earned over time rather than received all at once.
- A common setup in startups is four years with a one-year cliff. Y Combinator's guidance on splitting equity describes it this way: before the cliff, a founder who leaves keeps none of their shares, at one year they receive 25 percent, and the rest vests monthly over the remaining time.
- For a student team, a much shorter version is fine, for example a trial period of four weeks and then a review.
- What happens if someone stops contributing, or has to leave for a good reason (a job, family, health)? Decide now what they keep.
7. Decisions and money
- Who has the final say on product decisions, and what needs everyone to agree?
- Who can speak for the team (social accounts, emails to judges or customers)?
- If the project makes money or wins a prize, how is it shared? If it spends money, who approves?
8. Review date
- Put a date in the calendar, usually four to six weeks away, when you re-read this page and change what is no longer true.
Template you can paste
FOUNDER NOTE (simple version)
Project: ______________________ Date: ____________
Team and roles: ________________________________
Hours per week each: ___________________________
Weekly check-in: day ______ time ______
Who owns the work: ______________________________
Ownership split: ________ (or: to be agreed by ______)
If someone leaves: _____________________________
Decisions: final call on ______ is ______
Prize or income: ________________________________
Review date: ____________
Signed (names): ________________________________
How to have the conversation
- Do it early and in person. A call or a coffee works better than a long message thread.
- Let everyone fill in the page alone first, then compare. Differences show you where the real conversation needs to happen.
- Keep it kind and factual. "I can give 8 hours a week" is a statement, not an accusation.
- Write down what you decide and send it to everyone, the same day.
If you have not worked with these people before, run a short trial project first. Our guide on finding a co-founder as a student covers a two-week trial, and the 15 questions to ask before inviting a co-founder help you discover mismatches before you write anything down.
When to get a lawyer
The note above is enough while you are a few friends building a class project. Talk to a lawyer or an adviser at your school's incubator when any of these happen:
- you register a company or take money from anyone;
- someone brings in work that already belongs to an employer or a client;
- you sign anything with a customer, a sponsor or a competition that mentions ownership or intellectual property;
- a team member leaves and there is a dispute about what they keep.
For a longer look at ownership questions in student projects, see who owns the code and the idea in a student team project, and for splits specifically, chia cổ phần co-founder khi còn là sinh viên (in Vietnamese).
Where buildtolaunch fits
buildtolaunch is a free community for university students across Southeast Asia, open to any major, and you do not need to code to start. You can open a Space for your project, set a weekly focus with your team and build with an AI teammate that takes tasks on the board. Pasting this checklist into the Space on day one is a simple way to start. When you have something to show, post it to the Launch League, which resets every Monday. Join free.
Read the full guide: Build cùng đồng đội (Vietnamese).
FAQ
Do student teams need a founder agreement?
If you are building a class project for a week, probably not. If you plan to keep working together after the semester, enter competitions together, or might earn money, then yes. A one-page note takes under an hour and prevents most of the arguments that end teams.
Is a one-page note legally binding?
It depends on the country, how it is written and what it covers, and a note between friends may not be enforceable in the way a formal contract is. Treat it as a written record of what you agreed and a basis for a proper document later. For anything involving a registered company or money, ask a lawyer.
Should we split ownership equally?
Equal or near-equal splits are common and avoid the awkward negotiation, and Y Combinator's guidance argues for them among co-founders. They work best when everyone commits similar time and risk. If one person will do far more or far less, say so and adjust, or defer the split until after a trial period.
What is vesting and do students need it?
Vesting means ownership is earned over time instead of handed over on day one, so someone who leaves early does not keep a full share. Student teams do not need a formal four-year schedule, but a trial period with a review date gives you the same protection in a simpler form.
What if a teammate wants to leave?
Decide the rules before it happens: what they keep, how they hand over their work and accounts, and how much notice they give. Remove their access, thank them, and update the note. If the split was based on contribution, adjust it to match what they actually did.
Who owns the code if we use AI tools to build it?
The rules on this are still developing and differ by country and by each tool's terms of service. Read the terms of the tools you use, keep the team's ownership rule in the note, and ask a lawyer or your school if the project is going to be sold or entered in a competition with its own rules.