The AI Team Blueprint — Virtually Structured
Virtually Structured
The AI Team Blueprint
A Virtually Structured Workshop

The AI Team
Blueprint

Build It. Train It. Let It Run.

You're going to walk through a guided conversation with Claude that helps you design, build, and train a custom AI team for your specific business. This isn't a template you fill in — it's a custom build based on how your business actually works.

Before You Start
A Claude account on a paid plan — you'll need this for the conversation to work well (claude.ai/upgrade)
This guide open alongside your Claude chat — two windows or two tabs works great
60–90 minutes for your first session — longer if you're building multiple team members in one sitting
1Your Business Snapshot
2Your Systems Snapshot
3Your Tools & Connections
4What's Taking Your Time
5Your Team Diagnosis
6Build Your Team
7Train Your Team
8Your Handoff Plan

Keep this guide open in one tab. Open Claude.ai in another. You'll paste each prompt directly into your Claude chat.

Step 1 of 8 — Your Business Snapshot

Who you are and who you serve.

Before Claude can recommend your team, it needs to understand your business. This step builds the foundation everything else is built on. Open a new Claude chat and paste the prompt below.

Paste to Claude
I'm building a custom AI team for my business. Before we figure out who I need, help me get clear on how my business actually works. Ask me the following — one at a time, and push back if my answers are vague:

1. What do you do? (Your core service or offer — one sentence. The main thing.)

2. Who do you serve? (List 3–5 specific types of people or businesses. Be narrow.)

3. What does your client get? (The transformation or outcome — what changes for them after working with you?)

4. What stage is your business in? (Just getting started / growing and getting busy / established and ready to scale — pick the one that fits best and describe what that looks like for you.)

5. How do you currently get clients? (Word of mouth, email list, podcast, social media, referrals — all of it.)

Once I've answered all five, summarize what you heard back to me in 3–4 sentences so I can confirm before we move on.
Answer each question. Let Claude push back and tighten your answers. When Claude summarizes and you confirm it feels right, move to Step 2.
Step 2 of 8 — Your Systems Snapshot
New

What's working — and what isn't.

An AI team built on broken or missing systems will underperform — not because the team isn't good, but because they won't have a foundation to work from. This step maps what's actually in place right now so Claude can build the right team for where you actually are.

There's no wrong answer here. You can build an AI team at any stage of business. This isn't a readiness check — it's a reality check. Knowing where your gaps are means your team will be built to fill them, not ignore them.
Paste to Claude
Now let's take a snapshot of the systems behind my business. I want to know what's actually in place — not just what tools I use, but whether things are running smoothly or breaking down.

Ask me about each of these areas — one at a time. For each one ask me: Do you have a system for this right now? Is it working well, or does it feel chaotic or nonexistent? Where does it break down most often?

Areas to ask about:

Client experience (onboarding, communication during the project, offboarding)
Content and marketing (planning what to create, actually creating it, publishing consistently)
Sales and follow-up (tracking inquiries, following up with leads, converting prospects)
Operations and admin (scheduling, task management, documents and contracts)
Finance and money (invoicing, tracking what's coming in, knowing your numbers)
Team or contractor coordination (if you have any support right now — VA, contractors, anyone)

After I answer all areas, give me:
1. A quick summary of where my systems are strong
2. Where my biggest gaps or breakdowns are
3. One note on how those gaps might shape the AI team we build — so we build the team I actually need, not a generic roster
Be honest here. The more specific your answers, the more targeted your team will be. When Claude gives you the summary and it resonates, move to Step 3.
Step 3 of 8 — Your Tools & Connections

What your team can actually work with.

Your AI team members are only as useful as what they can connect to. This step maps what's already in place so Claude knows what your team can do directly — and what will require you to execute manually for now. Paste this into the same Claude chat.

Paste to Claude
Now let's map the tools and systems I use in my business. I want to know what my AI team can work with directly and what they'll need to hand off to me.

Ask me which of the following I use — and for each one I say yes to, ask me how I use it in my business:

Project management (ClickUp, Asana, Notion, Monday, etc.)
Email (Gmail, Outlook, ConvertKit, Flodesk, etc.)
Website platform (Squarespace, Showit, WordPress, etc.)
Scheduling (Calendly, Acuity, Google Calendar, etc.)
Video calls (Zoom, Google Meet, etc.)
Community or messaging (Slack, Circle, Facebook Group)
CRM or client tracking (HoneyBook, Dubsado, spreadsheet, or inside a project management tool)
Design (Canva, Adobe, etc.)
File storage (Google Drive, Dropbox, etc.)
Payment processing (Stripe, PayPal, platform checkout)

After I answer, tell me: which of these you can connect to directly in Claude.ai, and which ones will require me to execute manually for now.
Answer fully. This becomes your team's connection map — you'll reference it when you build each member. When Claude has confirmed what's connected and what's manual, move to Step 4.
Step 4 of 8 — What's Taking Your Time

Find the tasks that drain you.

This is where you identify what your AI team will actually do. Your team exists to take tasks off your plate — but first you have to name what's on it. Paste this into the same Claude chat.

Paste to Claude
Now let's figure out where I actually need help. I want to identify the tasks that are eating my time, the ones I keep dropping, and the ones I wish someone else was handling.

Ask me about each of these areas — one at a time. For each one, ask me: Is this something you're currently doing? How much time does it take? Do you enjoy it or does it drain you? Is it something you'd trust someone else to handle if they knew your business well?

Areas to ask about:

Content & marketing (writing, newsletters, blog posts, social, podcast prep)
Client experience (onboarding, check-ins, offboarding, welcome sequences)
Sales & follow-up (inquiry responses, proposals, pipeline tracking, follow-up emails)
Operations & admin (scheduling, inbox, task management, file organization)
Finance & revenue (invoicing, payment tracking, revenue reporting)
Website & visibility (SEO, site updates, landing pages, tech issues)
Community & engagement (community management, member experience, event coordination)
Research & strategy (competitor research, market trends, planning, offer development)

After I answer all areas, give me a summary of where my biggest time drains are and where an AI team member could make the most immediate impact.
Be honest here. The more specific you are, the more useful your team will be. When Claude gives you the summary, confirm it and move to Step 5.
Step 5 of 8 — Your Team Diagnosis

Build your custom roster.

Now Claude puts it all together. Based on your business, your systems, your tools, and your time drains — it recommends which team members you actually need, in the order you should build them. Paste this into the same Claude chat.

Paste to Claude
Based on everything we've talked through — my business, my systems, my tools, and where my time is going — I want you to build me a custom team diagnosis.

Give me:

1. A recommended team roster — the roles I need, each described in one sentence. No more than 8–10 to start. Prioritize based on where I'll feel the most relief fastest.

2. A build order — which member to build first, second, and so on. Explain why that order makes sense for my business right now.

3. A "not yet" list — roles that might make sense later but aren't the right priority right now, and why.

Format it clearly so I can see my recommended team at a glance.
Review Claude's recommendations. You can push back, swap priorities, or ask it to explain any role. When your roster feels right, confirm it and move to Step 6.
Step 6 of 8 — Build Your Team

Create each member, one at a time.

Now you build each team member — one role at a time. Don't rush it. One well-built member is worth more than five half-built ones. Use the field below to fill in your role, then copy the prompt and paste it into Claude.

Which role are you building?
Type the role from your roster — it'll drop into the prompt automatically so it's ready to copy.
Paste to Claude
Let's build my next team member. I'll tell you the role, and you'll help me build them out fully.

The role I'm building: [type the role in the field above]

Walk me through these one at a time:

1. Name — suggest 3 name options that feel like a real person, not a job title. I'll pick one.

2. Personality — based on the role, describe how this person shows up. Their working style, their strengths, how they communicate with me.

3. Responsibilities — list the specific tasks this team member handles. Be concrete. "Writes content" isn't enough — I want to know exactly what they do.

4. Connections — based on the tools I told you I use, which ones does this team member need access to? Which are connected and which are manual for now?

5. Skill file — write a full skill file for this team member. Include: who they are, what tools they use, their tasks with step-by-step instructions, their boundaries, and their current autonomy stage (Stage 1 — Baby Steps: drafts everything, I execute).

After you build the skill file, ask me: does anything feel off? Is there a task missing? Is there something they should never do?

When I'm satisfied, ask me to copy the skill file and store it somewhere I can find it.
Repeat this step for each team member on your roster. Clear the field above, type your next role, update the prompt, and paste it into the same Claude chat. Take breaks between members — this is deep work.
Step 7 of 8 — Train Your Team

The three stages of autonomy.

Building your team is just the beginning. A team member on paper isn't useful until you know how to work with them — and until they've earned the right to work without you watching every move. This is the framework that makes it work long-term.

Stage What It Means Your Role
Stage 1
Baby Steps
Member drafts, proposes, and flags. Nothing goes out without your eyes on it. You review and approve everything. This is where everyone starts — no exceptions.
Stage 2
Supervised
Member handles routine tasks with light oversight. Internal work moves without you in every step. You review before anything client-facing goes out. You've seen them get it right enough times to trust the pattern.
Stage 3
Autonomous
Member runs their area. Routine work happens without you in the loop for every task. You set direction and review exceptions. You see the output, not the work.
You decide when to move a team member forward — not them. The signal is trust built through repetition. When their drafts are consistently right, when their judgment matches yours, when their output doesn't need editing — that's when you consider Stage 2. Never skip Stage 1. Not even for tasks that feel simple.
Paste to Claude
Now I want to map out where each team member starts and what moving to the next stage looks like for them.

For each team member we built, tell me:

1. Their starting stage (everyone starts at Stage 1 — just confirm this and note what Stage 1 looks like specifically for their role)

2. What "Stage 1 done well" looks like — the specific signals that would tell me they're ready to move to Stage 2

3. What Stage 2 would look like for their role — what changes, what I still review

Format this as a simple table I can save and refer back to as I work with my team.
Save this table. It's your team's training roadmap. When you have it saved, move to Step 8.
Step 8 of 8 — Your Handoff Plan

How you'll actually run your team.

The final piece. Knowing your team exists isn't enough — you need a clear picture of how you'll work with them day to day, and how tasks actually move from "I do this" to "they handle this." Paste this into Claude.

Paste to Claude
We've built my team and mapped their training stages. Now I want to create my handoff plan — the practical picture of how I actually work with this team going forward.

Help me answer these:

1. How do I activate a team member? (What do I say, how do I open a session with them, what context do I give them?)

2. What's my weekly rhythm? (Which team members do I check in with regularly vs. only when something comes up?)

3. Where do team flags go? (When a team member notices something that needs my attention, where does that surface so nothing gets lost?)

4. How do I know a task is ready to hand off? (What's the checklist — for me to trust it and for them to be ready for it?)

5. What's my 30-day plan? (Which team member do I activate first, what task do I hand off first, and what does success look like in 30 days?)

Deliver this as a one-page operating plan I can save and come back to anytime.
This is your operating plan. Save it alongside your skill files. You now have everything you need to run your AI team.

Your team is built.

You've done the hard part. Everything you need to run your AI team is now in place — custom-built for your business, your tools, and your stage of growth.

What You've Built
A custom team roster built around your business — not a generic template
A skill file for each team member with clear responsibilities and boundaries
A training roadmap with autonomy stages for every role
A handoff plan so you know exactly how to work with your team day to day
A 30-day activation plan to get your first member running
Your Next Session
Open Claude. Pull up your first team member's skill file.

Tell Claude: "I'm activating [name]. Here's their skill file: [paste it]."

Give them their first task. That's it.
Your team is built. Now let it run.
Copied to clipboard