Field notes
What these engagements actually look like
These are illustrative scenarios, not customer case studies. We do not publish client names or invent metrics. What follows is the honest shape of the work: the mess we find, the sequence we follow, and the signals that tell us it worked.
A note on evidence. Every scenario below is a composite drawn from patterns we encounter repeatedly. No client is named, implied or fabricated, and no figure is presented as a measured customer result.
Multi-site operations
Purchase approvals across twenty-two sites
A multi-site operator where every site manager requested purchases over messaging, and two directors approved them from their phones. Nobody could reconstruct why a purchase had been approved, and finance discovered commitments only when invoices arrived.
Read the noteConstruction & real estate
Turning site photographs into a progress record
A developer whose site engineers reported progress as percentages in a weekly message, supported by photographs that were never linked to anything. Billing disputes were routine because progress claims could not be evidenced.
Read the noteDistribution & trading
From an ageing report to a collections workflow
A distributor with a long tail of accounts where receivables were reviewed monthly from an accounting export. Follow-up depended on which relationships each salesperson happened to remember, and disputes surfaced far too late to resolve cleanly.
Read the noteYour version of this
The first step is describing the mess accurately.
Bring us the process as it really runs — including the workarounds. That is the raw material of a Process Audit.