Master Legal · The AI workforce for legal matters

Your matters, augmented.

Spawns N workers per matter. Drives Outlook and your DMS. Produces filing-ready claim files, defensible positions, full audit trails. One matter, as many workers as it needs — one per document, one per event, one per clause.

A counsel's desk: stacked contracts and a hand-annotated FIDIC volume on the left, Vonbuild's structured claim file and audit trail on the right

Left — 400 documents on your desk · Right — the defensible position Vonbuild assembles

Who Master Legal serves

Not just the counsel.

In-house counsel is the daily driver. But Master Legal runs into every cross-functional moment that touches a clause — variations, bid risk, contract redlines, supplier disputes. Four roles converge on the same workforce.
Marketplace · Legal extensions

Six patterns your firm builds.

Reusable capabilities your firm builds once. Workflows, knowledge packs, mini-apps, always-on agents, encoded processes. The six below are examples — your library grows from your protocols. DSI keeps the governance gate.
Workflow
3 wk → 3 days
EXT-LEG-01

Build the claim file

The signature workflow below. 18 months of correspondence reconstructed into one defensible position. Full evidence chain.
Agent
always-on
EXT-LEG-02

Forfeiture deadline patrol

Watches every contract. Alerts at T-30 / T-15 / T-7 days before any notification window closes. Drafts the letter.
Process
1 wk → 4h
EXT-LEG-03

CCAP / CCTP risk-rating

Your firm's contract-review protocol, encoded. Scores every clause against precedent. Flags deviations from your house redlines.
Mini-app
2 wk → 2 days
EXT-LEG-04

Run windowed delay analysis

Concurrent-delay analysis over your chosen windows. As-planned vs as-built variance. Critical-path attribution.
Knowledge pack
3 wk → 5 days
EXT-LEG-05

Multi-jurisdiction PPP review pack

FIDIC, NEC, JCT, AIA, CCAG, SIA 118 cross-mapped. The clauses that shift risk allocation by jurisdiction.
Workflow
4 wk → 5 days
EXT-LEG-06

Build the expert-witness brief

Chronology, exhibit index, cross-examination Q-set. Formatted to the receiving tribunal.
Inside the app · Marketplace

Where your firm's legal methods live.

Every workflow your team builds — claim-file assembler, FIDIC clause matcher, EoT calculator — versioned, searchable, DSI-gated. Available to every in-house counsel from day one. Knowledge stops walking out the door.

Extensions

Context
vonbuild·Org=design_officeFunc=engineering
Filters
Organisation:design_office×Function:engineering×Disable auto-filters
+ Filter
Clear all
Plugins9— groups skills + agents + commands
Legal & Contractspluginvonbuild

Construction contract analysis, claims management and legal risk assessment

7 / 26 workspaces· Legal
1 skill
Estimation & Costingpluginvonbuild

Construction estimation — DPGF/DQE/BOQ analysis, quantity validation and unit price comparison

Active everywhere· Sales
2 skill
Site Operationspluginvonbuild

Site supervision, defect tracking, daily reports and works acceptance

7 / 26 workspaces· Ops
1 skill
Planning & Orchestrationpluginvonbuild

Multi-agent orchestration — workspace scan, document classification and execution roadmap generation

10 / 26 workspaces· Plan
1 agent
Procurement & Subcontractingpluginvonbuild

Supplier management, invoice verification, subcontract tracking

3 / 26 workspaces· Proc
1 skill
Technical Directionpluginvonbuild

Technical feasibility, pre-construction studies, engineering review (Eurocode / DTU / SIA)

3 / 26 workspaces· Tech
1 skill
Skills7— not attached to a plugin
DTU StandardsskillvonbuildFR

DTU pitfalls — installation errors causing non-conformities and insurance claims.

9 / 26 workspaces
SIA StandardsskillvonbuildCH

SIA standards — Swiss federation of engineers and architects technical norms

5 / 26 workspaces
FIDIC Contractsskillvonbuild

Standard FIDIC contracts — Red, Yellow, Silver books for international construction

5 / 26 workspaces
CCAG TravauxskillvonbuildFR

CCAG general administrative clauses for public works in France

5 / 26 workspaces
MCP3
Revit 2027mcptenant

Autodesk Revit 2027 — BIM model querying, family extraction, clash detection via Computer Use.

