// Posted 2026-07-30

Your Legal Queue Has 34 MSAs Stuck in Redline for 22 Days

Your GC opens the contract queue Monday, 34 MSAs open, oldest sat 22 days, one $410K deal slipping the quarter. Legal ops is a function you never staffed.

Grid of translucent indigo contract tiles arranged along a stretching amber redline timeline, one large pink tile pulsing at the day-22 marker, blue signature beams routing toward a central legal engine but stalling midway, dark near-black backdrop

It is Monday, 9:22 AM. Your GC opens the contract queue in Ironclad. 34 MSAs open. She sorts by days-since-received. The top row is a $410K deal that landed the buyer's redline June 25th, sat six days before the AE forwarded it, went to outside counsel July 8th, came back July 14th with three open comments on indemnity, IP assignment, and data residency. The counter-redline draft has been open in her Word doc since July 18th.

She scrolls. A $180K deal on day 17 sits on a data processing agreement the buyer's privacy lead flagged for two GDPR clauses nobody in legal has touched. A $95K deal on day 14 needs a mutual NDA amendment the AE promised the buyer would land inside 48 hours. Nine of the 34 open contracts carry a redline the buyer sent more than fourteen days ago and heard nothing back.

Pull the last four quarters. 214 MSAs closed, average time-in-legal 22 days against a target of 7, 34 percent of Q2 deals slipped a quarter on the legal cycle, $1.6M in ARR pushed from June commit to September because a redline sat in a Word doc. The board deck shows deal velocity. The board deck does not show that 41 percent of Q2 pipeline movement was legal cycle drag, not sales cycle drag.

Legal review is a function. Most Series B and C teams have not staffed it because the first fifty MSAs were reviewed by the founder on a paper printout. The count grew to 214 a year across three product tiers, an Ironclad instance the previous GC half-configured in 2024, a Docusign envelope tracker two ops people manage, an outside counsel retainer that bills $340 an hour for redlines a template could handle, a clause library the associate updated in April, and a "Contracts" folder in Drive with 940 executed PDFs nobody indexed. The function lives in the gap between the GC who owns the risk position, the associate who drafts redlines, the outside counsel who handles anything past a standard fallback, the RevOps lead who reports cycle time, and the AE who signed the term sheet. On the org chart it sits under Legal. In practice it sits inside a Word doc the associate rebuilds every second Friday.

The 22-day legal cycle math

Pull every deal that touched legal in the last twelve months. Log signature date, redline received date, first internal response date, counter-redline sent date, executed date. Count deals sitting past day 7 with no counter drafted. Count deals sitting on outside counsel past day 10. Count deals blocked on the same three clauses (indemnity cap, IP assignment, data residency) more than twice. Most teams past Series B find 45 to 60 percent of MSAs miss the day-7 counter milestone, average time-in-legal lands between 18 and 28 days, and one in three quarter-end deals slips a quarter on redline drag.

Walk one deal. The $410K MSA received June 25th, forwarded by the AE July 1st, opened by legal July 2nd, sent to outside counsel July 8th on a bespoke indemnity clause the standard fallback did not cover. Outside counsel returned July 14th, the associate flagged three open comments to the GC July 16th, the GC opened the doc July 18th between two board prep sessions and has not returned to it since. The buyer's procurement lead sent a follow-up July 22nd asking for a status update, and the AE has forwarded that email to legal three times without a reply.

The team that should own this knows it is broken. The GC runs a Friday deal review that sorts by ARR and hides cycle time behind the deal-stage bucket. The associate carries 14 to 22 active redlines and drafts counters on the top three. The outside counsel retainer bills for standard fallback edits a template would handle in an hour. The RevOps lead reports a cycle-time metric she pulls from Ironclad on the third Wednesday of the month.

Hiring a contracts manager is the slow answer

The textbook fix is a senior contracts manager or a director of legal operations. Loaded comp in the US runs $130K to $180K a year. Months one through three go to auditing the clause library, rebuilding the intake form, and standing up a weekly cycle-time report tied to deal stage. Months four through nine are when average time-in-legal drops from 22 days to 9, day-7 counter rate lifts from 40 to 78 percent, and quarter-end slippage on legal cycle falls from 34 percent to under 12.

The fractional version is faster and stops at the same wall. Six to nine thousand a month buys ten to fifteen hours a week of senior contracts work. The first month rebuilds the clause library and the intake triage. The 214-MSA annual volume keeps drifting because a fractional lead cannot triage every redline the hour it lands, draft every counter against a fallback library, catch every buyer clause that maps to a standard exception, escalate every past-day-10 deal to the GC, and reconcile Ironclad against the CRM every morning.

