73. Contracts

A contract is not a formality after a deal is closed. It is the operating memory of the deal: what is being bought, who owns what, when money moves, what happens when something breaks, and how much risk the company has accepted.

This is founder guidance, not legal advice. Use it to understand what you are signing and where to involve counsel.

The core contract question is: does the document match the commercial reality of the deal, and is the downside survivable if something goes wrong?

Founders should not become full-time lawyers. But they must learn to spot clauses that can quietly damage the company: broad IP transfer, unlimited liability, impossible SLAs, slow payment cycles, vague scope, harsh termination, unusual jurisdiction, and data obligations the product team cannot actually meet.

The founder contract rule

Never sign a contract you cannot explain in plain language. You should be able to answer:

What are we promising?
What are they promising?
When do we get paid?
What can go wrong?
Who owns IP, data, and deliverables?
What is our maximum downside?
How can either side exit?
What happens if there is a dispute?

If you cannot answer these, the contract is not ready for signature.

Customer contracts

Order form

The order form should capture the commercial truth: customer name, product or service, users or usage limits, term, price, payment schedule, taxes, start date, renewal, support level, and any special terms. Many disputes start because the sales conversation promised one thing and the document said another.

MSA or SaaS agreement

The master services agreement or SaaS agreement sets the main legal terms. It should cover scope, access, acceptable use, customer obligations, fees, invoicing, payment, warranties, confidentiality, IP, data, support, liability, termination, dispute process, and governing law.

For early startups, keep the agreement readable. A giant enterprise document copied from a large company can slow deals and create obligations you cannot meet.

SLA and support terms

Do not promise 24/7 support, strict uptime, penalties, dedicated account management, or custom response times unless your team can actually deliver. Enterprise customers may ask for strong SLAs, but each promise has an operational cost. If you are early, define support windows, severity levels, exclusions, maintenance windows, and what remedies apply.

DPA and security terms

If you process personal data or customer confidential data, customers may require a data processing agreement, security schedule, breach notification clause, subprocessors list, audit rights, data deletion terms, and data location details. Do not treat these as “lawyer-only” issues. Product, engineering, support, and operations must know what the company promised.

Payment and renewal terms

Early founders often accept bad payment terms because they want logos. Be careful. “Payment in 90 days after invoice approval” can turn into a cash-flow problem. Define invoice timing, GST or tax treatment, late payment consequences, purchase order requirements, renewal process, cancellation window, and what happens if the customer keeps using the product without payment.

Vendor contracts

Vendor contracts matter because vendors often touch your code, data, customers, brand, or infrastructure.

For agencies, freelancers, developers, designers, marketers, consultants, and implementation partners, insist on:

Clear scope and deliverables.
Acceptance criteria.
Timeline and milestones.
Payment terms tied to delivery.
IP assignment to your company.
Confidentiality.
Data protection obligations.
Repository, account, and credential return.
Termination rights.
Liability and indemnity proportionate to the risk.

The biggest vendor mistake is assuming “we paid, so we own it.” Payment does not always equal ownership. If an agency builds your MVP, branding, website, app, content, or design system, make ownership explicit.

Partnership contracts

Partnerships are seductive because they sound like distribution without sales. Most weak partnerships fail because nobody is obligated to do anything concrete. A useful partnership agreement should define target customers, responsibilities, lead sharing, revenue share, exclusivity if any, marketing obligations, customer ownership, data sharing, support responsibility, termination, and how conflicts are resolved.

Avoid broad exclusivity unless the partner is giving you real distribution, minimum commitments, or money. Exclusivity without performance is a cage.

Contract review rubric

Use this quick filter before signing:

Clause	Founder question
Scope	Is it clear what we must deliver and what is excluded?
Price	Is the amount, currency, tax, invoice trigger, and due date clear?
Payment	Can we survive the payment cycle?
IP	Do we keep our product, code, tools, templates, and learnings?
Data	Are we promising security or privacy practices we actually follow?
Confidentiality	Can the team understand and honor it?
Liability	Is our downside capped and proportionate?
Indemnity	Are we taking responsibility for things outside our control?
Termination	Can we exit if the relationship becomes harmful?
Dispute	Do we understand the forum, law, and practical cost of dispute?

