Article Read Time
Here’s something I keep hearing from smart, busy people who use Claude.
They open it a few times a week. They ask it something. They get an answer that’s pretty good, sometimes really good. They close the tab. Three days later they think: I should really figure out how to use this properly.
And then they don’t. Because they don’t know where to start, and everything they read online assumes either that they’re a developer or that they have 10 hours to spend building a system from scratch.
So they keep using Claude the same way they always have. Which means they’re getting maybe 20% of what it can actually do. Not because they’re not capable. Because nobody sat down with them and set it up.
That’s what this post is about.
What “setting up Claude properly” actually means
Most people think using Claude means prompting it well. And yes, how you ask matters. But prompting is the last step, not the first.
Before any prompt can do its best work, three things need to be in place.
Claude needs to be connected to your real tools. Right now, Claude probably doesn’t know what’s in your calendar, what tasks are sitting in your project management system, or what’s sitting in your inbox waiting for a response. It’s answering you blind. When you connect Claude to your tools via what are called MCP connectors, it can actually see your world and help you navigate it rather than just answer generic questions.
Your projects need proper instructions. Most people who use Claude projects have either no instructions or instructions they wrote in five minutes without really knowing what to put in them. Instructions are what make Claude behave consistently in a specific context. They tell Claude who you are, what you need, how you communicate, and what the guardrails are. Without them, you’re starting from scratch every time.
Your tone of voice needs to be installed as a skill. If you’ve ever felt like Claude’s outputs don’t quite sound like you, this is why. A tone of voice skill teaches Claude your exact communication style so that any output it generates in any chat anywhere sounds like it came from you, not from a generic AI assistant. Once it’s installed, all you have to type is “use my voice” and Claude adjusts.
When all three of these are in place, Claude stops being a search engine you talk to and starts being something closer to a thinking partner who actually knows your context.
What a Claude setup workshop is
A Claude setup workshop is a live, personalized session where an expert connects Claude to your real tools, configures your project workspaces with proper instructions, installs tone of voice and workflow skills, and builds working automations with you in real time.
It is not a course. It is not a template you fill in on your own. It is not someone building a system for you while you sit back.
It’s a done-with-you session. Your accounts. Your screen. Your life. The expert guides you through every step while you’re in the room, which means by the end of the session you understand what was built and why, and you can use it immediately.
The session typically covers installing the Claude desktop app if you don’t have it, connecting Claude to your tools via MCP connectors, reviewing and improving your existing project setup, writing proper project instructions for each area of your work, installing a tone of voice skill so Claude writes like you, and building and testing two to three recurring workflows that you’ll actually use.
The result is not a theoretical setup. It’s Claude running in your accounts, connected to your tools, trained on your voice, with workflows you tested before the call ended.
What MCP connectors are and why they matter
MCP stands for Model Context Protocol. It’s the system that lets Claude connect directly to external tools, which means Claude can actually read your calendar, pull your tasks, check your email, and interact with tools like ClickUp, Google Drive, Canva, Gamma, HubSpot, and more.
Without connectors, Claude is working from what you tell it in the moment. With connectors, Claude is working from your actual data in real time.
The difference is significant. Instead of you copying and pasting your week’s tasks into Claude and asking it to help you prioritize, you can type one command and Claude pulls everything from ClickUp directly. Instead of telling Claude about an email you need to respond to, you can have it scan your inbox for anything that needs action and draft replies in your voice.
Connectors are what make Claude feel less like a chatbot and more like a system that’s actually integrated into how you work.
What happened when I ran the first Life in Claude session
The first person I ran this session with was an existing client and dear friend. She’s a CEO and founder of several businesses. In essence. she runs four professional identities simultaneously and she is one of the busiest, most organized people I know.
She’d been using Claude Pro for a while. She had projects set up. She used it regularly. But she’d never installed the desktop app, had no connectors set up, and had zero instructions in any of her projects. Which means every time she opened a project, Claude had no idea who she was, what she was working on, or how she communicated.
In our three-hour session, we installed the app, connected nine tools including ClickUp, Google Drive, Canva, Gamma, HubSpot, Google Calendar, and Gmail, rebuilt her project architecture so each of her roles had its own properly configured workspace, and built her first custom skill. She tested it live before we closed the call.
She called me the next day to book ongoing sessions to keep building.
That’s what a properly configured Claude setup does. It doesn’t just answer questions better. It changes how you work.
How to know if you need a Claude setup workshop
You probably need one if any of these are true.
You have Claude Pro but still feel like you’re mostly just asking it things and getting okay answers. You have projects set up but they don’t have instructions, or you’re not sure your instructions are doing anything. You’ve tried to use Claude for a specific workflow but it didn’t work the way you hoped and you’re not sure why. You know Claude should be doing more but you don’t have the time or the clarity to figure out what that looks like.
You don’t need one if you’re already deeply technical, you’ve already configured connectors, written solid project instructions, and built skills. In that case you’re probably already in the 20% of Claude users who are getting full value.
For everyone else, a setup session compresses what would take weeks of trial and error into a few hours with someone who’s already made the mistakes for you.
What to do next
If you want to see exactly what this kind of session looks like and what it includes, the full details are on the Life in Claude workshop page. That’s the done-with-you option for people who want the setup handled properly with an expert rather than figuring it out alone.
If you want to start somewhere on your own first, the next post in this series covers the single most common reason Claude users don’t get good results, and it has nothing to do with your prompts.
Frequently Asked Questions
A Claude operating system is the combination of connected tools, configured project workspaces, installed skills, and recurring workflows that make Claude function as an integrated part of how you work rather than a standalone chatbot you visit occasionally.
A done-with-you setup session typically takes three hours for the core configuration including connectors, project instructions, and two to three workflows. Building out a full system with scheduled automations and multiple skill files takes additional sessions over several weeks.
No. Connectors, project instructions, and skills all work through the Claude interface without any coding. The technical complexity is handled by the platform itself. What you need is the time to configure things correctly and an understanding of what to put where.
Claude chat is a fresh conversation with no persistent context. Claude projects are saved workspaces where your files, instructions, and conversation history are retained across sessions. Claude Cowork is the desktop automation layer that lets Claude read and create files on your computer and run multi-step tasks autonomously in the background.
As of early 2026, Claude has connectors for Gmail, Google Calendar, Google Drive, ClickUp, Canva, Gamma, HubSpot, and a growing list of other tools. New connectors are added regularly. You can browse available connectors inside the Claude app under Customize.
Gina Dunn is the founder of OG Solutions and a brand strategist with 25 years of experience helping female founders find and sustain their authentic brand voice. She works with founders, consultants, and creative professionals globally from her base in the Netherlands. Her Mirror, Not Mask framework is built on one conviction: strategy isn’t invention. It’s remembrance.