The multi-department approach
Multi-department rollout works best as a phased model. Start with one team and one bounded job. Make it stable, make the approvals clear, then expand one team at a time.
The alternative is a big-bang rollout across the whole company. That usually creates unclear ownership, too many approvals at once, and a system people do not trust yet. Starting small keeps the rollout calmer and easier to manage.
Start with one department
Pick the team that wants agents first. Launch one bounded job and make the review pattern clear.
Expand one department at a time
Add finance, operations, or support one at a time. Reuse the same safe pattern as you expand.
Shared controls across all
Keep one approval model, one activity history, and one clear ownership pattern across the rollout.
Rollout sequence
The rollout sequence has four stages: first team, expansion inside that team, second team, and ongoing expansion. Each stage should feel bounded and easy to review.
| Stage | Scope | Duration | Exit criteria |
|---|---|---|---|
| First team | Launch one agent for one clear job | Longest stage | Approvals are working and the team trusts the setup |
| Expansion inside the same team | Add more agent jobs in the same area | Faster than the first stage | Ownership stays clear and the team is confident |
| Second team | Launch the first agent in a new team | Shorter than the first launch | The rollout pattern transfers cleanly |
| Ongoing expansion | Add more teams one at a time | Steady pace | The rollout stays visible and easy to control |
Department onboarding checklist
Each new team should follow the same onboarding checklist. That keeps approvals, ownership, and visibility consistent as the rollout grows.
Pre-onboarding tasks:
- Identify the team lead who will own agents in this area
- Confirm the department wants agents and is ready to adopt
- Pick the first job for this team, ideally high-frequency and low-risk
- Confirm the stack is already connected (or connect it via OAuth)
Onboarding tasks:
- Set approval rules for this team
- Assign the team lead as the primary owner
- Describe the first agent in plain English with the team lead
- Launch the first agent and review the first approvals together
- Check the activity history for this team
Post-onboarding tasks:
- Confirm the approvals are sensible and the team trusts the setup
- Check whether the agent is saving time or removing manual work
- Add adjacent agent jobs in the same team only after the first one is stable
- Confirm the team lead is confident before moving to the next team
How controls scale across departments
As you add more teams, the goal is to keep the control model simple. Each team should know what it owns, who reviews which actions, and where to see the history.
- Unified approval model. Sales ops approves CRM agents. Finance manager approves QuickBooks agents. Support ops approves Zendesk agents. Each team lead owns approvals in their domain.
- Unified activity history. Every action, decision, and approval is visible across all teams. The rollout owner can still see the whole picture in one place.
- Spend caps per department. Set a hard limit for each department. When a department hits the cap, all agents in that department pause and notify the owner.
- Scoped permissions per department. Sales agents only touch Salesforce. Finance agents only touch QuickBooks. Support agents only touch Zendesk. Boundaries stay clear as the rollout grows.
Frequently asked questions
Can we deploy to all departments in parallel?
It is better to start with one team, get the first setup working well, then expand. Rolling out everywhere at once usually creates confusion, unclear ownership, and too many approvals at the same time.
How long does multi-department rollout take?
The first team usually takes the longest because you are setting the pattern. After that, expansion gets faster because the approval model, ownership, and review habits are already in place.
What if one department is not ready for agents yet?
Skip them for now. Start with the teams that want the change, have a clear job in mind, and are ready to review the first approvals.
Who owns agents when they span multiple departments?
Give the agent a primary owner from the team that needs the outcome most. That person owns the approvals in their area, while the rollout owner keeps access, visibility, and cross-team alignment clear.