Need help with startup agreements? We can handle it for you.
Founders treat agreements like paperwork. Something to get through, not something that does anything. That's the wrong model.
An agreement is an operating system for a relationship. It tells two people what happens when things go well, and, more importantly, what happens when they don't. Every relationship your startup forms — with a co-founder, an employee, a vendor, a customer, an investor — eventually needs one, because every one of those relationships will eventually hit a moment where memory and goodwill aren't enough.
This guide maps every agreement an Indian startup signs, from the first handshake with a co-founder to a Series A term sheet. Not to make you sign everything on day one — most of these you'll never need in year one — but so you know what's coming, why it exists, and what breaks if you skip it.
Why startups sign agreements at all
Two co-founders agree to split equity 50-50. No document, just a conversation over coffee. Eight months later, one of them has written most of the code and closed every customer; the other has been mostly absent. Both remember the conversation differently. Neither can prove what was actually agreed. This is not a hypothetical — it is the single most common founder dispute in early-stage India, and it is entirely preventable with one document signed on day one.
Verbal understanding fails for a boring reason: memory is reconstructive, not recorded. People don't lie on purpose — they each remember the version that made sense to them at the time, shaped by what they contributed and what they expected. Add eight months, a falling-out, and money on the table, and two honest people can recall two contradictory agreements. A contract doesn't just prevent dishonesty. It prevents this far more common failure: two good-faith memories that no longer match.
Ambiguity has a cost even when nothing goes wrong. Vague agreements mean every disagreement becomes a renegotiation instead of a lookup. That's time, trust, and often money, spent re-litigating something that should have taken one sentence to settle.
Once a startup has more than one person in it, agreements stop being legal overhead and start being infrastructure — the same category as your incorporation documents or your accounting system. Every arrow in the diagram below is a relationship that, sooner or later, gets formalised: founder to co-founder, founder to employee, founder to contractor, founder to vendor, founder to customer, founder to investor.
This article is general information, not legal advice. If you need advice for your specific situation, contact BuildWright directly.
Prefer to skip the paperwork?
BuildWright can take this off your plate — done properly, the first time.
Get new templates and compliance updates by email.
Founder ↔ Co-founder — a Founder Agreement
Founder ↔ Employee — an Employment Agreement
Founder ↔ Contractor — a Consultant or Service Agreement
Founder ↔ Vendor — a Vendor or Supply Agreement
Founder ↔ Customer — a Service Agreement, MSA, or SOW
Founder ↔ Investor — a Term Sheet, Subscription Agreement, and Shareholders Agreement
How agreement needs evolve as you grow
You don't need every agreement in this guide today. You need the right one at the right stage. Here's roughly how the stack builds, from idea to expansion.
Idea
Nothing binding yet, but if you're discussing the idea with someone outside your founding team, a one-way NDA is cheap insurance.
Co-founder
Essential: Founder Agreement covering equity, roles, vesting, decision-making, and exit. This is the single highest-leverage document you'll ever sign.
Prototype
IP Assignment from anyone who touches code or design — including yourself, from any entity you previously worked under. Consultant Agreements for freelance help.
First customer
Essential: a Service Agreement or set of Website Terms, depending on what you sell. Add a Privacy Policy the moment you collect any personal data.
Hiring
Essential: Offer Letters and Employment Agreements with confidentiality and IP assignment clauses built in. Recommended: an Employee Handbook and a POSH policy — the POSH policy is a legal requirement, not optional, once you have 10 or more employees.
Scaling
Recommended: Master Service Agreements with repeat customers, Vendor Agreements with suppliers, Non-Solicitation clauses to stop poaching as your team grows.
Investment
Essential: Term Sheet, Subscription Agreement, Shareholders Agreement — or a SAFE/Convertible Note if you're raising a smaller, earlier round.
Expansion
Growth stage: Distribution, Reseller, and Licensing Agreements as you extend beyond direct sales; Data Processing Agreements as you handle more third-party data.
The four things every agreement is actually doing
Strip away the legal language and every agreement — founder, employee, vendor, investor — is doing the same four jobs. Once you see these four, most contract clauses stop feeling like boilerplate and start making sense.
1. Clarify expectations
Who does what, by when, for how much. Removes the guesswork that turns into arguments later.
2. Allocate risk
If something goes wrong — a missed deadline, a data breach, a defective product — the agreement decides in advance whose problem it is.
3. Resolve disputes
A dispute resolution clause decides how disagreements get settled: negotiation, mediation, arbitration, or court, and where.
The fourth job — protecting value — is why founders should care even when a relationship is going well. An agreement locks in your IP ownership, your confidential information, and your equity structure so that value you've already built can't quietly walk out the door with a departing co-founder, employee, or contractor.
The master agreement matrix
Here is the full reference table: every agreement covered in this guide, the stage it typically shows up, whether it's mandatory, what it's for, and what tends to go wrong without it. Use it as a checklist against your own stage, not a to-do list to clear in one sitting.
Agreement
Typical stage
Mandatory?
Purpose
Risk if missing
Founder Agreement
Co-founder
Yes
Locks equity, roles, vesting, and exit terms among founders
A silent or absent co-founder keeps full equity forever, with no way to resolve it
Shareholders Agreement (SHA)
Fundraising
Yes, once investors join
Governs shareholder rights, board control, exit, and anti-dilution
Investor and founder rights are undefined; governance disputes at the board level
Subscription Agreement
Fundraising
Yes
Records the actual share purchase — price, conditions, warranties
The investment can't be legally recorded; cap table disputes
Employment Agreement
Hiring
Yes
Defines role, pay, notice period, IP ownership, confidentiality
Ex-employee disputes ownership of what they built; unclear termination process
Consultant Agreement
Any stage
Yes
Defines scope, deliverable ownership, and payment for non-employees
Consultant claims IP in the work; labour authorities reclassify them as an employee
Territory, exclusivity, and targets for third-party distributors
A distributor sells competing products or disputes territory rights
Reseller Agreement
Scaling sales
Recommended
Pricing, margins, and branding rules for resellers
Undercut pricing, brand misuse, unauthorised claims about your product
Licensing Agreement
IP monetisation
Recommended
Terms for letting others use your IP, brand, or technology
Licensee overuses, resells, or misrepresents your IP
Partnership Agreement
Strategic partnerships
Recommended
Defines joint responsibilities, revenue share, and exit terms
Unclear ownership of joint output; revenue-share disputes
Settlement Agreement
Dispute resolution
As needed
Formalises the resolution of a dispute and releases future claims
The same dispute resurfaces with no enforceable closure
Founder agreements: the one to sign first
If you sign nothing else in this entire guide, sign this one. A Founder Agreement is the contract between co-founders that covers equity split, roles, decision-making authority, what happens in a deadlock, and — the part almost everyone skips — what happens when someone leaves.
Sign it before you write a line of code or talk to a single customer, not after. Once real value exists — a working product, a paying customer, a term sheet — the conversation about who owns what gets harder, not easier, because now there's something worth arguing over.
What actually needs to be in it
Equity split, and the vesting schedule attached to it
Roles and decision-making authority — who has final say on what
What counts as a deadlock, and how it gets broken (a casting vote, a mediator, a buy-out clause)
IP ownership — confirming the company, not any individual founder, owns what gets built
Exit terms: what a leaving founder is entitled to, and what they're not
Good leaver vs bad leaver definitions, and how each affects unvested equity
Dispute resolution — how disagreements between founders get resolved before they become public
Vesting is the clause that does the most work here. Standard structure in Indian startups mirrors the global norm: a four-year vesting period with a one-year cliff, meaning a founder earns nothing if they leave in the first twelve months, then vests monthly or quarterly after that. Reverse vesting applies the same logic to equity founders already hold at incorporation — instead of assuming it's earned, it makes them earn it going forward, exactly like a new grant.
Case study: Two founders split equity 60/40 at incorporation, no vesting attached. The 40% founder leaves after six months to take a full-time job. They keep the full 40% — for a company they spent half a year on, out of what could be a ten-year journey. The remaining founder has now given away nearly half the company for six months of work, with no way to claw it back. A one-year cliff would have reduced that 40% to zero. This is the single most common — and most preventable — founder dispute in early-stage India.
This is also where a Founder Agreement connects to two documents you'll need later: your cap table, which has to reflect vesting accurately from day one, and your ESOP pool, which uses the same vesting logic to bring employees in as owners. Get the founder-level vesting right first — everything downstream copies the same structure.
The employment ecosystem
Hiring your first employee triggers a stack of documents, not just one contract. Most founders sign the Employment Agreement and stop there, then find out later that the gaps were in the surrounding documents, not the main one.
Offer Letter — the initial terms: role, compensation, start date. Not the full contract, but binding on what it promises.
Employment Agreement — the full terms: notice period, confidentiality, IP assignment, termination grounds, non-solicitation.
Employee Handbook — company-wide policies: leave, conduct, working hours, remote work rules.
Confidentiality and IP Assignment — often folded into the Employment Agreement, but must explicitly assign anything the employee creates to the company.
Acceptable Use Policy — rules for company systems, devices, and data, especially relevant once you handle customer data.
POSH Policy — legally mandatory for any employer with 10 or more employees under the POSH Act, 2013. This is not optional and not just for larger companies.
Leave Policy — statutory minimums plus whatever additional leave you offer.
Performance Improvement Plan template — protects you if a termination is later challenged as arbitrary.
Termination and exit documents — full and final settlement, relieving letter, exit interview record.
The IP assignment clause deserves specific attention because it's the one founders assume is automatic and isn't. In India, work created by an employee in the course of employment generally belongs to the employer by default — but 'in the course of employment' has been litigated, and a side project built on a personal laptop after hours sits in a genuine grey zone. Don't rely on default law. Put it in writing.
Contractors and consultants: the classification trap
Founders default to hiring freelancers with nothing more than a WhatsApp conversation and a UPI payment. Two separate risks follow from that: the freelancer can later claim ownership of what they built, because nothing assigned it to you, and if the relationship looks enough like employment, labour and tax authorities can reclassify the contractor as an employee — retroactively, with back-dated PF, ESI, and tax obligations attached.
Factor
Employee
Contractor
Control over how work is done
Company directs hours, methods, tools
Contractor controls their own process and schedule
Company owns work created in the course of employment
Contractor owns it unless explicitly assigned in writing
Termination
Governed by notice period and labour law protections
Governed purely by contract terms
A proper Consultant Agreement fixes both risks in one document: it assigns IP explicitly, defines payment on a deliverable basis rather than a salary basis, and states plainly that the relationship isn't employment. If you're treating someone like a full-time employee in practice — daily standups, fixed hours, company laptop — no contract label will save you from a misclassification claim. The agreement has to match the reality.
Customer agreements
What you sign with customers depends on what you're selling. A one-off project uses a single Service Agreement. A repeat B2B relationship splits into a Master Service Agreement — the umbrella terms that don't change project to project, like payment terms, confidentiality, and liability caps — plus a Statement of Work for each specific project's scope, deliverables, and price.
SLA (Service Level Agreement) — uptime, response time, and support commitments, mainly for SaaS and managed services
Change Request process — how scope changes get priced and approved mid-project, so 'just one more thing' doesn't erode your margins
Payment terms — milestones, due dates, and what happens on late payment
Warranty — what you guarantee about your product or service, and for how long
Limitation of Liability — caps how much you can be sued for if something goes wrong; without this clause, your exposure is technically unlimited
Termination and Dispute Resolution — how either side exits the relationship, and where disputes get resolved
The limitation of liability clause is the one founders most often leave out of a first-draft contract, and it's the one that matters most. Without a cap, a customer who suffers a loss connected to your product can, in theory, come after damages far beyond what you were ever paid for the engagement.
Vendor agreements
Vendor relationships run the same risk-allocation logic in reverse — now you're the one depending on someone else's delivery, quality, and data handling.
Risk
Who typically bears it
How the agreement should allocate it
Late delivery
Your business, in lost time and revenue
Delivery deadlines with penalty clauses or termination rights
Defective goods or services
Whoever the contract assigns it to
Warranty terms and a defined remedy period
IP infringement by the vendor
You, if a third party sues over vendor-supplied IP
Indemnity clause requiring the vendor to cover such claims
Data breach via a vendor
You, under data protection law, even if the vendor caused it
A DPA plus indemnity, and insurance requirements on the vendor
Price fluctuation
Whoever didn't lock in pricing
Fixed pricing for the contract term, with a defined renewal process
Insurance and indemnity clauses matter more with vendors than founders usually assume — if a vendor's negligence causes you a loss, an indemnity clause is what lets you actually recover it, rather than just having a moral high ground.
Digital agreements
Every business with a website or app needs some subset of these. Which ones depend on what the site actually does.
Business type
Website Terms
Privacy Policy
Cookie Policy
DPA
SaaS Terms
Content or informational site
Required
Required if any form collects data
Recommended
Not needed
Not applicable
E-commerce store
Required
Required
Required
Recommended if using third-party payment processors
Not applicable
SaaS product
Required
Required
Required
Required
Required
Mobile app collecting personal data
Required
Required
Not applicable
Required if data is shared with processors
Depends on model
Agency handling client data
Required
Required
Recommended
Required
Not applicable
Refund and Shipping Policies follow the same logic for e-commerce specifically — both are effectively mandatory once you're taking payment for physical goods, and both are frequent sources of consumer complaints when left vague. A Data Processing Agreement is the one founders most often skip because it sounds like enterprise-only paperwork — it isn't. Any startup that processes personal data on behalf of a business customer, or hands customer data to a vendor, needs one to stay compliant under India's Digital Personal Data Protection Act.
Investment agreements: a quick map
This deserves its own guide in full — here's the shape of it. Early rounds in India typically run through a SAFE (Simple Agreement for Future Equity) or a Convertible Note, both of which let you raise money now and defer setting a valuation until a priced round. A priced round itself moves through a Term Sheet (non-binding terms both sides agree to work from), a Subscription Agreement (the actual share purchase), and a Shareholders Agreement (ongoing governance, rights, and protections).
Every subsequent round typically triggers SHA amendments rather than a fresh document — new investor rights get layered onto the existing agreement. This is exactly where due diligence catches most problems: an investor's legal team will read every agreement your company has ever signed, and gaps or inconsistencies here — an unassigned IP, a founder without proper vesting, a customer contract with unlimited liability — slow down or kill deals at the worst possible time. The agreements you sign at seed stage are read closely at Series A.
Managing agreements once you have them
A signed contract sitting in someone's email inbox is barely better than no contract. Every agreement has a lifecycle, and most startups only manage the first half of it.
Draft
Start from a template built for the relevant relationship, not a generic one pulled off the internet.
Review
Check it against the four purposes: does it clarify, allocate risk, define disputes, and protect value for your side.
Negotiate
Track what changed and why — this history matters if a dispute arises later.
Approve
One person signs off internally before it goes out for signature, even in a two-person startup.
Sign
Execute with both parties' details correct — names, designations, dates — errors here can affect enforceability.
Store
One central, searchable location. Not someone's personal inbox.
Revisit terms before auto-renewal locks you into another cycle on outdated conditions.
The practical version of this: one shared folder, organised by counterparty type (founders, employees, vendors, customers, investors), with a consistent naming convention — date, counterparty, agreement type — and one register (a simple spreadsheet works) tracking every agreement's start date, renewal date, and key obligations. This is most of what BuildWright means by Documentation:
Put it on paper. BuildWright's Documentation service builds the agreement stack your stage actually needs, and helps you keep it organised as you grow.
AI tools draft a first pass of a standard agreement fast and cheap. They're genuinely good at that: producing a structurally sound NDA or a first-draft Employment Agreement in minutes. What they don't do well is judgment — knowing which clauses actually matter for your specific deal, catching a one-sided liability clause a counterparty's lawyer slipped in, or knowing when a 'standard' term isn't standard for your industry or jurisdiction. Hallucinated case citations and outdated statutory references are a known, documented failure mode of general-purpose AI tools drafting legal text — always verify anything that looks like a specific legal citation.
Approach
Speed
Cost
Risk
Best used for
AI drafting alone
Fastest
Lowest
Highest — no judgment on deal-specific risk, possible hallucinated references
A rough first draft, or low-stakes internal documents
Generic template
Fast
Low
Moderate — doesn't reflect your specific deal or jurisdiction
Most startup agreements — the practical default for most stages
Human review checklist before signing anything AI-assisted: Does it reflect your actual business context, not a generic scenario? Are the parties' names, dates, and figures correct? Does the liability cap match what you can actually afford to lose? Is the governing law and jurisdiction clause set to India, and to a city that's actually convenient for you? Has a human read the whole document, not just skimmed the headings?
Three founder journeys
SaaS startup
Agreement-heavy from day one, because the product is intangible and the customer relationship is recurring.
Founder Agreement before writing code
IP Assignment for all early contributors
SaaS Terms, Privacy Policy, DPA before first signup
MSA + SOW once enterprise customers appear
Common mistake: shipping a DPA-less product to a B2B customer, then scrambling when their legal team asks for one during procurement
Agency
Contract-driven revenue from the start — the Service Agreement is the business model.
Founder Agreement and IP Assignment
Service Agreement or MSA + SOW for every client
Limitation of Liability in every contract, without exception
Contractor Agreements for freelance talent, with IP assignment built in
Common mistake: starting client work on a verbal 'yes' before the SOW is signed, then chasing payment with nothing in writing
D2C brand
Physical goods bring a different risk set — supply chain and consumer-facing terms dominate.
Founder Agreement, Vendor Agreements with manufacturers
Distribution or Reseller Agreements as retail partners come on
IP protection for brand and packaging
Common mistake: no written terms with a manufacturer, discovering the gap only after a quality dispute or a delayed shipment
Your starting toolkit
You don't need every agreement in this guide today. You need these four systems in place so that every agreement you do sign stays organised and enforceable.
An agreement checklist mapped to your actual stage — not the full matrix above, just what applies now
A contract register (a spreadsheet is enough) tracking every signed agreement, its renewal date, and its key obligations
A renewal calendar with reminders set well ahead of auto-renewal or expiry dates
A clause checklist for your most common agreement type — the one you'll sign again and again — so nothing gets missed in future drafts
A due diligence folder — every founder, employee, and investor agreement, stored in one place, ready to hand over the day a term sheet arrives
Frequently asked questions
Do I need an NDA before every meeting?
No. Most early conversations — with potential co-founders, advisors, or casual introductions — don't warrant one, and asking for an NDA before a first meeting can come across as a red flag to experienced investors and partners. Use one specifically when you're sharing something genuinely sensitive: source code, a customer list, unreleased financials, or a novel technical approach with someone outside your core team.
Should freelancers sign agreements?
Yes, always, even for a single small project. A short Consultant Agreement that assigns IP and defines payment terms takes an hour to put in place and closes both the ownership risk and the misclassification risk described above.
Can ChatGPT or other AI tools draft my contracts?
For a first draft of a standard document, yes. For anything you're actually going to sign — especially a founder agreement, an investment document, or anything with a liability clause — get a human to review it. AI drafting tools are known to occasionally fabricate legal citations or reference outdated law with total confidence, which is a particularly dangerous failure mode in a document you intend to rely on later.
What agreements should I sign before hiring my first employee?
At minimum: an Offer Letter and an Employment Agreement with confidentiality and IP assignment clauses. If you're above 10 employees, a POSH policy is a legal requirement, not optional.
Can founders split equity verbally?
They can agree to it verbally, but it isn't enforceable, isn't recorded anywhere the company or a future investor can verify, and has no vesting attached by default. This is the single most common source of founder disputes in early-stage Indian startups. Put it in writing before you build anything of value.
What legal agreements does a startup need first?
In order: a Founder Agreement if there's more than one founder, IP Assignment for anyone touching the product, then whatever your first revenue relationship requires — a Service Agreement for a customer, or Website Terms and a Privacy Policy if you're operating a live product.
Which agreement should co-founders sign first?
The Founder Agreement, before any other document, and ideally before writing any code or approaching any customer.
Do startups need NDAs with vendors and customers, not just investors?
Yes, whenever confidential information changes hands in either direction. A mutual NDA is the right form when both sides are sharing sensitive information, such as during vendor due diligence or a joint pilot.
Is a Founder Agreement legally required in India, or just good practice?
It isn't a statutory requirement in the way, say, a Privacy Policy is under data protection law. But once a company is incorporated, the equity, vesting, and exit terms it sets out become the practical mechanism for resolving founder disputes — without it, you're relying entirely on general contract and company law principles, which are slower, more expensive, and far less predictable than a document you control the terms of.
What happens if we never sign a Founder Agreement and a co-founder leaves?
They keep whatever equity they hold, in full, with no vesting to claw any of it back — regardless of how long they actually stayed or contributed. Resolving it afterward means negotiating a buy-back after the relationship has already broken down, from a far weaker position than if the terms had been set in advance.
Do I need a separate Privacy Policy if I already have Website Terms?
Yes. Website Terms govern how someone may use your site or product. A Privacy Policy discloses what personal data you collect and how you use it — a legally distinct obligation under India's Digital Personal Data Protection Act. They cover different things and both are typically required.
How is a Consultant Agreement different from an Employment Agreement?
An Employment Agreement creates an ongoing employer-employee relationship with statutory protections, PF/ESI obligations, and default IP ownership in the employer's favour. A Consultant Agreement is a service relationship between independent parties, paid against deliverables, with IP ownership only transferring if the contract says so explicitly.
When do we need a Shareholders Agreement instead of just a Founder Agreement?
The moment anyone outside the founding team — an investor, typically — takes shares in the company. A Founder Agreement governs the founders among themselves; a Shareholders Agreement governs all shareholders, including new investors, and usually supersedes or sits alongside the founder-level terms.
How often should we review and update our agreements?
At minimum, at every major stage change — before hiring your first employee, before your first outside investment, before expanding into a new state or country. Templates that were fine for a two-person company rarely hold up unchanged at twenty people.
What's the minimum agreement stack for a two-person startup with no revenue yet?
A Founder Agreement with vesting, IP Assignment from both founders, and Website Terms plus a Privacy Policy the moment anything goes live publicly. Everything else in this guide can wait until the relationship that needs it actually exists.
The list in this guide is long on purpose — most of it doesn't apply to you yet. What matters is knowing what's coming, and not being the founder who finds out what a document was for only after not having it.
Not sure which agreements your startup actually needs right now? BuildWright's Documentation service maps your stage to the right stack, drafts what's missing, and keeps it organised as you grow — put it on paper before you need it in a dispute.