Helping a studio go faster

For consultants — how to set a studio up, run the first diagnostic, and hand control back. Optional by design; the owner can do all of this themselves.

This section is for consultants — advisors who help studio owners get up and running with Kula Intelligence.

A quick framing first: everything here, the owner can do themselves. Kula is built so a non-technical owner can set up, run a diagnostic, and keep going without help (that's the owner guide). Your value isn't that you're required — it's that you make it faster and clearer. You do the setup in minutes, run the first diagnostic alongside them, frame the early wins, and hand back something they can run on their own.

The shape of an engagement

Three steps, then you're out:

1. Set up on their behalf — connect the studio's data using a single-use connect link, so the owner doesn't have to wrangle keys.
2. Facilitate the first diagnostic — run Studio Ignition with the owner, and turn what it finds into a short list of early wins.
3. Hand off cleanly — give the owner the keys, revoke your own access, and leave them with a simple weekly rhythm.

The owner stays in control throughout

• The studio's data lives in its own private database, tied to the owner's account — not yours. See Security & data handling.
• Any access you're given to help is revocable, and you revoke it at hand-off. The owner is never dependent on you to keep using Kula.
• You never see more than the owner's chosen permission level allows — the same limits apply to you as to them. See Permission levels.

Working with more than one studio

Each studio is completely separate — its own database, its own account, its own access. There's no shared view across studios, by design. So working with several studios just means repeating this clean set-up → diagnose → hand-off cycle for each, with no risk of one client's data touching another's.

Start here

→ Set up on their behalf