50% deposit, 50% on completion means you are financing 100% of the labor from the moment the deposit runs out until the day the client decides the job is "done." On a three-week job, that's often two full weeks where your crew, your materials, and your overhead are all in the ground and the only money you've collected is gone.

The fix is not a bigger deposit. It's a payment that lands in the middle. Split the back half into milestone releases so the client pays as the work progresses — not in one lump at the end where they hold all the leverage and you hold all the risk.

Why the two-payment split fails you specifically

The deposit covers your upfront materials and the first stretch of labor. Fine. But the second half sitting at "completion" creates a gap the exact size of the job. The longer the project, the longer you carry unpaid work.

And "when it's done" is not a date. It's a judgment call the client owns. Every punch-list item, every "can you just also," every delayed walkthrough is now something they can hold your final payment hostage against. You've handed them a reason to slow-walk the close and a discount they can negotiate for after the work is already installed.

The deeper problem: at no point in a two-payment structure are you square. You're either owed the deposit or owed the balance. There's no moment mid-job where the paid work and the collected money line up.

If your only two checkpoints are 'started' and 'finished,' you've built your cash flow around the one moment you have the least control over.— operational note for project-based trades

Restructure the back half into stages

Keep the deposit. Then break the remaining balance into releases tied to observable milestones — not calendar dates, not percentages of time, but points a client can look at and verify.

A framing job: deposit, then release at rough-in complete, release at inspection passed, release at final. A kitchen: deposit, demo complete, cabinets set, countertops in, final. Pick the natural checkpoints that already exist in how you sequence the work.

The rule that protects you: never let the unpaid work exceed the value of one stage. When rough-in is done, rough-in gets paid before framing the next section starts. You're always carrying one milestone of exposure — never the whole job.

Make the release automatic, not a phone call

Milestones only protect you if the money actually moves when the stage clears. If each release requires you to invoice, follow up, and chase, you've just added four collection headaches instead of one.

This is where holding funds in escrow against defined milestones does the structural work. The client funds the stage up front. The money sits committed — they can see the work is coming, you can see the payment is real. When the milestone is verified, the release happens against the agreed trigger, not against a client's mood on a Friday afternoon.

That turns "when it's done" into a series of small, defined, already-funded gates. The client stops carrying the fear of paying for work they can't see. You stop carrying weeks of unpaid labor waiting on a walkthrough.

The version that fits your jobs

The right number of milestones depends on your ticket size and project length. A two-day job might need one middle release. A six-week build needs four or five. The point is the same: no single unpaid stage should ever be large enough to sink a month.

If you want to see how milestone releases and funded escrow get set up for the kind of work you run, the contractor plans lay out the structure.