Progress Billing01

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.

  • AI implementation services
  • Your billing rules, encoded per contract
  • Every bill on cycle, in the owner’s format
  • Exceptions reach a human queue

Official services partner of the platforms defining AI

NVIDIAAnthropic
Peter Enestrom, founder of Zaigo

Every engagement is led personally by Peter Enestrom and the Zaigo AI & engineering team

YaleColumbia UniversityMicrosoft
The billing-cycle scramble01

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 costs02

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.

Full FridayAssembling each period’s pay apps from job-cost exports, spreadsheets, and email
Weeks laterWhen the cash arrives against a bill that went out days late
One personWho carried each contract’s billing rules — method, frequency, retention cap, format

From anonymized engagements — general contractors and specialty subs, $10–100M in revenue

How it works03

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.

  1. 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.

    First job
  2. 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.

    Per contract
  3. 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.

    Every cycle
Not another tool

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.

In production
On cycleEvery progress bill assembled from live job data on the billing calendar — not a full Friday late
Exception queueWhere missing backup, unpriced change orders, and met retention-release conditions land — reviewed by a person
One rule setPer contract: percent-complete method or milestones, frequency, retention cap, backup, owner format
Compressing the invoicing cycle is getting paid weeks sooner.
Operating partner, seven portcos, sub-$250M each
Peter Enestrom, founder of Zaigo
Who builds it

Led by Peter Enestrom.

Founder — leads AI & Engineering

Pete Enestrom

Every engagement is led personally by Pete, working with the Zaigo AI & engineering team from the two-week audit through the production handover. The person who scopes the work is the person who builds it.

Education
Yale & ColumbiaGraduate
Background
Microsoft & IntelFormer
Experience
Exited FounderVenture-Backed

Background

Questions04

Asked by controllers and owners.

The straight answers, before you book anything.

Construction progress billing is invoicing for work in progress: instead of one invoice at completion, the contractor bills the owner at regular intervals — usually monthly — for work completed and materials in place, less a retained percentage held until closeout. Each bill is measured against the contract’s schedule of values, so payment follows the job and the contractor is not financing the work. On the financial statements, cumulative progress billings are set against costs incurred to show whether a job is over- or under-billed.

Milestone billing is progress billing with a different measuring stick. Under a percent-complete method, each bill reflects the share of the contract completed in the period, measured against the schedule of values. Under milestone billing, amounts become billable only when a defined event is reached — a passed inspection, a delivered phase, a signed acceptance. Both bill against the same contract; what differs is the trigger and the evidence each bill has to carry.

AIA billing is a standard format for progress billing, not a different process. Progress billing is the cycle: billing the owner periodically for work in place against the schedule of values. AIA billing runs that cycle on the AIA-style G702 application and G703 continuation sheet, with defined lines for change orders, stored materials, and retainage. Many owners expect the AIA format even when the contract is not an AIA document — the billing rules still come from the contract.

It is the accounting term for over-billing: cumulative progress billings on a job exceed the costs incurred plus recognized profit to date, and the difference sits on the balance sheet as a liability. The opposite — costs in excess of billings — is under-billing, an asset. Both surface on the WIP schedule, which is why over- or under-billing is usually discovered there instead of in the period it happened.

Monthly is the norm on commercial work — one pay application per period, on the cutoff date the contract specifies. The contract controls: some owners fix a cutoff with payment due a set number of days later, and a bill that misses the cutoff can slide into the next cycle. Whatever the cadence, the discipline that matters is billing on cycle every period — a bill out days late is cash that arrives weeks later.

Start with one workflow.

Tell us where your team loses hours. We will come back with a straight answer on whether AI can help, what it would take, and what it would pay.