Who it's for

The same project finances, three very different roles

The developer owns the budget. The general contractor carries the risk in the middle. The subcontractor lives on thin margins across many jobs. AIMZ is one platform, but it is set up according to where you stand in the contract chain – and which numbers you are measured on.

One contract chain

A change is the same event seen from three sides

The subcontractor gives notice, the general contractor passes the claim on, the developer assesses it against the contingency. The same amount, three ledgers – and three different deadlines. AIMZ uses the same change model for all three, so the number means the same thing wherever you sit.

The subcontractor

Notifies the change, prices the work and needs it invoiced before the deadline passes.

Measured onMargin per job
The general contractor

Receives the claim, passes it on to the developer and carries the difference that is not recovered.

Measured onResult against target sum
The developer

Assesses the claim against contract and contingency, and decides before the amount becomes an invoice.

Measured onFinal cost against approved budget

What all three groups get

Numbers with a source

Every cost is linked to the invoice, change or contract it comes from. No number without an origin.

The ledger stays put

AIMZ fetches invoices and vouchers from Tripletex and other accounting systems. You do not replace what works.

AI suggests, you decide

Invoices are classified and matched automatically to line items and changes. The suggestion can always be overridden.

History for final settlement

Notices, decisions and amounts are dated and traceable – the evidence is ready the day someone disagrees.

See AIMZ set up for your role in the chain

Book a demo