← All use casesUC-25 · use case

Integrator hand-off

Set it up, hand the client the keys.

A partner builds and configures the client’s org, transfers ownership, and gets scoped access on demand later.

Two ways to start: provision a ready-made solution and connect your own keys, or build it yourself from the template. Free during beta — see pricing.

In practice

A consultant builds a client’s agent-org, configures it, then transfers ownership so the client runs it themselves. Two months later the client grants time-boxed access for a tweak — the change is made and the access expires automatically.

The team

Positions in the org — each filled by an agent, a person, or both.

Integrator
Human
Client owner
Human
Client org
AI agent

How everyone works together

People and triggers reach the agents, which act on your services and escalate to a human.

PEOPLE & TRIGGERSAGENTSSERVICES & TOOLSrequestsact onescalate · approveCustomersmessages · eventsClient orgOwnership transferScoped third-party accessRevenue shareSOONHUMANS · OVERSIGHTIntegrator · Client owner

How it works

  1. 1

    A client hires you to set up their agent-org.

  2. 2

    You build and configure positions, agents and sources.

  3. 3

    You transfer ownership to the client, who self-runs it.

  4. 4

    Later, the client grants you scoped, time-boxed access for changes.

Set it up with prompts

Three ways to build this — pick a variant and type the prompts in order. Each step says which agent to address. A working Integrator hand-off workspace in minutes.

The clean hand-off: you build it, the client owns it, nothing of yours left inside.

Apps in this variantOwnership transferTemplates
  1. 1Build for the clientOnboarding box

    New workspace → "Describe your company" → Build my company (client's workspace)

    Set up [CLIENT]'s org per our agreed spec: [the org prompt you designed together]. Include an Owner seat for [CLIENT NAME] and a temporary Integrator seat for me with admin rights, clearly named "Integrator (temporary)".

    The build happens in THEIR workspace from day one — no migration cliff at hand-off.

  2. 2The go-live checklistCore Agent

    Inbox → Core Agent (client workspace)

    Run the go-live check: list every agent with its guardrails, every connected app with its owner's credentials (none of mine), every approval rule. Flag anything still pointing at the integrator seat.

    An auditable go-live: the client sees exactly what they own, and that it is really theirs.

  3. 3Transfer & step outYou (UI)

    Settings → Members

    Transfer ownership to the client and remove (or downgrade) your Integrator seat. The audit log records the hand-off.

Make it yours
  • Training gift: "Record a 10-line 'how to ask your Core Agent for changes' note into their knowledge."
  • Warranty window: keep a read-only seat for 30 days by agreement, then auto-expire.

What you get

Deliver a working org, then hand over the keys

Clients self-run; you help on demand

Setup fee plus ongoing revenue

What it connects to

Ownership transferScoped third-party accessRevenue sharesoon

Available today via Google, HTTP and MCP sources. Items marked soon are on the connector roadmap.

Set this up for your Integrator hand-off

Provision a ready-made solution, or build it yourself — start with one agent in one role and grow into the full team.

← More use cases