Legal × product · The intelligence underneath · July 2026

What the legal work runs on

Every step of contract work turns on a lawyer's judgment, and that judgment draws on specific things they know: the law, the department's positions, its own signed paper, what happened last time. Named, those become eight types of intelligence, and each runs on data that either exists today or doesn't. This page names the eight types, shows which steps use which, and specifies the data each requires, so legal and product can see what has to exist before any step can be made intelligent.

01
The idea

Every step runs on judgment, and judgment runs on intelligence and data

Every contract step runs on a lawyer's judgment. That judgment comes from what the lawyer already knows: what the law requires, the department's position, what this party agreed to before, who can sign.

Each type of intelligence runs on its own data. Some of that data already exists and stays current, some sits locked in the department's documents until someone pulls it out, some has to be written down by lawyers, and some exists only while the work happens and vanishes unless someone captures it. Once the types and their data have names, the build conversation gets concrete.

02
Where it lives

Three rings, three data problems

Where a type of intelligence physically lives decides what data problem it is. That single fact shapes every row on this page.

Inner ring

In and around the agreement

The agreement itself, plus everything attached to it: amendments that change the original deal, order forms that add new purchases under it, the template it started from, and the playbook that sets what the department will and won't accept. To know what a company agreed to, this is where you look, in the agreement or a step away from it.

Extract into structure; write the playbook as records
Outer ring

The systems and people around them

Email, CRM, HR records, negotiators' heads: the places that say what an agreement currently means. What is captured here goes out of date with nothing to flag it, and most of it is never captured at all.

Capture at the moment, under governance
External ring

Outside the company entirely

Laws and regulations, court decisions, industry standards and best practices, and market intelligence on what terms are normal at this size and industry. The outside world keeps all of it up to date, and none of it is unique to any one company. The job here is to subscribe and keep up.

Someone else maintains it
03
The eight types

The types, in the order the work meets them

A request comes in, and there's a reason behind it. The department pulls up its own past agreements, applies the positions it has already settled on, stays inside what the law requires, and holds to terms the market treats as normal. Then it negotiates the gaps with the other side, the right person signs, and how the deal plays out teaches the next one. The eight types below run in that order; the step numbers show where each one is used.

Enters at 01
Business context
03 · 05
Agreement data
02 → 07
The playbook
03 · 05
Public law
04 · 07
Market terms
08
Negotiation history
09 · 10
Authority state
12 · 13
Outcome data

The flow starts and ends in the outer ring: the reason a deal exists and what it taught are the first knowledge in and the last knowledge out, and neither is captured today.

Two of these are the hard ones to get. Market terms need more comparable deals than any single company has signed. Negotiation history needs what got said in the room, which nothing writes down. Those two are where most of the real work sits; the rest is mostly extracting and maintaining what already exists.

Click any card to see which steps use it and what data it needs.

04
The lifecycle

Walk the thirteen steps

Click a step to see the intelligence it runs on, what it produces, and the data that has to exist underneath it. The filled chip is the step's primary dependency. Or click a type of intelligence above to light up every step that uses it.

Showing: step by step

05
The data

Each type, the records it requires

The whole page in one table. Five of the eight types already exist somewhere: two are maintained by the outside world, one is read live from the systems that own it, one is locked in documents until extracted, and one is written by lawyers. The other three exist only while the work happens. Capture them then, and each is one field on a record. Miss the moment, and they have to be dug out of email later, at real cost, and with nothing anyone can trust. The executive briefing sorts these five states into four simpler fates.

Maintained outside · the world keeps it current Read from the source · fresh from the owning system, never trusted stale Locked in documents · extraction turns paper into data Must be written · systems can draft it; only lawyers can ratify it Capture it or lose it · exists only while the work happens
TypeThe data underneathStateWho keeps the judgment
06
The byproduct

The steps produce data too

Six of the steps produce intelligence that later steps need, and most of it gets lost in inboxes and people's heads. So the team negotiates with no record of past negotiations, and renews deals without knowing how the last one turned out.

Step 01 · Intake

The why

Deal rationale, stakes, the walk-away, what the client says they need. Used again at triage, drafting, and escalation.

Capture: structured why-fields on the request record
Step 07 · Redline

Deviation decisions

Which departures from the playbook the team accepted, and why. Used again at the next redline of the same clause.

Capture: a deviation event per accepted departure
Step 08 · Negotiation

Concession history

What was conceded, to whom, in exchange for what. The verbal layer no document captures. Used again at the next negotiation with the same party.

Capture: one structured line per concession
Step 09 · Escalation

Exception rationales

Why the exception was granted. Used again the next time the same exception is requested.

Capture: rationale text on the approval record
Step 10 · Signature

The authorization record

Who was authorized to bind, and did. The one emission already kept as data.

Already captured: the completion record
Step 12 · Obligations

Performance events

Whether both sides delivered, and where it hurt. Used again at the renewal call.

Capture: outcome tags linked to agreement and clause IDs
07
The people

Who maintains what

Lawyers

Own outright: the playbook and the reasons behind each position, plus the call on whether a deal turned out well. Both are legal judgment.

Curate: what counts as market, how big the stakes are, whether the other side's position is real. The systems hold the data; the lawyer makes the call.

The platform

Everything else: pulling data out of documents, keeping it fresh, wiring to the systems that own it, and building the places where those six byproducts get captured as they happen instead of lost to email.

The playbook owner and the outcome grader are the two lawyer roles this map creates, and both sit with the legal engineer.

Governance before capture

Business context, negotiation history, and outcome data are the most useful types, and the most sensitive. Before any capture tool goes live, set the privilege rules: what can be recorded, who can see it, how long it's kept. Keep the records light enough to prove the work was done without storing the privileged detail. A capture program without these rules is a discovery program.