altoby.

Care operations · United States

The operation that outgrew its spreadsheets — and became a product.

A care-facility operator had the process mastered in spreadsheets and Google Workspace, and could not take on the next facilities because of it. The system got built around their process. It runs the facilities today and is on its way to being sold to other operators.

1 week
to read the spreadsheets as a specification
0
big-bang cutovers — each module replaced its sheet after a demo
Live
the system runs the facilities today
Spreadsheets and disconnected tools consolidated into one system built around the operationsheets, inboxes,one person's memoryyour systemone place, built aroundhow you actually work

Where it started

The team ran their facilities well. Competence was never the problem. The problem was that the process lived in sheets, drive folders, and a few people's heads — and every new facility multiplied the copy-paste rather than absorbing it.

Growth offers were on the table. The tooling said no. That is the quiet ceiling most good operators hit: not a market limit, a filing limit.

The spreadsheets were not the failure

They were the specification. Years of refined process encoded in columns, colour rules, and workarounds that existed because something real once went wrong.

So the Blueprint read them as requirements. The system got specified around how the operation actually runs — not how generic software assumes an operation should run, which is the reason the off-the-shelf attempts had not stuck.

What got built

An operations system, module by module, standing beside the tool it replaced rather than in front of it: facilities and residents, shift and task management, compliance records, reporting.

Each module took over only after it had proved itself in a Friday demo. Nobody arrived on a Monday to find their job had changed overnight. That sequencing is not politeness — it is how you keep an operation running while you replace the thing it runs on.

Where it's going

The system runs the facilities. And because it encodes how a genuinely good operator works, it is on the road to being sold to other facility operators as a product of its own.

That is the version of this most operators never get told is available: the operation is the moat. The software just ships it.

off-the-shelf ceiling → scalable systemoperator first, product secondproductization track

Why this runs without a name. This story runs without the client's name while their written sign-off is outstanding. Nothing here is padded to compensate: the named version adds who they are and a quote in their words, and changes nothing else.

Keep reading

Your version of this story starts with a week.

One week, one price, and a written specification you could take to any engineer. That's the point.