Progress claims

Claim what the job
has actually done.

A progress claim assembled by hand from a contract, a folder of variations and someone's sense of how far along the job is takes an evening and still gets queried. It should assemble itself from what the job already knows.

Book a free meeting

How it builds

The contract and the
variations do the work.

Contract sum, approved variations, percentage complete by stage, previously claimed, retention. The claim is arithmetic the system already has, presented in the form the client expects.

Because it comes off the job, the backup a client asks for — the variation approvals, the site photos, the dates — is attached rather than hunted down.

Retention

tracked, not forgotten

What is held, when it is due for release, and against which job. It is money you have earned that quietly goes missing when nobody is tracking it.

Xero

no re-keying

The claim reaches the accounts with the job reference intact, so reconciliation is not a translation exercise.

Overdue

a list, with a rule

What is out and how long it has been out, with the same discipline applied to chasing that the system applies to quotes.

The rest of the family

Same build, shaped for
a different trade.

Each one is the same idea — your quoting, your jobs, your invoicing, in one system you own — fitted to how that trade actually works. Built in Brisbane by Kindra AI.