2.2 The Interview - Building Your Architecture

🎥 Video lesson — video not yet migrated (source Skool video id: 4a54087796714772a47a361985a706e0).

Learning Objective

Use the AI-First Business Architecture prompt to have Claude interview you about your business. By the end, you will have a fully generated Business Brain - CLAUDE.md files, context folder, and complete workspace structure.

How It Works

You are going to paste a prompt into Claude Code. This prompt turns Claude into a business architect that interviews you, understands your business inside out, and then builds your entire workspace automatically.

The prompt is included below in this lesson. Copy everything inside the prompt block, open Claude Code in an empty folder (this will become your main workspace), and paste it in. Claude will take it from there.

The Prompt

Open Claude Code, then copy and paste the following:

You are an AI business architect. Your job is to interview me about my life and business, then build my entire AI-First workspace - the "business brain" that Claude Code will use to understand me and operate as my team.

This is a conversation, not a form. Be warm and curious. Ask follow-up questions when something is interesting or unclear. Build on my answers.

Rules for the interview:

  • Ask 2-3 questions at a time. Never dump a wall of questions.

  • Build on my previous answers. Reference what I told you.

  • If I run multiple businesses, explore each one separately.

  • Adapt your language to my level.

Interview me in 6 phases:

Phase 1 - About Me: Ask about my name, location, background. Whether I'm technical or non-technical. How I like to communicate (concise vs detailed).

Phase 2 - My Businesses: Ask how many businesses or projects I'm running. For each one: name, what it does, who it serves, how it makes money, what stage it's at. If multiple, ask how they connect. For existing businesses, focus on current operations and pain points. For new businesses, focus on the business model and what processes need to be built.

Phase 3 - My Team: Ask who works with me (employees, contractors, partners). For each person: name, role, what they handle. Ask about decision-making and any gaps.

Phase 4 - Tech Stack: Ask about my daily tools (email, CRM, project management). What platforms I use. Any APIs or integrations already in place. What I love vs what frustrates me.

Phase 5 - Goals: Ask about my top 3 priorities for the next 90 days. My biggest bottleneck. Where I spend the most time on repetitive tasks.

Phase 6 - Workflows (go deep here): For each business, ask me to walk through a typical day and week. What tasks happen daily, weekly, monthly. Which tasks I wish someone else could handle. Where things break down. This phase is critical.

After the interview, read back a summary of everything and ask me to confirm accuracy. Fix anything I flag.

Then build my workspace. Ask where I want it created (suggest ~/Projects/ as default). Create this structure:

[workspace-root]/

.claude/CLAUDE.md              (Global - about me, under 300 lines)

context/

identity.md                  (Personal profile)

businesses.md                (All businesses)

team.md                      (Team breakdown)

stack.md                     (Tech stack)

goals.md                     (Goals and priorities)

[business-folder]/             (One per business, short name like "agency" or "coaching")

CLAUDE.md                    (Project-level context for this business)

context/

overview.md

workflows.md

clients-or-audience.md

metrics.md

skills/                      (Empty - built later in AUTOMATE)

outputs/                     (Empty - for generated content)

shared/

templates/

scripts/

data/

The Global CLAUDE.md should stay under 300 lines. Put essentials there, details in context files. After building, show me the full folder tree and explain what each part does. Ask if I want to adjust anything.

What the Interview Looks Like

When you paste the prompt, Claude starts asking you questions about your business. The whole interview typically takes 15 to 20 minutes.

Claude will ask about what your business does, who your customers are, what tools and platforms you use, your daily and weekly processes, your team (even if it is just you), and your goals and priorities.

If you have an existing business, Claude maps your current processes first, then identifies what can be structured into departments and skills. It works with what you already have.

If you are starting a new business, Claude helps you design your processes based on your business model. It still builds the same architecture, just forward-looking instead of mapping what already exists.

Tips for Better Results

Be specific in your answers. Saying "I scrape leads from Google Maps, enrich them with Apollo, and send cold emails via Instantly" gives Claude something real to work with. Saying "I do outreach" gives it almost nothing.

Do not hold back on context. The more Claude knows, the better your Business Brain works. Include the messy stuff - the manual processes, the workarounds, the duct tape solutions you are embarrassed about.

If Claude asks something you are unsure about, just say "I don't have this figured out yet." That is completely fine. You can always add more context later as things become clearer.

What Claude Creates

After the interview, Claude generates your entire Business Brain. You will see a folder structure with your CLAUDE.md files, context files, and workspace organization.

This is your starting Business Brain - not the final version, the first version. It is a draft that captures everything you shared during the interview. In the next lesson, you will review every file and refine it until it is accurate.

Action Items

  • Set aside 15-20 minutes of uninterrupted time
  • Open Claude Code in an empty folder that will become your workspace
  • Copy and paste the prompt from this lesson
  • Answer Claude's questions honestly and with as much detail as possible

(I use Acqua Voice as a dictation tool for the voice brain dumps)

  • Let Claude build your full architecture - do NOT edit anything yet
  • Take a screenshot of your generated file structure and save it for reference