For enterprise
Augment and scale your in-house legal team.
Your lawyers were hired for judgment. Most of their week goes to volume — intake, first-pass review, chasing signatures, keeping the record straight. FinePrint puts an in-house AI legal counsel alongside your team: agents run the routine under your playbook, your lawyers take exactly what needs them, and every matter lands in a record that’s current by construction.
41
endpoints that run under your playbook — whole transactions, not suggestions
3
judgment lanes — and your lawyers decide what runs in each
1
price for the company — nobody in the business is rationed a seat
0
documents from your record ever used to train a shared model
Four facts about the product, not four claims about your team. There are no customer counts on this page, no logos and no percentage improvements — when measured numbers exist they will replace these tiles, and they will be dated when they do.
What changes for your team.
Three things move: the front door, the playbook and the record. Everything you hired lawyers for — the judgment, the negotiation, the calls that carry real exposure — stays exactly where it is, with more of the week available to do it in.
Front door
One address for legal — and the work starts itself.
Give the business a single front door: forward it to Legal. Every request becomes a matter, triaged by lane. Routine work starts immediately — the contract read against your playbook, the response drafted, the signature routed. What needs a lawyer reaches yours with the record, the documents and the history already assembled. Nothing reaches your team late, and nothing gets asked twice.
How the front door worksPlaybook
Your positions, enforced on every matter.
Your negotiation positions, fallbacks and thresholds become the standard every endpoint runs on — across every contract, every business unit, every request. Your team’s judgment stops living in people’s heads and being applied one matter at a time. It becomes the operating standard, and the record shows it was applied.
What an endpoint runsRecord
A record diligence can’t surprise.
Every entity, every executed document, every approval — filed by the endpoint that produced it, versioned and indexed in the Legal DataRoom. When the audit, the financing or the deal arrives, the data room is a share link, not a quarter of somebody’s year. And Today shows your team what’s missing, what doesn’t match, and what’s due — across the whole structure.
Inside the Legal DataRoomA worked example
One matter, from the business’s inbox to the record.
Legal at scale does not fail on hard questions. It fails on volume: the same vendor agreement arriving from four business units, each time read from the beginning by whoever has capacity, each time answered slightly differently, and none of it written anywhere the next person will find it.
Here is one of those, run as an endpoint under your playbook — including the single moment it stops and asks a lawyer, and who that lawyer is.
RUN /review-contract
inbound: forwarded to the legal address by an operations manager
entity: US operating company · playbook: commercial, current version
✓matter opened from the forwarded mail · counterparty resolved in the recordTue 7:12 AM
✓read record — three live agreements with this counterparty, one DPA, one order form expiringTue 7:13 AM
✓19 deviations from your playbook · 16 inside your written fallbacksTue 7:26 AM
●indemnity carve-out for AI-generated output Yellow routed to your counsel, file builtTue 7:27 AM
✓position confirmed in-house · redline regenerated on the confirmed positionTue 10:04 AM
✓redline and issue list returned to the requester, your team copiedTue 10:11 AM
→/route-for-signature — signing order from the entity’s authority matrixTue 10:12 AM
Your counsel decided one thing. The intake, the record read, the deviation list, the redline and the signature routing ran without a lawyer touching them. The one question carrying a real position went to your team with the file already built — and the position they confirmed becomes the playbook’s, so the next request of the same shape gets the same answer without anyone being asked again.
What the agents take. What stays with your lawyers.
Drawn as a table, because this is the question a Head of Legal actually asks and a paragraph is a convenient place to be vague about it. Nothing in the right-hand column moves left without your team moving it.
| The work | Runs as an endpoint | Where your lawyers come in |
|---|---|---|
| NDAs, in and out | Triaged against your positions on either side’s paper, redlined, routed for signature, filed with the counterparty written to the record. | The ones your fallbacks don’t answer — an embedded non-solicit, a term that outlives the relationship. |
| Your own commercial paper | Generated from the record with the right entity, signatory and approvals, executed, filed, and the obligations it creates written back. | The form itself, and every change to it. Your paper is your team’s document, not ours. |
| Counterparty paper | Read against your playbook. Every deviation listed and scored against your written fallbacks, with a redline and a plain-English issue list returned to whoever asked. | The deviations outside the fallbacks, and any position the playbook hasn’t taken yet. |
| Hiring and employment | Offer packets, invention assignments, state notices, payroll and unemployment registrations, and the recurring obligations a new state creates. | Classification calls, terminations, and anything touching a covenant from a prior employer. |
| Equity and the board | Grants checked against the pool, consents drafted from the record, signing order built, minute book and ledger updated after. | Anything that changes the capital structure — and every question the board asks about it. |
| Entities and compliance | Registrations, annual reports, foreign qualifications, and the dates surfaced in Today before they are due rather than after. | A new jurisdiction, a new regulated activity, a change to the structure itself. |
| Diligence and the data room | Nothing to assemble: the Legal DataRoom is already built, versioned and indexed. A request becomes a scoped share and an index. | The disclosure schedules, and the answers only a lawyer should be giving. |
| Policy and playbook | Applied — on every matter, in every business unit, with the record showing which version was applied and when. | Written. The playbook is your team’s judgment; the system only enforces it. |
Your lawyers hold the lanes.
The same three levels that govern every FinePrint matter — with your team in the seat of judgment.
Green — agents execute.
Under your playbook, with the approvals you’ve configured. Licensed reviewers score samples of the output continuously.
The lane is not a permission slip you sign once. Which endpoints run green, under which entity, at which thresholds, and who has to approve before anything moves are settings your team holds — and changing one changes every matter after it.
Yellow — your counsel confirms.
Flags route to your team first, file already built — with the OpenLegal network behind them when you want the overflow handled. Included either way.
What arrives is not a request for help. It is a matter with the record read, the documents assembled, the deviation named and the options written down, so the time your lawyer spends is spent deciding rather than reconstructing. Nothing moves while it waits.
Red — a specialist leads.
Yours or the network’s. A financing, a dispute, a regulated question — taken with the record, the documents and the history already in hand.
The file travels with the matter: entity history, executed documents, approvals and the version trail behind each one. A specialist who has never seen your company starts from a complete record instead of an hour of somebody explaining it.
What review means, precisely: continuous review samples green-lane output — it is not a lawyer reading every document. A lawyer reads your matter when it goes Yellow or Red, and nothing starts until someone you have authorized approves it. On Enterprise, that someone can be your own counsel. The two modes of review
Enterprise
Your policies, your keys, your terms.
Enterprise is the plan where the governance around the machine is yours.
Your keys
Encrypted, company-isolated, per-document keys. Multiple entities under one record. Export in full or delete, permanently, any time.
Your data, never training data
The Two-Corpus Rule: OpenLegalLM learns from its contributors — never from your record. Your documents are retrieved for your matters only.
Your paper
Custom policies, API access, and your paper for the engagement — with a security review that has real answers, on the record.
Rolling it out without turning it into a project.
Three things you already have: your entities, your playbook, and the documents the company has already signed. The entities and the signed documents are loaded into the record; the playbook becomes the standard the endpoints run on. After that the change is behavioral — the business forwards to one address instead of hunting for a lawyer, and your team works a queue instead of an inbox.
- Entities — several companies under one record, each with its own charter documents, officers, registrations and calendar. A matter carries its entity, and the endpoint uses that one.
- Approvals you configure — which endpoints run without a human, which need an approver, which need two, and who may be an approver, by entity and by threshold.
- Business units, one front door — the address goes to the business; matters land tagged with who asked and what for. Your team sees a queue with lanes, not a mailbox.
- Your playbook, versioned — positions, fallbacks and thresholds are a document your team owns and edits. Every matter records the version it ran under, which is what makes an audit answerable.
- The paper you already hold — signed documents the company holds today are filed into the Legal DataRoom and the graph is built around them. They are marked as arriving from outside: they carry what we can verify about them, not what an endpoint observed.
- API access — endpoints are callable from the systems the business already runs, so a matter can start from a ticket or a procurement flow as easily as from an email.
Enterprise is priced Custom — one price for the company, never per seat, set against your entities, your volume and the governance you need. Every other plan’s price is published in full, with the arithmetic behind it, on the pricing page.
The questions a General Counsel actually asks.
Is this replacing my team?
No — it’s the opposite trade. The agents absorb the volume that never needed a lawyer; your lawyers keep every decision that does. The team you have covers more of the business, faster, with a record that proves it.
Does anything we run train the model?
No. OpenLegalLM learns from the network’s contributors — never from your record. Your documents are retrieved for your matters and are never training material for a shared model. That rule has a name, the Two-Corpus Rule, and it’s load-bearing: it is how a federated legal model and enterprise confidentiality coexist.
Can our own lawyers be the reviewers?
On Enterprise, that’s the design: flags route to your counsel first, with the OpenLegal network behind them for overflow and for specialist matters. Nothing runs until someone you’ve authorized approves it.
What does the security review look like?
The security page names the subprocessors, the encryption model — company-isolated, per-document keys — and the deletion terms: immediate in live systems, completing as backups expire. Bring your questionnaire; the answers are on the record.
What exactly is an endpoint?
The whole transaction, not a template. Take /hire-employee: it produces the offer packet, the invention assignment, the state notices, the board consent for the option grant, the signature routing in the right order, and the payroll and unemployment registrations a new state requires — then writes back, so the pool, the headcount and the compliance calendar are correct without anyone editing a spreadsheet.
There are forty-one of them in eight categories, and every one ends with the record updated rather than a document in somebody’s downloads folder. The whole catalogue
Can we keep our outside counsel and our firms?
Yes, and for the matters that need a firm you should. What changes is what reaches them. A financing, a dispute or a regulated filing arrives with the entity history, the executed documents, the approvals and the version trail already assembled — instead of a call where somebody explains the company from the beginning.
If your existing firm would rather take a Yellow or Red matter than the network, they can, with the same file built for them. FinePrint is a legal technology company, not a law firm; it does not practice law and it does not give legal advice. Where judgment is required, a licensed attorney reviews the matter or takes it, engaged by you, with the scope shown first and the review included in your plan.
How does a correction on one matter become a fix for everyone?
Through the network and a release process, not a support thread. When licensed reviewers flag a pattern rather than a one-off, the fix lands in the endpoint itself: curated, tested against evaluation suites, gated, and shipped as a version. A single correction never changes production, and every company running that endpoint gets the improved version at the same time.
See it against your own playbook.
Bring the agreement your team reads most often. That is the demo.
Thirty minutes, live: your playbook, one real matter shape, run start to finish — and what FinePrint would take off your team’s desk first.
Book a demoOr start with the paper trail your security team will want anyway.
Security and isolation