Case studies
Real departments, real numbers, measured on the client's own reporting rather than on ours. Client work is confidential by default, so most cases are described by industry and function. There is at least one here for every situation.
Tender-driven, where winning the mandate and executing it both decide the year. Sixty percent of the company licensed and trained. Fluency for the executives deciding, guardrails and policy, a diagnostic on the estimation and RFP response departments, and an aspiration with the first cases chosen to prove it.
Read the caseAn estimating department at capacity, in a business won through bidding. The diagnostic counted ten to fifteen thousand hours a year against the department's own volumes, two to three times what leadership had hoped for, and the build is deploying against it now.
Read the caseThousands of inbound containers a year and a team spending its whole week on coordination. A digital coordinator now owns the container lifecycle from supplier outreach to warehouse arrival. Includes the video.
Read the caseA new aircraft program arrived with one hundred and twenty thousand parts, and every one of them had to be classified before anyone could say which plant would make what, so no manufacturing plan existed at all. Two months of hand classification had cleared somewhere between ten and twenty thousand, and no amount of hiring was going to close the rest.
Read the caseA patient portal that already existed, already worked and had been paid for, with adoption stuck at about a third. The blocker was one manual step: linking each new profile to a record, by name, across a hundred thousand patients.
Read the caseA well-run operating framework spread across five disconnected tools, with the same figure appearing in several of them under two different definitions. A clerk that reads the sources, keeps one record and writes nothing without approval.
Read the caseForty leadership measures across seven departments and three plants, each site calculating them differently or not at all. Nothing central can be managed, or proved, until the numbers mean one thing.
Read the caseEvery one of these started with a process map, not a software choice. If your team is buried in coordination work, that is where the conversation begins.