Clients are described by sector rather than name. What each system does, and why it had to be built that way, is the part worth reading anyway.
Kegs tracked through filling and washing, line stoppages explained to the minute, and data pipelines an engineer configures in a browser instead of commissioning.
Every vehicle coming off the line gets its wheel geometry and headlight aim measured and adjusted to spec, with operators guided by live readings as they turn the adjusters.
One map of a mixed fleet, showing not just where each vessel is but what its onboard systems are reporting — fuel, machinery state, running hours — plus who is aboard.
Member records, board composition and a shared calendar for a three-tier federation — rebuilt off mod_perl, including a password migration no member ever noticed.
An inventory of every file across many Windows servers — what's there, what changed, what's duplicated, and who can actually get to it once group membership is resolved.
The systems a two-factor authentication vendor runs itself: issuing keys and certificates under audit, delivering passcodes by SMS worldwide, and tracking who is licensed for what.
Maintenance and asset management from two directions at once — a plant looking after its own installations, and a supplier servicing the ones it sold — in a single application.
Paper questionnaires and hand-calculated scores replaced by a link the client fills in and results that compute themselves — and a new instrument needs no code changes to the core.