Contract review without a CLM — the deliberate no-platform stack

This is not a cheaper version of the enterprise CLM stack. It is the opposite decision, taken on purpose, and it has a different failure mode.

The 2026 ACC Law Department Management Benchmarking Report, published in June, describes the department this is written for. At companies under US$1 billion in revenue the median legal function is two lawyers and four total legal staff, with a median of zero legal operations professionals. Median annual legal technology spend in that band is US$65,000 — 5% of total legal spend, the highest technology share of any revenue band in the survey, because small departments buy software instead of headcount they cannot fund. The enterprise CLM stack, by comparison, runs US$370,000 to US$900,000 a year.

The budget gap is the obvious problem. The staffing line is the real one. A CLM implementation assigns configuration, playbook maintenance, and adoption enforcement to an owner, and at the median this department has nobody to be that owner. So the choice is not “CLM or no CLM.” It is: buy the three things a CLM does that can be bought separately, and be explicit about the fourth thing you are giving up.

How the pieces fit

• The intake form is a form you already own, not a product. One Microsoft Form or Google Form in the tenant you are already paying for, one destination channel, one queue. Six required fields decide everything downstream: counterparty, contract type, whose paper it is, deal value, needed-by date, and a link to the document. “Whose paper” and “deal value” are the two that route; the rest are what you will search on eighteen months from now. A free-text “describe your request” box is the failure mode — it moves the triage work from the requester to the lawyer, which is the cost this layer exists to remove. Legal intake covers the field design, and the legal request intake router covers the routing if you want it automated rather than read.

• One playbook review engine, in Word. LegalOn and Ivo are both Word add-ins that redline a counterparty draft against a playbook and propose the edit rather than flag the clause. They are substitutes, not layers — see the routing rule below. LegalOn’s entry tier, Core Review, ships 50+ attorney-authored playbooks, unlimited review and redlining, a repository with search, 100+ market-standard templates, and a free trial; the company reports 8,000 customer organizations. Ivo redlines against your playbook and against market benchmarks, and Ivo Intelligence links amendments and restatements back to their base agreement without manual tagging; it raised a $55M Series B led by Blackbird in January 2026 at a reported $530M valuation. Neither publishes a price.

• DocuSign eSignature is execution, and by default it is also your repository. eSignature Standard is $30/user/month and Business Pro is $45/user/month on annual billing — $360 and $540 per user per year, both published. The load-bearing move is not the signature: it is putting the six intake fields on the envelope as custom fields, set at template level rather than per envelope, so the completed archive is queryable by counterparty and contract type instead of by whoever remembers the filename. This is the layer people skip, and skipping it is what turns “we have all our contracts in DocuSign” into a folder nobody can search.

• Existing storage is the system of record, with one naming convention. SharePoint, Google Drive, or Notion — whichever the company already runs. The convention is the same six fields in the same order. It holds only while one named person enforces it, which is the constraint that eventually ends this stack.

Named handoffs

1. Form submitted → routed on “whose paper” + deal value. Their paper above the threshold goes to a named reviewer; your own template below it is approved without review. Reversing this is how an NDA and a $500,000 MSA get the same attention.
2. Counterparty draft attached → opened in Word → review engine runs the playbook → deviation list returned. The reviewer edits the draft, not a portal copy of it, so there is one document and no reconciliation step.
3. Deviation outside the floor → the escalation named on the intake form. The approver is chosen by the form’s routing at step one, before anyone has an opinion about the clause.
4. Agreed draft → envelope created from the template carrying the custom fields → sent. Creating the envelope from scratch loses the fields, which is the single most common way this stack degrades into an unsearchable pile.
5. Envelope completed → PDF filed under the naming convention, fields already on the envelope record. Retrieval works two ways after this: DocuSign’s field search for anything signed, the folder for anything you need to hand someone.

Why one review engine and not two

LegalOn and Ivo overlap almost completely, and a team that buys both ends up with two playbooks that disagree. Route on whether you already have a written playbook:

• LegalOn when you do not. Its 50+ pre-built playbooks are the playbook on day one, which is the difference between reviewing in week one and reviewing after an attorney has spent a month writing standards nobody has tested.
• Ivo when you do, and volume is high enough that the quality of each proposed edit dominates. The market-benchmark comparison is worth paying for once you know your own positions and want to know where they sit against the market.

Cost reality

For three legal seats and roughly 250 negotiated agreements a year:

• Intake form: $0. It is in the Microsoft 365 or Google Workspace tenant you already pay for.
• DocuSign eSignature Standard, 3 seats: $1,080/year, published.
• Storage: $0, existing.
• Review engine: the only quote-only line in the stack.

