Switch to progress billing tied to verifiable milestones. That's the fix. If you're waiting until the end of a job to collect the bulk of what you're owed, you've built your entire cash position around the moment you have the least leverage — the moment the work is done and the client's motivation to pay has evaporated.
Lump-sum billing feels clean on paper. One price, one invoice, one payment. But the structure is backloaded by design, and every dollar you haven't collected is a dollar you've effectively loaned the client at zero interest, secured by nothing but goodwill and a signature.
Where lump sum actually hurts you
The problem isn't the total number. It's *when* the money moves relative to *when* you spend it.
On a lump-sum job you carry the material costs, the labor, the equipment, and the overhead out of pocket for the entire duration. You're the bank. And the day you finish is the day your exposure peaks — you've spent everything and collected little to nothing. That's the exact moment a client decides the tile grout looks off, or that they want to "hold a little back until we're sure."
Now you're negotiating from behind. The work is complete, so your only remaining leverage is threatening a lien or a lawsuit that costs you more than the holdback. Clients who slow-pay know this. Some count on it.
The last 20% of a lump-sum contract is where 100% of the collection fights happen — because that's the only money the client still controls.— General contractor, commercial buildouts
What progress billing changes structurally
Progress billing breaks the job into defined stages, each with its own payment due when that stage is verifiably complete. Demo done, draw released. Rough-in inspected, draw released. Drywall hung, draw released.
This does two things. First, it keeps your cash position roughly flat instead of deeply negative — you're getting reimbursed as you spend, not months later. Second, and more important, it keeps leverage on your side at every phase. If a client won't fund the next milestone, you stop before you've sunk another dollar into their project. You never end up with $40,000 of your money buried in a job and nothing to show for it but an unpaid final invoice.
The key word is *verifiable*. Milestones only protect you if both sides agree, in advance and in writing, what "complete" means for each stage. Vague milestones — "framing mostly done" — just move the argument, they don't end it.
Make the milestones enforceable, not just written
A progress schedule in a contract is a start, but a schedule alone still relies on the client choosing to cut a check when you hit each mark. That's the same trust gap that sinks lump-sum jobs, just spread across more invoices.
The stronger version is milestone-based escrow: the client funds each stage before the work begins, and the money releases automatically when the agreed deliverable is verified. The funds already exist — they're committed and sitting in a neutral holding account — so there's no "the check is coming" phase and no reason to chase. You do the work, the milestone clears, the money moves. Your exposure at any point is capped at a single stage instead of the whole contract.
That structure turns your payment terms from a promise into a mechanism. And a mechanism doesn't forget, doesn't stall, and doesn't wait until the job's done to develop second thoughts.
If you're rebuilding how your jobs get funded, it's worth seeing how milestone escrow maps onto the kind of work you actually run.