What I Tell Clients When They Ask About My Team

The question showed up on a client discovery call about three months after I'd replaced most of my execution work with AI agents.

"How many people are on your team?"

I paused. For the first six months running this way, I'd say something vague: "I work with a few specialists." It was technically true. It also felt like a small lie every time.

When I Started Telling the Truth

The honest answer is this: it's me plus a set of AI agents that run like departments. A Marketing department with a Content Creator, SEO Specialist, and Email Marketing Specialist. An Engineering department with a Backend Architect and Code Reviewer. Support, Testing, Project Management — all running as .md files through Claude Code.

When I started saying that out loud, something unexpected happened. Most clients didn't care the way I thought they would.

What they cared about was whether the work got done, how fast, and whether it was good. That's it.

What Clients Actually Ask After

The follow-up questions were practical, not philosophical.

"Who's reviewing your outputs?" Me.

"Can I talk to someone if there's a problem?" Yes, me.

"What happens if something goes wrong?" I handle it. The agents catch most errors before they reach you.

Those three answers covered about 90% of the anxiety. Clients aren't worried about AI in principle. They're worried about accountability gaps. When the answer to "who's responsible?" is a person they can call, most of them move on.

What the Agents Actually Handle

Here's what a normal client project looks like with my current setup.

The Content Creator agent drafts deliverables based on a brief I write. The SEO Specialist reviews it for search alignment and suggests keyword adjustments. If there's code involved, the Backend Architect handles the build and the Code Reviewer checks it before anything goes to the client.

For ongoing accounts, the Email Marketing Specialist writes the sequences. The Support Responder handles incoming questions and flags anything that needs my actual attention. The Status Reporter keeps a running project log so nothing falls through.

I spend my time on two things: writing the briefs and making the judgment calls. That's the actual work of a director.

A client I'd worked with for 11 months told me response quality had improved since I "expanded the team." I hadn't hired anyone. The agents had gotten better at understanding her brand voice because my briefs had gotten more specific.

What Stays With Me

The list is shorter than you'd expect, but it matters.

Every pricing decision. Every go/no-go on a new client. Every moment when something isn't working and I need to figure out whether the problem is the brief, the agent, or the strategy.

Client relationships are mine. I do every intro call, every check-in, every difficult conversation. AI agents can draft a follow-up email. They can't read the room.

Strategy is mine. Where the business goes, which clients to take, which ones to walk away from, what to build next — these are judgment calls agents can inform but can't make.

That's not a limitation. That's the job.

Where to Start Based on What You Do

If you're a service business owner, the Marketing department is where most of your execution time is going. Content Creator, Email Marketing Specialist, and Social Media Strategist handle the bulk of it.

If you're building a product, start with Engineering. The Backend Architect and Code Reviewer save more hours per week than any other combination I've found.

If you're client-facing and overwhelmed by communication, pair the Support Responder from the Support department with the Status Reporter from Project Management. Response times drop from hours to minutes.

Pick the department that handles your biggest current bottleneck. Start there.

The Honest Part

This won't work if you need headcount for optics.

Some clients, particularly large enterprises and government procurement, need to see actual employees, insurance certificates, and LinkedIn profiles. AI agents don't have those. If your deal pipeline depends on appearing to have a 20-person team, this setup won't satisfy that requirement.

But if what your clients need is fast, high-quality work delivered consistently, the size of your team is mostly irrelevant. What matters is the output and the person accountable for it.

I tell clients I'm a solo founder with an AI team. The ones who need actual headcount leave. The ones who stay care about the work.

Those tend to be the better clients anyway.

---

You're still the decision-maker. You're just no longer the only worker. Start here.