Founding

Revuity Systems

Building an operational systems company

Economic consequence: Operating Leverage / Margin

Ink drawing of a small independent office early in the morning: one desk at a tall window with a laptop and papers, a pinboard of cards on the wall, a single chair and a plant in the corner.

Context

Revuity Systems is an operational systems company based in Los Angeles. It exists because organizations repeatedly treat operating problems as procurement problems, and because rebuilding the system around the work rarely has an established owner.

Operating thesis

Important work should not have to fight the systems around it. The people doing the work are usually not the problem. They are absorbing one, and that absorption is expensive and almost entirely invisible because it shows up as effort rather than as a line item.

Method

Trace how work actually moves, which is reliably different from how it is documented. Find the seam rather than the symptom. Build the smallest intervention the constraint requires, which is sometimes software and often a change to sequence, ownership, or what information arrives with the work. Deploy into live conditions and stay through the period where the operation and the system are still negotiating with each other.

What the engagement does not do

It does not start from a tool decision. If the first conversation is about which platform, the diagnosis has not happened yet. It does not deliver visibility and call it a fix. It does not end at go live, and it does not leave behind a system only its author can maintain.

How the work is judged

The exit condition is operational ownership. The organization can run the system, explain why it works the way it does, and change it without the people who built it. Adoption and satisfaction are proxies. The question is whether the work moves differently now, and whether it still does in six months.

Outcome

Building an operational systems company.