You are the glue
Your studio runs on six systems that never talk to each other, and you are the one joining them. Here is the same morning with the glue removed: a spoken briefing, a drifting member caught, and a teacher who sees her future in the two minutes after class.
It is 9:40 on a Tuesday and you are exactly where you should be: on the floor. A member stops you on her way out. She wants to pause her membership while she travels, and she wants to know what happens to the two weeks she has already paid for.
The answer exists. It lives in the office, behind a login, split across two systems that have never spoken to each other. So you say the sentence every operator says a dozen times a week. "Let me check and get back to you."
You are the glue
A studio runs on five or six systems. Bookings in one. Payments in another. Payroll, accounting, marketing, messages. Each is competent at its own job. None of them share what they know. Any question that spans two of them gets answered by a person walking to a desk and lining up tabs. The industry never built the integration layer. It quietly assigned the job to you.
And the desk is expensive in a way the clock does not show. This business is built standing up: the welcome back after three weeks away, the chat after class that turns a casual into a regular, the ninety seconds before a class starts. Members rarely leave loudly. They drift, and drift gets caught by whoever is on the floor talking. Every trip to the office is a conversation that never happened, and some of those conversations were worth a membership.
The other version of the day
Here is the same morning with the glue removed.
It is 9:58 and you are walking to studio two. You say, out loud, to the earbud you are already wearing: "Hey Kula, I am about to take Maya's class. What should I know?"
By the time you reach the door, this comes back. Spoken, not shown.
Twelve in the class. Debbie hits her 200th class today.
John is back after three weeks away, but he is drifting. On his current pattern he is likely gone in two months. His remaining lifetime value is about $450.
Maya carries around $100K a year in revenue at a 25% margin. She ranks sixth on performance and second on member connection. She has asked twice about taking on more classes. Talk to her after class.
One question. Four systems: bookings, payments, accounting, communications. Read, joined, ranked and spoken in the time it took to walk there. No login. No tabs. No trip to the office.
What you do with ninety seconds
You open the class by celebrating Debbie's 200th in front of the room. It costs nothing and lands forever.
You catch John on the way out. Not with a win-back email three weeks after he cancels, but with "good to see you back, we missed you," and a real conversation about what got in the way. That conversation is how drift ends. On the numbers above, it is the difference between $450 of lifetime value and roughly double that.
And then Maya
Maya is the one most systems would never flag at all, because she is not a risk. She is an asset. She wants more classes, and the usual answer is the desk answer: "Let me look at the schedule and get back to you."
Instead, you stay where you are standing and dig deeper, with her.
"Which slots could Maya realistically take?" Tuesday 6am and Thursday 7pm are running under capacity and have been patched with covers for six weeks.
"What happens if she takes them?" Her regulars follow her. She is second on connection, and when her classes move, her members move with them. Two more classes puts her among the top teachers by revenue carried.
Now the conversation about her future happens while she is still in the room, with real numbers underneath it. She asked for more classes. What she gets is a path: which classes, why those, and what it means for her income and her standing. Teachers leave when they cannot see a future. This one just saw hers, in the two minutes after class, because you did not have to say "let me get back to you."
The glue becomes software
Everyone else in this industry is bolting an AI assistant into their own box. The booking platform gets one, the payments platform gets one, each smart about its own data and blind to the rest. That leaves you exactly where you were: the glue, now between smarter boxes.
Kula Intelligence takes the other route. It builds one model of the business underneath the systems you already run: who booked, who paid, who taught, who was messaged, and how it all connects. Then it answers across all of it, wherever you are standing, and lets you keep asking. Nothing to replace on day one.
In a business built on people, the measure of software is not how good its screens are. It is how rarely you need them. Your time belongs to the room, and to the Debbies, the Johns and the Mayas in it.
If you want to feel it, ask a question at kula.digital/ask.
