Find the one bottleneck killing your revenue.
30-minute free strategy call with Charles. We diagnose your highest-leverage AI bottleneck, install Charlie OS live on your Mac or Windows in one hour, and map your exact next 30 days, all on the same call.
Claude Code just helped a complete beginner build their first real application in two days. No prior coding experience. No CS degree. Just the right setup and the right framework.
If you’ve been staring at Claude Code wondering where to even start, welcome to the club. This walkthrough is going to fix that.
Want to skip the entire setup and go straight to building? and get my full setup, frameworks, and skills pre-installed so you can start day one.
I’m Charles Dove, founder of Charlie Automates and CC Strategic. I teach entrepreneurs and regular people how to use AI tools to solve real business problems, not theoretical ones. This is the Claude Code tutorial I wish existed when I started.
The Real Problem With Most Claude Code Tutorials
Most tutorials show you the tool. They don’t show you the setup that makes the tool actually work for you.
You install Claude Code, open a terminal, stare at a blinking cursor, and then what? That gap between “installed” and “building something useful” is where most people quit.
This post closes that gap. You’re going to walk away with a working environment, two frameworks that handle ideation and building, and a clear mental model for how to use this thing without losing your mind.
Who Claude Code Is Actually For
Let me clear something up fast. This isn’t just a tool for developers or business owners.
If you work a regular job, if you have repetitive tasks, if you’re drowning in processes that could be automated, Claude Code is for you. Jobs in 2026 and beyond are going to require AI skills. Getting good at this now puts you ahead of basically everyone.
And here’s the mental model that matters most: there’s a difference between AI automation and AI augmentation.
Automation is getting AI to handle tasks. Augmentation is feeding Claude massive amounts of context so it becomes your personal expert, counselor, and thinking partner. You want both. But augmentation is where the real leverage lives.
The Subscription You Actually Need
Don’t start on free. Don’t even bother with Pro if you plan to use this seriously. You’ll hit limits constantly and it’ll kill your momentum.
The minimum I recommend is Max 5x. That’s what I use when I’m getting started with a new project. Once you’re seeing real ROI, upgrade to Max 20x. But start with Max 5x. Don’t overthink it.
Step 1: Install Claude Code
Head to code.claude.com (linked in the video description) and grab the install command for your system.
- Mac: copy the Mac command
- Windows: use PowerShell, not regular terminal
Paste the command into your terminal, hit enter, and let it run. If Claude doesn’t boot automatically after install, close the terminal, open a new one, type claude, and hit enter. You’re in.
Step 2: Create Your Workspace Folder
Here’s where most beginners skip a critical step. You want Claude working inside a specific folder, not just anywhere on your computer.
Create a folder on your desktop. Call it something like your-name-workspace. Inside that, create a secondary folder called your-name-dev. This is your mono repo. Everything you build with Claude lives here.
Why mono repo? Because Claude gets smarter the more context it has. When all your projects, files, and instructions live in one folder, Claude builds a picture of your entire operation. That makes it 100 times more effective than using it cold every single session.
I have my entire business context in my mono repo. Multiple apps, multiple businesses, custom instructions that teach Claude to speak and think like me. That’s what you’re building toward.
Step 3: Set Up VS Code
You could work out of a raw terminal. But you’re going to regret it fast.
Download VS Code at code.visualstudio.com. It’s free. Once installed, open your workspace folder inside VS Code. Now you’ve got:
- A file explorer so you can see everything Claude builds
- An integrated terminal so you can run Claude without switching windows
- Multiple sessions you can name and manage
- Live preview of files as Claude builds them
For appearance, I move the primary sidebar to the right and keep the panel at the bottom aligned left. You can copy this setup exactly from the video. The point is to organize your screen so you’re not hunting for things mid-session.
To boot Claude into your specific workspace from VS Code: drag your folder into the terminal path, ask Claude “what command do I use to boot directly into this folder”, copy that command, and paste it every time you start a new session. Now Claude is always working inside your mono repo.
Step 4: Set Up Your Folder Structure
Inside your workspace, create these folders:
.claudeadminappswebsitesworkflows- your business name as its own folder
This is the foundation. The .claude folder is where you’ll eventually store your CLAUDE.md file, which is basically Claude’s instruction manual for working with you. We’ll come back to that.
Step 5: Install Seed and Poll
This is where things get good.
Seed is an ideation framework. It interviews you about the project you want to build, packages the idea, and structures it so Claude understands exactly what you’re trying to create.
Poll (PAUL) is the building framework. Once Seed has your idea packaged, you hand it off to Poll. Poll scaffolds a full project folder, tracks the build state, manages your roadmap, and breaks the build into phases you execute one by one.
To install both: grab the install commands from the repo links in the video description. Open a terminal without Claude running, paste each command, hit enter, and select global when prompted. Do this for Seed first, then Poll.
Once installed, type / inside Claude to access custom commands. Run /seed and Claude will start asking you questions about your project. Answer them with as much context as you can. The more detail you give it, the better the output.
When the idea is packaged, Seed will hand it off to Poll. Poll runs its own init, scaffolds the project folder, and you start building phase by phase. Plan and execute are separate commands. That’s intentional. It keeps you from rushing the build.
The CLAUDE.md File: Your Most Important Setup Step
Run /init inside Claude to generate your CLAUDE.md file. This is your top-level instruction document. It’s how you teach Claude about your folder structure, your preferences, and how you want it to behave.
Right now it’ll be mostly empty. That’s fine. As you work with Claude, ask it to update the MD file whenever you want it to remember something. “Hey Claude, update the MD to remember I always want X” and it writes it in. Over time, this file becomes your Claude’s personality and operating system.
What This Looks Like In Practice
I want to show you a real example of how I use this at Charlie Automates, because the setup only matters if you actually use it on a real problem.
My biggest bottleneck: people fill out my intake forms and I can’t write custom emails to all of them. I have leads sitting there getting generic follow-ups while I’m building. That’s revenue walking out the door.
So I built a workflow using Claude Code I call the Bottleneck Pipeline. Here’s how it works:
- Someone fills out my intake form
- Claude connects to my CRM (Go High Level) via an MCP connector
- It pulls in all their form details
- It analyzes whether they’re a low ticket or high ticket prospect
- It activates my copywriting skill, subject line skill, and humanizer skill
- It writes a custom email that sounds like me
- It stages them in the pipeline and sends the email with my booking link attached
I didn’t write code for this. I used Seed to package the idea and Poll to build it phase by phase. The whole thing took Claude maybe a few sessions to construct.
That’s the power of starting with your real bottleneck instead of a toy project.
MCPs: The Connectors That Make Claude Actually Powerful
MCPs are how Claude talks to external software. Think of them as a toolbox that lets Claude reach outside your computer and interact with real apps.
I currently have Claude connected to:
- Go High Level (my CRM)
- Skool (my community at CC Strategic AI)
- Trello
- Higgsfield (AI video and image generation)
From one terminal inside VS Code, I can pull data from my CRM, check my community, manage tasks, and trigger content creation. This is the end game you’re building toward. You don’t need MCPs on day one. But knowing they exist changes how you think about what’s possible.
Free MCP resources are available on charlieautomates.com.
Key Takeaways
- Start with Max 5x subscription minimum. Free and Pro will kill your momentum with limits.
- Build a mono repo workspace so Claude accumulates context over time.
- Use VS Code instead of raw terminal. Multiple sessions, file previews, organized sessions.
- Seed packages your idea. Poll builds it. Use both together.
- Your CLAUDE.md file is your secret weapon. Update it constantly.
- Always start with your biggest bottleneck, not a random project. Solve a real problem first.
- MCPs connect Claude to real software. That’s where the advanced workflows live.
- Ask Claude anything you don’t know. Seriously. Type “I’m trying to do X but I don’t know how” and let it guide you.
Ready to Go Deeper?
The fastest way to get dangerous with this tool:
and get my entire setup, frameworks, skills, and context files pre-installed. Skip the headache and start building on day one.
Want to learn everything from A to Z:
Join CC Strategic AI on Skool where I’ve got full training modules, the complete framework library, and a template vault covering everything I use.
FAQ
Do I need coding experience to use Claude Code?
Not at all. I’ve had clients build their first application within two days of picking up the tool with zero coding background. The key is starting with a real problem you actually care about solving, not a practice project.
What’s the difference between Claude Pro and Claude Max?
Pro hits rate limits constantly when you’re doing real work. Max 5x gives you enough runway to actually build and iterate without stopping every 30 minutes. Once you’re seeing ROI, upgrade to Max 20x. Start with Max 5x minimum.
What are Seed and Poll and do I need them?
Seed is an ideation framework that helps you package your project idea through an interview process before you start building. Poll is the building framework that scaffolds your project folder, tracks build state, and manages your roadmap. You don’t technically need them, but they eliminate the chaos that kills most beginners before they finish their first project.
What’s an MCP and when should I start using them?
MCPs are connectors that let Claude communicate with external software like your CRM, project management tools, or content platforms. Don’t stress about them on day one. Get your setup working, build one real thing with Seed and Poll, and then start exploring MCPs once you’re comfortable. The free MCP resources on charlieautomates.com are a good starting point.
Ready to install Charlie OS?
Stop reading. Start shipping.
The AI Bottleneck Protocol is a 30-minute free call. We pinpoint the one task eating the most hours and the most money in your business right now. We install Charlie OS live on your machine in under an hour. We map your exact path to fix the bottleneck on the same call. If we’re not a fit, you walk away with a clear diagnosis of where your business is leaking time and money. Either way, you win.