The founder redline playbook

When a customer or vendor sends a contract, separate issues into three buckets.

Must fix

These are terms that can seriously harm the company:

Unlimited or disproportionate liability.
Transfer of your core product IP.
Broad indemnity for things outside your control.
Security or compliance promises you cannot meet.
Data terms that conflict with your actual product operations.
Exclusivity without minimum commitments.
Payment terms that create cash-flow risk.
Termination rights that let the other side avoid payment after work is done.

Negotiate if possible

These are worth improving, but may not kill the deal:

Shorter payment cycle.
Clear acceptance process.
Narrower audit rights.
More realistic support commitments.
Better renewal or price increase terms.
Notice and cure period before termination.
Mutual confidentiality.

Can accept

These are tolerable if they match the business:

Reasonable customer procurement steps.
Standard confidentiality.
Ordinary tax documentation.
Limited reporting obligations.
Practical security questionnaire responses.

This triage prevents founders from fighting every clause with equal intensity.

Contract ownership inside the company

Every signed contract should have:

Business owner.
Legal or review owner.
Signed copy location.
Start date and renewal date.
Payment terms and invoice trigger.
Key obligations.
Data or security promises.
Termination window.
Open risks.

Put renewal dates and notice periods into a calendar. Many startups lose leverage because they notice auto-renewals, payment milestones, or termination windows too late.

Contract Stack By Stage

Do not wait until every deal is enterprise-scale to create basic contract hygiene.

Stage	Minimum contract stack
Pre-revenue	Founder agreement, contractor template, advisor template, NDA/confidentiality, IP assignment.
First paid pilots	Simple order form, pilot terms, payment terms, scope, success criteria, data access terms.
Early SaaS/product sales	MSA or SaaS terms, order form, privacy policy, support terms, DPA where relevant.
Services-to-product	Statement of work, milestone acceptance, IP split between reusable platform and client deliverables.
Enterprise sales	MSA/SaaS agreement, DPA, security schedule, SLA, procurement docs, vendor onboarding pack.
Partnerships	Referral/reseller/implementation agreement, lead ownership, revenue share, support, brand use, termination.

The stack should match the business. A founder selling a Rs. 20,000 pilot does not need a 60-page contract. A founder handling sensitive customer data for a large enterprise needs more than an email confirmation.

Contract Negotiation Process

Run contract negotiation like a sales and risk workflow.

Capture commercial terms before legal review: price, scope, users, usage, timeline, payment, support, data, custom work.
Identify non-negotiables: IP, liability, data, payment, exclusivity, security promises.
Mark who owns each issue: founder, sales, lawyer, finance, engineering, security.
Redline once with a clear explanation instead of many scattered comments.
Keep a decision log for accepted risks.
Convert obligations into an internal checklist after signature.

The worst contract process is when legal, sales, finance, and product each negotiate different realities. The signed document should match what the team can deliver.

Contract Review Meeting Agenda

For important deals, run a 30-minute review before final redlines.

Agenda item	Founder question
Commercial truth	Does the contract match what sales promised and what the customer expects?
Delivery reality	Can product, success, support, and engineering actually deliver the obligations?
Cash timing	When can we invoice, when will cash arrive, and what documents are required for payment?
Risk cap	What is the maximum downside if the deal goes wrong?
Data/security	Are privacy, security, audit, breach, deletion, and subprocessor commitments accurate?
IP	Are we protecting our platform, tools, templates, libraries, and pre-existing work?
Exit	Can we terminate or suspend if the customer does not pay, abuses support, or creates risk?
Exceptions	Which non-standard terms are we accepting consciously?

The meeting should produce a decision: sign as-is, redline, escalate to counsel, change commercial terms, or walk away. A contract review that produces only anxiety is incomplete.

