We asked ChatGPT for this month’s Committed Club.
It pulled the members who hit their attendance commitment straight out of BTWB — names, streaks, the dots on the calendar — and turned them into an Instagram reel. One prompt. No export, no spreadsheet, no designer, no copying numbers from one screen into another.
That is the part worth sitting with. It did not just answer a question about your gym. It went and got your actual data and made something you can post.
What’s live, and what’s landing
BTWB connectors have been live in Claude and Notion for a while now. Gyms are already using them to pull daily WOD boards, run revenue and churn numbers, and dig into how coaching clients are actually progressing.
This week we’re adding two more:
- ChatGPT — chatgpt.com and the desktop app
- Grok — grok.com
Same data, same connectors, same permissions. Whichever assistant you already have open is the one that works.
Connecting is about to get a lot simpler
If you set up a BTWB connector before now, you remember the part where you had to go find an OAuth client ID on your Gym Tools page and paste it into the AI. That step is gone.
The new flow:
- Add BTWB as a custom connector in your AI, using the URL
- Click Connect
- Enter your email, open the magic link we send you
- Approve the connection
That’s it. The assistant auto-detects everything else.
The reason this matters beyond convenience: ChatGPT and Grok both require a piece of the OAuth spec our old sign-in couldn’t support. Getting there meant BTWB had to become its own authorization server rather than leaning on the legacy one. So the thing that makes connecting easier is the same thing that makes ChatGPT and Grok possible at all. Supporting the next assistant after these is now mostly a matter of adding it to the list.
Two connectors, and you want both
There are two BTWB connectors, and they’re designed to work together.
Operations — the business side of the house. Revenue and MRR, membership plans and subscriptions, churn and cancellations, class and appointment attendance, clients and leads, scheduling, retail, documents, the WOD board, the results board, Committed Club.
Coaching — your clients’ training. Logbooks, PRs and benchmarks, max weights, volume summaries, imbalance and fitness-level reports, macros and nutrition, body measurements, badges and milestones.
Connect both. Operations answers “how’s the business.” Coaching answers “how are my people actually doing.” Most of the questions worth asking cross that line.
Things worth asking
A few that work well today:
- “What’s my MRR this month, and how does it compare to the last six?”
- “Which clients haven’t checked in since the start of the month?”
- “Who’s up for a membership anniversary in the next three weeks?”
- “Pull this week’s results board and write me a caption for it.”
- “How has Sarah’s back squat moved over the last year?”
- “Show me this month’s Committed Club and make me something to post.”
You don’t have to name the connector or learn any syntax. Tell it to go look at your BTWB data and it figures out which tools to use. The protocol is self-describing — the moment an assistant connects, it asks BTWB what it can do, and BTWB tells it. You can literally ask “what can you do with my gym?” and it’ll read the list back to you.
Why it’s us
Workout apps have your training data but not your books. Gym management platforms have your books but barely touch training.
We have both, on one identity model, joined cleanly. Which means a gym owner can ask one question — how’s my revenue and churn this month, and are my coaching clients actually getting fitter? — and get one answer. That’s not a feature we bolted on. It’s a thing that’s only possible if you own both halves of the data, and it’s the reason we think this gets more interesting from here rather than less.
There’s a permissions story underneath it too: a coach sees a client’s training because the gym’s billing relationship says they should. The access control falls out of the data being joined in the first place.
Already connected? Here’s what to do
Your existing Claude or Notion connection will keep working until its sign-in expires.
When it does — or whenever you want the new tools, and we’ve added a batch of them in the last week alone — delete the connector and add it again. The new flow takes over automatically and you’ll never touch a client ID again.
If you’re setting up fresh, there’s nothing to migrate. Just connect.
What’s next
More tools, continuously. Every capability we build for our own apps shows up as an AI tool at the same time, from the same definition, so the two can’t drift apart. There’s no separate “AI roadmap” — there’s just the roadmap, and the assistant gets all of it.
The bigger shift ahead is going from reading to writing: telling your assistant to log a workout or program a track, instead of only asking it questions. We’re building toward that.
For now: connect both, open whichever AI you like, and ask it something about your gym.