> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/for-consultants/consultants.md).

# Helping a studio go faster

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](/readme.md)). 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**](/for-consultants/set-up-on-their-behalf.md) — 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**](/for-consultants/facilitate-the-diagnostic.md) — run Studio Ignition *with* the owner, and turn what it finds into a short list of early wins.
3. [**Hand off cleanly**](/for-consultants/hand-off.md) — 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](/trust-and-legal/security.md).
* 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](/connect-claude-and-access/scopes.md).

## 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](/for-consultants/set-up-on-their-behalf.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/for-consultants/consultants.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.