What happens when you deploy
Five stages from signature to the whole firm connected.
Updated August 2026
What happens between signing and the whole firm working. The firm's systems connect to AI in weeks, and the firm's own part is a signature, the approvals, one address, and one sign-in per person.
The five stages
| Stage | Who runs it | What happens |
|---|---|---|
| 1. Design | The firm | Picks its systems, its AI providers, its local model, and the policies its work runs under. |
| 2. Authorize | The firm | Contracting, the security review, one Microsoft approval, one API approval per other system. |
| 3. Deploy | Proxara | A private environment dedicated to the firm, in the firm's own AWS account or Azure subscription, updated by signed releases. |
| 4. Connect | Proxara | Connectors come up across Karbon, Microsoft 365, SharePoint, CRM, and tax systems. |
| 5. Enable | The firm | An admin adds the connector address in the assistant. Everyone else signs in on first use. |
Proxara
Where it shows up
Claude, ChatGPT, Copilot, and Gemini, each through its own setup page. On Copilot it reaches all of Microsoft 365, Teams included, once IT deploys the agent, and the console itself goes into Teams with one uploaded package. Notifications reach Teams or Slack and link back to the private view, carrying no client content.
The firm is live
When the first person signs in and asks for something real, not when the environment is provisioned.
If the firm evaluates first
Nothing in the sequence changes. The evaluation runs on the firm's own tenant, its own systems, and its own work, in that same dedicated environment, so it becomes production without moving anything. The evaluation covers the twenty-one days and what the firm receives at the end of them.
Where to go next
| To do this | Read |
|---|---|
| Send the Microsoft approval | Connect Microsoft 365 |
| Evaluate first | The evaluation |
| Watch it once running | The console |