For Project Directors · Project Managers · Construction Directors

Your portfolio, recovered.

A marathon between subs, owners, and your commercial team. One missed EOT deadline costs €100K+. One unspotted overbill eats your 2% margin. A workforce runs the schedule, drafts the claims, audits the invoices. You focus on the next milestone.

A project director's desk: hand-annotated P6 Gantt on the left, Vonbuild's recovery dashboard on the right

Left — the Gantt you re-draw every Monday · Right — the recovery options Vonbuild models overnight

Today vs tomorrow

Fire-fighting today. A factory tomorrow.

Today

47 active issues. You hear about the worst one when it's already a fire.

Monday morning the mason calls — they're 14 days behind. You spend Tuesday in Teams trying to figure out who knew when, Wednesday drafting an EOT letter in panic, Thursday chasing the QS to verify the next sub-invoice is clean. By Friday, the deadline window for notifying the owner has closed and you've lost the claim on procedural grounds.
Monthly P&L review: explaining the margin slip — again.
With Vonbuild

1,000 workers watching every signal.

Vonbuild isn't a chatbot. It's a factory. When a sub slips, the workforce re-runs the critical path, drafts the EOT response, and audits the next batch — in parallel, across three Masters. You walk into Monday's owner meeting with the recovery plan ready.
Monthly P&L review: defending the margin you protected.
The cross-functional superpower

A 14-day slip. Three Masters. Four hours.

When the mason slips, three things have to happen at once. Operations re-runs the schedule. Legal drafts the EOT. Procurement watches the next batch. All three. In parallel. From one signal.
01
Master Operations

Re-runs the critical path.

The mason's 14-day slip triggers an overnight critical-path re-compute on the live P6 schedule. Affected trades identified (electrical · MEP · cladding). 3 recovery options modelled with cost/schedule trade-offs. Result: 6am.
02
Master Legal

Drafts the EOT claim.

Operations hands the chronology + delta to Legal. Legal cites the exact contractual basis (CCAG Art. 19.2 / FIDIC Sub-Clause 8.4 / NEC compensation event 60), drafts the notification within the 28-day window, attaches the evidence chain. Result: 9am.
03
Master Procurement

Watches the next batch.

Procurement flags the mason's next invoice batch for line-by-line audit — they often overbill on disrupted scope. Cross-references against BOQ + site measurements. Result: caught before payment.
Result · 4 hours across 3 Masters
vs. 2 weeks of fire-fighting

Schedule recovered · EOT filed · margin protected. Same day.

Critical-path recovery plan + filed EOT + overbill audit — assembled into one cross-dept brief. You walk into the owner meeting with the plan, the claim, and the receipts. €420K of margin defended in 4 hours.
Live process · Cascade

One signal. Five masters. One decision.

From a single revised drawing on OneDrive to a fully reconciled, evidence-backed decision in your hands. Three minutes. Zero meetings.

Signal

14:32 — a revised structural drawing lands in OneDrive.

The structural engineer uploads rev 3.2 of the plan for beam P-12. The section changed from B22 to B25. Nobody emails you. Nobody schedules a meeting. The system detects the event and wakes up.

Source: OneDrive · rev_3.2_structure_beam-P12.pdf
Routing

The system reads the drawing. Identifies 5 impacts. Dispatches.

The plan change affects structural loads, cost estimation, material procurement, contract eligibility, and project planning. Each department receives its specific sub-task — automatically. No human decided who should work on what. No email chain. 312 milliseconds.

5 departments activated · 312 ms · 0 human input
5 departments. In parallel.

Each one produces a concrete deliverable.

Sales recalculates the bill of quantities. Operations updates the Gantt and finds the slip. Procurement flags the steel order to re-consult. Engineering runs the EC3 verification inside Robot. Legal checks amendment eligibility and drafts the notification letter. Five outputs. Three minutes. All sourced.

MASTER
Sales
+€48K
DPGF delta — gros œuvre +€12.4K, fondations +€3.8K
dpgf-delta-rev3.xlsx
MASTER
Operations
+11 days
Critical-path tasks T-12 (formwork) and T-15 (pour) impacted
planning-rev3-delta.gantt
MASTER
Procurement
Reorder
PO-23-447 — S355 steel lot LV-3, 3 suppliers to reconsult
procurement-impact-rev3.md
MASTER
Engineering
EC3 ✓
Beam P-12 section B25 verified, utilization 68%
calc-poutre-P12.report.pdf
MASTER
Legal
VC-024
Variation eligible — CCAP Art 9.2, notification by May 19
avenant-rev3-draft.docx
5 deliverables produced · all traceable · all sourced
Convergence

5 analyses. One impact note. Ready to validate.

The outputs converge into a single cross-domain impact note: +18% structural loads on foundation FF-3 · +€48,300 total (gros œuvre + fondations) · Amendment eligible under CCAP Art 9.2 — 15-day notification window · +11 working days on critical path · Steel lot LV-3 must be reordered. Every line is sourced. Every document is linked. Every number is traceable to the agent that produced it and the tool that computed it.

