Decide which few terms really matter before the first redline, hold firm on those, and be flexible on everything else. For most startups selling to larger customers, the terms worth fighting for are the liability cap, IP ownership, termination, payment terms and exclusivity. Startups lose deals by over-lawyering small points, and they put the company at risk by giving in on the big ones.
Key takeaways
- Pick no more than five must-have terms for each type of deal, and agree on them with your team and counsel up front.
- Respond to a customer’s redlines quickly, in one marked-up draft, with business reasons for each pushback.
- A one-page contract playbook lets your team handle routine terms and send the risky ones to counsel.
- Don’t sign an uncapped indemnity just to land a big logo.
- AI tools help you prepare for a negotiation. They don’t know what is market for a startup.
Which contract terms are worth fighting for?
Every deal is different, but for a startup selling software or services to a larger company, these five come up again and again.
| Term | What to ask for | Reasonable fallback |
| Limitation of liability | A mutual cap equal to the fees paid in the prior 12 months | A higher cap (a “super-cap”) for confidentiality, data breach and IP indemnity, instead of unlimited liability |
| IP ownership | The customer owns its data. You keep your platform, know-how and improvements | The customer owns deliverables built only for it, and you get a license to reuse general know-how |
| Termination | No termination for convenience during the committed term | Termination for convenience on 90 days’ notice, with fees paid through the notice period |
| Payment terms | Net 30, interest on late payments, no right to withhold unrelated amounts | Net 45 or net 60 for a large enterprise customer |
| Exclusivity and non-solicitation | Delete them | A narrow, short non-solicit of each other’s employees |
The liability cap and IP ownership are the two where a bad term can sink the company. An uncapped indemnity can exceed the value of the whole business. Giving a customer ownership of your core platform, even by accident through a broad “work product” clause, can make it impossible to sell to anyone else.
How do I decide what to concede?
Not every point is a deal-breaker. Notice periods, reporting requirements, insurance certificates, audit rights within reason, and the customer’s preferred form of the boilerplate are usually worth conceding. Giving ground on terms that don’t matter builds goodwill, keeps the deal moving, and makes the other side more willing to move on the terms that do.
Flexibility doesn’t mean signing anything. The opposite mistake is just as common: a founder who wants a big logo signs an uncapped indemnity or gives away IP to close the deal. If a customer won’t move on one of your must-have terms, it’s worth asking whether the deal is worth the risk.
How do I respond to a customer’s redlines?
Acknowledge the redline within a day, even if you need longer to review it. Then sort each change into one of four groups: accept, accept with a tweak, push back with a reason, or walk away. Send back a single marked-up draft with short comments, rather than a long email thread.
Explain your pushback in business terms, not legal ones. “We can’t get insurance for uncapped liability, and our cap is 12 months of fees for every customer” persuades a procurement team far more than a citation to case law. Large customers negotiate hundreds of these contracts a year. Clear, consistent positions get approved faster.
What does this look like in a real deal?
Say a startup is closing a $60,000-a-year contract with a large retailer. The retailer’s paper asks for uncapped liability, ownership of “all work product,” and termination for convenience on 30 days’ notice.
A reasonable counter is a mutual liability cap of 12 months of fees ($60,000), with a super-cap of two or three times that for data breach and confidentiality. On IP, the retailer owns its data and any custom reports built only for it, and the startup keeps the platform and everything it learns building the product. On termination, the startup offers 90 days’ notice after an initial committed term. Everything else in the retailer’s paper, such as its insurance requirements and invoicing process, the startup accepts.
Should I use a contract playbook?
Yes, once you are negotiating the same kind of contract more than a few times. A playbook is a short document, often one page, that lists your preferred position on each key term, the fallbacks you can accept, and the points that must go to a lawyer. It keeps your positions consistent across deals and lets different people on your team negotiate without reinventing the wheel each time.
A playbook also answers a common question: should non-lawyers redline customer contracts? Yes, for commercial terms and any position the playbook already approves. Indemnity, liability, IP and data clauses should go to counsel.
Should I sign a pilot or proof-of-concept agreement?
Pilots are a good way to get into a large customer, but keep them simple. A pilot agreement should cover the scope and how success will be measured, a short term (often 60 to 90 days), whether it is paid, how the customer’s data is handled and deleted at the end, and how it converts into a full contract if it works. It shouldn’t transfer any IP or grant exclusivity.
Which governing law should we use?
Pick one and keep it consistent. For a Delaware corporation, Delaware or the law of the state where you are based (often New York or California) are common choices. If a large customer insists on its home state, that is usually fine as long as the state’s law isn’t unusual for the issues in the contract. Be cautious about agreeing to disputes being heard in a foreign country without advice from local counsel.
Can I use AI to review customer contracts?
AI tools are good at summarizing a redline, spotting where a draft departs from your playbook, and helping you prepare questions. Many enterprise procurement teams already use them. They are much weaker at knowing what is market for a startup selling to a large company, or which concessions you can live with. Use AI to prepare, not to decide.
How do I avoid over-lawyering?
Over-lawyering is when counsel fights every clause, slowing the deal, running up fees and sometimes killing it over points that don’t matter. It often comes from training at large firms that represent large companies, where removing every last bit of risk makes sense. For a startup, the bigger risk is usually not closing deals. Work with counsel who understands that tradeoff, focuses on your must-have terms and moves fast on the rest.
When you are ready to move from startup-style contracts to an enterprise-ready set, you will usually want a master services agreement with order forms, a data processing agreement, a service level agreement and a one-page playbook. See What Should Startup Founders Know About Drafting Strong Contracts?, Service Level Agreement (SLA), NDA: What It Means for Startups and What Are the 10 Contracts Every Startup Should Have on Hand? For help with a specific deal, see our contract review service, or contact us.