Accepted Risk Memo

Sometimes a startup accepts a risk because the customer is strategic, the cash matters, or the clause is not worth killing the deal. That can be reasonable. What is dangerous is accepting risk without memory.

Use a short accepted risk memo:

Deal:
Customer/vendor:
Risk accepted:
Why we accepted it:
Who approved:
Operational owner:
Mitigation:
Review date:

Examples:

Longer payment terms accepted because the customer is a strong reference, with finance tracking cash impact.
Custom support response accepted for a pilot, with a defined end date.
Narrow exclusivity accepted for one segment, with minimum performance commitments.
Security roadmap commitment accepted, with engineering owner and deadline.

This memo helps the company avoid two bad habits: founders forgetting what they promised, and teams discovering risky promises only after signature.

Clause Risk Map

Use this map to decide when to slow down.

Clause area	Low risk	High risk
Scope	Clear product access or specific deliverable.	Vague “all services required” language.
Payment	Due date tied to invoice or milestone.	Payment only after broad acceptance, customer discretion, or long approval cycle.
Liability	Capped and proportionate.	Unlimited, uncapped, or tied to broad indirect losses.
IP	Startup keeps platform, tools, pre-existing IP.	Customer owns all improvements, code, methods, or future learnings.
Data	Matches actual product and security practices.	Requires controls, storage, audits, or breach timelines the team cannot meet.
Exclusivity	Narrow, paid, time-bound, with performance commitments.	Broad, unpaid, long-term, blocking other customers.
Termination	Notice, cure period, payment for work done.	Customer can terminate freely after heavy customization without paying.
Jurisdiction	Understandable and commercially practical.	Forum or law that makes enforcement unrealistic.

If a clause is high-risk and material, do not rely on instinct. Get legal review and decide consciously.

Enterprise Onboarding Pack

For B2B India and global enterprise sales, prepare a standard pack:

Incorporation documents.
PAN, GST, bank details, cancelled cheque or bank proof where needed.
Product/security overview.
Privacy policy and data processing terms where applicable.
Standard MSA/SaaS agreement and order form.
Support/SLA document.
Insurance details if applicable.
Customer references or case studies.
Authorized signatory details.
Invoice format and payment instructions.

This reduces delay after the buyer says yes. Many deals stall not because the customer changed their mind, but because the startup is slow with paperwork.

After Signature: Obligation Tracker

Every signed contract should produce an obligation tracker:

Obligation	Owner	Due date or trigger	Evidence
Invoice customer	Finance/ops	On signature / milestone / monthly	Invoice copy and receipt.
Provide access	Product/support	Start date	Account created.
Security commitment	Engineering/security	Ongoing	Control or policy link.
Support response	Support/founder	SLA trigger	Ticket logs.
Renewal notice	Sales/ops	X days before renewal	Calendar reminder.
Data deletion/export	Product/engineering	Termination or customer request	Completion log.

The contract is not done when signed. It is done when the company can perform it.

India angle

Indian enterprise deals often include purchase orders, vendor onboarding, GST details, payment approval workflows, information security questionnaires, procurement negotiations, and long payment cycles. The salesperson may say “approved,” but finance may not pay until PO, invoice format, GST, bank details, and vendor registration are correct.

For Indian customers, clarify whether the quoted price is inclusive or exclusive of GST, whether TDS applies, who issues the PO, what invoice details are required, and when the payment clock starts. For global customers, clarify currency, withholding tax, tax residency documents, data processing terms, and governing law.

Founder scripts for hard moments

When a customer asks for unlimited liability:

“We are a startup and cannot take unlimited exposure. We can stand behind our product with a liability cap tied to fees paid, and we can discuss specific carve-outs that are proportionate to the risk.”

When a customer asks to own everything you build:

“We can assign customer-specific deliverables if that is part of the deal, but our platform, tools, libraries, templates, methods, and pre-existing IP must remain ours.”

