Should You Sign a Founder Agreement Before You Build Together?

Sign a founder agreement before the work creates something valuable or the relationship becomes difficult to change. The agreement should make the important assumptions visible: who is doing what, how ownership is earned, who owns the work, and what happens if one founder leaves.

This does not mean forming a company on the first day you meet someone. It means moving from an informal collaboration to a written agreement when you are sharing code, customer conversations, money, or a serious product commitment. The document is a decision tool, not proof that the partnership will work.

Key takeaways

• Use a short working agreement before a long legal process when you are still testing the fit.
• Discuss roles, time commitment, ownership, vesting, decision rights, and departure scenarios directly.
• Assign startup-related intellectual property clearly, including work created before incorporation.
• Treat four-year vesting with a one-year cliff as a common starting point, not a rule that fits every team.
• Have qualified counsel prepare or review the legal documents before you issue equity.

What needs to be agreed before you build?

Start with the disagreements that would be expensive later. Write down each founder's expected time commitment, responsibilities, decision area, and contribution so that "we are equal" does not hide different expectations.

Use questions like these:

• Who owns product, engineering, sales, operations, and fundraising decisions?
• What happens if one founder is in school, working another job, or can only contribute part time?
• How will you divide ownership, and what evidence supports that split?
• Which decisions require both founders, and which can one person make?
• What happens if someone stops contributing, wants to leave, or cannot continue?

The point is not to predict every future argument. It is to find the assumptions you currently hold without saying them aloud. If you cannot discuss these topics calmly, that is useful evidence about the partnership.

Use a working test before formalizing equity

If you have only met a potential cofounder recently, do a small project before making an irreversible commitment. Pick one real customer problem, define the work each person will do over two to four weeks, and decide how you will review the result. Notice whether each person keeps commitments, handles disagreement, communicates bad news, and does work that the other person can trust.

This is different from postponing every hard conversation. Agree on the test's scope, expenses, ownership of the test work, and what decision follows it. A written trial can be simple, but it should not leave ownership of code or customer materials ambiguous.

When the project becomes the company, replace the trial assumptions with proper documents. Y Combinator's guidance on splitting founder equity emphasizes that the split should reflect the work of getting the company to market, not only who had the first idea. It also explains why vesting gives a team a way to handle an early departure.

Make ownership earn its way into the future

Founder equity is not only a reward for work already completed. It is also an agreement about the work each person expects to contribute over time. Stripe's founder-equity documentation describes vesting as ownership accruing over time and identifies four years with a one-year cliff as a common setup for founders. Under that structure, no shares vest before the first year, 25% vests at the cliff, and the rest vests monthly.

That common structure is a starting point, not a magic number. Discuss the vesting start date, the cliff, what happens to unvested shares when someone leaves, and whether any acceleration applies in a sale. Put the result in the actual equity documents rather than relying on a message thread or a spreadsheet.

Do not use vesting to avoid deciding the ownership split. A 50/50 split with no decision process can still deadlock. An unequal split with no explanation can still create resentment. Write the reason for the split, the decisions each founder owns, and the process for resolving a disagreement.

Protect the work you are creating

Code, designs, research, customer lists, and written materials can exist before a company does. Decide which work belongs to the startup and which prior projects remain with the founder who created them. List excluded prior inventions explicitly instead of assuming everyone remembers the same conversation.

Stripe's incorporation-document overview describes founder stock and intellectual-property assignment documents, including coverage for relevant IP created before and after incorporation. That is a reminder to handle ownership as a legal document, not just as a sentence in a founder memo.

Keep company property separate from personal accounts where practical. Use a shared repository, record who created important assets, and save signed agreements where both founders can find them. These habits will not replace legal advice, but they reduce the chance that a departure turns into a scavenger hunt for the company's own work.

Decide how the partnership can end

An agreement is incomplete if it only describes the happy path. Discuss:

1. A founder leaves voluntarily.
2. A founder stops contributing but does not formally leave.
3. The founders cannot agree on a major decision.
4. The company runs out of money or changes direction.
5. A founder's other employer, school, or prior contract claims an interest in the work.

For each case, identify who decides, what notice is expected, what happens to unvested equity, and how access to company systems is removed. Avoid writing homemade legal clauses from a template you do not understand. Cooley GO's founder guidance explains that founder arrangements touch ownership, responsibilities, and other legal issues that should be handled with appropriate counsel.

A simple decision test

You should move from an informal collaboration to a signed founder agreement when most of these are true:

Question	Ready signal	Wait signal
Are you building one shared thing?	Shared repository, customers, or product commitment	Separate experiments with no shared assets
Are contributions becoming meaningful?	Regular time, money, or specialized work	A single conversation or idea
Can you discuss ownership?	Specific split and vesting conversation	Avoiding the topic because it feels awkward
Can you name decision rights?	One owner for each major area	Every decision is implicitly unanimous
Is the work legally clean?	Prior IP and outside obligations are identified	Employer or school restrictions are unknown

If the wait signals dominate, keep testing the working relationship and document the trial. If the ready signals dominate, stop treating the partnership as casual and get the agreement reviewed before the next major build or customer commitment.

FAQ

Do I need a founder agreement before I have a company?

You can start with a written collaboration or trial agreement before incorporation, then update the documents when the company exists. The right timing depends on what you are sharing and the laws that apply. Get legal advice before assigning equity or valuable intellectual property.

Should cofounders always split equity equally?

No. Equal ownership can be reasonable when expected contributions and commitments are genuinely comparable, but the label is less important than a clear rationale, vesting, and decision process. Revisit the assumptions before resentment becomes the operating system.

What if one founder already built the prototype?

Separate credit for prior work from the ownership and work expected going forward. Identify the existing IP, decide whether it will be assigned or licensed to the company, and record the agreement. A lawyer can help structure the transfer correctly.

Can a template replace a lawyer?

No. A template can help you list questions, but entity type, jurisdiction, tax treatment, employment obligations, and prior IP can change the answer. Use qualified counsel for the documents that create ownership or assign valuable work.

Wrap up

Before you build the next meaningful version together, write the roles, time commitments, ownership logic, vesting approach, decision rights, IP boundaries, and departure plan on one page. Use that conversation to test the partnership, then have qualified counsel turn the decisions into the right documents.

If you want peers to pressure-test the working agreement before you spend months building, bring the questions to the buildpurdue cohort.