INFRASTRUCTURE
The half that makes it hold.
The systems underneath your business, built the way it already works. Pay, programming, scheduling, time off, your documents and your numbers, in one place behind one sign-in. Nothing anyone does is ever overwritten, and when a rule changes, history stays true.
01 · THE SYSTEMS UNDERNEATH
The systems underneath — what gets recorded, by whom, and how often. The unglamorous machinery that decides whether anything else you change actually holds.
In practice that means finding every place the same event gets written down twice, or not at all. Each one is a future argument with no way to settle it.
02 · THE MONEY
The money — what was delivered, what was billed, and every gap between the two. The gaps are small, regular, and where your revenue actually goes.
In practice that means putting the two records side by side for one pay period and reading the differences out loud. Nobody has done that and found nothing.
03 · WHAT SURVIVES ME
What survives me — built to run without me. Documented, tested and handed over, so the thing that changed stays changed after I’ve gone.
In practice that means it has tests, a backup that has actually been restored at least once, and a written record of who decided each rule and when. If it only works while I’m answering the phone, it isn’t finished.
Diamonds are forever. So is your data.
Everything we build is yours: the records, the rules, the history, all of it. You work with a small team that builds it with you, and nothing in it is ever held over you later.
A lot of software runs on “pay us forever or lose everything.” This doesn’t.
THE METHOD
ONE OF THEM, RUNNING
This one was built for a coaching gym. Coaches log the week as it happens, and the week closes on its Sunday. The owners correct it on top with their name and a reason (the coach’s own entry is never overwritten), tick each client through as it’s billed, and carry a failed card to a later pay period without touching the record.
Every pay figure comes from one file of rates and one file of rules. A rate change is one line, and every past pay period keeps the table that priced it.
Every number in it is invented. Yours would hold your floor, your rates and your exceptions, and nobody outside your business would ever see them.
WHAT’S IN IT
The week — every coach’s 1:1 sessions, ticked through as they’re billed. What’s left still needs doing.
Payroll — each person’s pay period as one sheet, in book order. Every line explains itself, and the total at the bottom is the one that goes to the books.
Programming — the whole quarter on one board. Every save keeps the week it replaced, and an assistant proposes changes that a person accepts or doesn’t.
Scheduling (rolling out) — a schedule in two-week blocks that match the pay period. Coaches offer and take classes, an admin approves, and the owner can see it as any coach before it goes out.
Time off — a request is one line, answered on the same line, against a six-month calendar that says at once whether the days cross somebody else’s.
A projection — a coach models their own month. The owners see where the quarter is trending, at two paces, and the page says in so many words that these are projections.
The numbers — the year’s books, uploaded as they are and read by quarter, month or year, with members on old rates sized from your own files. Owners only.
The manual and the handbook — in-app readers with chapter markers. A coach acknowledges a version by name, and the acknowledgement keeps naming it after the book changes.
A helper — answers from the site’s own guidebook, says plainly when it can’t, and will walk you to the screen and ring each thing to press.
What needs you — one list on the home page, worked out from the records at the moment of asking. Nothing is stored to raise a notice, so a notice can’t go stale.
Underneath: an audit log of what was done, nightly backups to a separate store, and a floor model that runs on invented people and provably cannot reach real data.
Built how — one self-contained application behind a single sign-in. No build step, no framework. Deployed as a zip, tested headless — a few thousand tests, including guards that read the pages the way a person does. A new system that other systems could come to lean on goes in behind its own switch, off, until it has been tried for real.
HOW YOU GET ONE
01 · FIRST WE MEASURE
You have products on your floor nobody else has, priced in ways that made sense at the time, with exceptions everyone knows and nobody wrote down.
So we measure how your money actually moves — not how it’s supposed to. Who bills, who chases, what happens when a card fails, and which things live only in somebody’s head.
02 · THEN WE WRITE IT DOWN
Then we write down your floor and your exceptions — your products, rates, covering rules and holidays, including the ones only true on Saturdays. Each gets a name and a source.
03 · THEN YOU GET YOURS
You get your version, not a configuration of mine. The rules that are yours are built as yours. The parts every fitness business shares (sign-in, calendar, backups, audit trail) come already tested.
04 · AND I STAY WHILE IT RUNS
The first pay period is where you find out what the room actually does. That’s not the moment for the person who built it to be gone.
IT ISN’T A LOGIN YOU’RE GIVEN. IT’S YOURS, AND IT’S BUILT ONCE.
Still here? You can keep scrolling, or you can get started. You pick.