Short answer
A Claude Cowork guided intake is a structured, conversational setup interview that maps your business into Claude and turns it into a configured workspace. In one sitting it produces five working assets: a Business Blueprint, a populated Cowork Vault, an active Memory Stack, a Connector Map, and your first Custom Playbooks.
If you have already tried Claude Cowork and found that it forgets who your clients are by Thursday, the problem was never your prompting. It was the absence of a setup process built to capture your business once and configure the workspace around it. The Guided Intake is that process, and the Foundation Plugin is what turns the conversation into a workspace that Claude reads on every session.
What the Claude Cowork Guided Intake Actually Builds

Most people assume that setup means typing a longer prompt or pasting a CLAUDE.md file into the project. That is not what the Guided Intake does.
The Guided Intake is a live conversation. Claude asks you direct questions about your business, your voice, your clients, your tools, and your week. By the end of that conversation Claude holds a foundational map of your business that a static instructions file never produced. Instead of one note you wrote once and forgot to update, you get a set of connected assets the workspace keeps using.
- A Business Blueprint: who you are and how you operate, in your own words.
- A Cowork Vault: your documents brought into protected, working context.
- A Memory Stack: the context that carries from one session to the next.
- A Connector Map: your tools, ranked by how much of your week they touch.
- Custom Playbooks: your recurring work, made repeatable.
Inside the 30-Minute Interview: What It Actually Asks

The interview is conversational, not a checklist you fill out alone. Claude asks, you answer, and each answer becomes a configuration decision. Expect questions across five areas:
- Business identity: what you do, who you serve, and how you describe it.
- Voice and tone: how you write to clients versus how you write internally.
- Client and project context: the recurring names, accounts, and relationships Claude needs to recognize.
- Tool stack: the systems you already run your business through, which sets up the Connector Map later.
- Weekly cadence: the recurring work that happens every week whether or not you remember to ask for it.
None of this requires technical knowledge. It asks you to answer the way you would explain your business to a capable new hire on day one. You talk; the Foundation Plugin does the configuring behind the scenes.
The Business Blueprint: Your Foundation Document
Every Guided Intake produces a Business Blueprint. This is the artifact Claude reads at the start of every session going forward. It is not a file you have to remember to attach, and it is not a prompt you retype.
This is the structural difference between the Guided Intake and a CLAUDE.md file. A CLAUDE.md file is a note you wrote once and probably never revisited. The Business Blueprint is a living reference tied to the rest of the Cowork Strategy Stack, refreshed as your business changes. When your positioning shifts or you take on a new type of client, you update the Blueprint rather than re-teaching Claude from scratch in every chat.
The Cowork Vault and the Memory Stack: Where Context Actually Lives

Once the Blueprint exists, the next phase imports your documents into active context. Files are indexed and organized inside the Cowork Vault, with your originals kept protected rather than overwritten.
This is also where the Memory Stack starts doing its job. Instead of re-explaining your brand guide or your service structure in every new chat, you let Claude log those details once so it can reference them in later sessions. Persistence here is configured, not magical: Claude carries forward what the Guided Intake intentionally stored, so the more context you commit at setup, the more your workspace compounds instead of resetting.
The Connector Map: Wiring Your Tools Into One View
The Connector Map is where the tools you already run your business through, your email, calendar, and other systems, get wired into a view Claude can read from directly. This is the part most people expect from day one and are disappointed to find missing when they try Claude Cowork cold. Without it, Claude can only work from what you paste into the chat window.
During the intake, connectors are mapped and prioritized by impact, starting with the tools you touch most in a normal week rather than an arbitrary integrations list. Connections are set up as you authorize them, so you stay in control of what Claude can reach. Under the hood this layer follows the open Model Context Protocol, the same standard the wider Claude ecosystem uses to connect tools, which is why the Connector Map is portable rather than locked to a single vendor.
Custom Playbooks and Persona Packs: Where the Stack Gets Specific
The final phase turns a configured workspace into working routines. Custom Playbooks are the specific, repeatable workflows your business runs every week, built on top of the Business Blueprint, Cowork Vault, and Connector Map from the earlier phases. Rather than describing the same monthly report or client onboarding sequence from memory each time, you capture it once and run it.
Persona Packs sit alongside Playbooks as industry-specific bundles of capability. Instead of starting from a blank Claude and hoping it improvises correctly, a Persona Pack adds pre-built skills matched to how a specific type of business actually operates. The packs are available through the Persona Packs catalog, and they layer onto the base configuration the Guided Intake creates rather than replacing it.
It helps to keep one distinction clear. Claude Code is the developer tool that Claude Cowork is built on, documented in the Claude Code overview. The Guided Intake, the Foundation Plugin, and the Persona Packs are the configuration layer that makes that foundation usable for running a business, not writing software.
Guided Intake Workflow: What It Asks vs. What It Configures
Here is the direct mapping between interview questions and the configuration each one produces.
| What the interview asks | What it configures |
|---|---|
| What does your business do, and for whom? | Business Blueprint, identity section |
| How do you sound when you write to clients? | Business Blueprint, voice and tone rules |
| Which clients, accounts, or projects recur most? | Memory Stack entries and Cowork Vault tags |
| Which documents does your business run on? | Cowork Vault ingestion, originals protected |
| Which tools do you touch every week? | Connector Map, prioritized by impact |
| What tasks repeat every single week? | Custom Playbooks and matched Persona Packs |
Why Founders Choose the Guided Intake Over Prompting Alone