0 / 26 workspaces
ERP 2027mcptenant

Sage / Cegid ERP 2027 — purchase orders, supplier ledgers, situation reports.

Active everywhere
HubSpotmcptenant

HubSpot CRM — deals, contacts, pipeline sync for the Sales tower.

0 / 26 workspaces
One pattern · The 400-document claim file

Build a claim file.

One pattern, many deliverables. Claim file today. Witness brief next week. Multi-jurisdiction review the week after. Same workflow: aggregate, cross-reference, build the defensible position.
claim-file-builder.workflow~400 workers · RUNNING
01Ingest
Pulls 400+ documents from your matter folder via Outlook + DMS connectors. Indexes attachments, threads, addenda.
02Index
Extracts every event, communication, decision into a structured 312-event chronology with source citations.
03Cross-reference
Every contract clause linked to every triggering event. Notification windows mapped against the as-built programme.
04Evidence chain
Defensible position assembled with full citations, quantum draft, and counter-arguments anticipated.
05Audit trail
Document hashes (SHA-256), timestamps, user, model version, approval chain. JSON-exportable for discovery.
Consolidated output · 3 days end-to-end
412-document claim file · 312-event chronology · clause-to-event matrix · quantum draft · negotiation letter · full audit JSON. Filing-ready.
~400
Documents processed
312
Events indexed
18 mo
Timeline rebuilt
3 days
vs. 3 weeks senior
Time stats are illustrative — industry benchmarks (Monograph 2025, Part3 2025) compressed by the workforce model. Not measured Vonbuild outcomes per project.
Live process · Legal cascade

One command. Five legal agents. Contract analyzed.

A direct instruction to Master Legal spawns five specialized agents in parallel. Ninety seconds from command to a signed risk report. Two deadlines auto-tracked.

Signal

An event arrives at 14:32.

Any source can fire it: a file dropped in OneDrive / Google Drive / any drive, an email landing in Outlook, a scheduled task firing, or you pressing a button. In this scenario, an event arrives via YOU.

Source: YOU · FIDIC-Silver-Book-2017.pdf
Routing

MASTER LEGAL routes.

It classifies the impact across 21 semantic categories and dispatches to the 5 specialized agents concerned. No human in the loop. No meeting scheduled.

5 specialized agents dispatched · 312 ms
Parallel reaction

5 specialized agents. In parallel.

Each agent accesses its own toolset — apps, browsers, MCP connectors, project documents and company knowledge — and produces a structured output. Concurrently, not sequentially.

AGENT
Contract Reader
23 clauses
scope mapped
AGENT
Clause Analyzer
4 red flags
high-risk clauses
AGENT
Time-Bar Tracker
2 deadlines
14d, 28d remaining
AGENT
Letter Drafter
VC-024
reservation letter
AGENT
Audit Logger
Trace cr_2026
immutable
5 outputs produced
Convergence

Outputs return. One narrative.

The 5 specialized agents return their outputs to MASTER LEGAL. It reconciles them into a single decision card.

1 reconciled decision
Validation

Handed to you. One click.

MASTER LEGAL presents the consolidated decision to you. Full evidence chain, all sources linked. Three minutes after the signal landed. One approval. One trace ID. Action executed.

3 min · signal → decision
Self-scheduled trigger

T+14 DAYS. The system wakes itself up.

During the parallel phase, a agent scheduled a follow-up task on its own. T+14 DAYS — without you, without a meeting, without a reminder email — MASTER LEGAL wakes itself, dispatches the right agent, and executes autonomously. You delegated the mental load.

T+3minT+14 DAYS · auto-fired
Auto-fired · 0 human intervention
Specialization · The corpus

Built for the contracts your matters live in.

Pre-trained on the standards and concepts your work runs on. No configuration.
Contract families & standards
FIDIC Red Book 1999FIDIC Red Book 2017FIDIC Yellow BookFIDIC Silver BookNEC4JCT 2016AIA A201CCAG Travaux 2021SIA 118VOB/BICC RulesLCIA RulesUNCITRAL
Legal concepts & operations
Extension of TimeConcurrent delayWindowed delay analysisCondition precedentForce majeureFrustrationCalderbank offerWithout prejudiceAttorney-client privilegeDisruption claimsSub-Clause 20.1 notificationLiquidated damages capTime at large
A week with Master Legal

What changes for in-house counsel.

