> 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/facilitate-the-diagnostic.md).

# Facilitate the first diagnostic

Once the studio's data is in, the highest-value thing you do is run the **Studio Ignition diagnostic** *with* the owner — not at them. They watch the picture of their own business build, you provide the read and the judgement.

The diagnostic itself is documented for the owner in [Run your first diagnostic](/get-started/first-diagnostic.md). This page is about running it *as the facilitator*.

## Before you run it

* **Confirm the import finished.** Ask: *"List the tables you can see and roughly how much data is in each."* If the spine looks thin, give the import more time or check the connector.
* **Do the operator intake carefully.** Early on, the diagnostic asks how the studio actually works. This is where your knowledge of the studio earns its keep — get it right and everything downstream is sharper.

## Run it

Kick it off in the AI assistant:

> *"Run the Studio Ignition diagnostic on this studio."*

Then facilitate:

* **Let part one land before reacting.** The diagnostic establishes what's *true* first — volumes, gaps, how well the data links together — with no rosy projections. Read these findings with the owner and **sniff-test them together**. If a number surprises the owner, that's a conversation, not a failure.
* **Hold the line on integrity.** Resist jumping to "here's the upside" before the owner has agreed the foundation is real. The diagnostic is built to gate this on purpose.
* **Then move to the levers.** Once the owner trusts the picture, part two surfaces where revenue slips, which relationships hold members, and how classes and pricing really perform — each traced to their own numbers.

## Turn findings into early wins

Your deliverable to the owner is **not** the raw diagnostic — it's a short, honest list of **two or three things worth doing this month**, in their language. Ask the assistant to help you draft it:

> *"From this diagnostic, give me the three highest-value, lowest-effort actions for this studio, each with the evidence behind it."*

Keep it human. The Ignition principle is *more human, not less* — the early wins should sound like advice from someone who knows the studio, because they are.

## Save it so it lasts

The diagnostic saves what it builds, so the owner's future questions are fast and consistent. If you've shaped a particularly useful view, consider saving it as a [skill](/skills/build-your-own.md) so the owner can re-run it after you're gone.

## Next

→ [Hand off cleanly](/for-consultants/hand-off.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/facilitate-the-diagnostic.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.