When payment terms are too long:

“We can support your procurement process, but as an early company we need payment terms that match delivery. Can we structure an upfront payment, milestone billing, or a shorter cycle?”

When security terms overstate your maturity:

“We do not want to misrepresent our posture. Here is what we have today, here is the roadmap, and here are the controls we can commit to contractually.”

Payment Terms And Collections Design

For an early company, payment language is not a legal detail. It is runway design.

A contract should answer these questions clearly:

Question	Why it matters
When can you invoice?	Signature, start date, milestone, delivery, acceptance, monthly cycle, or usage trigger.
When is payment due?	Net 7, 15, 30, 45, 60, or custom terms change cash planning.
Who must approve the invoice?	Procurement, finance, department head, business owner, or purchase order team.
Is a purchase order required?	Some customers will not pay without a PO even if the contract is signed.
Is GST included or extra?	Ambiguity creates disputes and short payments.
Is TDS or withholding applicable?	You need to understand cash received versus invoice value.
What happens if payment is late?	Suspension, interest, reminders, escalation, or renewal hold.
What happens if the customer disputes the invoice?	The dispute process should not allow the full amount to be held hostage for a small issue.

If you sell to Indian enterprises, design a collections workflow before signing: legal entity name, GST details, PO process, vendor registration, invoice format, payment contact, finance contact, escalation path, and expected payment date. The founder should know this before celebrating the deal.

Data Processing And Security Terms

SaaS, AI, fintech, healthtech, edtech, HRtech, and marketplace startups should not treat data terms as boilerplate.

Before accepting a customer’s data processing addendum or security schedule, map:

What data you collect.
Whether it includes personal data, sensitive business data, financial data, health data, children’s data, employee data, or regulated information.
Where the data is stored and processed.
Which vendors or subprocessors touch it.
Whether support, analytics, AI tools, or logs expose it.
How access is controlled.
How deletion, export, correction, and incident reporting work.
What you can truthfully promise about uptime, encryption, backups, and audits.

Do not agree to security language you cannot operate. A false promise is worse than an honest limitation. If a customer asks for enterprise-grade controls, show current controls, planned improvements, and specific exceptions instead of signing a wish list.

Change Requests And Custom Work

Many startup contracts quietly turn product companies into agencies.

Protect the product with clear change-request rules:

The base product and standard support are included.
Custom integrations, reports, migrations, training, workflows, data cleanup, or consulting require a written scope.
Customer-specific deliverables should not accidentally transfer your platform, tools, libraries, templates, or methods.
Timelines depend on customer dependencies such as data, API access, approvals, and testing.
Custom work should have acceptance criteria and payment milestones.
Ongoing maintenance for custom work should be priced or excluded.

The founder question is: will this contract create reusable learning, reusable product, or one-off service debt? Sometimes custom work is worth doing to win a strategic customer. But the decision should be conscious.

Renewal, Expansion, And Exit Terms

Good contracts make future revenue easier. Weak contracts make every renewal a new negotiation.

Check these terms:

Term	Founder lens
Renewal	Auto-renewal, notice period, renewal quote, price increase, and cancellation process should be clear.
Expansion	New users, new locations, additional usage, new modules, and professional services should have pricing logic.
Suspension	If the customer does not pay or misuses the product, you need a practical remedy.
Termination	Convenience termination, cause termination, cure period, data export, deletion, and final payment should be clear.
Survival	Confidentiality, payment, IP, liability, data, and dispute clauses may need to survive termination.
Transition	Enterprise customers may need export or transition support. Decide whether it is included or paid.

Contracts are not only about closing the first sale. They should protect the second year of revenue.

Contract Red Flag Triage

Founders do not need to redline like lawyers, but they do need a red-flag triage habit. When a contract arrives, mark each issue as stop, escalate, negotiate, or accept.