For a solo founder, Claude Cowork was never a prompting problem. It is a context problem, and prompting cannot solve a context problem no matter how well written the prompt is. A founder running a lean operation does not have time to reconstruct business context in every new chat.
The Guided Intake exists so that reconstruction happens once, inside a single interview, instead of every session for the life of the account. The Foundation Plugin is what makes that stick: it connects the Business Blueprint, Cowork Vault, Memory Stack, Connector Map, and Custom Playbooks into one coherent system rather than five disconnected features. If you are still deciding whether your current attempt is even working, it is worth a look at whether your Claude Cowork setup is actually working and how the Claude Cowork plans compare before you rebuild anything. You’ll find the full walkthrough in the CoworkStack file-intelligence walkthrough.
Running the intake yourself is one path. If you would rather have the workspace built for you, it is worth weighing a guided course against a done-for-you Claude Cowork setup and deciding which one fits how your team actually works.
Keep in mind
A Guided Intake configures a workspace; it does not replace your judgment. Claude retains context only through what the intake intentionally stores in the Business Blueprint, Memory Stack, and connected systems. Treat its output as a well-briefed draft you still review, not an autopilot.
Frequently Asked Questions
What is the Claude Cowork guided intake?
It is a structured, conversational setup interview that maps your business into Claude, producing a Business Blueprint, a populated Cowork Vault, an active Memory Stack, and a Connector Map the workspace uses going forward.
How is the guided intake different from a CLAUDE.md file?
A CLAUDE.md file is a static note you maintain by hand. The Guided Intake configures the workspace, Vault, and Memory Stack through a live conversation, and the resulting Business Blueprint updates as your business changes.
Do I need technical skills to complete the guided intake?
No. You answer questions about your business the way you would brief a new hire, and the Foundation Plugin handles the configuration behind the scenes.
What comes after the guided intake is finished?
Your documents move into the Cowork Vault, your tools are wired into the Connector Map, and Custom Playbooks with matched Persona Packs turn recurring work into repeatable routines.
Is the guided intake worth it if I already tried Claude Cowork?
Yes. Most stalled attempts at Claude Cowork come from missing setup, not weak prompting, and the Guided Intake is built specifically to close that gap.
Turn a Blank Workspace Into a Configured One
The real comparison
A blank workspace versus thirty minutes that fills it. That is the choice. One leaves you re-explaining your business in every chat; the other captures it once and configures Claude around it.
The Claude Cowork guided intake is not a feature you toggle on. It is an interview that produces a Business Blueprint, populates the Cowork Vault, activates the Memory Stack, builds your Connector Map, and sets up your first Custom Playbooks and Persona Packs. If your earlier attempt at Claude Cowork stalled, the fix is not a better prompt; it is running the actual intake and letting the Cowork Strategy Stack do what custom instructions never could.
Get the free Foundation Plugin and run your own Guided Intake. You can also work through the free Learn Claude guides as you build out your workspace.
