Startup Law

Founders Agreement Before Building an MVP: What to Put in Writing Early

A simple conversation today can prevent an expensive founder dispute when your startup starts to matter.

July 27, 2026 8 min readAdv. & Notary Zion Bahalul
Summary

A founders agreement should be signed before code is written, contractors are hired, or an MVP goes live. It helps founders align on ownership, roles, vesting, IP, decision-making and what happens if someone leaves, while also making later investor diligence far smoother.

Why sign before the MVP exists

Most founder disputes do not start after a financing round. They start much earlier, when the company is still an idea, enthusiasm is high, and nobody wants to talk about uncomfortable topics. That is exactly why a founders agreement should be signed before building the MVP, not after the product is live or users arrive.

At the pre-MVP stage, founders are still negotiating from a position of relative equality. Once one founder has written most of the code, brought the first customers, or invested more money, the discussion becomes emotional and far harder to resolve fairly. Early documentation preserves relationships because expectations are clear before leverage shifts.

Key point: A founders agreement is not a sign of mistrust. It is a risk-management tool that protects the business, the friendship and future fundraising.

In practice, an MVP often creates legal value faster than founders expect. Source code, product designs, domain names, branding, datasets and customer feedback all become assets that someone must legally own. If those assets are created before the founders agree on ownership, roles and transfer obligations, a startup can later discover that its most valuable IP is not properly assigned to the company.

The issues founders should settle early

A good founders agreement is not just about splitting shares. It is the first operating constitution of the startup, setting the rules for how the founding team works before institutional governance is in place. The goal is to document the points most likely to cause conflict while the company is still small enough to fix problems cheaply.

  • Who the founders are and what each person contributes
  • How equity is divided and whether vesting applies
  • Who serves as CEO or product/technology lead
  • What decisions require unanimous approval versus majority approval
  • How IP, code, inventions and know-how are assigned to the company
  • What happens if a founder leaves, is terminated, or stops contributing

Founders should also deal with practical matters that often get ignored: time commitment, salary expectations, expense approvals, whether side consulting is allowed, and how deadlocks are broken. These issues feel operational rather than legal, but they are often what trigger the first serious breakdown between co-founders.

The right level of detail depends on the stage. A two-page memo is usually too thin, while a heavily negotiated shareholders' agreement may be premature before incorporation. The best approach is usually a focused founders agreement that is commercially realistic, legally enforceable and capable of evolving into fuller company documents once the startup is ready to raise.

Equity, vesting and decision-making

Equity is where founders tend to focus first, but the percentage split is only one part of the picture. A clean agreement should explain why the split was chosen, what each founder is expected to contribute, and whether ownership is earned over time. That last point matters because startups change quickly, and contribution levels almost never remain equal for long.

Vesting is often the most important protection in the document. If one founder receives a large share upfront and leaves after three months, the remaining team may be forced to build the company while a disengaged former founder still holds a meaningful stake. A standard vesting schedule with a cliff is often the fairest solution, especially where the MVP has not yet been built.

Real-world example

Two technical founders split the company 50/50 on day one. One founder then accepts a full-time job elsewhere and contributes very little, while the other spends a year building the product. Without vesting or repurchase rights, the inactive founder may still keep half the company.

Decision-making rights should be addressed just as clearly as ownership. Founders should define who can approve hiring, fundraising, material contracts, pivots, bank authority and product strategy. Many early teams assume they will 'just decide together,' but deadlock becomes a genuine company risk once money has been spent and the startup must move fast.

Not sure what legal steps your startup needs?

Get a quick legal fit-check before you incorporate, sign, or raise capital.

IP, confidentiality and side projects

For a pre-MVP startup, intellectual property is often the core asset even before revenue exists. The founders agreement should make clear that inventions, code, designs, documentation, product specifications and business materials created for the venture belong to the company or will be assigned to it immediately upon formation. Without that wording, ownership can remain fragmented across individuals.

  • Pre-existing IP each founder brings in
  • New IP created during the venture
  • Open-source software use and approval
  • Confidentiality obligations
  • Limits on competing projects or side businesses
Common diligence issue

A founder develops the prototype on a personal laptop before the company is incorporated and later uses a freelance developer paid informally. When investors begin diligence, nobody can show a full chain of title for the code. What felt like speed early on becomes a financing problem later.

Side projects need careful drafting, especially in Israel's startup ecosystem where founders may consult, work part-time or experiment with multiple ideas. The agreement should distinguish between approved outside activity and competing activity, and it should require disclosure of relevant prior inventions. Clear IP language is much cheaper than trying to reconstruct ownership after a term sheet arrives.