Tuesday 9am — the partner asks for claim quantum on the bridge variation. Friday mediation. By Wednesday 8am the chronology, the evidence chain, the quantum draft are on your screen. You spend the rest of the week refining your strongest argument, not reconstructing a timeline.
Input · Tuesday 9am
Matter folder pointed at
412 emails · 67 contracts · 18 months
Output · Wednesday 8am
312-event chronology, clause-to-event matrix, quantum draft. Filing-ready.
Input · Always-on
Every contract under watch
SC 20.1 notification windows · every matter
Output · T-30 / T-15 / T-7
Alert in your Outlook calendar. Letter drafted. Forfeiture defence ready before the window closes.
Input · Pre-execution
500-page developer contract
CCAP / CCTP · FIDIC · JCT
Output · 4 hours later
Clause-by-clause risk score against your firm precedent. Every deviation from house redlines flagged.
The week's most expensive output is no longer correspondence reconstruction. It's the argument that wins the mediation.
Always on · Always aware

The project remembers itself.

Every email. Every drawing. Every clause. Captured the moment it lands. Connected across the project. Indexed for the dispute that hasn't arrived yet.
Project-centric · firm-aware on non-sensitive · sensitive stays gated
47 documents indexed
Ingestion processing 47 documents
Automatic capture

You don't upload. It sees.

Every document in your matter folder. Every email. Every contract addendum. Every site-report excerpt. Captured the instant it arrives. The matter memory grows itself.
Hidden connections

Dots you can't see, joined.

A clause in the CCAP. An amendment. A delay event. A notification window. An OS issued out of sequence. The system sees the links. Ask anything across 400 documents — get a sourced answer in seconds.
Team-shared

Your senior sees what the junior pulled.

The associate sees what counsel highlighted. In-house and external work the same matter file. Same memory, different views. No "did anyone send me the latest?"
Audit-ready

Half the dispute file is built before the dispute.

When a litigation arrives, the chronology is in your hands. Every document timestamped. Every decision traced. Every clause linked to its triggering event. Nothing to reconstruct.
Working into the future · Self-scheduling
Visible in your Outlook · calendar "Vonbuild"

Schedule any task — once or recurring.

The same modal your counsel uses to schedule a deadline follow-up is the engine the agent uses to schedule its own future work — autonomously, no prompt needed. Both surface in the same Outlook "Vonbuild" calendar. The agent watches notification windows; you read the alerts.
Option A · One-time
Option B · Recurring
Live demo · Computer Use on your stack

It drives the systems your firm already runs on.

No new UI to learn. No documents leave your tenant. The agent operates inside the tools you already audit.
outlook.office.com/mail/matter-folders/bridge-variation-2026
Worker · running
Matter folders
Aldgate Tower
Bridge Variation 2026
Heathrow T6 Phase 2
Crossrail Snag DLP
Genoa Bridge Arbitration
Worker action — claim_file_assembler
Indexing 387 of 412 emails — extracting timeline events…
elapsed 04:21 · est. remaining 00:53
Events extracted (preview)
2025-11-04Variation Order #47 issued by Engineer (Sub-Clause 13.3)
2025-11-09Contractor notice of EoT under SC 20.1 — within 28-day window
2025-12-02Engineer determination — partial acceptance, 12 days awarded
2026-01-15Contractor dispute notice (SC 20.2) — concurrent delay raised
308 more events…
Integrates with your existing stack
Outlook (web)iManageNetDocumentsSharePointTeamsPlus any software with MCP
Drafting and tabular work happen in Vonbuild's built-in editor. Anything else with an MCP server connects. DMS permissions inherited. No document leaves your tenant.
Mechanism · How it works

One instruction. N workers. One consolidated output.

01
Decompose
The instruction breaks into parallel sub-tasks: chronology, citation, drafting, audit.
02
Spawn workers
One worker per document. One per event. One per clause. No queueing.
03
Load extensions
Marketplace extensions run — chronology builder, FIDIC clause matcher, EoT calculator, audit logger.
04
Consolidate
Results merged into the deliverable — claim file, deadline alert, redlined contract, witness brief.
Master Legal is not a chatbot. It is a factory. Each matter sizes the workforce to the volume — 412 emails, 67 contracts, 312 events. Workers run in parallel. The output reaches your screen with every document hashed, every action logged, every approval traced.
Four routes. One promise.

