Progress Billing
Progress billing that runs on cycle, in every owner’s format.
We encode each contract’s billing rules against the job data you already keep, so every progress bill assembles itself on cycle, in the right format.
Built with the leading AI platforms
The billing-cycle scramble
The definition was never the problem. The calendar is.
Progress billing is how a contractor gets paid for work in progress: instead of one invoice at the end, the contractor bills the owner at set intervals — usually monthly — for work completed and materials in place, less an agreed retention held until closeout. Each bill shows the period’s progress against the schedule of values; on the owner’s side the same cycle arrives as progress payments. The definition is not the buyer’s problem. Every contract runs its own rules — percent-complete method or milestones, billing frequency, retention cap, required backup, the owner’s format — and those rules live in the PM’s and the biller’s heads. From contractors we have sat with: general contractors and specialty subs between $10M and $100M, billing monthly against multiple owner formats — not shopping for software, drowning between the calendar and the contract terms.
A full Friday, every period
Pay apps assembled by hand from job-cost exports, spreadsheets, and email — a full Friday, every period, and the bill still goes out late.
Percent-complete by feel
Each PM makes the percent-complete call their own way, and over- or under-billing surfaces at the WIP review instead of when it happened.
Billing off stale contract terms
Contracts and addendums sit in SharePoint, rekeyed into the ERP — billing runs on last version’s rates, with no audit trail per field.
Retention in a side spreadsheet
Release conditions differ per contract and nobody checks them systematically — collecting at closeout means reconstructing the job’s history by hand.
The rules walked out the door
This owner’s format, that owner’s backup rules, who takes change orders as separate lines — it lived in one person’s head; she left.
What manual costs
A bill out days late is cash weeks later.
What the manual way looks like at a contractor billing monthly against multiple owner formats. Your numbers will differ — the first contract we encode puts figures on yours before the rest get built.
From anonymized engagements — general contractors and specialty subs, $10–100M in revenue
How it works
We encode your exceptions.
No new system for your team to learn. The billing rules your best person carries in their head become the billing cycle.
- 01
Read one job’s last three cycles
We read one job’s last three billing cycles against its contract — what could have been billed and wasn’t, and where percent-complete diverged from the method.
- 02
Encode the contract’s billing rules
Percent-complete method or milestone definitions, frequency, retention cap, backup evidence, owner format — documented end-to-end against the job data you already keep.
- 03
Every bill assembles itself
Each progress bill builds from live job data on the billing calendar; missing backup, unpriced change orders, and retention-release conditions land in a human queue.
The software holds the data and the forms. It doesn’t hold your billing rules.
Progress billing software holds the job-cost ledger and prints the forms; the invoicing apps own the small-contractor end. Neither holds the judgment — this contract’s percent-complete method, that owner’s retention cap, the milestone definitions your PM negotiated.
We encode those — our AI does the reading: job-cost actuals, approved change orders, stored-materials evidence, contract PDFs. Your encoded rules do the judging — what is billable this period, per contract, per owner format.
Questions
Asked by controllers and owners.
The straight answers, before you book anything.
What’s holding your business back?
A workflow ready for automation. An AI product you want to build. A problem that has sat on the roadmap for years. Let’s talk about what it would take to solve it.
Talk to Zaigo

