Replacing a CEO-run spreadsheet process with an automated operating system

The situation

A founder-led specialty healthcare provider was growing, and the CEO was personally running patient logistics every week out of spreadsheets.

It worked. That was the problem. The process produced correct results because one experienced person was watching it closely, which meant the ceiling on volume was that person's calendar. Any real growth would have required either more of the CEO's week or a second person trained to think exactly like them.

Before I came in, the CEO had already tried to build a replacement themselves. It did not get to something usable.

The real constraint

The workflow had no operating system behind it. Scheduling, fulfillment, tracking, group rules, and exceptions all depended on spreadsheets and individual attention.

That distinction mattered for what we built. This was not a case of one bad spreadsheet that needed replacing with a better spreadsheet. There was no underlying system that held the rules, moved work forward, or surfaced the things that needed a human decision. Every part of the process was reconstructed by hand, every cycle.

What we built

We built an automated workflow covering the full path: patient data intake, group rules, fulfillment, tracking, and exception handling.

The design goal was to make the routine cases move on their own and to make the unusual ones visible instead of escalated. The rules that used to live in the CEO's head are now encoded in the system, and the cases that genuinely need judgment surface as exceptions rather than arriving as a weekly pile of work to sort through.

We deliberately kept it inside tooling the business already owned and already paid for. That kept the cost of the build down and meant nobody had to learn or administer a new platform to keep it running.

The result

The weekly process no longer depends on the CEO. What used to be hands-on work every week became oversight, and the operating team got hours back as well.

The system was designed to support materially higher volume than the business runs today, without adding headcount. That is the capacity it was built to carry, not a level it has been run at yet.

What happened next

The engagement is expanding into patient-scheduling alerts and financial-operations reporting.

This is the pattern the whole practice runs on. Land on one specific problem, deliver something that works, and let the next piece of work be earned rather than sold. The second and third projects came from the first one being right, not from a proposal.