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.
My own platform: a plant looking after its own installations and a supplier servicing the ones it sold, both served by one asset register — because the hierarchy hangs off a company.
Kegs tracked through filling and washing, line stoppages explained to the minute, and data pipelines an engineer configures in a browser — .NET and Akka.NET at the edge, Rails for the analysis on top.
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 — off mod_perl and onto Rails, including a password migration no member ever noticed.
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.
A controller that reads the building's meter every few seconds and hands the charge point exactly the capacity that's spare — fast charging without tripping the main fuse.
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.
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.
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.