Product
This page follows one fictional deal, Project Meridian, from the first upload to the portfolio view. At every step the AI shows its sources and a person makes the decision.
Your team reviews the extracted items itself, at its own pace.
Step 1 · Upload
Upload the SPA, disclosure schedules, TSAs, IP annexes and side letters as PDF or DOCX. Each document shows its status while it is read: uploaded, parsing, analysing, needs review.
Measured monthly as the number of TSA services still in use.
“The Purchaser shall reduce its use of the Transitional Services in line with the Exit Plan, so that no Transitional Service is provided after 30 June 2027.”
Step 2 · Review
Every extracted item lands in a review queue with its source passage and confidence score. Approve, edit or reject each one, or approve all high-confidence items at once. Nothing is monitored until someone commits it.
Step 3 · Workspace
After a commit, the deal overview is rebuilt from all committed documents. Every field shows its source and confidence, and a manual change is never overwritten. Obligations, documents, calendar, waivers and activity each have a tab.
“The Source Code shall be deposited with the Escrow Agent within 30 days of Completion.”
No definition of “Escrow Agent” in the SPA or any other document in this workstream.
Fictional deal: Project Meridian.
Step 4 · Exceptions
Telovant compares the documents in each workstream and reports conflicts, overlaps, gaps and cross-references, with both passages quoted. How a waiver gets its two approvals is shown under Flags below.
Step 5 · Portfolio
Goal statuses roll up from objective to workstream and portfolio. The overview shows each workstream's covenant results, upcoming deadlines and open findings, and every number links to the clause it came from.
1 more workstream: IP & source code, on track
Step 6 · Flags
Every flag shows the clause, the report and the number behind it, and the date that report was received. After a flag, your team decides what to do and every step is logged. When Telovant is wrong, you correct it.
A flag only uses reports received by its date, and every number links to the clause or report it came from.
The two approvals must come from two different people with the right roles. The server checks this on every decision, and each step goes into the audit log.
Every correction is saved in the audit log.
Want to see this on a deal you already closed?Run a back-test
Early access
Tell us about your deals and we will walk you through the full flow, from upload to monitoring.