Skip to content
All writing

We replaced Wodify with a gym OS we built and run

The idea: stop renting your gym's software

Persistence Athletics is our own gym, a CrossFit gym in Belltown, Seattle. We run it on the system we build, so we feel every bug first. Like most gyms, it ran on Wodify. Membership, billing, class booking, programming and member messages all lived inside one vendor's product.

None of it quite fit how the gym works. We record every class with two cameras and a wireless mic. We bill the whole gym on Sunday night, not on each member's signup date. Off-the-shelf software fought us on both.

So we did what we do. We did not add a plugin or buy another tool. We built the gym one system, and now we run it. One codebase, one database, one place for membership, billing, programming, class booking and member messages.

It is live today at app.persistenceathletics.com, with an iPhone app in beta and a coach assistant built into the member app. Here is how it got built.

Why we wrote our own billing

The hardest choice came first, and it was about money. Stripe, the payment company we use, has a good subscriptions product. We did not use it. The reason is one rule: this gym bills everyone on Sunday night.

Stripe subscriptions bill each person on the day they signed up. There is no clean way to make them bill a whole gym on the same evening. So we turned it around. Our system decides when to bill. Stripe just takes the payment.

That is simple to say and full of sharp edges to build:

  • Every Sunday night, our system finds every membership that is due and makes one invoice per member.
  • We charge each invoice ourselves. Stripe never charges on its own.
  • Stripe tells us when a payment works or fails, and we update our own records. Those records are what the member sees.
  • On Friday the system sends renewal reminders. Every day it closes out drop-ins and punch cards, and cancels memberships that have been paused past the limit.

Each membership keeps its own next billing date, its renewal setting, its failed payments and its pause. A pause lasts up to four weeks and only starts next week, never this one. Those are the gym's rules, not Stripe's, which is why they had to live in our code.

Owning the billing means owning every way it can fail, and we paid for that lesson. One member was charged $95.76 instead of $86.98 because tax was added twice.

Two of our five ways to charge a card forgot tax entirely, so members saw different totals. A job set for Monday morning ran on the wrong day, because the server keeps a different clock. Invoices showed "Invalid Date" because two dates were never saved.

And one member paid with Stripe Link instead of a card. Our system only looked for cards, so the next charge had nothing to bill.

Each of those became a rule we now use on every billing system we build:

  • Pick one way to add tax, never two.
  • Every charge goes through one shared path, so tax is always the same.
  • Turn off Stripe's automatic retries, so the gym decides when to try a card again, not Stripe.
  • After any card is added, make it the default. And look for every way to pay, not just cards.

The sales tax and the business tax now go on one line, at 11.021 percent. Every invoice keeps the subtotal, the tax and the total, so the member always sees the breakdown.

24 emails that sound like a coach, not a corporation

A gym system lives or dies on the messages it sends. We built 24 branded emails. They cover billing (receipts, failed payments, upcoming charges, card updates), joining (welcome, trial, waiver), the account, every membership change (confirmed, changed, paused, resumed, cancelled, expired), class booking, and community (birthdays, milestones).

Two details mattered more than the count. First, the logo image would not show in real email apps, so we rebuilt the header as styled text: green Persistence over dark Athletics, with a green bar.

Second, the tone. These read like a coach talking to an athlete: personal and direct, with no corporate filler. A receipt from your gym should not sound like a software invoice.

Programming as rules, not a spreadsheet

The gym's daily training comes from a set of rules for strength and conditioning. It is not a PDF that someone edits by hand. It is tables of sets and reps, with checks.

We rebuilt the model so the work changes from day to day, with 24 set-and-rep patterns across eight volumes and three intensity levels. Then we updated 52 weeks and 173 days of programming in one pass, and checked all 173 days against the rules. All 173 passed before anything shipped.

On top of that sits a logbook with suggested weights, which makes the program personal. We keep each member's best lifts and the gym's real set of resistance bands. The system reads the percentages in each day's program and suggests a working weight, rounded to five pounds.

For work set by effort, on a scale of 1 to 10, it turns the effort into a percentage and shows what the member lifted last time. We filled in the best lifts of about 70 members from their history, so the feature was useful on day one, not empty.

The coach assistant, and testing it safely

The coach assistant is part of the member app. A member can ask it to log a max, look one up or suggest a weight. It also files feedback and bug reports straight into a review list for the coaches.

It runs on one hard rule: never say a task worked when it did not. An assistant that says it logged your lift when it did not is worse than no assistant.

The hard part was keeping a closed beta safe. We launched to 12 testers. The assistant had to work with both the live data and a test copy, without ever mixing them.

So each member's record says whether they are a tester, and every request goes to the matching side. The scheduled jobs run on both sides with opposite filters: the live side skips testers, and the test side only serves them. One assistant, two worlds, no mixing.

The iPhone app: ship the wrapper, earn the rebuild

Members wanted an app on their phone, with Face ID and push notifications. We had a choice: rebuild the whole member portal as a native app, or wrap the web app we already had. We shipped the wrapper.

The app opens the member portal inside a native shell, with Face ID, push notifications, swipe-back, pull-to-refresh and a real error screen with retry. It is signed for Apple and is in Apple's beta program today.

This was a deliberate call. A wrapper put a real, installable app with Face ID in testers' hands in a day instead of a quarter, and every feature we ship to the web shows up in the app for free. A full native rebuild is something you earn once you know which screens deserve it.

The part nobody sees: the class videos

One more piece is pure time saved. We film every class, and four editors handle the footage. That used to mean someone scrubbing through hours of video for usable moments.

Now the computer does the first pass. It pulls the sound from both cameras and turns the speech into text. Claude reads the text and lists the good moments. Then a script cuts clips from both angles, plus extra footage from the gaps.

The first run turned one class into 53 listed moments and 152 clips, then handed them to the editors with the work already assigned. The gym makes the content; the software does the scrubbing.

What "we build it, then we run it" actually means

None of this is a demo. The billing charges real cards every Sunday. The emails land in real inboxes. The coach assistant works for real members in the app.

When tax was charged twice, a real person paid nine dollars too much. We found it and fixed it because we run the system, not just deliver it. That is the whole model: learn the business, build the system it needs, and keep running it.

We dropped our gym software and got a system shaped exactly like our gym. That is the difference between renting software and owning how you run. 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