Skip to content
Hunter Green
← Services

Run-your-own workshop

Plan how your conversational tool deploys into a client's systems.

A 90-minute guided builder for teams putting a chat or voice product inside an enterprise. It produces one packet in two parts, the runbook your engineers build from and the review your client's security team signs off.

Start the builderPreview the output

The plan today

"We will connect to their systems."

The plan two teams can act on

The CRM contact record, read only through their MCP server, with every write tool denied until a human confirmation step exists.

The plan today

"It needs to be fast."

The plan two teams can act on

First token under 800 milliseconds at the median, streamed, with slow tool calls kept off the realtime voice turn.

The plan today

"It has to be secure and compliant."

The plan two teams can act on

Model and storage pinned to the EU region, PII tokenized before logging, and a SOC 2 report and signed DPA as the evidence.

The plan today

"A human can take over when needed."

The plan two teams can act on

On escalation, generate a summary, transfer the full history to a person in the client console, and keep the user in the same window.

What you leave with

One packet, two audiences.

Every answer maps to a decision in the plan. You export one Markdown file and hand Part A to your engineers and Part B to the client's security and platform teams, or feed the whole thing to Claude, ChatGPT, or an internal assistant to write the plan.

  • An integration surface map, every system, the data, and the owner
  • The connection chosen per edge, with the alternative you rejected
  • The connections the experience cannot lose, each with a target and a fallback
  • A data-flow and residency map that marks the trust boundary
  • The egress and identity path, gateway, private link, SSO, and least-privilege tokens
  • Experience controls, latency, streaming, timeouts, retries, and idempotency
  • A handoff map for every seam where control passes
  • A logging and audit plan with PII redaction before write
  • A compliance control map with the evidence a security review asks for
  • A coverage pass that stress-tests the integration before the client does
  • Checks and SLOs with measured acceptance targets
  • A handoff table split into an engineering runbook and a client review packet

Export preview

enterprise-integration-plan.md
├── LLM instructions
├── Deployment profile
├── Docs and standards targets
├── Part A, engineering runbook
│   ├── Integration surface
│   ├── Connection per edge
│   ├── Critical connections
│   ├── Experience controls
│   ├── Handoff map
│   ├── Coverage and stress-test
│   ├── Checks and SLOs
│   └── Handoff table, engineering
├── Part B, client security review
│   ├── Data-flow and residency map
│   ├── Egress and identity path
│   ├── Logging and audit
│   ├── Compliance control map
│   └── Handoff table, client review
├── Open decisions
└── Backlog seed

Start here

Enter your email to unlock the workspace

Your answers stay in this browser unless you export them. The email unlocks the builder and the blank guide, and lets us send you occasional new tools.

Pressure-test my product