Insights

Notes on building operational systems

Practical writing about the systems behind day-to-day operations — what breaks, what lasts, and what is worth building.

The point at which a spreadsheet stops being a tool and starts being infrastructure — and the four signs it has already happened.

Most integrations do not fail on launch day. They fail three months later, and almost always for the same handful of reasons.

Not every repetitive task should be automated. A simple way to decide which ones pay for themselves and which ones will not.

Have a process that is not working?

Start with a conversation. We will help you scope the problem before anything gets built.