Get started

Adoption starts with one inbox, in shadow mode.

The agent proves it is safe before it does anything. It starts with one pilot, on one surface, in shadow mode, and expands cohort by cohort and surface by surface, each pairing earning the next.

One precondition; a short list of accounts; three roles; four phases. Nothing classifies, drafts, or sends until each gate is passed and measured.

The one precondition

Ratify the governance model before anything connects.

Sign-off gates the connection

No data flows until the model is signed.

Because the pilot user is also the firm's General Counsel, the sign-off is theirs. The governance model is ratified per version, and once ratified it binds the whole firm. Provisioning accounts in parallel is fine; but no data flows into the agent until this is signed.

Accounts and access to line up

What to provision, and the rule that carries the weight.

These can be provisioned in parallel while the governance model is ratified. Data flows only after sign-off.

Models

Firm model gateway

The firm's model gateway, through which every model call is routed and data-class routed.

Mail and calendar

Microsoft 365 and Microsoft Graph

Per-user mailbox and calendar scopes on Microsoft 365 and Microsoft Graph. These scopes need tenant-admin consent.

Storage

Supabase, general and walled

A general store on Supabase, plus a separate walled store for the most sensitive classes.

Secrets

Secrets vault

A secrets vault holds every credential; nothing sensitive lives in code or environment files.

Tasks

Linear project pair

A per-user project pair in Linear: one for personal tasks, one for agent operations.

Messaging

Slack app, Events API

The Cockpit app in Slack, registered with the Events API so surfaces can be wired in later.

Accounting

Sage Intacct connector

The accounting connector on Sage Intacct, read-only, granted to permitted tiers only.

Investor portal

Juniper Square connector

The investor-portal connector on Juniper Square, read-only, granted to permitted tiers only.

Observability

Langfuse tracing and evals

Langfuse for tracing and evaluations, so every run is observable and every shadow-mode gate is measured.

The rule that carries weight

Connector credentials are issued per role tier, exactly as the access matrix grants them. A tier that is not granted a connector never holds its credential; and the datastore tool always runs under the caller's own access context.

Who you need

Three roles to stand it up.

Ratifies and pilots

General Counsel

Ratifies the governance model and is the pilot user. Theirs is the hardest inbox in the building, spanning legal, finance, and HR.

Builds

Builder

Comfortable with TypeScript or Python, Postgres with row-level security, OAuth, and MCP. The runtime is LangGraph.

Grants consent

Tenant admin

Can grant Microsoft Graph admin consent and provision Azure and Entra ID for the tenant.

The phased rollout

Build the walls first; earn every step after.

  1. Phase 0 · Foundations

    Build the walls before any data. Apply row-level security and prove it with a red-team that injects sensitive fixtures and confirms zero rows leak. Connect one read-only integration. Zero automation.

  2. Phase 1 · Shadow triage

    The classifier turns on in shadow. It predicts and explains, the morning brief becomes the first output, and your corrections become labels. Still nothing acts.

  3. Phase 2 · Draft and approve

    The agent drafts replies in your voice, surfaced to approve or rewrite. Follow-ups and calendar time-blocking begin. Still nothing auto-sends.

  4. Phase 3 · Limited autonomy

    A narrow, reversible slice of auto-send on low-risk operational actions. Legal, HR, and finance stay approval-gated permanently.

The order of adoption

One pilot first, then cohort by cohort and surface by surface.

The pilot is the COO and General Counsel, because theirs is the hardest inbox in the building, spanning legal, finance, and HR. Each pairing of cohort and surface passes its own shadow-mode evaluation before advancing.

The pilotCOO and General Counsel
The hardest inbox in the building is proven first. Once the pilot clears its gates, the path opens for the cohorts behind it.
Role cohortsR1 through R6
After the pilot clears its gates, role cohorts onboard in order, from R1 through R6, each earning its reach the same way.
SurfacesEmail, then calendar and tasks, then Slack
Surfaces activate in order: email first, then calendar and tasks, then Slack. Each pairing of cohort and surface passes its own shadow-mode evaluation before advancing.
First week, definition of done

What "done" looks like at the end of week one.

Next

Start small, earn reach, expand with confidence.

Adoption is staged and safe by construction: one pilot, one surface, shadow mode, and gates that must be passed and measured before anything grows.