Red flag	Why it matters	Founder action
Unlimited liability	A small deal can create company-ending exposure.	Stop and get legal review. Push for a rational cap.
Broad indemnity	You may be accepting risk for customer misuse, third-party systems, or events outside your control.	Escalate and narrow the clause.
Transfer of core IP	The customer may accidentally own your platform, tools, improvements, or reusable methods.	Stop unless it is clearly limited to customer-specific deliverables.
Exclusivity	You may block future customers, segments, geographies, or investors.	Accept only if narrow, paid, time-bound, and tied to performance commitments.
Payment above 60 days	Revenue can become a cash-flow trap.	Negotiate milestone billing, advance, shorter cycle, or clear PO process.
Acceptance controlled only by customer	Delivery may happen, but payment can still be delayed.	Define objective acceptance criteria and deemed acceptance after a period.
Security promises beyond current capability	A signed promise can become breach risk.	Map current controls, exceptions, and roadmap before signing.
Data deletion/export obligations unclear	Product and support teams may be unable to perform what legal promised.	Confirm operational process and owner.
Non-standard governing law or forum	Enforcing rights may be expensive or unrealistic.	Escalate for legal and commercial review.
One-sided termination	Customer can exit after you invest heavily, or vendor can leave during critical work.	Add notice, cure, payment for work done, and transition terms.

Use this simple rule: if the contract can affect survival, ownership, cash, customer trust, data, or future fundraising, do not treat it as admin work. Slow down, mark the risk, and decide consciously.

Contract Playbook By Deal Type

Not every contract needs the same level of review. Build a deal-type playbook so the founder knows when to move fast and when to slow down.

Deal type	Main risk	Founder checklist
Small pilot	Unclear success, free work, no conversion path.	Define scope, timeline, price/free rationale, success criteria, next commercial step.
Enterprise SaaS deal	Liability, security, payment delay, procurement drag, support expectations.	Review liability, DPA/security, SLA/support, payment terms, renewal, implementation obligations.
Services or implementation	Scope creep, IP ownership, unpaid custom work.	Define deliverables, change request process, acceptance, payment milestones, ownership.
Partnership	Misaligned incentives, exclusivity, channel conflict, data sharing.	Define responsibilities, economics, exclusivity, termination, customer ownership, confidentiality.
Vendor or agency	Agency owns work, poor handover, data/security issues.	Include IP assignment, access handover, confidentiality, data handling, milestones, termination.
Strategic/customer-funded build	Customer controls roadmap, future product restrictions.	Define what is custom, what becomes product, rights, pricing, support, future use.

Before signing, write a one-paragraph contract decision:

This contract is worth signing because [business reason]. The main risk is [risk]. We accept or mitigate it by [mitigation]. The owner for obligations after signature is [owner]. We will review it on [date/event].

This forces the founder to separate commercial excitement from operating responsibility. A signed contract is not the end of sales. It creates promises the company must now keep.

The more important the deal, the more you should involve counsel before signature. The goal is not to negotiate every clause into perfection. The goal is to understand which risks are normal, which are negotiable, and which could damage the company later.

Contract Deal Desk

Even a small startup needs a lightweight deal desk once contracts start affecting cash, support, data, security, or product roadmap. This does not need a legal department. It needs a repeatable founder review before important agreements are signed.

Create a deal desk rule for any contract that matches one of these triggers:

Trigger	Why founder review is needed
Deal value is material to runway.	Bad payment terms, cancellation rights, or non-payment can change cash planning.
Customer asks for custom work.	The product roadmap may turn into services debt.
Contract includes sensitive data, DPA, security schedule, or audit rights.	Product and engineering must be able to deliver what legal promises.
Liability, indemnity, exclusivity, or IP terms are non-standard.	One clause can create company-level risk.
Payment depends on PO, acceptance, milestone, or customer discretion.	Revenue may not become cash when expected.
The customer is strategic or public.	Reference value can justify exceptions, but only consciously.
Vendor touches code, data, brand, customers, or infrastructure.	Poor vendor terms can damage ownership and security.

Run a 20-minute review:

What is the commercial upside?
What must we deliver?
What can delay payment?
What risk are we accepting?
What product, support, security, finance, or legal work does this create?
Who owns the obligation after signature?
What would make us walk away?

Record the output:

Field	Example
Contract	Customer/vendor/partner and document type.
Decision	Sign, redline, escalate, change commercial terms, or reject.
Accepted exceptions	Payment term, support term, data term, liability cap, custom scope.
Owner	Person responsible for delivery, invoicing, renewal, and risk follow-up.
Evidence	Signed contract, redline, approval note, risk memo, obligation tracker.
Review date	Renewal, milestone, payment date, pilot end, or customer success review.

The deal desk protects the company from a common founder failure: celebrating signature while the team quietly inherits impossible obligations.

Clause Risk Triage

Founders do not need to become lawyers, but they should know which clauses deserve attention. Use this triage before signing anything material.

Clause area	Founder question	Escalate when
Scope	What exactly are we promising to deliver?	Scope is vague, custom, or controlled by the customer after signature.
Payment	When does money become due and collectible?	Payment depends on acceptance, PO delays, long cycles, or subjective milestones.
Term and termination	How can either side exit?	Customer can terminate easily but you carry heavy setup cost.
Liability	What is the maximum downside?	Liability is uncapped or not tied to fees/realistic exposure.
Indemnity	What third-party claims are we accepting?	Broad IP, data, security, or compliance indemnities appear.
IP ownership	Who owns product, custom work, improvements, data, templates, methods?	Customer or vendor terms may capture your core product or reusable work.
Confidentiality/data	What data or confidential information do we touch?	Sensitive data, cross-border data, audit rights, breach notices, or DPA terms appear.
Exclusivity/non-compete	Are we restricted from selling elsewhere?	A small deal limits future market, customer segment, geography, or roadmap.
SLA/support	What response, uptime, service, or penalty do we promise?	Commitments exceed current team capacity.
Governing law/dispute	Where and how are disputes resolved?	Enforcement would be impractical or expensive.

Use three labels:

Green: standard enough to sign after business review.
Yellow: acceptable only with owner, mitigation, or advisor note.
Red: do not sign without counsel and founder decision.

Most contract mistakes are not because founders miss a clever legal nuance. They happen because founders sign business obligations the company cannot actually deliver.

Commercial Terms Sheet Before Legal Review

Before a lawyer reviews a contract, the founder should write the deal in business language. This prevents a common failure: sales agrees one thing, finance expects another, product hears something else, and legal redlines a document without knowing the real commercial intent.

Use a one-page commercial terms sheet for any meaningful customer, vendor, agency, partnership, or strategic build agreement.

Field	What to write
Counterparty	Legal name, business name, GST details if relevant, billing address, decision owner, finance contact.
Deal type	SaaS subscription, pilot, services, implementation, reseller, referral, agency, vendor, data access, strategic build.
Business reason	Why this deal matters: cash, learning, reference, distribution, product input, strategic account, cost saving.
Scope	Product access, deliverables, services, usage, users, locations, integrations, support, training, exclusions.
Success criteria	What must happen for the customer, partner, or vendor relationship to be considered successful.
Price and taxes	Amount, currency, GST/tax treatment, discounts, setup fee, usage fee, renewal price, payment method.
Invoice trigger	Signature, PO, kickoff, milestone, delivery, acceptance, monthly date, usage threshold, renewal.
Payment path	Who issues PO, who approves invoice, payment cycle, TDS/withholding, bank details, finance escalation.
Term and renewal	Start date, end date, auto-renewal, renewal notice, price increase, cancellation window.
Custom work	What is custom, what is standard, what requires change request, who owns custom deliverables.
IP and data	Who owns product, deliverables, data, generated output, templates, methods, and pre-existing work.
Operational promises	SLA, support hours, uptime, onboarding, reporting, security, privacy, audit, deletion, export.
Risk exceptions	Liability, indemnity, exclusivity, unusual jurisdiction, data promises, payment delay, termination rights.
Internal owners	Sales, founder, finance, product, engineering, customer success, legal/advisor owner after signature.
Walk-away line	Terms that would make the deal not worth signing.