How the work actually gets done.

When the agent picks up a task, it works through these four routes in order. Whatever produces a real, verifiable result, ships. If nothing does, you hear back — never with a made-up number.
01
A tool that already exists

Reach for what's on the shelf.

Your firm has built this workflow before. Or Vonbuild ships it out of the box. The agent picks the right one and runs it — like your engineer reaching for a checklist they trust.
02
A tool the agent builds

Make the missing one.

Need a calculation nobody's done in your firm yet? Hand the agent the norm — EN 13474 for glazing, Eurocode 2 punching shear, RT2020 thermal. It builds the calculator, checks it against known cases, runs your project. Next project, that calculator's already in your firm's library.
03
A tool that talks back

Connect straight through.

Some of your software — Revit, a growing list of cloud tools — lets the agent connect directly, without going through screens. No clicking, no waiting. The cleanest route when it's available.
04
A tool the agent uses like you would

Click through, like an engineer would.

Everything else — Robot, ETABS, Coupa, Procore, your supplier portals. The agent logs in with your licence and works the interface exactly as your engineer or QS would. Same software, same result, same paper trail. None of your hours.
Or — you hear back, with the reason
No made-up numbers
When none of the four routes works, the agent tells you what it tried, where it stopped, and what would unblock it. It does not invent a number to fill the gap. The output on your screen is always a real result from a real tool — or there's no output.
Polycentric model

Legal alone, or Legal in concert.

Legal leads (sole driver)
  • Forfeiture deadline patrol
    Always-on. No other workforce involved.
  • Claim file assembly
    Initiated by counsel, executed end-to-end.
  • Contract redline & risk-rating
    Pre-execution review against firm precedent.
Legal supports another lead
  • Variation impact assessment
    Engineering leads · Legal verifies contractual entitlement
  • Bid risk review
    Sales leads · Legal flags onerous clauses pre-submission
  • Supplier dispute
    Procurement leads · Legal builds the contractual position
  • Subcontractor termination
    Operations leads · Legal drafts the notice and reservations
What this workforce guarantees

How does the evidence chain hold up in front of a judge?

What it produces is admissible because what it produces is provable. Every artefact hashed. Every action logged. Every approval traced. The chain ships with the deliverable.
Document hashing
Every source artefact carries a SHA-256 hash captured at ingestion. Tampering is detectable.
Full action log
Per action: timestamp · user · action · model version · source-document references · approval chain.
JSON discovery export
Audit trail exportable as structured JSON. Drops directly into discovery review platforms.
Privilege protection
Tenant-resident execution. Your data never trains the model. Attorney-work-product handling preserved.
audit_trail.json
{
"matter_id": "BR-VAR-2026-04",
"action": "claim_file_assembled",
"user": "[email protected]",
"timestamp": "2026-05-15T08:14:23Z",
"model_version": "vonbuild/legal-1.4.2",
"extension": "EXT-LEG-01",
"documents_processed": 412,
"document_hashes": [
  "sha256:7a4f9c2e...",
  "sha256:c182be01...",
  "..."
],
"approval_chain": [
  { "approver": "[email protected]", "ts": "2026-05-15T09:02:11Z" }
],
"exportable": true
}
Live demo · Audit trail

Every cascade traceable. Every action logged.

Master Legal → 412 workers → consolidated claim file. The full execution graph stays visible, exportable as JSON, defensible in discovery years later. When the opposing counsel asks how the position was built, you hand them the receipts.
Conversation graph
Tick conversations to spawn or merge them.
0 selected
Merge 0 conversations
Into tower
Master
Legal
Sales
Technical
Operations
Procurement
Cancel
Live demo · Human-in-the-loop

The agent prepares. You sign.

Every binding action — external email, contract send, filed claim — blocks for your explicit approval. The AI never sends on your behalf. Your signature still stands. Liability stays with you. Privilege stays inside your tenant.
Governance

Your firm's privilege boundary doesn't move.

Tenant-resident inside your existing Microsoft 365 or Google Workspace. Your conditional access, DLP boundary, retention policies — inherited automatically. Project-scope extensions need DSI approval before tenant-wide promotion. Data Processing Addendum on request.

Full security and governance architecture →

Start with your most expensive open matter.

The file you've been postponing — that's where it earns it. Upload the folder. See the chronology by morning.