Skip to content
All writing

The operating system thesis

A small-business owner once showed me what her business really ran on. It was a sticky note on her monitor with six logins. A billing tool, a scheduling app, a customer list, an email tool, a spreadsheet that tied three of them together, and the password to the spreadsheet.

Six bills a month. Six vendors. And one person whose real job, several hours a day, was carrying data from one tool to the next by hand.

That's not a problem you fix with a seventh tool. That's the whole industry's default answer, and it's wrong. Here's what we believe instead: a business shouldn't run on a pile of rented apps stitched together. It should run on one system, built for how it actually works, that we build and then run.

A tool does a slice. An operating system runs the work.

Every rented software product is a slice. Billing is a slice. Scheduling is a slice. The customer list is a slice. Each one is fine on its own, and each one assumes the other slices are someone else's problem. The gaps between them become your problem. That spreadsheet on the sticky note is the gap, made visible.

When we build for a business, the billing, the customer app, the point of sale, the screens, the AI that does the routine work, and the links that move data are all parts of one system. They connect because we built the whole thing, not because someone bought six products and hoped a connector app would hold them together.

Take Persistence Athletics, our own gym. It ran on Wodify, plus the usual ring of tools around it. We run it on the system we build, so we feel every bug first. We didn't add a feature. We replaced the whole platform.

Its billing (Sunday billing, pause and resume, a check that a card is on file, tax, retries on failed cards, real invoices) shares one database with the member app, the programming and the coach assistant inside the app.

So when a member asks the assistant to suggest a weight, it reads the real program and the real logbook, not a guess.

That only works because it's one system, not six that happen to be in the same building.

Why this was impossible last year, and isn't now

Be honest about the old math. A real system for one business meant an agency's six-month timeline and an agency's six-figure bill. No small business could justify that, so they rented slices and lived with the gaps. The pile of tools wasn't anyone's choice. It was all the budget allowed.

AI changed the math, and not by a little. We build with Claude Code and Codex. The code doesn't write itself. But one focused team now ships what used to take a floor of engineers, in weeks, and keeps shipping after launch. You can see it in what gets built:

  • Persistence, our own gym, got its own billing, 24 branded emails, an iPhone app in beta, a coach assistant in the member app, a rules-based programming engine and a tool that sorts the class videos. That's an agency's quarter of work, run by a small team.
  • A four-store retailer runs its point of sale, a menu designer and 31 store screens that update themselves every day, all from one dashboard. One person updates 31 screens across four stores without leaving their desk.

None of these could be delivered at a small-business price two years ago. What's new isn't the ambition. It's that the ambition is now affordable.

Build it, then run it

Custom software has a quiet way of failing: the day it launches is the day it starts to age. The agency ships, sends the final invoice and disappears. Six months later the thing is brittle and nobody owns it. That's why "we run it" is the half of this idea that carries the weight, not a footnote.

We run what we build. We watch it, so problems get caught before customers feel them. We fix it fast, because we wrote it and know where everything is. And we ship new features every week, so the system gets better instead of older.

The gym's system has a live copy and a test copy, so we test without touching real members. The retailer's screens update themselves every day, and the stores never think about it. Software that's run stays alive. Software that's delivered and left behind dies on a schedule.

You still own it

Running it is not the same as holding it hostage. The business owns the system. Keep us running it, or take it in-house whenever you want, with clean, documented code and a written handover. No per-seat fee, no vendor roadmap you can't change, no lock-in.

When a gym wants a billing rule changed, we change it that week, because it's theirs and we're right there.

That's the thesis, and it's a simple one. Don't rent six slices and become the glue between them. Build the one system your business actually runs on, own it, and have someone keep it alive.

AI is what finally makes that affordable for a business with a sticky note on its monitor. Build it once and walk away, and you get software that decays. Build it and run it, and you get your business, on autopilot.

Tell us what eats your week.

A free 20-minute call. We'll show you what we would take off your plate.

Book a call