Building a Legal Playbook for Your Startup: Every Template You Need (Free)

A legal playbook is the quiet leverage multiplier in every well-run startup. It is the single asset that lets a 40-person company operate with the legal sophistication of a 400-person one — without hiring a GC, without paying a law firm to review every contract, and without slowing down sales cycles.

Most Indian founders know they need one. Very few actually have one. The gap between those two states is the subject of this guide.

This is a complete, working blueprint: every template a pre-seed to Series A startup needs, how to version them, build-versus-buy decisions, and the access control system that prevents the playbook from becoming a stale Google Drive folder.

What a Legal Playbook Actually Is

A legal playbook is not a folder of Word documents. It is an operating system for a company's legal work, consisting of four linked assets:

1. Template library — every contract the company signs, authored and maintained in canonical form.
2. Clause library — pre-approved alternative clauses for known negotiation positions (e.g., three approved versions of the liability cap).
3. Negotiation positions — written guidance on what is non-negotiable, what is flexible, and what requires escalation.
4. Approval workflows — who signs what, at what deal size, after what review.

The reason playbooks fail is that most startups treat them as just the first asset. A clean set of templates sitting in a folder, with no version control, no escalation rules and no clause library, provides roughly 30% of the value a real playbook delivers.

The Minimum Viable Playbook: 15 Templates

For an Indian startup from pre-seed through Series A, the core template library has 15 documents. The list is boring and load-bearing.

Founder and governance

1. Founders' Agreement — equity split, vesting, IP, roles, exit provisions.
2. Share Subscription Agreement (SSA) — standard angel/SAFE/convertible note format.
3. Shareholders' Agreement (SHA) — adapted from your investor's template at first round.
4. ESOP Scheme Document — includes plan rules, grant letter format and exercise notice.

Employment and contractors

5. Offer Letter — short-form, binding acceptance document.
6. Employment Agreement — full form, with IP, confidentiality, non-solicitation, DPDP flow-through.
7. Independent Contractor MSA — master services agreement for freelancers.
8. Intern Offer Letter — compliant with stipend and POSH norms.
9. Advisor Agreement — equity compensation, confidentiality, no employment relationship.

Customer and commercial

10. Customer MSA — your standard "sell-side" template.
11. Order Form / SOW template — the pricing and scope overlay on the MSA.
12. Data Processing Addendum (DPA) — DPDP-compliant, used for any customer handling personal data.
13. Mutual Non-Disclosure Agreement (NDA) — the most-used document in any startup.

Vendor and operations

14. Vendor Purchase Order Terms — counter-template for vendor contracts.
15. Office Lease Addendum or Leave & Licence template — for the first physical office.

Reference and policy documents (6)

• Privacy Policy.
• Terms of Service.
• Acceptable Use Policy.
• Information Security Policy.
• POSH Policy and Internal Committee constitution.
• Data Retention Policy (DPDP-aligned).

Any startup that has clean, current versions of these 21 documents is ahead of 90% of its peers.

Build vs Buy: When to License, When to Write From Scratch

A common founder mistake is to write every template from zero. Another is to licence everything and end up with templates that do not reflect the company's actual business.

The right rule:

| Document type | Default: Build or Buy? | Why | |---|---|---| | Founders' Agreement | Buy (top firm) | High stakes, legally sensitive, one-time | | SHA/SSA | Buy (investor's template as base) | Industry standard | | ESOP Scheme | Buy | Regulatory-heavy; do not reinvent | | Employment Agreement | Build + lawyer review | Needs company culture and context | | Offer Letter | Build | Tiny, standardised | | Customer MSA | Build (this is your sales weapon) | Drives revenue; must reflect pricing and delivery model | | DPA | Buy / adapt | Regulatory; standardised | | NDA | Buy / adapt | Commodity | | Contractor MSA | Buy / adapt | Mostly standardised | | Vendor T&Cs | Build | Company risk tolerance shows here | | Privacy Policy | Build + lawyer review | Must match actual data flows | | POSH Policy | Buy / adapt | Statutory template available |

The single document most worth investing in is the Customer MSA. It is the contract that governs the startup's revenue, it is negotiated most often, and a well-built customer MSA can reduce average deal cycle time by 30–50% by front-loading standard clauses that customers rarely push back on.

Versioning: The Most-Skipped Step

Every template needs three pieces of metadata that almost no startup tracks:

• Version number (e.g., "Customer MSA v3.2").
• Last reviewed date (e.g., "Last lawyer review: 2025-11-15").
• Expiry / next-review date (e.g., "Next mandatory review: 2026-05-15").

Templates need mandatory re-reviews every 6–12 months. Regulations change, and a 2023-era DPA has not kept up with the 2026 state of DPDP Act rule-making. A 2024 employment contract does not reflect the notification status of the Code on Wages, 2019.

A simple Google Sheet or Notion table mapping template → owner → version → last review → next review is enough, provided someone actually checks it quarterly.

