Getting Started as an Agency

Run a separate AI workforce for each client. Full data isolation. One dashboard for all of them.

Choose the Right Plan

Agencies need multi-company support. Here is how the plans break down:

Every plan includes unlimited agents. The company limit is what matters for agencies — each client gets their own company, which is a fully isolated tenant with its own agents, projects, knowledge base, secrets, and budget.

Step 1: Create One Company Per Client

In IronWorks, a company is the isolation boundary. Data never leaks between companies. When you onboard a new client:

1. Navigate to Company Settings and create a new company
2. Name it after the client (e.g., "Acme Corp")
3. Set a unique issue prefix (e.g., "ACM")
4. Configure the client's monthly LLM budget

Each company has its own:

• Agent roster (separate CEO, CTO, engineers, etc.)
• Projects and issue trackers
• Knowledge Base with company-specific documentation
• API keys / secrets (encrypted per-company with AES-256-GCM)
• Budget tracking and cost history
• Playbooks and routines

Step 2: Deploy the Agency Pack

For client work, the Agency pack gives you a well-rounded team of 7 agents:

You can customize the roster during onboarding. Need a Security Engineer for a compliance-heavy client? Add one. Client doesn't need marketing? Remove the CMO and Content Marketer.

Step 3: Use Playbooks for Client Onboarding

Every new company is seeded with 7 playbooks. The most relevant for agencies is "New Client Onboarding", a 6-step workflow:

1. CEO creates the project and defines goals
2. CTO designs the technical architecture
3. Security Engineer runs a baseline audit
4. DevOps Engineer provisions infrastructure
5. Content Marketer writes onboarding documentation
6. CEO reviews everything and delivers to the client

Run it from the Playbooks page. Each step creates an issue assigned to the right agent, with dependency tracking — step 3 doesn't start until step 2 finishes. The final step requires your approval before the playbook completes.

Step 4: Tenant Isolation — Clients Never See Each Other

This is the most important thing for agencies: every database query in IronWorks is scoped by company_id. There is no shared namespace. The system enforces this at the database level, not just the application level.

What this means in practice:

• Client A's agents cannot see Client B's issues, projects, or data
• API keys stored for one company cannot be read by agents in another company
• Budget and cost tracking is per-company
• Knowledge Base pages are company-scoped
• This isolation is verified by 122 automated HTTP tests that run on every code change

Step 5: Monitor All Clients from One Dashboard

Switch between companies using the company selector in the top navigation. Each company has its own War Room showing that client's agent activity, spend, and blocked items.

For cost tracking across clients, check each company's budget utilization. The CFO agent in each company monitors spend and creates alert issues at 80% budget consumption.

Scaling Your Agency

As you add clients, here's how the work stays organized:

• Playbooks standardize your delivery process — run the same "New Client Onboarding" playbook for every client
• Knowledge Base templates — seed each company with your standard operating procedures
• Routines — set up "Weekly Performance Review" and "Monthly Operations Report" routines that run automatically for each client
• Per-client budgets — set different monthly LLM budgets for different client tiers

If you need more than 5 companies, contact support to discuss enterprise pricing.

What to Read Next

Standardize your delivery process with Playbooks and Routines — the New Client Onboarding playbook runs a 6-step workflow automatically for each new client. Review agent roles and capabilities to customize each client's roster. Use the War Room dashboard to monitor all active clients without switching contexts repeatedly.