Case file 005 · Internal · Everywhere we work

The Client Is Us

Every internal tool is a scar with a version number. Here are ours.

AI agents · automation · our own tooling

The brief

We are the smallest company in this industry. To compete with the large firms, we cannot hire our way out of problems. So we build our way out, and we are our own most demanding client.

The file

1. We built a vault for multi-factor codes. It was not on a roadmap. We built it because we kept locking ourselves out of things.
2. At 03:01 every morning an automated report tells us one of our systems has no configuration changes and is healthy. It is the only correspondent that wants nothing from us. We look forward to it more than is reasonable.
3. Once a week an automation platform emails to say one of our flows has failed. Just one. Never which one. Never why. Like a partner saying "it's fine" and going to bed. We built our own monitoring.
4. A meeting recording from May expired, deleted itself, and then emailed to say it had. Most of our systems are quietly operated by previous versions of people, including previous versions of us.

What we did

• A shared team memory: every fact we learn about a client's systems is written down once, with a date and a source, and marked stale when it might no longer be true. Dead ends are recorded so nobody tries them twice.
• AI agents in the delivery loop: they draft, test, check configuration against code every night and flag drift before a client notices it.
• Credentials kept in a vault, never in documents, chats or emails.
• One board that matches the code, reconciled regularly, so "done" means done.

Outcome

A small team that delivers like a large one, and remembers more than any of us individually. It is the same toolkit we bring to every client project.

We did not build this because it was clever. We built it because we were tired.

(Clients, colleagues and numbers stripped out. The dysfunction is ours to share; theirs isn't.)