Economic symptom
Four hours of preparation per case, three information handoffs, two days waiting for approval and manually triggered invoicing.
Composite example · no client data
What leadership gets in ten days.
This example combines recurring field patterns. Names, figures and circumstances are fictional or composite, so no client can be identified.
Multi-site B2B services company · 140 employees
Flow studied
Request → qualification → collection → preparation → approval → delivery → invoicing.
Constraint
Information reconstruction and approval between preparation and delivery concentrate waiting time and delay invoicing.
Recommended decision
Define one source of truth, clarify three exception thresholds, instrument lead time, integrate the required data, then automate only stable follow-ups and controls.
Illustrative baseline
- 4 h preparation per case
- 3 information handoffs
- 2 days waiting for approval
- Manually triggered invoicing
Flow 90 plan
- 1Days 1–15: baseline, roles and rules
- 2Days 16–35: simplification and source of truth
- 3Days 36–60: integrations and targeted automation
- 4Days 61–90: adoption, supervision and measurement
Success criterion
Move approval from two days to under eight hours and preparation from four hours to under 2.5 hours, without reducing quality.
This is an illustrative target, not a general promise. Every engagement starts with a baseline and validated assumptions.