You Did The Work.
Did You Get Paid For All Of It?

Dear Owner,

It's a Tuesday afternoon, about four o'clock.

The GC's superintendent walks over to your foreman on the third floor and points at a wall.

The feeders have to move. Something about the medical gas rough-in landing where your conduit was supposed to run. He doesn't hand anybody a piece of paper. He says: "Can you guys take care of that? We'll square it up."

Your foreman says yes.

Because that's the job.

Two men spend a day and a half on it. Nine hundred dollars of material comes off the truck. It goes in the daily log, because your foreman is good at his job and logs everything.

And that is where it stops.

No change order gets written. Nobody in the office hears the word "extra."

Three weeks later your PM is closing out the month. He's looking at budget lines. Every hour of that work is sitting in the cost column of a job where nothing on the revenue side ever moved.

You paid for it. All of it. Payroll ran on Friday like it always does.

You just never billed for it.

Now multiply that Tuesday by a year

Here's the part that surprises people: nobody did anything wrong.

The super wasn't trying to steal from you. Your foreman did exactly what a good foreman does — he kept the job moving. Your PM never saw a directive, so there was nothing for him to process. Your controller reconciled what was billed, and every number she had was right.

Everyone was correct.
And the money still walked out the door.

Because the work was recorded in one system. The money lives in another. And the bridge between them is a human being, working by hand, at the end of a long day, against a deadline he can't see.

That's not a people problem.

The problem nobody owns

Stop and look at what is actually missing on that job.

The work isn't missing. It got built — there's conduit in that wall right now.

The records aren't missing either. The directive happened. The daily log entry exists. The labour hours are in your payroll and the material is on an invoice.

Every single piece of it is sitting in your company somewhere.

What's missing is the connection between them.

No system owns that connection. Your field software knows what happened. Accounting knows what got billed. Neither one is asked the only question that matters:

what was directed, performed and costed — and never billed?

Nobody is failing at their job. The question simply isn't anybody's job.

And it doesn't get asked once. It goes unasked every week, on every job, in the same nine places:

• Verbal direction. Exactly the Tuesday above. The crew builds it, nothing becomes a change order.
• The notice window. Your contract gives you days to give written notice. The paperwork shows up after it closed.
• Approved and never invoiced. The change order is signed, sitting in a folder. It never reaches a pay application line.
• Signed tickets that never convert. A field ticket with the super's signature on it — in a truck, a folder, somebody's phone.
• Scope that grew without anyone deciding it had. A little more each week, none of it big enough on its own to stop and write up.
• Waivers that release claims nobody submitted. Every progress payment signs something away. Sometimes it signs away work you were owed.
• Back charges accepted without being tested. It came off the payment, somebody assumed it was justified, and nobody went back to check.
• Retainage that quietly stops being chased. The job ended, the file closed, and the last few percent stayed where it was.
• Closeout that ends the conversation early. Open commercial items still on the table when the paperwork says finished.

Every one of those is money you have already spent. The payroll ran. The material shipped. The only thing missing is the invoice.

Recognise more than one of those? Book a 20-minute Profit Leak Review →

And unlike every other money problem, this one has a clock on it

A bad estimate you fix on the next bid. A slow-paying GC you chase.

This is different.

This expires.

Notice windows close in days. Not months.

Lien and bond deadlines are statutory. They don't care why the paperwork was late.

Every progress payment waiver you sign releases whatever wasn't submitted by that date.

And after final payment, the conversation is simply over.

There is no appeal to a job that closed clean.

Which runs against instinct: the projects worth looking at first are the ones closest to closeout — not the ones that just started. The job you're about to finish is the job with the least time left on it.

The longer you wait, the more expensive the problem can become

Missing revenue is one problem.

Discovering it months later can create a second one.

Because now you may have to go back to the customer and say: "We found work from this project that was never billed."

Even when the work was entirely legitimate, that conversation can be uncomfortable.

He may ask why it wasn't identified earlier. The invoice may be questioned line by line. What was simply an internal handoff gap can start to look, from his side of the table, like poor administration.

And on an account that matters, the cost may not stop at the invoice.

An unexpected billing dispute at the end of one project can affect how a customer feels about awarding the next one. Nothing has to follow from it. But you already know which of your customers you would rather not have that conversation with.

The missing invoice may not be the only thing it costs you.

It is worth following the whole chain once, because each link is small and the end of it is not:

Not every link follows from the one before it. Plenty of late items get paid without a word. But each step down that list costs more to fix than the step above it — and the first two have already happened before anybody notices.

Which is the real argument for looking early.

Not because late recovery is impossible. Plenty of it is entirely recoverable. But a gap you find while the job is still running is a change order conversation — and the same gap found eight months later is a claim conversation.

Same money. Very different meeting.

