In this guide:
What legal review is actually testing for · The mistake that stalls every deal · The redline-readiness playbook · What legal delays really cost you in time · Your first move this week
Your champion says yes on the demo call, forwards the contract to legal, and then goes quiet for three weeks. You didn't lose that deal to a competitor, and you didn't lose it on price. You lost it to a redline sitting unanswered in someone's inbox. Nobody drills founders on this part of enterprise sales before the first big contract lands, and it quietly eats more pipeline than any objection you'll ever hear on a call.
What legal review is actually testing for
Negotiation and legal review now eat 35 to 40 percent of total enterprise sales cycle time, and that's not because your buyer's legal team works slowly. It's because most SaaS vendors arrive at this stage with nothing prepared: no standard DPA, no fallback position on liability caps, no answer ready for the indemnification clause that shows up in almost every enterprise contract.
Each redline round costs roughly 3 to 10 business days depending on complexity. Legal review isn't testing whether your contract is perfect. It's testing whether you're the kind of vendor who has already thought through the clauses that always come up, or the kind who's inventing a position for the first time under deadline pressure.
The mistake that stalls every deal
Founders treat legal review as something that happens to them after the real selling is finished. It isn't. It's the last mile of the sale, and it's the mile where your champion has the least internal leverage, because procurement and legal report to someone else entirely.
If you show up unprepared at this stage, you're sending your champion to fight a battle on your behalf with no ammunition, on a clause you haven't thought about until this exact moment. They stop pushing. The deal goes quiet. You call it "stuck in legal," but it's really stuck on you.
The redline-readiness playbook
Five moves, done before you're under deadline pressure, not during it:
- Build your standard contract packet before you need it. MSA, DPA, security addendum, and standard SLA, written as templates with your accepted fallback positions already decided. The first deal takes real work to build this. Every deal after that starts from a document, not a blank page.
- Know your five recurring redlines before they show up. Liability caps, indemnification, data retention and deletion timelines, auto-renewal terms, and termination for convenience generate the large majority of enterprise redlines. Decide your walk-away line on each one before a buyer's legal team asks, not while they're waiting on your reply.
- Stay the single point of contact through legal, don't hand it off. Outside counsel can draft the language, but you stay visible. A founder who vanishes the moment legal gets involved reads as exactly the kind of vendor procurement is trained to flag.
- Set an internal 24 to 48 hour redline SLA. Commit to turning around any redline within two business days. Response speed, not perfect language, is what shortens negotiation-to-close time the most.
- Write your champion a one-page internal memo. A plain-language summary of what changed in a redline and why it's fine, something they can forward internally without translating legalese themselves. This is usually the single highest-leverage document in the whole process, and almost nobody writes it.
What legal delays really cost you in time
At $100K-plus ACV, enterprise SaaS deals now run roughly 170 days start to close, with procurement and legal combined responsible for 4 to 12 weeks of that timeline.
Standardized templates and pre-decided fallback positions cut contract cycle times by 30 to 50 percent in practice. Run the math on an unprepared deal with three redline rounds at 10 business days each: six weeks just on redlines. The same three rounds with a packet ready and a 48-hour SLA run 2 to 3 days each, under two weeks total. That's a month of cycle time back on a single contract, and it compounds across every enterprise deal you sign that year.
Your first move this week
If a deal is sitting in legal right now, don't wait for perfect templates to fix it. Tonight, write down your walk-away position on the five recurring clauses above, and send your champion the one-page memo. If nothing is stuck yet, spend the highest-leverage hour of your week building the standard packet before your next enterprise deal lands, so the next stall doesn't start from zero.
Every enterprise deal eventually tests the same thing in a different format: whether you're a vendor who's already thought this through, or one who's figuring it out live while your champion runs out of patience. The founders who close on time aren't the ones with the cleanest contract. They're the ones who weren't starting from a blank page when the redline landed.
This stage sits right next to two other gates in the same enterprise motion: handling a security questionnaire without SOC 2 and pricing your first enterprise SaaS deal correctly in the first place.