Run Your Templates Through AI-Powered Compliance Checks

Clause Libraries: The Unsexy Superpower

A clause library is a collection of pre-approved alternative clauses for known negotiation points. It turns contract negotiations from a creative exercise into a multiple-choice test.

Examples from a standard SaaS Customer MSA:

Liability cap

• Default (your position): 1x fees paid in the trailing 12 months.
• Fallback 1 (for mid-market customers): 1.5x fees paid in the trailing 12 months.
• Fallback 2 (for enterprise customers with hard requirements): 2x fees paid; super-cap at 3x for IP infringement indemnity.
• Never accept: Uncapped liability.

DPDP / data processing

• Default: DPA attached as Schedule; processor duties per DPDP Act.
• Fallback: Customer's DPA accepted if it mirrors our obligations and does not impose audit rights beyond once per year.
• Escalate: Any cross-border transfer restriction, any "specific technical and organisational measures" drafting requiring approval from engineering.

Termination for convenience

• Default: 30 days' notice, no pro-rata refund on pre-paid fees.
• Fallback: 60 days' notice, pro-rata refund for unused portion of current billing period.
• Never accept: Termination at customer's discretion with no notice, full refund of all paid fees.

Three to five approved positions per clause, written in plain language, with a note on who can approve each fallback. Sales, legal and finance all read from the same script.

Negotiation Positions: Writing It Down Changes Everything

A negotiation playbook is a written document, typically 10–30 pages, that captures the company's position on every meaningful clause in its Customer MSA and common vendor contracts.

A useful format for each clause:

• Clause name (e.g., "Indemnification for third-party IP claims").
• Our default position (1–2 sentence summary).
• Why we take this position (business and legal rationale).
• Acceptable fallbacks (in priority order).
• Must-haves (what we will not drop under any circumstances).
• Approval authority (who can accept which fallback).

When a founder or salesperson is on a call and the customer's counsel asks for a specific change, the playbook produces an answer in seconds. Without it, every request becomes a back-and-forth that loses two or three days of cycle time.

Approval Workflows: Who Signs What

Approval workflows are where the playbook becomes operational. The rule of thumb is simple:

| Deal / contract type | Approver | |---|---| | NDAs | Any authorised employee (typically BD) | | Standard Customer MSA on pre-approved template | Sales leader or Head of Commercial | | Customer MSA with 1 or more clauses at Fallback 2 | COO or CEO | | Customer MSA with any "never accept" deviation | CEO + external counsel | | Employment contracts for ICs | Head of People | | Employment contracts for senior/C-suite hires | CEO | | Fundraising documents | CEO + top-tier law firm | | Acquisition-related documents | CEO + Board + top-tier law firm |

E-signature routing should follow these tiers automatically. If the approval matrix requires CEO sign-off, the document should not be able to route to the counterparty before that approval is logged.

Where to Store the Playbook

Three components:

