How to Onboard Claude for Business Workflows

TL;DR

Treat Claude as an employee who needs structured onboarding, not as a calculator that answers isolated prompts. Add personal preferences, create a persistent folder structure, connect only essential business tools, and build reusable skills for repeated work. This setup reduces rebriefing, scattered context, copy-pasting, and unnecessary switching between applications.

Transcript

Stop using claude like it's chat GBT. The way you're using AI is the reason it isn't changing your business. It's not the model and it's not the prompts. You can learn as many as you want. It is the way that you set it up for yourself. Most founders right now are running Brilliant AI on a broken configuration. And until that changes, every single A... Read More

Key Insights

• Claude co-work mode is presented as a workspace rather than a calculator. A calculator starts every interaction without memory, while a properly configured workspace gives Claude persistent business context, organized files, connected tools, and reusable instructions that support work across multiple sessions.
• Repeated rebriefing is a symptom of broken AI configuration. When business information remains outside the assistant, each project requires more explanation, each conversation partly resets, and completed outputs must be manually copied into the email, storage, planning, or communication tools where work actually happens.
• Personal preferences are Claude's company handbook. Founders can import context from an assistant they previously used, ask Claude what additional information it needs, answer questions about goals, audiences, communication style, and pet peeves, then save the completed context for future conversations.
• A dedicated folder structure gives Claude a persistent virtual desk. Inputs, references, drafts, scripts, documents, and analyses can live in one organized location, allowing later work to build on earlier material instead of becoming scattered across temporary folders and unrelated conversations.
• Claude projects should map to meaningful business folders. A root folder can contain separate businesses, projects, or clients, while the internal organization should reflect the founder's actual workflow. The specific structure matters less than keeping relevant context coherent and consistently available.
• Connectors introduce Claude to the tools used by the wider team. Connections to email, storage, calendars, Notion, Slack, and other services can let Claude retrieve information or update work within a conversation, reducing tab switching and manual copying between applications.
• Limited access is safer and more useful than connecting everything immediately. Start with two or three tools used every day, choose non-invasive access first, and preserve privacy through guardrails such as a separate Notion account that can access only specifically shared pages.
• Skills are reusable instruction files for repeatable business processes. A skill can encode a preferred playbook for motion graphics, proposals, reports, email sequences, meeting summaries, or lead qualification, helping future Claude sessions follow established methods instead of guessing how the work should be performed.
• More videos from this channel:
  • How to Build a Reliable Gemini Business Setup
  • How to start an AI business with zero dollars
  • How to Validate and Build an AI Business
• More from this channel: AI Founders

Questions & Answers

Q: How do you onboard Claude for business work?

Onboard Claude in a deliberate sequence similar to onboarding an employee. First, provide personal and business context through personal preferences. Second, create an organized folder structure that serves as its desk. Third, connect a small number of essential business tools. Fourth, create reusable skills for repeated processes. Finally, build what the speaker calls a performance stack that sets Claude up to succeed.

Q: What should you include in Claude personal preferences?

Claude's personal preferences should contain the context needed to assist you consistently, including your role, background, business, audience, goals, preferred tone, decision-making style, communication habits, and pet peeves. The suggested process is to import memories from a previous assistant, ask Claude what else it needs to know, answer its follow-up questions honestly, and save the resulting material in personal preferences.

Q: How can you transfer context from ChatGPT or Gemini to Claude?

Open Claude's settings, go to capabilities, and select the option to import memory. Copy the prompt shown there and give it to the assistant you previously used, such as ChatGPT or Gemini. Bring the resulting context into a new Claude conversation, ask what additional information would make Claude most useful, answer the questions, and paste the completed profile into personal preferences.

Q: How should folders be organized for Claude co-work?

Create a dedicated root folder for Claude co-work, then add subfolders that match the way your business operates. The speaker uses separate folders for each business and additional folders for projects or clients. Each useful subfolder should map to a Claude project so source files, references, and generated work remain organized, persistent, and available for later tasks.

Q: Which business tools should you connect to Claude first?

Start with the two or three tools you genuinely use every day, such as email, cloud storage, or a project manager. The transcript also mentions Gmail, Google Drive, Notion, calendars, and Slack as possible connections. Connecting everything immediately can produce more noise than useful context, so access should expand gradually as clear needs emerge.

Q: How can you limit Claude's access to private business information?

Use guardrails and give Claude access only to the information required for its assigned work. Begin with a non-invasive connection and expand carefully. For Notion, the speaker suggests creating a separate account for Claude, then inviting that account only to selected pages. This preserves separation between private material and the specific resources Claude needs to complete approved tasks.

Q: What is a Claude skill for business workflows?

A Claude skill is a reusable instruction file that captures a repeatable playbook. It can be written once, either by the user or with Claude's help, and followed until it is changed. Skills can support client proposals, weekly reports, email sequences, meeting summaries, lead qualification, motion graphics, and other recurring tasks that should follow a consistent process.

Q: Why does AI feel faster without making a founder's life lighter?

AI can produce answers quickly while leaving the overall workflow unchanged. If it lacks business context, file access, connected tools, and reusable playbooks, the founder must repeatedly explain the situation, move information between applications, and reorganize outputs manually. The transcript compares this experience to calling a brilliant consultant who must be rebriefed during every conversation.

Summary & Key Takeaways

• The recommended approach begins by changing the founder's mental model of AI. Instead of opening Claude for isolated questions, treat co-work mode as a persistent workspace for an employee. Proper onboarding gives Claude background information, stable files, relevant business connections, and reusable operating instructions, reducing repeated explanations and fragmented work across separate tools.

• The first two onboarding steps establish personal and operational context. Import memories from a previously used assistant, let Claude ask follow-up questions, and place the resulting information in personal preferences. Then create a dedicated root folder with business, project, or client subfolders, mapping each relevant subfolder to a corresponding Claude project.

• The remaining setup connects Claude to selected tools and teaches repeatable playbooks. Begin with two or three daily tools, apply access boundaries, and avoid unnecessary connections. Create skills for recurring tasks such as proposals, reports, email sequences, meeting summaries, lead qualification, or motion graphics, then refine those reusable instructions as work continues.