Who we help
AI & dataTerms with no market standard yet B2B SaaSEnterprise paper, every deal Staffing & recruitingWhere your margin is decided Founders & executivesYour first big contract Sales & revenueDeals stuck in legal
What we handle
Contract review MSAs AI addenda DPAs & security exhibits Order forms, SOWs & NDAs Your own contract templates
More
How it works Pricing About Guides FAQ
Book a call Get my redline
Review & Negotiation

Contract Negotiation: Why Your Redline Needs a Fallback Plan

By Siddhant Madan · 9 min · K2 Consulting

You send a customer thirty tracked changes. Their counsel rejects twenty-five. The sales team wants to sign on Friday. Someone asks which points you can give up. You have a redline. You don't have an answer.

That's the difference between reviewing a contract and negotiating one. The markup explains what you want. The negotiation plan says what happens when you don't get it, who can approve a concession and what the concession costs.

The short version
  • Write an opening position and a fallback for every material issue before the redline goes out.
  • Trade on scope, process, thresholds and economics. Don't concede operational promises the business cannot perform.
  • Keep a single record of concessions across the MSA, SOW, order form and exhibits. The final document has to reflect the same deal.

Most enterprise negotiations don't fail because the first redline was bad. They slow down because neither side has a way to move off its opening position without looking as though it surrendered.

How Procurement Reads Contract Redlines

Twenty-six small drafting points and four material risks can look like thirty demands. The buyer's lawyer reads the volume before the substance. Your best arguments disappear among punctuation, boilerplate and definitions that don't change anyone's exposure.

Sort each issue into three buckets before sending it: must fix, can trade, and can accept. Don't make the customer do that sorting for you. Then ask what the buyer is actually trying to protect. The answer often gives you a less expensive way to solve the same problem.

This is our standard position, and we cannot make exceptions.

Illustrative procurement response

That line is an opening, not an explanation. Ask which risk or internal approval it addresses. Maybe the buyer needs assurance that data won't be stranded. Maybe it needs an audit trail. Maybe the limitation comes from an insurance requirement. The right counter depends on the underlying concern, not the word standard.

Where it breaks

The vendor refuses an unrestricted security audit but gives no alternative. Procurement escalates to its security team, which returns with a longer questionnaire and another week of review. The actual requirement was independent evidence of controls. That could have been discussed before anyone argued about physical access to systems.

How to Set Contract Negotiation Fallback Positions

Each material point needs five entries: what the current clause does, what you want instead, what you can accept if they reject it, who can approve the trade, and what happens if it stays unchanged. One page often gets you further than another round of comment bubbles.

Liability caps: negotiate the exceptions, not just the number

The buyer opens with unlimited liability for confidentiality, data incidents, legal compliance and indemnities. You want the general cap to protect normal service failures. Your opening edit narrows the exclusions to defined categories. A possible fallback is a separate higher cap for specified security claims, if the risk and insurance justify it. The business decides the number; the redline records the scope.

Read what uncapped actually reaches in an indemnity before treating an agreed multiplier as a win.

IP ownership: separate the deliverable from the product

The customer asks to own everything developed during the engagement. You can agree that it owns customer materials and defined bespoke deliverables without assigning the tooling, methods and background software you use for other clients. If it needs to run the deliverable, offer the licence necessary for that use. Don't transfer your reusable platform because the statement of work used the word development.

Incident notice: choose a clock the team can actually meet

The buyer wants a fixed notice period from the moment an event occurs. Your security lead may not know about an event until later, and law may prescribe a particular trigger or deadline. Negotiate the event definition, awareness standard, initial notice and follow-up updates together. Never describe a proposed contractual clock as safe without checking the laws and customer obligations involved.

Termination: decide who pays when the buyer changes its mind

For an annual prepaid subscription, the customer might ask to terminate for convenience and recover unused fees. That changes the economics the sales team priced. A fallback could preserve an initial minimum term, permit termination at renewal or revise the price for a more flexible commitment. The right trade depends on margins, deployment costs and whether the buyer will actually use the flexibility.

A fallback is not a weaker redline. It's the next position you are prepared to defend.

The trade is usually somewhere other than the clause

A buyer wants broader support. You may be able to offer it in exchange for a different fee or response tier. A buyer wants an exit right. You may be able to price it into a shorter term. A buyer wants an expansive data audit. You may be able to replace unrestricted access with a specified independent report and a narrower exceptional audit right.

Those are exchanges of value, not legal gymnastics. The important part is that product, security, finance and sales know what is being promised. If the position is unlawful, technically impossible or outside the team's authority, it's not a bargaining chip.

What to counter with on a difficult call

Don't spend the call repeating the markup. State the buyer's risk, explain where its wording goes too far, and propose the narrower mechanism that solves the concern. Then ask who has authority to approve it. If the answer is nobody on the call, record the issue and the exact decision required rather than conceding to keep the conversation friendly.

The edit

An illustrative way to answer a broad audit demand is to offer evidence first, then a defined additional process if a specific material concern remains.

Provider will make available a current independent security assessment summary reasonably relevant to the Services. Any additional audit shall be limited to a specific, documented material security concern not reasonably addressed by that assessment, subject to agreed scope, timing, confidentiality and protection of other customers' information.

This is an example of a negotiation mechanism, not a substitute for mandatory regulatory rights, sector-specific obligations or a tailored security schedule.

Make the final contract match the final conversation

One concession in an SOW can undo a limitation in the MSA. A change to the security exhibit can create an obligation the DPA assumes someone else will perform. After each round, reconcile definitions, precedence rules, liability caps, cross-references and implementation commitments. Keep an issues register with the approved position and the person who approved it.

At signature, the business should know three things: what it promised, which risks remain and which positions it can use in the next deal. Without that record, every new enterprise contract starts the same negotiation from scratch.

If the starting point is the customer's contract, see commercial contract review. If you need someone to hold the positions through the call and later rounds, see contract negotiation support. For your own standard paper, begin with commercial contract drafting.

Stop reading. Send the contract.

Marked up and explained, back within 24 hours.

Get my redline →

First one free. Mutual NDA on the form. Calls whenever they help.