What is your worst workflow costing you? The math contractors never run

Contractors price everything. Concrete by the yard, steel by the ton, labor by the crew-hour — nobody signs a sub without knowing the number. And yet almost every contractor we talk to is running an office workflow — pay-app assembly, job-cost reconciliation, waiver chasing, month-end close — that has never once been priced. It's just “what the office does.” This article is the five-minute version of pricing it. (If you'd rather have a tool do the arithmetic, we built a free 60-second calculator that runs this exact math.)

The formula

The direct cost of a manual workflow is four numbers multiplied together:

people involved × hours per person per week × 52 × loaded hourly rate

Three of those numbers get systematically lowballed, so be honest about each:

• People involved.Not just the person who “owns” the workflow. Count everyone it touches: the PM who compiles inputs, the coordinator who chases documents, the controller who reviews and re-fixes, the person who covers it during vacations. Most workflows named after one person actually consume pieces of three or four.
• Hours per week.Include the fragments — the fifteen-minute status checks, the re-work when an export was stale, the follow-up emails. Time studies in office work consistently find people underestimate recurring task time because it arrives in slivers. If a task “takes about an hour” but happens across Monday, Wednesday, and Friday with interruptions, it's consuming more than an hour of productive capacity.
• Loaded rate, not salary rate. A salary divided by 2,080 hours is not what an hour costs you. Payroll taxes, health insurance, retirement match, PTO, software seats, and office overhead typically put the loaded cost at 1.25–1.4× base wages — a standard range any CFO will recognize. A $70,000 accountant is roughly a $45–47/hour cost, not $33.65.

Worked examples (hypothetical)

These are illustrative hypotheticals, not client results — the point is the shape of the math at different firm sizes. Run your own numbers before believing any of them.

A $25M specialty sub: monthly pay applications

Hypothetically: one billing coordinator spends 12 hours/week assembling and correcting pay apps, and a PM contributes 3 hours/week compiling backup. Loaded rates of $42 and $58 respectively.

(12 × 52 × $42) + (3 × 52 × $58) = $26,208 + $9,048 = ≈ $35,000/year— for one workflow, at a firm where that's real margin. And that's before the cost of the pay app that goes in late or wrong, which we'll get to.

A $75M GC: job-cost reconciliation and close

Hypothetically: a controller spends 15 hours/week on Sage-to-Excel job-cost assembly and reconciliation, a staff accountant spends 20 hours/week, and two PMs each lose 2 hours/week feeding it. Loaded rates of $75, $48, and $65.

(15 × 52 × $75) + (20 × 52 × $48) + (4 × 52 × $65) = $58,500 + $49,920 + $13,520 = ≈ $122,000/year. That's more than a full salaried position, spent annually on moving numbers between systems that both already contain them.

A $150M builder: waiver and COI compliance tracking

Hypothetically: two AP/compliance staff spend a combined 25 hours/week logging, matching, and chasing lien waivers and COIs across a large sub base, with a controller spending 3 hours/week on exceptions and escalations. Loaded rates of $44 and $80.

(25 × 52 × $44) + (3 × 52 × $80) = $57,200 + $12,480 = ≈ $70,000/year — to maintain a tracking function whose failure mode (a recorded lien, a denied claim) costs multiples of that in a single event.

The costs the formula doesn't catch

The hours math is the floor, not the total. Three costs sit on top of it and are usually bigger:

• Rejected draws and payment delays.A pay application kicked back for a math error or missing backup doesn't just cost the re-work — it slips your payment by a draw cycle. On a $400K monthly draw, a 30-day slip is roughly $2,300 in financing cost at an 7% line rate, plus the sub payments you're now floating. Manual assembly is where rejection-grade errors come from; error rates rise with fatigue and volume in exactly the way automated checks don't. (Our pay-app automation pagecovers this workflow specifically — it's the one our founder automated inside a national home builder, where the manual version consumed 18 hours a week before the build replaced it.)
• Turnover of the people you can least afford to lose.The person doing eight hours of copy-paste per week is usually your most conscientious office employee — that's why they were given the tedious critical thing. They are also exactly the person with options. When they leave, you don't just pay recruiting and training costs; you discover the workflow lived in their head, and the next three closes are late. Grinding your best admin people on robot work is how firms convert their most reliable staff into their most expensive vacancy.
• Decisions made on stale numbers.If job-cost reporting takes two weeks to assemble, every steering decision — pull back on a bid, confront a fading job, chase a change order — is made against a picture that's two weeks old. This cost never appears on any ledger, and it's routinely the largest one.

How to pick which workflow to automate first

Run the formula on your three or four worst workflows, then rank them — but not purely by dollars. The first automation project should score well on all four of these:

• High annual cost. The formula output. Below roughly a half-FTE of loaded cost, automation rarely pencils as a standalone build; above a full FTE, it almost always does.
• High rule content, low judgment content. The best candidates are workflows where a competent person follows the same steps every cycle: extract, match, format, send. Workflows that are mostly negotiation or judgment automate poorly — automate the assembly around the judgment instead.
• Stable inputs. Data coming from systems you control (Sage, Procore, your bank, a consistent inbox) automates cleanly. Data arriving as photographed napkins does not — fix the intake first.
• A painful failure mode. Between two workflows of equal cost, pick the one whose errors are expensive — rejected draws, missed waivers, late WIP to the surety. You capture the hours savings and retire the risk.

In practice, that scoring usually points at pay applications, job-cost/month-end assembly, or waiver-and-COI tracking — which is why those are the workflows we've built our fixed-price offers around.

Run your number

The whole argument of this article compresses to one instruction: multiply four numbers you already know. If you want it done for you, the workflow cost calculatortakes sixty seconds, runs the same formula with a proper loaded-rate assumption, and gives you an annual figure you can put in front of a partner or CFO. Most people who run it are not surprised that the number exists — they're surprised that it has commas in it and has been recurring, silently, every year they've been in business.