Unpack a signed portfolio into a register of duties, each one citing the clause it came from and dated to when it falls due, and hold that register for a named commercial owner.
A contract is loaded, and the duties it creates are written out as lines, each with an owner and a date.
02
A schedule nobody has reopened since signature is read alongside the body it hangs off.
Reason
03
An obligation falls due, and it is dated from the clause that set the date, not from the filing date.
04
A duty runs toward the supplier, and the one running the other way is registered in the same pass.
05
A clause carries its exception in a second sentence, and the exception travels with the summary.
Decide
06
An amendment, side letter or change order is bound to the contract it altered before either is read.
07
A rebate, credit or price review has to be claimed, and the claiming is what the register dates.
Out
08
A clause resists extraction, and that resistance is recorded as a finding rather than left as a blank.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Reading, extraction and dating belong to the agent. Meaning belongs to a named commercial owner, who decides what a clause obliges and acts on it.
Example workflow
One contract, signature to register
AgentHuman
1Signed contract receivedExecuted agreements, schedules, amendments, side letters or change orders
2Obligations extractedThe duty, the party who owes it, the date it falls due and the clause it was read from
3Register entries raisedEach obligation, its owner, its due date and the extraction confidence
4Controls appliedClause-citation checks, amendment checks, date checks and extraction confidence
No human action required
Stages 1 to 4 run unaided, and nothing is waived or served at any of them — the agent is extracting, and the owner lane opens at the confidence gate.
5DecisionSplits at the extraction gate
Clause cited cleanly
Goes to the commercial owner to confirm.
Anything unreadable
Adds a contract-manager read first.
Commercial review
The obligation is held with its clause, its due date and the confidence it was read at.
Confirm · Reassign · Send to contract review
Confirmed — by the commercial owner▼
6Contract and calendar records updatedOnly where write access and records policy allow it
7Outcome evaluatedClause-citation accuracy, amendment coverage, owner corrections and what review found
Corrections
Each commercial-owner correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding what an extracted clause means.
Waiving an obligation the company owes.
Serving a notice under a contract.
Judging whether the company is in breach.
Automation boundaryAgent acts unaided
✓Read the signed portfolio into an obligation register.
✓Point each obligation at the clause it came from, in the document.
✓Date what falls due against the clause that set it.
✓Mark any obligation the document would not yield with confidence.
Nothing is waived or served except by a named commercial owner, inside agreed boundaries.
Agreeing a variation to a signed term.
Telling a supplier an obligation is met.
Choosing which duty to enforce and which to let go.
Changes to extraction rules or register owners.
Example output
One obligation, annotated
Our contract review agent reads a draft for legal risk before signature; this is the obligation register after it, and below is one entry exactly as the agent leaves it.
Obligation entry · single clauseIllustrative example
Obligation
Recorded as
Counterparty
Evidence of record
Confidence
Held for
Volume rebate, annual claim
Claimable only on written notice
A duty the buyer owes
Schedule 3, clause 4.2, page 41
Held unconfirmed
The commercial owner, by name
As receivedRead off the executed agreement and the schedule attached to it, and it claims nothing past those two.
What the record holdsThe clause as signedThe schedule it sits inThe amendment history
Why no confirmation hereDeciding what this clause obliges is a judgement the owner makes.
ActionConfirmReassignSend to contract review
What the score decidesBelow the threshold an entry gets a contract-manager read before the owner sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every obligationFrom the contract that created it
03Evidence
Where the evidence is used
Where an obligation was missed and the date has already gone by, the owner records what was forfeited against the clause, the entry reopens with its extraction attached, and the case joins the suite.
01Approved path
The clause outlives the deal
Negotiation ends and the file closes, but the duties it created run on for years, in schedules nobody has reopened since the day of signature.
02Human review
What was checked, and not found
No repository examined here states a duty. A contract repository stores documents, versions them and controls who may open them; a register of obligations is a different artefact, stating what is owed, by whom and by when, with a named owner against each line. Almost every company has the first and believes it has the second. Nothing in a signed document records whether the duty was performed, so the register holds what was extracted and what was not, and performance is asserted by the owner rather than read off the page.
04Build an evidence trail
The obligation, the clause it came from and the owner who holds it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A type-level extraction figure can read clean while rebate and credit clauses carry most of the entries an owner had to correct. Nestack reports the correction rate by obligation type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Rebate and credit clauses
10.5%
3.7×
Review
Buyer-side undertakings
7.5%
2.6×
Review
Amended or varied terms
4.7%
1.7×
Watch
Standard payment terms
2.3%
0.8×
Normal
Bar: correction-rate lift vs. standard-payment-term baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unread schedule costs
A cycle closes when the missed obligation is a regression case. That suite is what the next contract loaded is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on rebate and credit clauses.
02Diagnose
The obligation buried in a schedule to a contract nobody has opened since signature is worked backwards until one cause is left standing.
03Improve
Number the change; the contracts that drove it are filed beneath it.
04Verify
One contract case still failing holds the entire release back.
05Learn
It is retained permanently, and the extraction rules move with it.
Learn → DetectThe return edge. The next contract is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, extraction and register logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Portfolio discovery and automation-boundary design.
02Repository and amendment sources.
03Clause-to-obligation and register-coverage mapping.
04Contract ingestion and clause segmentation.
05Obligation extraction and clause binding.
06Confidence scoring and review routing.
07Commercial review workflow.
08Repository and calendar integration.
09Obligation and clause cases.
10Guardrails and extraction controls.
11Clause-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne portfolio, one entityProductionProduction contract workflowAdvancedMultiple entities / portfolios
Introduced at Pilot
Obligation extraction to your clauses✓✓✓
Named commercial-owner confirmation✓✓✓
Contract-inventory baseline✓✓✓
Introduced at Production
Reporting by obligation type—✓✓
Contract review workflow in your systems—✓✓
Approved write-back—✓✓
Contract-repository integration—✓✓
Introduced at Advanced
Multi-language clause reading——✓
Cross-entity obligation packs——✓
Large contract portfolios——✓
Multi-entity clause controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, portfolio size, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your signed portfolio and the entity each contract sits under→Contract ingestion and clause segmentationWeek 1
02Representative contracts, schedules and amendments→Clause binding, extraction logic and the obligation baselineWeek 2
03Your contract calendar and the owners it names→Clause mapping, obligation binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Repository, document and amendment source assessment, then integration setupWeek 2
05Obligations you would not want missed→Clause cases and the evaluation runWeek 4
06What no extracted clause may decide→Confidence scoring, review routing, guardrails and release controlsWeek 3
07A named commercial owner who confirms the entry→Release to the commercial owner, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The grid is not decoration. Where two phases genuinely run together, week five shows them both.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Portfolio discovery, clause mapping and the automation boundaryW2Repository integration and the contract-inventory baselineW3Extraction logic, register structure and release controlsW4Evaluation suite, clause cases and failure-mode testingW5Calendar integration, pilot contracts and targeted correctionsW6One contract cycle run under the commercial owner, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five carries a pair by design.
At the end of W6Once the obligation record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Procurement AI agent
Build a contract management agent around the obligation your last portfolio never registered.
Show us one contract you signed and the schedule nobody has opened since. Not a repository of documents. A register of duties, each with an owner and a date against it. An obligation the company owed and forfeited by silence comes back as a finding.
