92: Your Next Hire Doesn't Need Benefits: How Interior Designers Can Build an AI Team

If AI hasn’t worked for you yet, it’s probably not the tool.

It’s not the prompts.
It’s not that you’re behind.
And it’s not that AI “doesn’t work for designers.”

It’s an organization problem.

In this episode, John breaks down why most interior designers are using AI like a junk drawer and how shifting from “tool” thinking to “team” thinking completely changed how he runs his business.

After running bi-coastal offices and feeling stretched thin, he realized AI wasn’t about better prompts. It was about better infrastructure.

This episode walks you through:

• Why AI feels generic when you use it casually
• The junk drawer analogy that explains most AI frustration
• The difference between using a tool and building a system
• How to think of AI as specific assistants with specific roles
• Why onboarding matters, even for artificial intelligence
• The foundational document that makes everything work
• How small firms can gain leverage without hiring more staff
• The real emotional shift that happens when the system carries the weight

If you’re a solo designer or running a small firm and wearing every hat, this episode will reframe what’s actually possible.

This is the beginning of a deeper conversation about building infrastructure instead of chasing output.

Because your next hire might not need benefits.

Transcript

Imagine hiring a new assistant every single day.

You walk into the office and say,
 “Okay, here’s how I talk. Here’s what I believe. Here’s how I work with clients. Here’s what I would never say. Here’s my tone. Here’s how I position myself.”

And then tomorrow?

They forget everything.

You would never run your design firm like that.

But that’s exactly how most people are using AI.

And it’s not AI’s problem.

It’s an organization problem.

Hey y’all, you’re listening to the McClain Method Podcast, Episode 92.

If I sound a little under the weather, it’s because I am. I’m on the tail end of a cold. But this conversation has been sitting on my heart for a while, and I didn’t want to wait.

Today we’re talking about AI.

And I’m going to say something that might annoy you just a little.

If AI hasn’t worked for you, it’s probably not the tool.
 It’s probably not the prompts.
 It’s not because you’re behind.
 And it’s not because AI “doesn’t work for designers.”

It’s because nobody told you the thing that actually makes it work.

And once you understand this, you’re going to look back at every frustrating AI moment and think,
 “Oh. That’s why.”

So stay with me.

The Season I Was Stretched Thin

There was a time when I was running two offices. Florida and Los Angeles. Two coasts. Two teams. Projects everywhere.

Client fires.
 Team questions.
 Marketing that kept getting pushed down the list.

I love automation. I’ve always loved automation. Newsletters, onboarding, scheduling, payments. I’ve been using systems in my business for years.

So when AI came along, I thought,
 “This is like 20 team members.”

I remember sitting in my car between a site visit and a client call. Answering emails. Thinking about a proposal I had to write. Realizing my Instagram hadn’t been touched in two weeks.

And I thought,
 “If I could just clone myself for the business side of this, I could focus on the design.”

That’s where my head was.

I wasn’t looking for something trendy.

I was looking for breathing room.

So I opened AI. Typed in a prompt. Asked it to write a post.

And what came back?

Generic.

Overly polished. Structured. Clean.

And not me.

So I did what most of you have done.
 I rewrote the whole thing.

It took longer than just writing it myself.

And I remember thinking,
 “This is dumb. This is not saving me time.”

I almost stopped using it.

The moment that changed everything?

I stopped trying to get better output.

And I started building a system.

The Junk Drawer Problem

Most designers are using AI like a junk drawer.

You know the one. Batteries. Rubber bands. Old takeout menus. Three kinds of tape. A screwdriver that may or may not work.

Mine has charging cords from devices I don’t even own anymore.

When you need something, you open it. Dig around. Grab what you need. Close it.

That’s how most people use AI.

Open a new chat.
 Throw in a request.
 Hope something useful comes out.
 Close it.
 Start over tomorrow.

No context.
 No memory.
 No foundation.

Every conversation starts from zero.

That’s exhausting.

And it guarantees generic output.

The Shift: From Tool to Team

The shift for me happened when I stopped asking,
 “How do I get this to write better?”

And started asking,
 “What role does this play in my company?”

What if instead of one generic tool, you had specific assistants with specific jobs?

One for marketing.
 One for client communication.
 One for Instagram.
 One for newsletters.
 One for proposals.

Each one trained.
 Each one onboarded.
 Each one knowing your tone, your values, your no-no list, your boundaries.

That’s when AI stopped feeling like a novelty.

And started feeling like payroll.

Except:

One platform.
 No benefits.
 No turnover.
 No sick days.
 No office drama.

It just runs.

Quietly.

In the background of your business.

That’s when it clicked.

I wasn’t improving writing.

I was building infrastructure.

The Foundation Nobody Talks About

None of this works without a foundation.

You cannot build a team without onboarding.

And onboarding requires documentation.

For me, that became my Brand Bible.

It’s the single source of truth for:

How I sound
 What I believe
 My boundaries
 How I talk about money
 How I talk about designers
 What I refuse to say
 My positioning
 My values

Everything lives there.

Without that document, every assistant starts from scratch.

With it?

They reference the same brain.

Mine.

That’s when AI stopped guessing and started reflecting.

Not when I found a better prompt.
 Not when I watched another tutorial.

When I wrote the manual.

If you’ve ever hired a junior designer, you know this is true.

They’re not bad on day one.
 They’re untrained in your way.

AI is the same.

What This Changes for Small Firms

As a solo or small firm designer, there’s always been a ceiling.

Only so many hours.
 Only so much creative energy.
 Only so much administrative tolerance.

Hiring help is expensive.

Social media managers cost money.
 Copywriters cost money.
 PR costs money.
 Email strategists cost money.

And all of them require management.

What if instead, you built a system that already knows your voice and can do those jobs consistently?

Not perfectly.

Consistently.

This is leverage small firms have never had before.

And it’s not about replacing people.

It’s about removing unnecessary weight from your shoulders so when you hire, you hire for creativity and growth. Not because you’re drowning in admin.

When this started working for me, I felt something I hadn’t felt in a long time.

Relief.

Real relief.

Because I was no longer the bottleneck for every single piece of content or communication.

The system carried it.

Tool vs System

A tool is something you use occasionally.

A system runs whether you’re thinking about it or not.

A tool requires effort every time.

A system requires design once.

If AI feels frustrating, you’re probably still treating it like a tool.

Opening the junk drawer.
 Digging around.
 Closing it again.

Instead of building labeled drawers:

Marketing.
 Client communication.
 Content.
 Internal operations.

Clear roles.
 Clear training.
 Clear expectations.

That’s how companies run.

AI is no different.

Closing

This episode is the starting point.

If you’ve been frustrated with AI…
 If you tried it and gave up…
 If you secretly feel behind…

You’re not behind.

You just haven’t onboarded your team yet.

I’m going to keep talking about this. I’m building products around this exact idea.

Not hype.
 Not tricks.
 Infrastructure.

The designers who figure this out early are going to build quiet advantages that compound over time.

Not because they found a shortcut.

Because they built something that runs.

Since I started using AI as structured team members, it has saved me over 20 hours a week.

That’s real.

So stay with me in this series.

Your next hire might not need benefits.

And I’ll see you next time on the Method.