So the whole thing is $1,080 of published price and one negotiation. That single quote is where the argument is won or lost, and there is a hard test for it: the sub-$1B median technology budget is $65,000 a year, and the review engine has to leave room for legal research, e-billing, and entity management out of the same pocket. Roughly $30,000 is the ceiling that keeps this stack honest.

The number to hold it against is Summize’s Vendr median of $32,000 a year. If your review quote lands there, you have not avoided platform spend — you have bought a review engine at platform prices, and the deferral argument has already collapsed. Ask for the CLM quote again before signing.

Two costs are not on the invoice. The first is playbook authoring: pre-built playbooks are what let you skip it in month one, and a custom playbook is attorney hours you have to book rather than software you can buy. The second is enforcement of the naming convention, which at a median of zero legal operations professionals falls on a lawyer who has other work.

The two ceilings that end this stack

The envelope cap, not the seat price. DocuSign’s eSignature Standard and Business Pro annual plans include an allowance of up to 100 envelopes per user per year. Three seats is 300 envelopes — a real ceiling at 250 agreements once amendments and re-sends are counted. Guard: cross it on a volume decision, not by drifting into overage. The published exits are pre-purchased envelopes, or IAM Standard at $50/user/month with a three-user minimum ($1,800/year committed) for unlimited envelopes through the web app. That second exit is DocuSign’s on-ramp into the platform you deferred, and it is the cheapest platform you will ever be offered — which is exactly why it should be a decision.

Triage, not review. The form works while one person reads the queue every morning. When the queue needs routing rules instead of a reader, intake breaks first. Streamline AI Pro starts at $22,900 with four core users included, and its MCP connector reached general availability on 15 July 2026 so matter status can be asked of an assistant rather than a lawyer. Guard: at a $65,000 median technology budget, $22,900 for the intake layer alone is a third of everything legal buys — treat it as a re-plan of the stack, not an upgrade to it.

Match rules

Right pick when: revenue under roughly $1B with one to five lawyers and no dedicated legal operations hire; 100–400 negotiated agreements a year concentrated in NDAs, MSAs, DPAs, and order forms; a CLM was evaluated and deferred, or bought and abandoned; and most paper arrives from the counterparty rather than leaving on your template — this stack is review-heavy, not drafting-heavy.

Wrong pick when: post-signature obligations carry money (SLA credits, volume rebates, regulatory deadlines) — that is what the buy-side contract ops stack exists for; volume runs past ~2,000 agreements a year, where the enterprise CLM stack wins on workflow alone; contracting is distributed across sales, procurement, and HR with nobody reading a single queue; or an auditor or regulator will ask you to prove the approval chain, which a form submission and an envelope archive cannot produce. CLM vs CMS draws the same boundary at the product level.

Common variations

Swap the review engine for Summize when adoption is the binding constraint, not budget. Summize puts intake, review, approval, and repository search inside Word, Outlook, Teams, Slack, Salesforce, HubSpot, and Jira — the business never opens a legal tool. It also collapses this stack’s intake and repository layers into one vendor. At a $32,000 Vendr median it is not the cheaper path; it is the path you take when the reason the last CLM failed was that nobody logged into it.

Drop the separate intake form when your review engine grows into it. LegalOn’s Productivity Suite adds Matter Management, an Intake Agent, a Triage Agent that approves standard agreements and flags nonstandard terms, and intake from email, custom forms, Slack, and Microsoft Teams. Rule: take this when you are already on LegalOn and the queue has outgrown a reader — one vendor to administer beats two, and it reaches routing without the $22,900 line.

Add an SOP instead of a second tool when reviewer output is inconsistent. With two or three reviewers the variance is in what gets escalated, not in what the engine flags. The contract review SOP and the NDA playbook close that gap for the cost of an afternoon.

What this stack does NOT replace

• Post-signature obligation tracking. No renewal alerts, no SLA credit tracking, no rebate entitlements. The envelope archive records when something was signed, never what it committed you to. This is the one gap you cannot assemble from the parts above, and it is the honest reason to buy a CLM.
• A clause-level searchable repository. You get filename search and envelope custom fields. You do not get “show me every limitation-of-liability clause capped below 12 months of fees.”
• Approval-chain evidence. A form submission and a completed envelope are not an auditable routing record.
• Self-serve for the business. No template portal, no click-through generation. The business still emails you, and the form is the only thing standing between that and your inbox.
• Entity, board, and matter management. Those live in the tiers above Core Review, or in a separate product entirely.
• Legacy contract ingestion. Everything signed before this stack existed stays exactly as findable as it was.