People
Does it have one clear owner, and can it run without depending on one person?
You find where value is trapped, name who owns the work, and set the number you plan to improve. Each week answers one question and ends at a gate.
Where are we losing capacity, speed or resilience?
| Workflow | Capacity | Decisions | Resilience |
|---|---|---|---|
| WIP and cost-to-complete | Yes | Yes | Yes |
| Change orders | Yes | Yes | No |
| Owner billing (pay apps) | Yes | No | Yes |
| Subcontractor payments | Yes | No | No |
| Lien waivers and retainage | No | No | Yes |
| Subcontractor compliance | No | No | No |
| Job cost and commitments | Yes | No | No |
| Labor and equipment coding | Yes | No | No |
| Month-end close | Yes | Yes | No |
| Cash forecast | No | Yes | Yes |
Does it have one clear owner, and can it run without depending on one person?
Does it have a clear outcome and a repeatable path to get there?
Can people and AI reliably get, understand and trust the data it needs?
Where are we losing capacity, decision speed or resilience?
Who owns each workflow, and how does it really run?
What should we do with each one?
Where are we starting from?
Any workflow with two or more “yes” answers on capacity, decisions or resilience makes the shortlist. Many contractors land on WIP, change orders, billing and cash forecasting.
| # | Workflow | What it covers |
|---|---|---|
| 1 | WIP and cost-to-complete | Each job’s real margin and cost to finish |
| 2 | Change orders | Getting extra work priced, approved and billed |
| 3 | Owner billing (pay apps) | The monthly pay app out on time with the right backup |
| 4 | Subcontractor payments | Sub invoices approved and paid correctly |
| 5 | Lien waivers and retainage | Right waiver before payment; retainage held and owed |
| 6 | Subcontractor compliance | Insurance, W-9 and licenses current before work or payment |
| 7 | Job cost and commitments | What’s spent and what’s committed on each job |
| 8 | Labor and equipment coding | Field hours and equipment charged to the right job and cost code |
| 9 | Month-end close | Closing the books on time with reconciled accounts |
| 10 | Cash forecast | Cash position for the coming weeks |
The workflow card is a one-page operating procedure. The owner writes it with the people who do the work, walking through one real example from last month.
AI tools need the same things a new hire needs: a clear outcome, the rules to follow, and what to do when something goes wrong. Your workflow cards hold all three.
First, is it worth changing? If not, keep it or retire it. If it is, two questions route it: is the process clear, and is the data ready?
Process clear, data ready. Ready to build now.
Process clear, data not ready. Get the data flowing first.
Process unclear, data ready. Redesign the process.
Neither is ready. Fix both. Takes the longest; often worth the most.
It works. Leave it alone.
Nobody uses the output. Stop doing it.
Pick the number that matches your biggest constraint. The same number follows you through every later step. Estimates from interviews almost always come in low, so measure real work.
| If your constraint is | Measure | Example |
|---|---|---|
| Capacity | Staff hours per month on the workflow | 60 hours a month across AP and project managers |
| Decision speed | Days from start to done (or days to close) | 18 days from invoice received to paid |
| Resilience | Workflows that stop if one person is out, and how long an error goes unnoticed | 3 of 5 workflows have no backup |
The same number carries through every step: measure it now, move it on one workflow, then across the function.
You know where capacity, speed and resilience are being lost.
To move on: You can state the cost and where you’ll start.
Owners, processes and data are ready, and one improved workflow is running.
To move on: The workflow runs from its card, not from memory, for one full cycle.
New workflows run in production, and your team can build the next one.
To move on: Your team ships a new workflow end to end on its own.
About two hours a week for four weeks from the finance leader, plus short conversations with the people closest to each workflow. Week 1 is a free workshop.
No. Week 3 tells you which workflows have data problems worth fixing, and which ones are ready as they are.
No. The 30 days work with the systems you already use. Anything that works gets a Keep verdict and is left alone.
No. Nothing we build writes back to your ERP. Your team keeps review and approval of every output.
You do. The owners, workflow cards, verdicts and starting number belong to your team, whether or not we work together on what comes next.
We go down the list of construction finance workflows together, ask three questions of each, and leave you with a shortlist and the reason each one made it.
No cost and no commitment to the full 30 days.