How to Choose Between AI Agent Packages (Solo, Department, or Workforce)

I get this question on almost every discovery call: "Mark, I know I need AI agents, but I have no idea if I need one agent, five agents, or a full workforce. How do I decide?"

The honest answer is that it depends on three things — the number of distinct processes you want to automate, how connected those processes are, and how much of your current operations can run without you. Not your budget. Not the size of your team. Not how many competitors are using AI.

Let me walk you through the framework I use with every client. By the end of this, you will know exactly which tier makes sense for your business right now, and what triggers the move to the next level.

The Three Tiers

Before I get into the decision framework, here is what each tier actually includes. No fluff, just what you get.

Solo Agent ($750): One AI agent with a defined role, 5 skills, connected to one messaging channel. Think of this as hiring a single specialist — a booking agent, a lead qualifier, a follow-up agent, or a customer FAQ handler. It does one thing and does it well.

Department Build ($2,500): One department head agent plus 2-3 specialist agents working together. This covers an entire function — your sales pipeline, your customer service, your operations admin. The agents coordinate with each other. Cron jobs run daily for proactive monitoring. Think of this as hiring a small team.

AI Workforce ($7,500+): Full multi-agent hierarchy — a COO-level coordinator, department heads, and specialists. Eight to eighteen agents covering multiple business functions. Cross-department coordination, approval workflows, daily briefings. This is the 18-agent system I run for my own business.

Decision Factor 1: How Many Processes Need Automation?

Count the distinct processes you want off your plate. Not tasks within a process — the actual end-to-end processes.

1-2 processes? Solo Agent. If your main pain is lead follow-up and nothing else, one agent handles it. If you need appointment booking and reminders, that is still one process — one agent.

3-5 connected processes within one function? Department Build. If your sales function needs lead qualification, quote follow-up, nurture sequences, and pipeline reporting — those are connected processes that benefit from agents that communicate with each other. A department build covers this.

5+ processes across multiple functions? AI Workforce. If you need sales, marketing, operations, and admin all running with agents, you need a hierarchy. The coordinator ensures nothing conflicts across departments, and each department's agents specialize in their domain.

Decision Factor 2: How Connected Are the Processes?

This is the factor most people overlook. Disconnected processes can run as independent solo agents. Connected processes need agents that talk to each other.

Here is the difference:

Disconnected: Your lead capture process and your invoicing process. They involve different people, different data, and different timelines. Two solo agents work fine.

Connected: Your lead capture process, your quote follow-up process, and your post-sale onboarding process. A lead that converts needs to flow from one process to the next with context intact. The agent that qualified the lead should pass information to the agent that handles onboarding. This requires a department build where agents communicate.

Deeply connected: Your marketing generates leads that sales qualifies that operations fulfills that billing invoices. Information needs to flow across departments. A change in one department affects the others. This is workforce territory.

If you try to run deeply connected processes with independent solo agents, you end up being the human router between them. Which defeats the purpose.

Decision Factor 3: How Much Runs Without You?

Be honest about this one. If you disappeared for a week, what would happen to your business?

It would collapse because I do everything. Start with a Solo Agent targeting your biggest bottleneck. You need to learn the agent pattern before scaling. Going straight to a workforce when you have never worked with an agent is like hiring 18 employees on the same day — chaos.

A few things would keep running, but most would stop. Department Build. Automate the function that depends most on you personally. For most owners, that is sales or client management.

Most things would keep going, but slowly and with more mistakes. AI Workforce. You already have systems. The agents take those systems from "functional without you" to "excellent without you."

The Upgrade Path

Here is something I tell every client: you are not making a permanent choice. You are choosing a starting point.

Most of my workforce clients started as solo agent clients. They deployed one agent, saw the value, added another, realized the agents needed to coordinate, and upgraded to a department build. After running a department successfully, they expanded to cover more functions.

The solo agent teaches you how to define processes, set boundaries, and work with agents. The department build teaches you how agents collaborate. The workforce teaches you how an entire business can run with you as the strategic brain rather than the operational bottleneck.

Trying to skip steps usually backfires. I have had prospects come to me wanting the full $7,500 workforce who could not clearly describe even three of their processes. If you cannot map it, you cannot automate it. Starting small forces you to get clear on how your business actually works.

When Each Tier Is Overkill

I believe in being honest about this, even though it means leaving money on the table.

Solo Agent is overkill if: You get fewer than 20 customer interactions per week. At that volume, handling things manually is still manageable and the time savings do not justify the investment.

Department Build is overkill if: Your processes are genuinely independent. If your booking system and your invoicing system have nothing in common and do not need to share information, two solo agents are cheaper and simpler than a department build.

AI Workforce is overkill if: You are a solo operator without employees or contractors. The hierarchy pattern works because it models an organization. If there is no organization — just you — a solo agent or department build gives you the same benefit at a fraction of the cost.

The Quick Decision Matrix

Answer these three questions:

1. How many distinct processes do you want to automate?

   • 1-2 → Solo Agent
   • 3-5 in one function → Department Build
   • 5+ across functions → AI Workforce

2. Do the processes need to share information?

   • No → Solo Agents (one per process)
   • Within one function → Department Build
   • Across functions → AI Workforce

3. Have you worked with AI agents before?

   • No → Start with Solo Agent regardless of where you think you will end up
   • Yes, with one agent → Department Build
   • Yes, with a team → AI Workforce

If your answers point to different tiers, go with the lower one. You can always upgrade. Downgrading is wasteful.

After the Build: The Retainer Question

Once your agents are running, you will need ongoing maintenance. Agents are not "set it and forget it." Your business changes, your processes evolve, and the agents need to adapt.

The monthly retainer at $750/month covers agent tuning, new skill additions, priority support, and a monthly strategy call. Not every client needs it — if your business is stable and your agents are running smoothly, you might only need occasional support. But if you are growing fast or adding new services regularly, the retainer keeps your agents current.

What I Actually Recommend

For 80% of the business owners I talk to, the answer is start with a Solo Agent. Not because the other tiers are not valuable, but because the first agent teaches you more about your own business than any consultation could. You discover which processes are well-defined and which are chaotic. You learn what works for your customers and what does not. And you make better decisions about scaling because you have real experience.

The 20% who should start higher are businesses that already have documented processes, have worked with automation before, and know exactly what they want. For them, the department build or workforce makes sense from day one.

If you are not sure where you fall, book a call. I will ask you the questions above and give you a straight answer. Sometimes that answer is "you are not ready for any of this yet" — and that is fine too.