Three steps for setting up Claude the right way: connecting it to the tools you already use through connectors, loading it with your professional context through Projects, and handing off recurring work through Claude Cowork. No technical background required.
If Claude has been giving generic results, the setup covered here, not a better prompt, is usually the actual fix.
You got Claude because someone told you it was better than ChatGPT. You opened it, typed a question, got an answer, copied it into your work, and closed the tab. Ten minutes later you're back. Typing another question. And Claude has no idea who you are, what you're doing, or why any of it matters.
That's not Claude being bad at its job. That's Claude not being set up to do your job.
It has taken me 20 years of teaching and countless hours testing AI to figure out that the problem isn't which AI tool you're using, it's that nobody ever showed you how to set it up. Most people get taught the tool but rarely get taught the system. Those are completely different things.
Claude has features built into it that most people never turn on. Not because they're hidden but because nobody explained what they do or why they matter. Without them, Claude is just another chatbot.
In this video I'm going to walk you through three things: how to connect Claude to your tools, load it with your context, and hand off the work you're tired of doing yourself. Connect it, load it, hand it off.
By the end of this video, Claude will feel like it was built for your specific job, not just any job.
First you want to connect it using something called connectors, and once you understand what they do, the rest of this makes sense.
Claude can connect directly to your email, your calendar, your files, but only if you tell it to. Think of it like plugging a printer into your computer. Connectors do the same thing for Claude.
At the top, just click "customize" then "Connectors".
Here's the one that saves me the most time every single week: the Gmail connector.
Most of us spend at least an hour a day in email. I used to do all of that manually. Now Claude does most of it.
Here's how it works. I go into Claude and click customize at the top left, then I click on Connectors. I click the plus button and search for gmail. I click it and login to Gmail. Now Claude has access to my inbox.
That means I can ask things like, 'Find the last email about the contract renewal and tell me what's still unresolved.' Claude searches my inbox, finds it, and gives me a summary. Or I can say, 'Draft replies for anything that needs a human response'. Claude writes the reply. I read it, make a small adjustment if I need to, and send it.
The reason this works is because Claude isn't just guessing what my emails say, it's actually reading them.
Now, I know some people hear that and immediately think, "Wait, is that safe? Is Claude reading all my emails?" Fair question. Here's the answer. Claude's security is handled by Anthropic, the company that built it.
They don't store your emails on their servers. Claude reads what you ask it to read, and that's it. If you're worried about it, don't connect it. I've had this connected for months and it's never given me a reason to second-guess it. You stay in control of what it reads and what it doesn't.
The second connector I use is Google Calendar. Same setup process, go to Connectors, choose Google Calendar, log in. Now Claude can see my schedule.
So instead of opening my calendar, scrolling through the week, and trying to figure out where I have breathing room, I just ask. 'Find me an hour this week to work on my project but not first thing in the morning' Claude looks at my schedule and finds it. That's it.
But here's the part most people don't think about. Claude can also analyze how you're spending your time.
I told Claude what actually matters to me right now. Then I asked it to look at my calendar and tell me if I was spending time on those things. The honest answer was no. I was filling my week with stuff that felt productive but wasn't connected to anything I'd said was a priority. Claude pointed it out.
Now, those two connectors, Gmail and Google Calendar, are the ones I use most often. But there are others.
Claude can connect to Slack if your team uses that for communication. It can connect to Google Drive so it can read and reference documents you've stored there. It can connect to Notion if that's where you keep your notes and project plans.
The process is the same every time. Go to Connectors, choose the service, log in.
The second thing is to load it, and that's where Claude Projects come in. This isn't something I use day to day anymore, because Claude Cowork handles most of what Projects is designed for. But if you're spending most of your time in Claude Chat, this matters.
A Project is basically a folder with a memory. You create one, give it a name, and load it with everything Claude would need to help you with that area of your work. Your documents, your standards, how you want Claude to respond. All of it lives in one place.
Setting it up takes about two minutes. In the left sidebar, click New Project. Give it a name, something specific like "Client Reports" or "Weekly Newsletter." Then click Project Knowledge and upload whatever Claude needs to do that job. A style guide, a template, a document with your preferences. Finally, add a short instruction at the top telling Claude how you want it to behave inside this project. That's it. Next time you open it, all of that is already loaded.
The problem it solves is this. Every time you open a regular Claude chat, you're starting from zero. Re-explaining who you are, re-pasting the background, re-describing what you need. A Project means you do that once. After that, Claude knows and remembers that area of your work. This is perfect if you only are on the free plan.
But I moved past this stage when I saw what Cowork can do. But if you're not there yet, Projects is the bridge. It's the first time Claude starts feeling like it actually knows you.
Third is the hand off. That's Claude Cowork. And this is the one that made the biggest difference to how much I can get done and how much more is possible.
Before I get into it, I want to give you a quick picture of how Claude works across its three different modes, because most people don't know all three exist, and it changes how you think about what's possible.
On the left is Claude Chat. That's what you've been using, the web interface or the mobile app where you type something and Claude responds. Everything I've shown you so far, connectors, Projects, that all lives here. Most people spend all their time in this mode, and as you've just seen, there's a lot of leverage still untapped in it.
On the right is Claude Code and it's the most advanced. This is more for developers, people who write software and want AI working directly inside their codebase. If that's not you, you don't need it. I'm not a developer and I don't use it. But it exists, and it's worth knowing you have it.
In the middle is Claude Cowork. And this is the one I want to spend time on, because it's the most relevant for the professionals watching this.
Let me make sure that landed. Chat is for questions. Cowork is for jobs. That distinction is everything.
Cowork lives inside the Claude desktop app, that's a separate program you download and install on your computer, but they're all connected. Once you have it, you'll see Cowork in the top left corner. When you open it, it gives Claude the ability to control your computer and do tasks for you while you step away. It can even do work for you while you watch it in real-time.
Let me be clear about what that means, because it sounds more complicated than it is. You give Claude a task that involves clicking through different programs, maybe pulling a report from one app, putting the numbers into a spreadsheet, creating a chart, and sending it to your team. Normally, you'd do all of that yourself. With Cowork, you describe the task and Claude does the clicking for you.
Here's a real example. Every week, I want to know what's happening in AI, but there's so much going on. I used to try to piece it all together but it took at least 30 minutes and I still felt I was missing something.
Now I have Cowork scheduled to do it for me. I wrote out the task once, search for AI developments across the topics that matter to my work, filter out the noise, and compile everything into a short brief. Now that task runs every Tuesday and Friday at 3 a.m. When I wake up, the brief is already waiting in my inbox.
That's the shift. I'm not asking Claude a question and waiting for an answer. I've given it a job, and it's doing that job on a schedule without me touching it.
Cowork isn't perfect. Sometimes it gets stuck. When it does, I just tell it what went wrong the same way I'd talk to someone sitting next to me. It adjusts and keeps going.
None of this is hidden. Connectors, Projects, Cowork, it's all right there. But rarely do people explain what it's for. But now you have the setup. And that changes what's possible.
Don't try to set up everything at once. Pick the one that connects most obviously to your biggest daily frustration and start there. One thing. See if it saves you time. If it does, add another.
Now you have the setup. Connect it to your tools. Load it with your context. Hand off the work.
But most people do all of this and then go straight back to typing questions like nothing changed. The setup is only half of it. The other half is knowing how to talk to Claude once it's running, because that's where most people leave results on the table.
This video points to The Professional AI Interview Kit, the practical next step after watching.