Roles, commitment and founder departures

Many co-founder conflicts are not really about law; they are about mismatched expectations. One founder thinks the venture is a nights-and-weekends experiment, while another believes everyone is committing full-time within sixty days. A founders agreement should turn those assumptions into written commitments so the team knows what 'pulling equal weight' actually means.

The agreement should define each founder's role, reporting responsibilities, expected time input, and whether salary is deferred. It should also address misconduct, prolonged underperformance, incapacity and voluntary resignation. These points can feel awkward, but they are exactly what protect the startup if a key person disappears when the product is half-built.

  • What counts as a good leaver versus bad leaver
  • Whether unvested shares are forfeited
  • Whether vested shares can be repurchased
  • Who keeps access to code, accounts and customer data

Departure mechanics matter because a founder exit is rarely clean. Access credentials, Git repositories, cloud systems, social accounts and domain control should all be transferred promptly and predictably. A startup cannot afford to negotiate basic handover rules during a personal fallout or just before a demo to investors.

Investor-readiness and due diligence

Investors rarely view a founders agreement as a formality. They see it as evidence that the team understands governance, ownership and execution risk. If the founding relationship is undocumented, investors may worry about hidden promises, unclear cap table rights, unassigned IP or a future dispute that could derail the company after investment.

A clear founders agreement can accelerate diligence because it answers recurring investor questions early. Who owns what? Are the founders subject to vesting? Can a departed founder block the company? Has everyone assigned inventions to the company? The cleaner those answers are, the easier it is for investors and their counsel to move from diligence to documentation.

What investors often see

An angel investor likes a startup's traction but discovers that the product was built before incorporation, one founder holds the domain personally, and there is no written vesting arrangement. The investor does not necessarily walk away, but the round slows down and the legal cleanup becomes more expensive.

This is especially relevant before a SAFE, convertible loan or priced round. Financing documents assume the company has basic internal hygiene. Founders who paper the relationship early usually spend less time fixing preventable legal issues and more time negotiating the commercial terms that actually matter.

How to make the agreement practical

The best founders agreements are practical, readable and tailored to the actual startup, not copied blindly from a US template or taken from another team. Israeli founders in particular often start moving before the company structure is fully formed, so the document should work both before and after incorporation, with clear obligations to sign additional company documents later.

  1. Discuss the commercial points openly before anyone gets emotionally invested in a percentage.
  2. Record pre-existing IP, domains, code and data sources from the start.
  3. Use vesting and departure mechanics instead of relying on goodwill.
  4. Match the agreement to the intended funding path and company structure.

Founders should not try to over-lawyer the first version, but they also should not under-document it. A strong early-stage agreement can be concise while still covering the essential risk points. The right lawyer will help translate founder expectations into enforceable terms without turning the process into a distraction from product building.

The commercial message is simple: sign before the MVP, not after it gains value. Once a product exists, every unresolved issue becomes more expensive because there is now something worth fighting over. Founders who set the rules early give themselves a better chance of building fast, raising cleanly and surviving the pressure that early-stage companies inevitably face.

Checklist

Identify each founder and describe their expected contribution
Agree on the equity split and the commercial logic behind it
Include founder vesting and, where appropriate, a cliff
Define management roles and key decision-making thresholds
Assign all startup-related IP, code and inventions to the company
Set confidentiality, non-compete and side-project rules carefully
Document time commitment, salary expectations and expense policy
Plan for founder departures, forfeiture and handover of accounts/assets

Common Mistakes

✕Splitting equity quickly without discussing contribution, time and future roles
✕Leaving the agreement until after the MVP or first investor meeting
✕Failing to include vesting for founder shares
✕Assuming code or branding automatically belongs to the company
✕Ignoring side projects, consulting work or pre-existing IP
✕Not defining what happens if a founder stops working or leaves
✕Using a foreign template that does not fit the company's actual structure

Frequently Asked Questions

Not sure what legal steps your startup needs?

Get a quick legal fit-check before you incorporate, sign, or raise capital.

Adv. & Notary Zion Bahalul

Adv. & Notary Zion Bahalul

Startup Lawyer · Israel

Adv. Zion Bahalul provides legal counsel to founders, startups, tech companies and investors — from incorporation through fundraising, IP and ongoing counsel. Services in Hebrew, English and Spanish.

The information on this site is general information only and does not constitute legal advice. Each case depends on its circumstances, and it is advisable to obtain individual legal advice before making a decision or signing a document.