How to Set Up Claude Cowork FAST (the Right Way)
Most people download Claude Desktop, open Cowork, ask it to organize their Google Drive, and get frustrated when the output is generic.
That's an onboarding problem, not a Cowork problem.
Claude Cowork is now generally available on macOS and Windows. It has enterprise features, a Zoom connector, and plugin support that didn't exist 2 months ago. None of that matters if your first session starts with Claude knowing nothing about you.
For context: I build AI systems for founders who want to cut manual work without hiring. I set up Cowork for myself and for clients every week. Here's the exact process that turns it from a novelty into something you rely on every day, in under 30 minutes.
1. Connect your tools before you type a single prompt
Sounds obvious. Most people skip it.
Open Claude Desktop. Go to connectors. Connect everything you use daily:
Google Workspace (Drive, Gmail, Calendar). Non-negotiable. Most of your business context lives here.
Slack or Teams. If your team communicates there, Claude needs access to understand your workflows.
Notion, Asana, Linear, Monday. Wherever your projects and docs live.
Zoom. New as of April 2026. Cowork can pull meeting context and recordings.
Why this matters first: when you create your context files in step 2, Claude can pull from your existing documents instead of you typing everything from scratch. Connect first, configure second.
Quick test: ask Claude to find a recent document in your Drive. If it finds it, move on.
2. Build 3 context files (let Claude do most of the work)
Context files are documents that load every session. They're how Claude knows who you are without you re-explaining it every time.
You need 3.
File 1: about-me.md
Cover these in plain language:
What you do (1 sentence)
Businesses or projects you're running right now
Who your customers are
Tools you use daily
Key people Claude should know about (co-founder, assistant, key clients)
The shortcut most people miss: if you already connected Google Drive, tell Claude to scan your existing docs for company info, bios, and about pages. It will draft 80% of this file for you. Edit what's wrong. Save.
File 2: voice.md
This is how Claude stops sounding like a robot. Include:
Your communication style (direct and blunt? warm and conversational? somewhere between?)
Words or phrases you hate (if "synergy" makes you cringe, say so)
How you communicate differently by context (client emails vs. team Slack vs. social posts)
2–3 examples of writing you've done that sounds like you
Paste actual writing samples. A good email you sent. A social post that performed. Claude will reverse-engineer your patterns better than any style guide.
File 3: preferences.md
Tell Claude how to work with you:
Should it ask clarifying questions or just execute?
What format do you want outputs in? (bullet points, paragraphs, tables)
How detailed should first drafts be?
Any hard rules? ("Never use em dashes." "Always include pricing." "Keep responses under 300 words unless I ask for more.")
Save all 3 files in 1 folder. Name it whatever you want. Select this folder at the start of every Cowork session.
Join my newsletter, if you want more breakdowns like this
3. Set global instructions (your always-on brief)
Global instructions run in every session, even before you select a folder. Think of it as your executive brief that Claude reads before doing anything.
Take the key points from your 3 context files and condense them into roughly 800 words. Structure it like this:
Who I am (2–3 sentences)
How I work (preferences for task approach and communication)
Output defaults (format by task type: emails get bullet points, content gets paragraphs, research gets tables)
Voice (the 3–4 most important characteristics)
Key business context (what I'm working on right now, what matters most)
Rules (always do X, never do Y)
Activate it: Claude Desktop → Settings → Cowork → Edit next to Global Instructions → paste → save.
From here on, every new session starts with Claude already knowing your name, your business, your voice, and your rules. No more "I'm [your name], I run a company called…"
4. Install 3–5 Skills that match your actual work
Skills are pre-built capabilities that turn Claude from a general assistant into a specialist. Without Skills, Claude can chat. With Skills, it can:
Research and profile potential partners or podcast guests
Draft content that matches your voice and format preferences
Prep for meetings by scanning attendee backgrounds
Process data and generate reports from your connected tools
Run multi-step workflows end to end
How to pick: look at your last week. What did you do more than once that felt repetitive? Start there.
Use the plugin search in Cowork. Search by keyword (content creation, sales, research, meeting prep). Install 3–5 that match your highest-frequency tasks.
Don't install 20 Skills on day 1. You'll never use most of them. Start small, add as you hit friction.
Custom Skills are also an option. If no existing Skill matches your workflow, you can build your own. Deeper topic, but the door is open.
5. Create your first scheduled task
This is where Cowork becomes an employee instead of an assistant.
Scheduled tasks run on a schedule you define. No prompting required. Claude does the work and delivers the result.
Start with 1 of these:
Morning briefing (every weekday, 8am): check inbox for anything urgent, scan today's calendar, list top 3 priorities. Deliver as a summary.
Weekly recap (every Friday, 4pm): summarize completed tasks, flag anything overdue, highlight wins.
Meeting prep (30 minutes before any call): pull attendee context, check for previous communication, generate 3 talking points.
Ask yourself 3 questions to find more:
What do I do every day or week that's repetitive?
What do I always forget until it's too late?
What would save me the most time if it happened on its own?
Create the task with a plain-language schedule and a detailed prompt. The more specific the prompt, the better the output. "Summarize my inbox" gets you generic results. "Check my Gmail for unread messages from clients, flag anything that mentions a deadline or needs a response today, and list them by priority" gets you something you'll actually use.
6. The first-week calibration (don't skip this)
This step wasn't in my original version of this guide. It should have been.
Your first week with Cowork will not be perfect. The morning briefing will miss things you care about. The voice file won't capture every nuance. Scheduled tasks will need tuning.
That's the point. Treat week 1 as calibration, not production.
Every time Claude gets something wrong, tell it. "The tone on that email was too formal. Match the example I gave you in voice.md." "The morning briefing is too long. Cut it to 5 bullet points max."
By end of week 1, your context files should have 2–3 small edits. Your global instructions should be tighter. Your scheduled tasks should be tuned to match how you work.
By week 2, it should feel like Claude has worked with you for months.
The full setup
Here's the timeline:
Connect tools (5 minutes): Google Workspace + your core stack
Create context files (10 minutes): let Claude draft from your existing docs, then edit
Set global instructions (5 minutes): condense context files into the always-on brief
Install Skills (5 minutes): pick 3–5 for your most repetitive tasks
Create first scheduled task (5 minutes): start with a morning briefing
That's it. 30 minutes and Claude goes from "generic chatbot" to "knows my business, my voice, my tools, and runs tasks while I sleep."
The people who get the most out of Cowork aren't the ones with the most Skills installed. They're the ones who spent 30 minutes on setup and 5 minutes a day calibrating for the first week.
Do the setup. Do the calibration. Everything after that compounds.
If you want more weekly breakdowns on building AI systems, join my free newsletter.