1. Template documents — in a document management system with version history (Google Drive with tracked versions, Dropbox Paper, Notion, or a CLM like LexiReview's vault).
2. Clause library and negotiation positions — in a structured format (Notion table, Airtable, or a dedicated playbook tool).
3. Approval workflow logic — built into your e-signature tool (DocuSign, Signeasy, or a CLM with routing).

What matters is not the tool. What matters is that the three components are linked and that "where is the latest version?" has a single, unambiguous answer.

Access Controls: Three Tiers, No More

Role-based access is not optional for a legal playbook:

• Owner (1 person) — usually the founder, COO or GC. Can edit templates, approve new versions, update the clause library. Has audit log visibility.
• Contributor (3–8 people) — heads of Sales, Product, Engineering, Finance, People. Can propose edits, add clauses to the library, but cannot publish new template versions.
• Viewer (all employees who sign contracts on behalf of the company) — read-only access to current-approved templates. Cannot edit. Can request a fallback position via a defined escalation workflow.

Storing templates on a shared Google Drive where anyone can "Save As" is a recipe for version drift. Within six months, sales has its own version of the MSA that includes concessions legal never approved. Clean access tiers prevent this.

The Quarterly Maintenance Ritual

A playbook that is not reviewed quarterly is a playbook that will be wrong within a year. The quarterly ritual should cover:

• Any new statute or notification (DPDP rules, Code on Wages state-level notifications, MCA amendments).
• Any new clause or position that emerged from the previous quarter's negotiations.
• Any template that hit its "next review" date.
• Any clause that got pushed back on in more than three customer negotiations (usually a signal to update the default position).
• Any business change (new pricing, new product, new geography) that affects the Customer MSA.

Budget two hours a quarter for the owner plus 30 minutes from each contributor. Total cost: one Friday morning. Without it, the playbook ages into a liability.

Common Mistakes to Avoid

• Over-engineering on day one. 15 templates, built fast and reviewed, beat 40 templates built by lawyers and never used.
• Delegating playbook ownership to "the operations person." The playbook owner should be a senior commercial or legal hire, not an EA or office manager.
• Letting sales own the Customer MSA without legal backstop. Revenue and legal risk are both real; neither side should unilaterally dictate terms.
• Free templates from random websites. Indian contract templates on free-download blogs are typically US-origin, outdated, or legally defective. If you must start from a free template, have it reviewed before use.
• Forgetting Hindi and regional language provisions. In some states, local-language translations of employment contracts are required under state labour laws.

Putting It All Together: The 30-Day Implementation Plan

Week 1 — Inventory. List every template the company actually uses. Collect the most recent version of each. Note which are missing.

Week 2 — Build or buy core templates. Focus on the 15 core templates. Engage a boutique firm for the Tier 1 items (Founders' Agreement, SHA/SSA, ESOP Scheme, Employment Agreement).

Week 3 — Clause library and negotiation positions. For the Customer MSA and the Employment Agreement, write 3–5 approved positions per key clause. Get one lawyer sign-off.

Week 4 — Access controls and approval workflow. Set up the storage, define the three access tiers, wire the approval matrix into e-signature routing.

At the end of 30 days, a pre-seed or seed-stage startup has a working, maintainable legal playbook at under ₹2 lakh total cost. That is the playbook.

Build Your Playbook with LexiReview

Frequently Asked Questions

Can I really build a legal playbook for a startup without hiring a GC?▾

Yes, at pre-seed and seed stage, a playbook can be built entirely by the founder or a senior operator, supported by a boutique law firm for initial drafting of Tier 1 templates and by AI contract review tools for ongoing maintenance. The skill required is operational discipline — versioning, approval routing, quarterly review — more than legal expertise. Most sub-30-person Indian startups that have working playbooks got there without a GC. The role of the GC becomes meaningful when the volume of non-standard contracts exceeds what a fractional lawyer can handle in 20 hours a month.

Where can I get legally reliable Indian contract templates?▾

The best starting points are: (1) boutique law firms that offer a 'startup starter pack' of templates, typically priced between ₹40,000 and ₹1,50,000; (2) accelerator and incubator template libraries (YC India, Antler, 100X.VC all offer template sets to portfolio companies); (3) Bar Council-backed resources and MCA publications for statutory templates like POSH policies; (4) AI contract review and CLM tools that offer template libraries as part of the product. Free templates from generic legal-document websites are often US-origin or outdated and should never be used without lawyer review.

Should my Customer MSA be the same as my competitor's?▾

No. The Customer MSA is a commercial document that must reflect your pricing model, delivery model, SLAs, data handling practices, and risk tolerance. Copying a competitor's MSA almost always produces a document that misaligns with your actual operations — for example, uptime commitments that your infrastructure cannot meet, or indemnities that exceed your insurance coverage. The Customer MSA is the one template where building from scratch, tailored to the business, pays the highest dividend. Reference competitor MSAs for structure and clause identification, but write the substance yourself with legal review.

How often should contract templates be reviewed and updated?▾

Every 6–12 months at minimum, with additional ad-hoc reviews triggered by: (1) new legislation (DPDP rules, new labour code notifications, GST amendments); (2) any material change in business model (new product line, new geography, new pricing structure); (3) patterns in customer negotiations (if the same clause gets pushed back on three or more times, update the default); (4) any litigation, regulatory inquiry, or customer dispute involving the template. A strict annual review cadence is the baseline; six-monthly is better for fast-moving areas like DPDP and employment.

Who should own the legal playbook at a Series A startup?▾

At Series A, the playbook owner is typically the COO, the Head of Commercial/Revenue Operations, or a dedicated legal operations hire. If a GC or fractional GC exists, they are usually a co-owner. What matters is that the owner has operational authority (can enforce versioning and access controls), sits close to both sales and legal workflows, and has the bandwidth for quarterly maintenance. Founders own the playbook at pre-seed by default because there is no one else — but this should be delegated as soon as a suitable senior hire exists.

What is the single most important template to get right?▾

The Customer Master Services Agreement. It is the contract that governs every revenue-generating relationship, is the most frequently negotiated, and has the largest impact on cash flow, liability, and deal-cycle time. A well-built Customer MSA reduces average sales cycle time by 30–50% because most procurement teams accept clean, market-standard language and only push back on two or three specific clauses. A poorly built Customer MSA generates endless redlines, legal escalations, and lost deals. If a founder can invest in only one template, this is the one.

Do I need separate templates for Indian customers versus international customers?▾

Yes, usually. Indian customer contracts should reference Indian law, Indian courts or arbitration seated in India, Indian currency, Indian tax (GST, TDS under 194J/194C), and DPDP-compliant data handling. International customer contracts may need different governing law (typically English law, Singapore law, or Delaware law), different dispute resolution (SIAC, LCIA, or ICC arbitration), different currency and payment terms, and data handling compliant with GDPR or CCPA in addition to DPDP. Maintaining two customer MSA templates — one India-domestic and one international — is standard practice for B2B startups with mixed customer bases.