> 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/hand-off.md).

# Hand off cleanly

A good engagement ends with the owner able to run Kula **without you**. This page is the clean exit: give them the keys, leave them a simple rhythm, and revoke your own access.

## 1. Make sure the owner can get in on their own

* Confirm the owner can sign in to their Kula account and reach their dashboard.
* Confirm their **own** AI assistant is connected — not just yours. If you set up under a single-use connect link, have the owner connect their own assistant now (it takes two minutes — [Connect Claude](/connect-claude-and-access/claude.md)).
* Walk them through asking one real question and getting an answer, so they leave the call having done it themselves.

## 2. Leave a simple rhythm

Hand them [Your weekly rhythm](/get-started/your-rhythm.md) — it's written for exactly this moment. Point them at:

* The three questions to ask each week.
* The one weekly glance at the **Connectors** page.
* The monthly re-run of the diagnostic.

If you built any custom [skills](/skills/build-your-own.md) for them, show them how to run those by name, and make sure the skills are **published** to the studio so they survive after your access is gone.

## 3. Revoke your access

This is the step that makes the hand-off real:

* The connect link you used is already narrow and time-limited — but don't leave it dangling. Have the owner **revoke that connector** in **console.kula.digital → Connectors**, so the only access remaining is the owner's own.
* Confirm with the owner that, from here, **they** hold every key. Nothing about their ongoing use should depend on you.

Within about a minute of revoking, your access stops. The owner's data was always in their own private database under their account — revoking simply closes the door you came through.

## 4. Leave the trust story with them

If the owner ever needs to reassure a partner, accountant, or their own clients, point them at:

* [Is my data safe?](/get-started/trust.md) — the plain-English version.
* [Security & data handling](/trust-and-legal/security.md) — the detail.

## That's the engagement

Set up → diagnose → hand off. The owner keeps going on their own, and if they bring you back for a quarterly look, you run the same clean cycle again.