The terms sheet should be created before redlines begin. If the team cannot fill it, the deal is not ready for legal review because the business reality is still unclear.

Founder use cases

Use the terms sheet differently depending on the contract:

Contract	Main purpose of the terms sheet
Customer pilot	Prevent free consulting, vague success, and no conversion path.
Enterprise SaaS	Align procurement, payment, DPA, SLA, onboarding, renewal, and support expectations.
Agency or freelancer	Protect IP ownership, scope, milestone payment, handover, and account access.
Partnership	Confirm who brings leads, who closes, who supports, who owns the customer, and how revenue is shared.
Strategic build	Separate customer-funded custom work from reusable product rights.
Vendor	Confirm data access, service levels, termination, migration, and business continuity.

India operating note

For Indian B2B deals, the terms sheet should explicitly separate five events:

Verbal yes.
Contract signature.
Purchase order or vendor onboarding.
Invoice acceptance.
Cash received.

Many founders celebrate at step one or two, but runway improves only at step five. A contract that does not explain the path from signature to cash is not commercially complete.

Common mistakes

Unlimited liability

Unlimited liability can kill a small company. Push for a cap tied to fees paid or another rational amount. Some exceptions may be negotiated, but do not accept broad unlimited exposure casually.

Bad payment terms

Revenue is not cash until collected. If the contract lets the customer delay payment through acceptance, PO, invoice objections, or long cycles, model the cash impact.

No termination rights

You need a way out when a customer abuses support, a vendor underperforms, a partner does nothing, or a relationship becomes risky.

No IP clarity

Always separate customer-specific deliverables from your underlying product, tools, libraries, templates, methods, and prior IP.

No confidentiality or data process

Confidentiality is not only a clause. It requires access control, employee awareness, vendor discipline, and incident response.

No dispute process

Founders often ignore governing law and dispute clauses. You may never litigate, but a bad dispute forum can make enforcement unrealistic.

Contract Signature Control Gate

Before any important contract is signed, pause for a control gate. This applies to customer contracts, vendor agreements, partnership deals, agency contracts, investor side letters, and anything involving data, money, IP, exclusivity, liability, or long-term commitment.

Use this gate:

Question	Answer
Who owns this contract inside the company?
What business outcome does it create?
What are we promising to deliver?
What payment, refund, renewal, or termination terms matter?
What data, security, confidentiality, or IP obligations exist?
What liability, indemnity, penalty, or warranty risk exists?
What operational team must know after signature?
Which advisor should review before signing?

Signing is not the end of the contract. It is the start of obligations.

Contract Obligation Calendar

Many contract problems happen after signature because nobody tracks obligations.

Create a calendar:

Obligation	Owner	Date or cadence	Evidence
Invoice date
Payment follow-up
Implementation milestone
Security or compliance deliverable
Renewal notice
Price increase window
Termination notice period
Data deletion or return

This matters especially for Indian B2B sales where purchase orders, GST invoices, payment terms, security documents, and procurement steps may be separated across teams.

Negotiation Walk-Away Rules

Founders need walk-away rules before negotiation pressure begins.

Examples:

Term	Walk-away or escalation trigger
Payment terms	Payment period breaks runway or collections discipline.
Liability	Exposure is not proportional to deal value.
Exclusivity	Blocks the company from serving the market.
IP ownership	Customer or vendor claims ownership of core product.
Custom work	Scope turns product company into agency.
Security promises	Company cannot truthfully operate the promised control.
Termination	Customer can exit easily but company carries heavy setup cost.

A bad contract can make revenue look bigger while making the company weaker.

Non-Standard Clause Register

As the company grows, exceptions accumulate. One customer gets different payment terms. Another gets special support. A vendor keeps broad IP rights. A partner has exclusivity language. If nobody tracks these exceptions, the company slowly loses control.

