Five separate worked examples / Operations
Accepted work comes before the money calculation.
The same 40 onboardings take 160 staff-hours rather than 200. Of the 40 released hours, 24 are reused for six extra onboardings; 16 receive no financial credit.
- One time budget
160 original + 24 reused + 16 remaining = 200 staff-hours.
- Real conditions
Demand, scheduling and downstream quality must support the six additional starts.
- Count margin once
Once delivered: $12,000 at 40% margin is $4,800 before AI costs. Staff cost is already in that margin.
One hypothetical month · one 200 staff-hour budget
original work24 h
reused16 h
unassigned
160 h original work · 24 h reused · 16 h unassigned (one 200 h budget)
- 40 onboardings × 5 h → 4 h each
- 200 h → 160 h
- 24 reused hours ÷ 4 hours each
- 6 additional accepted starts
- Additional work, once delivered
- 6 × $2,000 = $12,000
- At an assumed 40% margin
- $4,800 gross profit, before AI costs
160 + 24 + 16 = 200 staff-hours. Demand, scheduling and downstream quality must hold. Allocated staff cost is already inside the margin; the same 40 hours are not also payroll savings.
Open the detail
Keep the setup, assumptions and checks in view.
How did a cleaner handoff release 40 hours?
How did a cleaner handoff release 40 hours?
The same accepted work required fewer staff hours.
A useful onboarding workflow shows what must exist before work moves forward: customer information, required documents, an assigned owner, the next action and the exception status. If a required input is missing, it goes back to the responsible person first. That prevents the next employee from discovering the problem halfway through the job.
The improvement comes from an approved checklist, complete inputs, clearer handoffs and early exception review. The four-hour figure includes the required review and any rework that remains, so the time has not just moved to another desk.
AI may help organize the queue or flag a missing item. It should not silently mark an onboarding complete. The responsible employee confirms whether the file is complete and acceptable, and the 40 hours remain capacity until someone assigns them.
Owner decision: verify that the four-hour process produces the same accepted onboarding standard, not merely a faster incomplete handoff. Then review the most common rework causes and fix the earliest handoff where each one appears.
Who owns each part of the handoff
- AI, where used
- Organizes the queue and flags a missing input. It does not decide that the file is acceptable.
- Responsible employee
- Confirms the file is complete and acceptable before it moves.
- Owner of the missing item
- Supplies it by the due date shown on the record.
- Operations leader
- Sets the acceptance standard, reviews exceptions and fixes recurring causes at their source.
How to test that four hours is real
- Compare the same kind of onboarding and the same acceptance standard.
- Log the whole effort, including review, chasing, exceptions and rework.
- Follow the files downstream, so problems pushed to the next team go back into the count.
How do 40 hours become 6 additional onboardings?
How do 40 hours become 6 additional onboardings?
| Use | Math | Hours |
|---|---|---|
| Original onboardings | 40 × 4 h | 160 |
| Additional onboardings | 6 × 4 h | 24 |
| Remaining, no financial credit | 40 − 24 | 16 |
| Total month | 160 + 24 + 16 | 200 |
Capacity only becomes value when demand and quality allow it.
The example reuses 24 of the 40 freed hours. At 4 hours each, 24 ÷ 4 = 6 additional onboardings, so accepted starts move from 40 to 46. Saving time does not create those six by itself. They need real customers, a workable schedule and accepted completion.
- Six customers are waiting. With fewer waiting, there are fewer starts, and the unused hours stay unassigned.
- Staff can be scheduled. The freed time has to exist in the right people’s weeks, not just as a total on a spreadsheet.
- Downstream teams hold quality. If the next team cannot absorb six more, the queue has only moved.
The remaining 16 hours may become room for exceptions, training or process improvement. Whatever they are used for, this example gives them no dollar value.
Owner decision: confirm the queue and downstream capacity before allocating the 24 hours to more onboardings, and name who is responsible for them.
What “46 accepted starts” does and does not say
It says 40 original plus 6 additional onboardings met the acceptance standard to begin. It does not say that 46 customers have been fully served, or that the money has arrived. Those are later events with their own records.
How does capacity become delivered value?
How does capacity become delivered value?
- Accepted start6 additional
- Completed and servedMust actually happen
- Delivered value6 × $2,000 = $12,000
- Gross profit$12,000 × 40% = $4,800
The six additional starts must reach delivery.
The illustration assumes each additional onboarding earns $2,000 when delivered: 6 × $2,000 = $12,000 of additional delivered value. At a 40% assumed gross margin, $12,000 × 40% = $4,800 of gross profit.
This is conditional. It depends on completing the onboardings, serving the customers and incurring costs at the assumed level. Because the 40% margin already includes allocated staff cost, the staff time is not deducted a second time. AI setup and running costs are not included, and no amount is assumed here. Take them from your own records before calling anything a return.
| Measure | Question |
|---|---|
| Accepted onboarding | Did it meet the same standard as the original 40? |
| Time to activation | Did customers get going sooner, later or at the same pace? |
| Rework | Did problems return further down the line? |
| Direct cost | Did costs stay near the assumed level? |
| Delivery completion | Was the work actually finished? |
Owner decision: measure accepted onboarding, time to activation, rework, direct cost and delivery completion before expanding the queue.
What must not be counted twice?
What must not be counted twice?
Released capacity is not avoided payroll by default.
The 40 hours freed from the original 40 onboardings are already used in the capacity model. Claiming those same hours as payroll savings would count them twice. No payroll expense disappears unless the company actually avoids a real expenditure, such as reducing paid hours or eliminating a role, and that would be a separate financial event needing separate evidence.
Allocated staff cost has a similar trap. It already sits inside the 40% margin, so it should not also be subtracted from the $4,800.
| Label | Example | What it is |
|---|---|---|
| Hours released | 40 h | Capacity |
| Additional accepted work | 6 onboardings | Output, if demand exists |
| Delivered value | $12,000 | Revenue, once delivered |
| Gross profit | $4,800 | Conditional, before AI costs |
| Actual AI cost | Your records | Not assumed here |
Owner decision: label each result correctly as hours released, additional accepted work, delivered value, gross profit and actual cost, and keep them separate in every report.
When could a payroll saving be real?
When the payroll actually falls, and the records show it. That is a decision about paid hours or roles, with its own evidence and its own effect on capacity. Those hours would no longer be available for additional onboardings, so the two stories cannot share them.