Both versions assume the work is a person reviewing a queue on a cadence. The work itself is triaging every incoming redline the hour it lands, drafting every counter against a live clause library, flagging every bespoke clause that needs outside counsel from every clause that matches a standard fallback, escalating every past-day-10 deal to the GC with a proposed counter, catching every AE who forwarded a redline late, running a live cycle-time report that reconciles Ironclad against the CRM against Docusign, and posting a legal health digest the GC reads before the Friday deal review. On 34 active redlines with 940 executed contracts feeding the fallback library that is 38 to 50 hours a week of senior legal work. No single hire clears that pile and holds the cycle-time number at the same time.

What a fractional AI legal ops function does

Hand the clause library, the Ironclad instance, the CRM, the Docusign envelope feed, the outside counsel retainer log, the last four quarters of redlines, and the executed contract archive to a fractional AI agent. The agent does the work a contracts manager, a legal ops lead, and a paralegal would do together. The cadence is per-hour on redline triage, per-day on counter drafting, per-week on the outside counsel spend review, and per-Friday on the cycle-time digest.

Every incoming redline triaged the hour it lands. The $410K buyer redline lands at 9:14 AM. By 9:47 the agent has extracted every marked change, matched twelve of fifteen edits to a standard fallback, flagged three (bespoke indemnity, non-standard IP assignment, EU data residency) as needing GC review, and drafted a counter Word doc for the associate to open.

Every fallback edit drafted against the clause library. The buyer struck a mutual liability cap and inserted a one-way cap at 2x fees. The agent notes the standard fallback the last 34 executed MSAs accepted (mutual cap at 2x with a data-breach carveout), drafts the counter language, cites the three precedent contracts, and routes to the associate for a one-look approval.

Every bespoke clause routed to outside counsel with a scoped brief. The bespoke indemnity clause goes to outside counsel with a three-paragraph brief that names the deal size, the buyer's regulatory posture, the two prior deals with a similar structure, and the specific question the GC needs answered. Retainer spend drops because the brief cuts the counsel's discovery time.

Every past-day-10 deal paged with a draft counter attached. The $180K DPA on day 17 lands in the GC's Slack Friday morning with a draft counter, the two GDPR clauses cited, the standard fallback proposed, and a one-line escalation the AE can send the buyer's privacy lead.

Every cycle-time report reconciled against three sources. The Friday cycle-time report shows time-in-legal against the CRM deal stage, the Ironclad envelope timeline, and the Docusign signature feed. Six deals move from green to yellow because the counter went out but the buyer sat on it. The GC reads a cycle time tied to a live signal instead of an Ironclad export.

Live legal-ops lattice with indigo contract tiles ranked by cycle-time bucket, amber clause-risk gauges pulsing on bespoke edits, pink escalation beams routed to GC and outside-counsel nodes, blue fallback-library feeds arriving at a central redline engine

The unit economics of a 22-day legal cycle

A Series B company at $22M ARR closing 214 MSAs a year on a 22-day legal cycle is burning three specific things. The GC, the associate, two AEs, and the RevOps lead spend a combined 12 to 18 hours a week on redline triage, counter drafting, and cycle-time cleanup against a fully loaded hour of $210 to $340. That is $10K to $22K a month of senior time on work a live agent clears. The associate gets six to nine hours a week back inside the first sprint.

The pipeline line is the second one. Moving average time-in-legal from 22 days to 9 pulls forward 18 to 26 percent of quarter-end deals that currently slip on legal drag. On $8M of quarter-end pipeline that is $1.4M to $2.1M of ARR landing in the quarter the sales team committed instead of the one after. The sales forecast starts hitting inside a 10 percent variance because legal stops being the silent slip driver.

The outside counsel line is the third. Retainer spend on standard fallback edits runs $8K to $18K a month at $340 an hour. Routing only bespoke clauses to counsel with a scoped brief cuts that spend by 50 to 70 percent. That is $50K to $130K a year the finance line stops carrying, on top of the ARR the deal cycle picks up.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one Ironclad seat than a contracts hire. Redline triage and clause library run in week one. Counter drafting and outside counsel routing run in week two. The cycle-time report runs off a live feed before the sprint closes.

What changes after the sprint

Picture the same Monday, 9:22 AM moment, thirty days after the sprint ships. Your GC opens the contract queue. 22 MSAs open. The $410K deal shows a counter shipped July 26th, the buyer's procurement lead replied July 28th accepting two of three edits, outside counsel signed off on the indemnity carveout Friday, and the executed contract is queued for Monday signature.

By Friday the GC reads a legal health digest that names the four deals crossing signature this week, the two deals that hit outside counsel with a scoped brief, and a cycle-time number tracking to 9 days against a prior baseline of 22. The associate runs point on the three bespoke redlines because the agent cleared the standard fallback triage. The AEs get answers inside 48 hours instead of chasing legal on Slack for a week.

If your legal queue currently reads 22-day cycle time with a third of quarter-end deals slipping on redline drag, the version where every incoming redline triages the hour it lands and every past-day-10 deal pages the GC with a draft counter attached is fourteen days away. Legal review is a function. You can hire against it, you can retain a fractional contracts lead for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.

// Related notes