@coreyganim: Most people download Claude De...
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 problem with Cowork itself.
Claude Cowork is now generally available on macOS and Windows. It has enterprise features, a Zoom connector, and plugin support that didn't exist two months ago. But none of that matters if your first session starts with Claude knowing nothing about you.
I set up Cowork for my business and my clients. Here's the exact process that turns it from a novelty into something you actually rely on every day.
PS: Every week I break down workflows like this inside the Build With AI newsletter. Agents, automations, and step-by-step setups you can run yourself or sell to clients.
-----------------------------------------
1. Connect Your Tools Before You Type a Single Prompt
This sounds obvious. Most people skip it anyway.
Open Claude Desktop. Go to connectors. Connect everything you use daily:
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 Three Context Files (Let Claude Do Most of the Work)
Context files are documents that load automatically every session. They're how Claude knows who you are without you re-explaining it every time.
You need three.
File 1: about-me.md
Cover these in plain language:
Here's 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 it gets wrong. Save.
File 2: voice.md
This is how Claude stops sounding like a robot. Include:
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:
Save all three files in one folder. Name it whatever you want. Select this folder at the start of every Cowork session.
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 three context files and condense them into roughly 800 words. Structure it like this:
Activate it: Claude Desktop → Settings → Cowork → Edit next to Global Instructions → paste → save.
From now on, every new session starts with Claude already knowing your name, your business, your communication style, and your rules. No more "I'm Corey, 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:
Here's 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 one. 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. That's a deeper topic, but know the door is open.
5. Create Your First Scheduled Task
This is where Cowork becomes an employee, not an assistant.
Scheduled tasks run automatically on a schedule you define. No prompting required. Claude does the work and delivers results.
Start with one of these:
Ask yourself three questions to find more:
Create the task with a plain-language schedule and a detailed prompt. The more specific the prompt, the better the output. "Summarize my inbox" produces 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" produces something you'll actually use.
6. The First-Week Calibration (Don't Skip This)
This step wasn't in the 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. The scheduled tasks will need tuning.
That's the point. Treat week one 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 one, your context files should have 2-3 small edits. Your global instructions should be tighter. Your scheduled tasks should be tuned to actually match how you work.
By week two, it should feel like Claude has worked with you for months.
The Full Setup (Under 30 Minutes)
Here's the timeline:
That's it. 30 minutes and Claude goes from "generic chatbot" to "knows your business, your voice, your tools, and runs tasks while you 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 per day calibrating for the first week.
Do the setup. Do the calibration. Everything after that compounds.
PS: Every week I break down workflows like this inside the Build With AI newsletter. Agents, automations, and step-by-step setups you can run yourself or sell to clients.