While the work is fresh, the crew that did it is still on the job, the records are still open and nobody has to be told anything awkward. That is when this is easy to handle professionally.

What happens when we actually look

You pick three projects. Any three — I'd suggest the ones nearest closeout.

You export the files we agree on and send them over. That's the entire data path. There is no integration, no login for your team, nothing installed, and nothing of mine can write to your systems, because no such connection exists.

Then I go looking for one specific thing: work that was directed, performed and costed, with no matching change order and no pay application line.

Every candidate gets tied to the documents that prove it.

Then I try to kill it.

Eight separate checks. Every one designed to disprove the finding before you ever see it.

Most candidates die there.

That's the point. What survives is what you can actually stand behind.

Here's what one page of the result looks like:

POTENTIAL REVENUE AT RISK   $30,700
  basis: sum of linked labour and material records:
         LR-991 $21,400, MR-552 $9,300
CONFIDENCE                  95/100 (HIGH)

WHY WE FLAGGED IT:
  1. Field Directive FD-118 (2026-05-04) — proceed with relocation of the
     level 3 electrical room feeders. (signed by GC superintendent)
  2. Daily Log 2026-05-11 confirms the work was performed in the field.
  3. Field Ticket FT-207 (2026-05-13) confirms the work was performed.
  4. Cost records linked (2): $21,400, $9,300.
  5. No approved change order matches this scope.
  6. No pay application line covers this scope.

Look closely at what that dollar figure is — and what it isn't.

It's the sum of your own cost records. Two of them, named, that your controller can pull up while you're both looking at the page.

It is not my estimate of what the work was probably worth. No cost records, no number: the finding says INSUFFICIENT EVIDENCE and states no value at all.

And those eight checks? Every one is reported on every finding — including the ones that pass:

• Was it already approved?
• Is it inside base scope?
• Has it already been invoiced?
• Is the evidence duplicated?
• Was it waived?
• Was notice given inside the window?
• Does the chronology hold?
• Is there an offsetting back-charge?

Eight, because that's how many there are.

Your controller can reproduce every confidence score with a pen and a printout. The detection engine contains no model call anywhere in it. Every conclusion is a rule applied to a structured record.

There's exactly one reason that matters.

You're the one who has to sit across from your GC and defend the number. A finding you can't audit is a finding you can't use.

Want to see this run against your projects? Book a 20-minute Profit Leak Review →

What lands on your desk on day fourteen

• Three projects examined end to end, chosen by you
• Every finding on one page, with the supporting documents named and all eight disproof checks shown — passes included
• A dollar figure built only from your own cost records
• An internal review file, a package your GC could actually read, and a note your counsel could use — for each finding
• A written record of what was examined and ruled out, so you know what the audit closed as well as what it opened
• A deadline register showing which window closes first, with the findings ordered by recoverable value
• Sixty minutes on day fourteen with whoever owns the numbers

Your team spends about two hours on this in total. The export is the only real work, and I'd rather name that than pretend it's free.

What it costs

If the audit doesn't identify recoverable exposure worth more than the fee, the audit is free. You keep the report. I keep nothing. Honored without argument and without negotiation.

Read that again, because it's the whole deal:

I only get paid if I find more than I cost.

The price is published and it's the same for everyone. It doesn't scale with your revenue. There's no custom quote to wait for and no proposal process to sit through.

The five questions I get asked

Seven things this is not

• Not a Procore replacement, an ERP, accounting software or a chatbot
• Not an integration — nothing of mine connects to your systems
• Not a claims service; I never contact your general contractor
• Not legal advice, and I don't negotiate or collect
• Not for records that are paper or scan-only — I can't read those yet
• Not for projects in active litigation
• Not a retainer and not a subscription — one engagement, one price, one report

Everything on this page is checkable

The price is published. The guarantee costs me and not you. The example above is labelled as invented, because it is. And the arithmetic behind every score can be reproduced by your own controller without me in the room.

That's deliberate. You're being asked to hand project documents to someone you haven't met — so nothing here asks you to take my word for anything.

Where this leaves you

The work is already built. The payroll already ran. The material is already on the job.

Every one of those dollars left your account weeks ago, and some of them are sitting in a daily log with no invoice attached to them.

Meanwhile the notice windows keep closing, the waivers keep getting signed, and the jobs keep closing out clean.

You can find out what that's worth on three of your projects — or you can find out nothing, which is also a decision, just a quieter one.

The next step takes twenty minutes. You describe how change orders actually move through your company — not how the org chart says they move — and I'll tell you whether there's anything here worth your time.

No slides. No pitch. If it isn't a fit, you'll hear that on the call.

Not ready to put a time in the diary? Ask me for the audit brief instead — the same three details, and you get what I ask for, what you get back and what happens on each of the fourteen days. No call, and no follow-up you didn't ask for.