A repository that reads its own paper: every contract carries a playbook score, every obligation has an owner and a lag count, and renewals are scored for risk while there is still time to act on the notice window.
The riskiest paper in the demo workspace scores 96 and carries $2.40M of ACV. The alert next to it is a to-do list: assign the owner, log the opt-out decision, re-bid if the uplift passes 8%.
contracts.cedxsystems.com — live build
Runs on demo data. The Northline legal repository in the chrome is the demo workspace, not a customer.
320 contracts · $143.5M ACV183 executed, 137 in flight
90 playbook clauses81 with five or more deviations
25.3 days to signaturemedian first-touch on intake: 2 days
What it is
Three places contract work stalls.
Intake with routing rules, not a shared inbox
New requests are typed — MSA, NDA, order form, SOW, vendor paper, amendment — and the rules route them: urgent to duty counsel on a 4-hour SLA, over $500K to senior counsel, NDAs to a paralegal fast track. The playbook auto-selects before a human reads a word.
24 open requests · 8 urgent on a 4h SLA
Median first-touch 2 days, on the card
Auto-routing rules printed on the screen
contracts — screen-2
A clause library that counts its own deviations
90 clauses with category, tier, uses, hit rate, deviations, risk and owner. Standard, alternate and restricted are tiers with meaning: 26 restricted-tier clauses require escalation, and the deviation count is on the row — one force majeure variant has drifted 15 times.
67% average playbook score across the portfolio
26 restricted-tier clauses, escalation required
Uses, hit %, deviations and risk per clause
contracts — screen-4
Renewals and obligations scored before they lapse
38 renewals sit in the notice window scored at risk; 51 obligations are past due with owners unassigned. The “Do this next” panel ranks the work by impact and effort — rescue the $2.40M MSA first, clear the lagged obligations after.
38 renewals at risk inside the notice window
29 obligations with high lag, 51 past due
Do-this-next ranked by impact + effort
contracts — overview
Product tour
Four screens, captured from the running build.
Not a mockup and not a concept deck. This is what opens at /app/contracts.
contracts.cedxsystems.com
01 — Overview
The portfolio's health, scored in public
320 contracts, $143.5M annualized under management, playbook adherence at 67% against a 78% target. The status bars say where paper sits: 183 executed, 40 in negotiation, 30 out for signature, 8 expired.
Draft 21 · in review 38 · negotiation 40
Out for signature 30 · executed 183 · expired 8
Signed versus cycle days, weekly
02 — Intake
The front door, with a clock
24 requests in queue across New, Triaged, In legal and Converted. Each carries type, value, urgency, status and wait — the 9-day-old MSA at the bottom is why the first-touch median of 2 days is a median, not a promise.
Request form auto-selects the playbook
Urgent box marks a 4-hour first-touch SLA
Owner pool named on the routing card
03 — Repository
Every contract, with its paperwork state
320 rows with type, party, status, ACV, end date, auto-renew flag, playbook bar and owner. The gaps are the point: 13 contracts are unowned, and the owner column says “Unassigned” in red rather than leaving the cell politely blank.
107 executed contracts on auto-renew
Playbook score as a colour bar per row
Filter chips: Executed through Auto-renew · CSV
04 — Clauses
The playbook, measured against reality
Each clause shows how often it is used, how often it holds, and how often it drifts. A standard clause with 96% hit rate and one with 15 deviations are both visible — the library improves because the misses are counted.
90 clauses · 81 with deviations ≥ 5
Tiers: Standard · Alternate · Restricted
Risk score and owner on every clause
Who runs it
Three roles keep the paper moving.
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Legal counsel
Works the restricted tier and the stuck redlines. A clause that has drifted 15 times gets rewritten or re-tiered, because the deviation count keeps asking.
devs 15 · restricted 26
Legal operations
Owns intake: the routing rules, the first-touch median, the 4-hour urgent SLA. The queue's wait column is their scoreboard.
first touch · 2d
The requestor
Submits through the form, not the hallway: type, counterparty, value, term, renewal motion. The playbook is already chosen by the time legal opens it.
intake · 24 open
The shape of it
What the demo workspace actually looks like.
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
320contracts in the repository$143.5M ACV
67%playbook adherencetarget 78%, then 90%
38renewals at riskinside the notice window
29high-lag obligations51 past due in total
Contracts by status320 contracts across six states · demo workspace
Executed183
Negotiation40
In review38
Out for signature30
Draft21
Expired8
Playbook adherence67% standard language across the portfolio
Standard language · 67%
Non-standard or deviated · 33%
Auto-renew share of executed paper107 of 183 executed contracts auto-renew
58%
Auto-renew · 107
Fixed term · 76
How it runs
A contract's life, in the order it actually happens.
01
Enter through the form
Type, counterparty, value, term and renewal motion — the playbook auto-selects and the routing rule assigns the lane before anyone reads it.
02
Negotiate against the playbook
Redlines resolve toward standard, alternate or restricted positions. A restricted clause means escalation, and the redline that sits 21 days appears on the Overview.
03
Execute, then assign
Signed paper lands in the repository with an owner, an end date and an auto-renew flag. The 13 unowned contracts are an alert, not a surprise.
04
Watch the window
Renewal risk is scored inside the notice window, obligations carry lag counts, and the do-this-next panel ranks what this week should actually touch.
One record
The paper hangs off the deal the estate already keeps.
A contract is the legal shadow of a commercial record that already exists. Contracts reads it, and writes back to it.
Finding this out on the third call is worse for you than reading it here, and worse for us.
Contracts is not generally available. What opens today is the live build running on demo data — the Northline legal repository in the chrome is the demo workspace, not a customer.
We have no named customers to show you, so this page shows none. The counterparties and clauses in the captures are demo data, not references.
The playbook — 90 clauses, three tiers, the 67% adherence score — is the demo library. Your positions and thresholds are built with your counsel, not inherited.
Nothing on this page is legal advice, and the software does not replace counsel. It routes, counts and remembers; judgement stays with your lawyers.
No audit or compliance certification has been issued. What we can evidence about hosting, encryption and access is on the security page.
Yes. Every screenshot is a capture of the running build at /app/contracts, on demo data. The demo repository is named in the chrome.
What does a playbook score measure?
How closely a contract's language matches the library's standard positions. The repository shows it as a bar on every row — green near 90, red near 50 — and the portfolio average of 67% sits on the Overview next to its 78% target.
How does renewal risk get scored?
Inside the notice window, renewals carry a risk score and a reason — the top one in the demo scores 96 and the alert lists the response: assign an owner, log the opt-out decision, re-bid above an 8% uplift.
What counts as obligation lag?
Promised actions with no owner or no movement. 29 obligations are flagged high-lag and 51 are past due; the fix the screen suggests is unglamorous — assign owners and run a weekly stand-up on the queue.
Is Contracts audited or certified?
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
The repository is running. Go and look at it.
Live build, demo data, no card. Then ask who owns your next renewal inside the notice window.