Your AI team, ready in under an hour.

Before you begin setup, make sure you have a Claude account. If you don't have one yet, go to claude.ai and sign up. A Pro plan works; Max is not required.

Right-click the zip file you received and choose Extract All. You'll get a folder called MyAITeam.

Where you put this folder matters. Every time you open Claude Code — whether you're in a terminal or using the app — you'll be pointing it at this folder. That means you'll reference this path regularly, not just today. Picking a spot you can find without thinking about it saves friction every single time.

The easy default is your Desktop. It's always right there, easy to open, and easy to drag into a terminal window. If you later decide to move the folder somewhere else, that's completely fine — just re-open it in Claude Code from the new location and you're back in business.

Once unzipped, peek inside the folder. Here's what you'll see:

• Team Inbox/ — your drop zone. Drag files here anytime you want the team to process them.
• Owner's Inbox/ — the team's outbox to you. Results and finished work appear here.
• Team/ — your team roster and each member's profile. Auto-populated during setup.
• Archive/ — long-term storage. Filed documents land here, organized by date.
• data/ — the team's searchable database. You don't need to open this.
• CLAUDE.md — the team's rulebook. Claude reads this at the start of every session.
• setup-guide.html — this file. Keep it open on a second screen.

In the Claude Code chat box, type the following phrase exactly and press Enter. No slash needed — just type the words.

Claude will respond with a friendly greeting and explain what's about to happen. It'll say it needs a few minutes and a few quick questions. When it asks if you're ready, just say yes or let's go — whatever feels natural.

From here on, Claude leads the conversation. Steps 5 through 12 walk you through each question it will ask, so you know what to expect and why.

Claude will ask two quick questions to personalize your team.

First: What should it call you? Just your first name is fine.

Second: In one sentence, what do you do for work? This helps your team understand your context from day one — so they give you relevant answers, not generic ones.

Example answer for the second question: "I'm a tax accountant at a CPA firm and I manage client returns, extensions, and correspondence."

Answer in plain English, as if you're telling a new colleague. There are no wrong answers. If you'd rather skip a question, just say "skip" and Claude will use a reasonable default.

Claude will show you a short list of common ways people use their AI team and ask which ones sound useful to you. You can pick as many as you like, or describe your own.

The list includes things like: research and background briefs, writing and editing, summarizing documents or meeting notes, project tracking, data work, and finding new tools or vendors.

Pick whatever matches how you actually work. If you're not sure yet, selecting all six defaults is perfectly fine — your team will adapt over time as they learn your patterns.

Claude will ask what industry or field you work in. This is optional — you can skip it if you prefer. But it's worth answering: your Researcher uses this to know where to look by default, so briefs start relevant rather than generic.

Example answers: "public accounting," "tax and audit," "financial services," "small business consulting."

One to three words is all you need.

This is the fun part. Claude will introduce each of your four team members one at a time and ask you to give each one a name. Here's who they are:

• Coordinator — your front door. Routes every request to the right team member. Never does the work directly.
• Researcher — looks things up, summarizes findings, delivers structured briefs.
• Recruiter — designs and hires new specialists when you need a capability your current team doesn't have.
• Archivist — files your documents, builds a searchable memory, keeps everything organized.

For each role, Claude will suggest five name options with a short rationale for each — personality sketches, really. You can pick one from the list or suggest your own. Nothing is created until you confirm a name.

The shortlists are right there in your Claude Code chat. Read them over and pick whichever name feels right. There's no wrong choice — these are just names that fit the spirit of each role.

Don't overthink it. Many people pick a name within ten seconds. The team will feel like yours regardless of what you choose.

After naming your team, Claude will ask a series of questions about how you actually work. These are called workflow discovery questions, and they're what makes your team genuinely useful rather than generic. You can skip any of them.

First question: Walk me through a typical week — what kinds of work regularly land on your plate?

A sentence or two is enough. You might say something like: "Most of my week is tax returns and client correspondence, with a standing weekly meeting to review a partner's open items."

The more honestly you describe your week, the better your team can anticipate what you need.

Claude will ask: what types of files do you deal with most often, and is there anything you regularly struggle to find when you need it?

Example answer: "Mostly PDFs — tax returns, engagement letters, client emails. I lose track of which folder things end up in, especially older client documents."

This feeds directly into how your Archivist organizes and tags your files. If you have a specific frustration here, say it plainly — that's exactly what your Archivist is designed to solve.

Two more questions in this section:

Friction: What about your current way of organizing files or notes frustrates you most? Even a small annoyance counts.

Automation wishlist: If you could hand off or automate three things from your regular workload, what would they be?

Example answers: "I hate digging through email threads to find the latest version of a document." / "I'd automate drafting follow-up emails, pulling together weekly summaries, and chasing down outstanding items."

Claude will also ask if there are standing projects or topics the team should know about from day one — recurring areas of your work that come up week after week. A sentence or two there is plenty.

The last workflow question: do you handle anything sensitive that the team should treat with extra care?

In accounting and professional services, the honest answer is usually yes. Client tax returns, financial statements, engagement letters, payroll records, and attorney-client materials all qualify.

Example answer: "Yes — client tax returns, financial statements, and anything with SSNs or EINs. Please flag before processing anything in those categories."

When you name specific categories here, your team will know to check with you before processing or sharing anything that falls into those areas. This is not a setting you configure — it's just a note your team carries from day one.

Once you've answered the questions, Claude will say something like: "Great. Give me a moment — I'm writing your team's files now."

This is the automatic phase. Claude is doing the following in the background:

• Filling in your team's rulebook (CLAUDE.md) with all your answers.
• Updating each team member's agent file with the names you chose.
• Renaming the agent files to match the names (so your Coordinator file is named after your Coordinator).
• Updating the team roster (Team/roster.md).
• Initializing the team's searchable database.
• Writing a welcome note to Owner's Inbox/welcome.md.

You don't need to do anything during this step. It takes about 30 seconds. When it's done, Claude will confirm with a summary of everything it created.

Read your welcome message. Open the Owner's Inbox folder inside your kit. There's a file called welcome.md — open it in any text editor. It lists your four team members by name and tells you exactly how to work with each one.

Try your first task. Go back to Claude Code and type something like this — substituting whatever names you chose during setup:

Replace the bracketed names with whichever names you chose. This shows you how the Coordinator routes a request to the Researcher and how results come back to you.

Day-to-day usage. Once you're up and running, using your team is simple:

• Drop files in Team Inbox anytime — invoices, notes, PDFs, screenshots, anything. When you're ready to have them filed and searchable, type: process my inbox
• Ask for things in plain English. Your Coordinator handles all routing. You don't need to know which team member to contact — just describe what you need.
• Check Owner's Inbox for results. Finished work, summaries, and answers show up there.
• Capture preferences with /remember. If you want the team to remember something permanently ("always use bullet points for summaries"), type /remember [preference] and it gets logged for all future sessions.

Growing your team over time. Your four starter members handle the most common needs — but they're not meant to be your permanent roster. When you hit a task none of them handle as well as you'd like, just tell your Coordinator: "I need someone who can [fill in the blank]."

The Coordinator will route to the Researcher to study what a real professional in that role does, then the Recruiter will design the new role and bring you a shortlist of three to five candidate names. You pick the name, you approve the hire. Nothing gets created without your sign-off. Your team grows with you.

If you hit a snag, check the README-WINDOWS.txt file in your kit folder — it has a troubleshooting section covering the most common issues. Or reach out to Trey directly.