EidralOperations Engine
Chapter 02

The audit: we learn how the work actually moves

4 weeks on site with the operations team. Process owners get shadowed rather than surveyed, because the shadow spreadsheet and the approval that happens in a hallway never come up on a call.

What it produces

A process and time map, a controls register, the exception taxonomy in your team's own wording, a volume baseline pulled from the systems rather than estimated, and a build plan signed by the people who run the work. $15–25k, credited in full against a build signed within 90 days.

Audit input 01 — Interviews

19 sessions with 15 people. Every session transcribed and tagged against the workflow it describes.

RoleSessionsMinutes eachFocus
Service coordinators590Queue work, which exceptions repeat, and the spreadsheets nobody documented
Warehouse leads460Pick, pack and the gap between the system and the floor
Procurement360Vendor onboarding packet, expiry tracking, supplier performance
Customer service manager460Routing rules, escalation paths, ticket taxonomy
COO and site managers345Service levels, expedite policy, what gets escalated
Audit input 02 — Documentation

46 sources ingested, indexed and made queryable. The working spreadsheets matter most, because they are where the real process lives when the SOP has drifted.

SOPs and work instructions14
Vendor onboarding requirements6
Service level agreements7
Returns and warranty policy5
Working spreadsheets found in use14
Audit input 03 — Software

11 systems mapped, including the ones nobody lists on an architecture diagram.

Scope
Systems mapped
11
Workflows analysed
15
Exceptions sampled
520
Manual hours per year
14,700

In-scope process work, not total department labour

Where the hours come from
DriverVolumeHours/yr
Customer service tickets34,000 at 11 min6,233
Order exceptions8,900 at 24 min3,560
Vendor onboarding210 vendors at 5.5 hrs1,155
Returns disposition4,200 at 18 min1,260
Intake routing and triage12,000 requests at 7 min1,400
Cross-system reconciliation12 cycles at 91 hrs, WMS against ERP1,092
Total in scope14,700
Of 14,700 manual hours a year
66% carried
  • Carried by agents9,702 hrs66%
  • Stays with people4,998 hrs34%

4,998 hours a year remain manual, and should: judgement calls, genuine exceptions, and the relationships that need a person on the other end. The two shares are complements of one another, so they sum to 100 by construction.

Priority workflows
P1

Order exception detection

74% automatable$224k

Catching a short ship before it leaves the dock is worth more than explaining it afterwards.

P2

Helpdesk triage

72% automatable$186k

Highest ticket volume of the five workflows and the most repetitive.

P3

Vendor onboarding

69% automatable$132k

Insurance certificates, tax forms and banking details, checked against what the packet requires.

P4

Intake routing

77% automatable$108k

Requests arrive in three shared inboxes and get read twice before anyone owns them.

P5

Returns disposition

61% automatable$84k

Lowest automatable share of the five because condition assessment stays with a person.

The five sum to $734k, the same modelled annual value shown in chapter 01. Bars are each workflow's value against the largest of the five.

Implementation timeline
W1
W4
W8
W12
W16
W20
  1. Audit · 4 weeks
  2. P1 Order exception detection
  3. P2 Helpdesk triage
  4. P3 Vendor onboarding
  5. P4 Intake routing
  6. P5 Returns disposition
  7. Operate · ongoing

Audit 4 weeks, build 12–14 weeks, then continuous operation. Workflows overlap because the connector work for one is usually most of the connector work for the next.

Illustrative

Session counts, document counts and hours are modelled against the basis company, not recorded from an engagement. The method is real; the volumes are what a 95-person operations function at that size would produce.