Create a non-standard clause register:

Contract	Non-standard term	Business reason	Risk	Owner	Review date
	Payment term		Cash impact
	Liability cap		Exposure
	Exclusivity		Market restriction
	Custom deliverable		Roadmap/support burden
	Data/security promise		Operational requirement
	Renewal/termination		Revenue or exit risk

Review the register before:

Fundraising.
Enterprise sales push.
Acquisition conversation.
Renewal season.
New pricing rollout.
Major product or support change.

The register prevents “we forgot we promised that” from becoming a customer, finance, or diligence problem.

Liability Cap Negotiation Ladder

Liability clauses can quietly make a small deal dangerous. Founders should not accept unlimited exposure casually, especially for early enterprise, agency, data, fintech, health, AI, or infrastructure deals.

Use a negotiation ladder:

Level	Position	When it may fit
Preferred	Liability capped at fees paid or payable under the order	Most standard SaaS or services contracts.
Stronger customer ask	Cap at 6-12 months of fees or a fixed amount	Larger customers with real operational risk.
Separate cap	Higher cap only for specific direct damages, confidentiality, or data obligations	When risk is real and priced.
Insurance-backed	Cap tied to cyber/E&O/professional insurance coverage	When enterprise customer requires comfort and company has coverage.
Founder escalation	Unlimited liability, broad indemnity, consequential damages, penalty, or uncapped data/security exposure	Do not accept without legal and business approval.

Liability sanity check

Before agreeing, ask:

Can this contract create liability greater than the revenue, cash balance, insurance coverage, or realistic company capacity?

If yes, the founder should slow down. A customer logo is not worth signing a clause that can threaten the company. If the customer needs higher protection, price the risk, limit the scope, improve insurance, or walk away.

Contract Handoff After Signature

Contracts fail when only the founder and lawyer know what was signed. After signature, run a handoff.

Team	What they need
Finance	Invoice date, payment terms, taxes, PO process, collections contact.
Product/engineering	Implementation, SLA, security, integration, data, or roadmap commitments.
Customer success/support	Support scope, escalation path, renewal date, success criteria.
Sales	Expansion path, discount limits, renewal and upsell notes.
Operations/legal	Contract owner, obligation calendar, non-standard clauses, termination window.

Use a short handoff note:

Customer/vendor:
Signed date:
Owner:
Commercial terms:
Non-standard clauses:
Operational promises:
Dates to track:
Risks:
Teams informed:

Signing a contract should create operational clarity, not hidden obligations.

Renewal And Termination Control

Contracts do not end after signature. Many expensive surprises come from missed renewal windows, auto-renewing tools, unpaid customer usage, stale SLAs, forgotten exclusivity, or vendor lock-in.

Create a renewal and termination tracker:

Contract	Commercial decision	Risk if missed
Customer	Renew, expand, renegotiate, or exit	Revenue loss, weak terms, unpaid service
Vendor	Renew, reduce, replace, or cancel	Auto-renewal, lock-in, data migration
Partner	Continue, amend, or end	Exclusivity, channel conflict, brand risk
Contractor/agency	Extend, close, or handover	IP, access, unfinished deliverables

Review 60-90 days before important dates:

Is the contract still useful?
Are payment, support, security, data, IP, or liability terms still acceptable?
Has usage changed since signature?
Do we need a price change, scope change, or exit plan?
What customer/vendor communication is needed before the deadline?
Is all data, IP, source code, documentation, or access recoverable if the relationship ends?

Renewal discipline protects cash, roadmap, support load, and leverage. A startup should not discover contract terms only when cancellation is impossible.

Reader action

Create a contract checklist and use it for every new customer, vendor, agency, contractor, and partner. Add a “red flag” rule: any unlimited liability, IP transfer, exclusivity, unusual data obligation, payment term above 60 days, or non-standard jurisdiction gets legal review.