1 consolidated impact note · 5 evidence chains
Validation

You open your laptop. The analysis is already done.

Three minutes after the drawing landed in OneDrive, the complete cross-domain impact note is waiting for you. Engineering verified. Cost recalculated. Contract eligibility checked. Planning updated. Notification letter drafted. You read the summary. Check the evidence links. Click Approve. The notification letter goes out. The timeline logs the decision. The procurement agent starts the reorder process.

3 minutes · signal to decision · 45 seconds of human time
7 days later. No human involved.

Tuesday, May 13. You forgot about this. The system didn't.

During the original analysis, the Sales department noticed the subcontractor had not acknowledged the variation claim. It scheduled a follow-up: check acknowledgement in 7 days. Seven days pass. You are on a different project, a different floor, a different problem. At 09:00 on May 13, the system wakes itself up. It checks whether an acknowledgement email has arrived. It has not. The agent drafts a follow-up letter, attaches the original claim reference, and submits it for your approval. You did not set a reminder. You did not write a post-it. The system remembered because that is what it does.

T+3minT+7 DAYS LATER · auto-fired
Auto-fired · T+7 days · 0 human reminders · 0 missed deadlines
Admissible · Provable · Defensible

When the owner disputes the claim, you have receipts.

Your signature goes on the EOT. These four guarantees hold up when the owner pushes back.
Guarantee 1 · No made-up numbers

Real measurements. Real BOQ.

Procurement extracts real numbers from your ERP. Operations reads real daily reports. If a number can't be sourced, the agent reports back — never invents.
Guarantee 2 · The evidence chain

SCL-aligned · arbitration-defensible.

Windowed delay analysis aligned with SCL Protocol. Every site event timestamped. Every weather day logged. Every causality traced. Defensible years after Practical Completion.
Guarantee 3 · Human in the loop

The AI drafts. You sign.

The agent drafts the EOT, the recovery plan, the supplier letter — never sends them. You review, adjust, click Send. Your signature stands. Liability stays with you.
Guarantee 4 · Tenant-resident

Your project data stays in your tools.

Procore credentials in your secret store. SharePoint permissions inherited. Site reports stay in the project tools they already live in. DPA on request.
Live demo · Guarantee 3 in motion

This is what "you file the EOT" looks like.

Critical-path re-run. EOT case built. Owner notification drafted. The modal blocks. Your click sends it. The agent prepares within the 28-day notification window; your judgement triggers the file.
Works where you work

No new app for your site team to install.

The agent operates Procore, P6, Teams the way your team does. Logs in with your licence. Posts updates to the systems they already trust.
Operates inside your stack
Primavera P6MS ProjectAsta PowerprojectProcorePlangridTeamsSAP · OraclePlus any software with MCP
Site WiFi tolerant
Runs server-side. Site teams see results when connectivity returns. Trailer router doesn't block anything.
No new UI for the foreman
Updates flow into your existing Procore / P6. Your site team opens the same screens they already know.
Your owner sees your format
EOT letters, recovery plans, monthly reports — exported to your firm's templates. Nothing breaks downstream.
For your CFO conversation

How to justify Vonbuild to your board.

Don't tell your CFO you bought an AI tool. Tell them you bought a schedule-recovery + claim-capture engine. Three bullets, ready to repeat.
Bullet 1 · Claim capture
€100K+
per EOT claim recovered

"We file EOTs within window — every time."

Industry pattern: 30–40% of valid EOT claims forfeit on procedural grounds (missed notification window). With workforce: every signal triggers a draft within 24h of the triggering event. Average recovery per valid EOT on mid-size projects: €100K–€500K.
Bullet 2 · Cost avoidance
3–5%
overbill caught

"We audit every invoice batch, not a sample."

Industry consensus: 3–5% overbilling routinely present on construction invoicing. Manual sampling catches a fraction. With line-by-line verification: the full delta becomes recoverable. On a €50M project, that's €1.5M–€2.5M of margin defended.
Bullet 3 · Throughput
projects per PM

"Same team. Double the project portfolio."

PMs typically run 2–3 projects in parallel because their week is consumed by fire-fighting. With the workforce handling the chase, the audits, the drafts — same PM team runs 4–6 projects. Hiring conversations move from "we need to hire" to "we're absorbing growth with existing headcount."
Live demo · Portfolio graph

8–15 projects. One shared graph.

Every project's schedule, cost, risk, change-order status — reconciled and time-stamped. The view your PM team needs to absorb portfolio growth without hiring.

3 contributors · 3 SharePoint departments · 1 shared project graph

Each user uploads their own folder. The Vonbuild knowledge graph stitches everything together — automatically, with cognitive confidentiality.
Numbers are industry benchmarks (SCL Protocol surveys, Monograph 2025, industry claim-capture consensus). Calibrated to your firm in the demo.

Start with the project that's quietly sliding.

The schedule you've been hoping to recover at the next milestone. The 47 subs nobody is chasing. The EOT you keep meaning to draft. That's where it earns it.