Every decision your business makes is an outlay. Outlay watches each one live and makes sure you get it back.
Outlay puts a target cost on every line of the plan and reads what the floor actually makes, uses and runs. A slow oven shows its projected cost climbing while there is still a shift left to recover it, not as a number filed weeks later.
By the time the report names it, the run that lost the margin is already overspending in real time, hours or days earlier. Traditional standard costing only listens at month-end, so the warning lands as history. Outlay reads it as it forms, while there is still time to act.
The overspend forms during the run; the report only names it once it is spent.
Spend smeared across a month, never costed per run, per operation.
Whoever could have headed it off had moved on before the figure landed.
Outlay closes that loop to the length of a reading, not a reporting period, so the warning arrives while you can still act on it.
Inputs feed a box; it burns materials, labour and machine time as it runs and passes output to the next. The standard says what it should cost, the floor says what it is costing now, and from the rate so far Outlay projects where each box finishes. A box drifting over shows its projected outlay climbing while it still has time to run, and the downstream boxes inherit the slip before it reaches the customer.
Live · each box projects its outlay from the rate it is holding. Click a box for its read-out.
Because an operation class is one dimension across the whole estate, you can ask “every line, today, making or losing money” and get one answer.
This is the cockpit. The schedule arrives already costed; the bakery reports against it live. Each run is projected from the pace it is holding, so a slow one shows its projected end and projected cost drifting past target while the shift runs. The co-pilot watches every run and, the moment a projection breaches tolerance, reads out the variance forming, the likely cause and the move, owned by name.
Reads the plan and the captured actuals as the work runs, across the whole bakery.
Extrapolates the pace it is holding, so a breach shows as it forms, while you can still act, not at month-end.
The co-pilot reads the conditions behind the number and drafts the why, not just the what.
Sends the digest to whoever can head it off, with the recommended move attached.
Outline cards carry the target cost; filled cards carry the live cost and variance, with a dashed tail to the projected finish. Click any run for the co-pilot read-out. No mock-up: this is the cockpit your floor would run on.
Your system of record stays the system of record. Outlay reads from it and writes back through standard, audited interfaces. No parallel ledger, no side process, no workaround.
What runs, where, in what order. Timing drives cost, so timing leads.
Live plan-versus-actual per unit, per operation, per site.
Counts, times and usage, tapped in where the work happens. This is what makes it live.
Rebalance people and assets across operations and watch the projected downstream cost recompute before you commit.
Connect a system, import a spreadsheet, or be the system of record.
Spend is only worth committing if it earns its return. Outlay turns every run from a cost you reconcile later into a return you protect live.
Same plan, same floor, same people. The difference is that you see every outlay while you can still change its outcome.
Your plan costed operation by operation, your floor reporting live, and a co-pilot that flags the leak as it forms and routes it to the owner with a move attached. Catch it on the shift, not in next month’s accounts.