What systems mean to us

The word "systems" is in our name. This is not incidental. It is the argument of the studio.

A system is not a piece of software. A system is what happens when a set of people, forms, rules, and tools run together for long enough that the output becomes predictable. Every company — every operation — already has systems. The question is whether those systems are legible.

Most of the operations we work with have systems that are illegible to the people running them. The CFO cannot see, on any given Monday, what the company produced on the prior Friday. The operations director cannot see which depot is short on stock until a driver complains. The founder cannot see which of the three acquisitions is actually profitable. The system exists — it is producing real outputs every day — but no one inside the system can read it.

Our job is to make the system legible.

Sometimes that means writing new software. Often it means writing less software than the client expected. Occasionally it means writing no software at all, and instead redrawing the form that the driver fills out at the gate so the dispatcher upstream can actually use it.

We are named for this because it is the most important thing we do. Custom software is a consequence of the work, not the point of the work. The point is the system.