The four parts of a Gen 2 fitness business: Intelligence, Tribe, apps and AI workers

Every fitness business runs on a stack of systems that were never designed to talk to each other. Bookings in one. Payments in another. Payroll, accounting, marketing, support, each with its own login and its own idea of who your members are. The person joining it all together is the owner, and the joining happens in their head.

A Gen 2 business puts that shared understanding into software, once, underneath everything else. This post is the map: the four parts that sit on top of it, what each one is for, and an honest line between what you can use today and where it is going.

The one idea underneath

Kula Intelligence connects across the systems you already run and builds one governed model of the business from them: members, bookings, attendance, staff, classes, payments, documents. It does not replace any of those systems and it does not ask you to migrate. It reads them, through safe views rather than raw access, and keeps the model current as the day goes.

That model is the shared context. Everything below draws on it, subject to policy and permissions. That last clause matters. What an instructor can see is not what an owner can see, and neither is what an AI worker would be allowed to act on.

Part one: Intelligence. Ask it.

The first thing you do with a shared understanding is ask it questions. Kula Intelligence is delivered as an MCP server, the plumbing that lets Claude, ChatGPT or Gemini reason over your business the way they reason over a document you paste in. You ask in plain language, in the app already on your phone, from wherever you happen to be standing.

The teacher who resigns on a Tuesday is the example we use because it crosses systems: who could take the classes, which members are anchored to that teacher, what to do first. One question, several systems, no prebuilt workflow. You can try it on a real studio's data at kula.digital/ask.

Available today for studios on Mindbody, Wix or GymMaster. Other booking systems are on the connector roadmap, and telling us yours moves it up the list.

Part two: Tribe. Put the context with the team.

The owner is not the only person who needs context. Instructors need it more, and they need it at 5:55am, not in a report.

Tribe is the teachers' app. Schedule across every studio they teach at, one login. Whispers before class: "Sarah's back after three weeks, welcome her home", with the reason attached, and the teacher still deciding what to say. Messages in one place. Covers offered to the people who are available and qualified, first to accept gets it, and the booking system updated. Compliance documents tracked.

Tribe is where the shared understanding reaches the floor. It is a prompt for human judgement, not a script. Tribe ships with Kula Fitness and is available today. Details at the Tribe app.

Part three: Apps. Build what you need.

Every studio has three or four things it does its own way. Instructor bonuses that reward the classes that fill. PT commissions. An intro-pass tracker that tells you who is about to lapse before the pass runs out. Off-the-shelf software either does not have them or has a version that does not fit.

Because the business model already exists underneath, those tools can be built on top of it rather than starting from raw exports. Our Instructor Bonus Builder is published on GitHub with full documentation and a live demo, so you can run it yourself or build your own from it, and the instructor bonus, PT commission and intro-pass examples we show at AusFit are exactly that: examples built on the business context, by people who know the business.

This part is the direction, not a catalogue. What you can build depends on your systems, your data and what you want the tool to do, so tell us the job and we will tell you what is possible now and what needs work.

Part four: AI workers. Give AI work.

The last part follows from the first three. Once the business is understood in one place, some of the work that draws on that understanding can be handed to an AI worker: the weekly read of what needs attention, the draft of the message to a member who has gone quiet, the first pass at next month's roster. Humans and AI working from the same understanding of the business, with the human making the call.

We are deliberate about this one. An AI worker acts inside the same policy and permission model everything else uses, every action is on the record, and nothing is sent or changed without approval where it matters. This is the direction of Gen 2 and we will show it as that: where it is going and what we are building towards, not something on the price list today.

The stack, in one picture

Access at every layer depends on supported connections, policy and permissions.

What to do with this

Start at the top of the stack. Bring one question you cannot answer without three logins, tell us which booking system you run, and see what a connected business looks like. Ask your whole business, or find us on Stand 65 at AusFit 2026.