One level at a time: how a studio actually becomes Gen 2

Every conversation about AI in a studio eventually hits the same wall: it sounds like a project. A migration. A month of someone's life and a risk to the thing that pays the bills. I want to take that wall down, because the way a studio becomes Gen 2 is the opposite of a project. It is a sequence of small steps, each of which pays its way before you take the next.

Start with the business you already have

A working studio: people above, the software they already use below. Owner, manager, teachers, PTs, members. Bookings, payments, CRM, accounting, marketing, payroll. Calm, not broken. That is the starting point, and it persists to the end. Nothing below gets replaced at any step.

Step one: connect it

Pick your booking system and connect in minutes. The Kula layer slides in between the people and the software. A single studio is usually ready in about thirty minutes, and we email you the moment it is. Bigger multi-site books take a few hours. Mindbody, Wix and GymMaster today; tell us yours if it is not on the list.

Step two: ask it

The same day, ask the questions that used to take three logins, in Claude, ChatGPT or Gemini, from wherever you are. This is where most studios start, and where many stay for a while. That is not a failure to progress. It is the level doing its job. Underneath, the shared memory is compounding: every answer, every correction and every outcome becomes context.

Step three: put intelligence with the team

When the team is ready, add Kula Fitness and give your instructors Tribe. Same context, now on the floor, before class. There is nothing to migrate because the context your instructors get is the one you have already been asking questions of.

Step four: build what you need

When a tool you wish existed comes up, describe it. Build one on the business, use it, then decide on the next. You will know you are here when you catch yourself saying "I wish something just told me when…" about the third thing that month.

Step five: give AI work

When there is a job you would hand to a capable new hire with clear rules, hand it to an AI worker with the same rules, inside the same policy and permissions, with approval where it matters. One job at a time. This is the direction, and it comes last because it needs everything before it.

You can stop at any level

This is the sentence I want every owner to hear. Each level uses the context the one before it built. Stop after step two and you are running a Gen 2 studio at level one, and it is already a different business than the one where you were the integration, the memory and the decision engine. Nobody is behind for staying at a level. Nobody has to do all four.

Why the memory matters more than the model

Models commoditise. Business understanding compounds. The AI you ask questions in will get better every few months whatever you do. The thing that gets more valuable with time is the understanding of your business that Kula holds: what actually happened, why a choice was made, what worked next time. It stays when people leave. Whichever level you are on, that memory is working for the next one.

How to begin

Bring one question you cannot answer without three logins, and tell us which booking system you run. Put the question to The Ask on a real studio's data first if you like. Then connect yours. Level one is thirty minutes away, and it is the only level you have to take today.