Skip to content
All writing

“You own it, we operate it”: what that actually means day to day

Most custom software starts to age the day it launches. An agency ships the build, sends the final invoice and moves on. A software vendor rents you a slice and points at a roadmap you don't control.

Either way, six months later you're stuck. The agency's code is brittle and nobody owns it. The vendor raised its price and dropped the one feature you needed.

We do the opposite. We learn the business, build the system, then run it for you. "You own it, we operate it" is the whole model. It's easy to say and hard to mean, so here's what it looks like in systems that are live right now.

Operate means we answer when something breaks

When something breaks at 6am, it's our problem before it's yours. That's only possible because we built the thing and know where everything is.

Take a four-store retailer we work with. It has 31 store screens, some for check-in and some for menus. They check for updates and install them on their own every day. No staff on a ladder, no store visit.

When the screen app needs an update, we send it to all 31 screens from one dashboard. The stores never think about it. That's what running a fleet of screens means: the boards are always current, and nobody in the store has to do anything.

Operate means features ship every week

Software that sits still decays. A system someone is actively running gets better. You can see it fastest at Persistence Athletics, our own gym. We built its system to replace Wodify and still run it today, so we feel every bug first.

It is not one app. It is our own billing (Sunday billing, pause and resume, a check that a card is on file, tax, retries on failed cards, real invoices), 24 branded emails, a member portal and an iPhone app in beta.

It also has a coach assistant in the member app, rules-based programming with a logbook and suggested weights, and a tool that sorts the class videos. A beta is running with 12 testers, and new features land every week.

Weekly shipping only works because we keep a live copy and a test copy of the whole system. We test on the copy, then release, without touching live members. The release log reads like a product team's, because it is one:

  • Billing live: our own billing replaced Wodify end to end.
  • Emails shipped: 24 branded emails across billing, joining, membership, classes and community.
  • iPhone app in beta, with its own assistant tab.
  • Programming and the coach assistant: rules-based programming, plus an assistant in the member app that works from the real program and logbook.
  • Class videos: speech turned into text, Claude picks the moments, editors get their work, and clips are cut on their own.

None of that would exist if we'd shipped the first version and walked away. It exists because someone is still in the code every week, with skin in the game.

Operate does not mean lock-in

Here's what separates this from a software contract. Running your system does not mean holding it hostage. You own it. The code is yours, clean and documented. Keep us running it because we're fast and know it well, or take it in-house whenever you want, with a written handover.

Rented software offers two choices: rent forever, or rebuild from scratch. There's no door in between. We give you the door. We can, because we don't profit from lock-in. We profit from running it well enough that you'd rather we kept going.

Build it once and walk away and you get software that decays. Build it and run it and you get a system that keeps getting better.

Why this is possible now

A few years ago, one team could not build a gym system and a four-store retail network, and also run both. The build alone was a floor of engineers and a six-month timeline. AI changed that math.

We build with Claude Code, so a small focused team ships what used to take many people. Then it has room to keep running everything after launch, instead of disappearing into the next contract.

So when we say "you own it, we operate it", it's not a tagline. It's someone who answers when it breaks, features that land every week, and code you can walk away with the day you choose. That's the difference between a project and an operating system. That's 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