Introduction

If you’re trying to get Claude Desktop, Claude Code, VS Code, Node.js, the Claude Chrome extension, Cowork, connectors, folders and random partner portals to all behave nicely in your brain, welcome to the circus.

And I say that lovingly.

Because for most business owners, the issue isn’t that AI is too hard.

The issue is that the setup feels like you’ve accidentally walked into a developer conference wearing a business coaching blazer, holding a coffee, wondering why everyone is talking about folders, terminals and extensions.

But here is why this matters.

Once your AI tools are set up properly, you stop wasting hours “figuring out the tech” and start using Claude to do actual business work.

Things like:

• SEO audits
• Blog production
• Content repurposing
• Grant applications
• Inbox triage
• LinkedIn lead research
• Team workflows
• SOP creation
• Website reviews
• Marketing automation planning
• Client onboarding systems

Setup pain now equals speed later.

And no, you do not need to become a software developer to make this useful.

You simply need to understand what each tool does, how they connect, where your files live, and how to stop opening 17 tabs while silently questioning your life choices.

This guide will walk you through the practical Claude Code setup for business owners, without the confusing developer waffle.

What Are You Actually Setting Up?

Before you start downloading things like a caffeinated raccoon, it helps to understand the role of each tool.

Claude’s current download page describes Claude as bringing chat, Claude Cowork and Claude Code together, with access across desktop, mobile and browser environments. It also lists Claude Code environments including Desktop, Terminal, VS Code, JetBrains and Slack.

That means you are not setting up one thing.

You are building a little AI workbench.

Think of it like this:

• Claude Browser is where you chat with Claude online.
• Claude Desktop is the app on your computer.
• Claude Code is where Claude can work with files, codebases and project folders.
• VS Code is the workspace where Claude Code can operate.
• Node.js may be needed for some development workflows or if you install Claude Code through npm.
• Claude Chrome lets Claude assist inside your browser.
• Connectors help Claude access tools such as Gmail, Google Drive, Calendar and other work apps.
• Cowork and computer-use features allow Claude to act more like a hands-on assistant, with your permission.

The big mindset shift is this:

You are not “installing AI”.

You are setting up a workspace where AI can help you produce business outcomes.

That is a very different thing.

Claude Desktop vs Claude Browser: Do You Need Both?

Your Claude browser account and Claude Desktop app are connected through the same Claude login.

According to Claude’s download page, your conversations, projects, memory and preferences sync across devices when you are signed in.

That means you do not need to panic if you start something in the browser and later open Claude Desktop.

You are not creating a second brain.

You are accessing the same Claude account through a different doorway.

When To Use Claude In The Browser

Claude in the browser is great for everyday AI work:

• Drafting content
• Asking questions
• Planning offers
• Reviewing copy
• Summarising documents
• Creating strategy
• Brainstorming campaigns

This is the easiest place for most business owners to start.

When To Use Claude Desktop

Claude Desktop becomes more useful when you want Claude closer to your actual computer environment.

For example, when you want to connect local tools, use desktop extensions, pair with mobile workflows, or use Claude Cowork features.

The desktop app is not just “another tab”.

It is the bridge between Claude and more of your working environment.

When To Use Claude Code

Claude Code is different again.

Claude Code is an agentic coding and project tool that can read your codebase, edit files, run commands and integrate with development tools. Anthropic describes it as available through terminal, IDE, desktop app and browser surfaces.

Now, do not let the word “code” scare you.

As a business owner, you may use Claude Code for far more than coding.

You can use it to manage structured files, create repeatable workflows, audit website folders, generate documentation, organise project assets and build systems that need file access.

In plain English:

Claude chat helps you think.

Claude Code helps you work inside a structured project folder.

Step 1: Download The Correct Claude Desktop App

Start with the official Claude download page.

Claude currently provides downloads for macOS, Windows, Windows arm64, ChromeOS and Linux. The same page also links to Claude Cowork surfaces, Claude Code environments, the Chrome extension and VS Code installation options.

If you are on Windows, pay attention to the difference between:

• Windows
• Windows arm64

Most Windows computers use standard Windows for Intel or AMD chips.

Some newer Windows devices use ARM-based chips, such as Qualcomm Snapdragon. Those usually need the Windows arm64 version.

If you are not sure which one you have, check your computer’s system information before downloading.

Simple Download Process

1. Go to the official Claude download page.
2. Choose the correct version for your computer.
3. Download the installer.
4. Save it somewhere obvious, such as your Desktop or Downloads folder.
5. Run the installer.
6. Follow the prompts.
7. Sign in with your Claude account.

If you cannot find Claude after installing it, use your Start menu on Windows and type “Claude”.

Don’t overthink this part.

The goal is simply to get the correct desktop app installed and logged in.

Step 2: Understand Where Node.js Fits In

This is one of the places people get themselves in a knot.

Claude Desktop chat does not require Node.js.

You can chat with Claude without Node.js sitting on your computer.

However, Node.js can matter if you are installing Claude Code through npm or working on projects that require JavaScript tooling.

Anthropic’s current Claude Code setup documentation says the npm installation requires Node.js 22 or later as of Claude Code v2.1.198.

So the practical rule is this:

If you are only using Claude chat, don’t obsess about Node.js.

If you are installing Claude Code with npm, working with web projects, or running tools that rely on Node, install the current official version of Node.js.

Why This Matters For Business Owners

When Node.js is missing or outdated, things can get weird.

Pages may load blank.

Commands may fail.

Installers may throw strange errors.

Claude may appear to be “broken” when the real issue is that your computer is missing part of the environment needed for that workflow.

This is why setup matters.

It is not glamorous.

But neither is wasting three hours because one invisible dependency was missing.

Step 3: Install Claude Code Properly

Claude Code now has several installation options.

Anthropic’s Claude Code quickstart recommends native installation and also lists options including Homebrew and WinGet. For Windows PowerShell, the docs provide an installation command, and for WinGet users they list winget install Anthropic.ClaudeCode.

For most non-technical business owners, the safest advice is this:

Use the official Claude Code installation instructions for your operating system.

Do not copy random install commands from a random forum, comment thread or “helpful” screenshot.

AI tools change fast.

Use the official docs.

After Installing Claude Code

Once Claude Code is installed, you will log in with your Claude account.

Claude’s quickstart explains that Claude Code requires an account and that once you start a session with the claude command, you are prompted to log in.

If you are not comfortable using the terminal yet, that is completely normal.

You do not need to become a terminal wizard overnight.

You just need to understand that Claude Code needs a working project location, which brings us to the next step.

Step 4: Install VS Code The Right Way

VS Code stands for Visual Studio Code.

It is a free code editor from Microsoft, but for our purposes, think of it as a clean project workspace.

It gives Claude Code a place to see your files, work inside folders and interact with your project properly.

Microsoft’s Windows setup guide says VS Code is available through a user installer, system installer and ZIP archive. For most people, Microsoft recommends the User setup because it does not require administrator permissions and supports smoother background updates.

How To Install VS Code

1. Go to the official VS Code website.
2. Download the version for your operating system.
3. On Windows, choose the User setup unless you have a specific reason not to.
4. Run the installer.
5. Open VS Code from your Start menu or applications folder.

Microsoft’s setup guide also notes that the installer adds VS Code to your PATH, and after installation you can run code . in a folder to open that folder in VS Code.

You don’t need to use that command if you are not ready.

But it is useful to know later.

Step 5: Install The Claude Code Extension Inside VS Code

This is the step many people miss.

Installing Claude Desktop is not the same as enabling Claude inside VS Code.

They are different surfaces.

To use Claude Code in VS Code, install the Claude Code extension inside VS Code.

The Visual Studio Marketplace lists “Claude Code for VS Code” by Anthropic, with the description that it lets you harness Claude Code without leaving your IDE. The listing also states that it requires VS Code 1.98.0 or higher.

How To Install The Extension

1. Open VS Code.
2. Go to Extensions.
3. Search for “Claude Code”.
4. Look for the extension published by Anthropic.
5. Check that it has strong usage and legitimacy indicators.
6. Install it.

Do not install random knockoff extensions.

This is a simple but important safety practice.

If you are letting AI work inside project files, you want to be very sure you are installing the real tool.

Step 6: Give Claude Code A Folder To Work In

Claude Code needs a working folder.

This is where many business owners get stuck.

They install everything, open the tools and then wonder why nothing useful is happening.

No folder means Claude has no clear workspace.

No workspace means it cannot easily read, save, organise or update your project files.

Anthropic’s quickstart explains that you start your first Claude Code session by opening your terminal in a project directory and running Claude from that location. It also explains that Claude reads project files as needed, so you do not have to manually add context every time.

In business-owner language:

Folder equals workspace.

Workspace equals context.

Context equals better outputs.

Create A Simple Starting Folder

Create a main folder somewhere sensible.

For example:

Claude_Business_Workflows

Then create subfolders like:

• SEO_Audits
• Blog_Content
• Grant_Applications
• Email_Triage
• Team_SOPs
• LinkedIn_Lead_Research
• Website_Reviews
• Client_Onboarding

Do not call your folder “stuff”.

Do not call it “AI things”.

Do not call it “new folder 7 final final actual”.

Name things like a grown-up because your folder structure becomes your business system.

Step 7: Open Your Folder In VS Code

Once your folder exists, open it properly inside VS Code.

Use:

File → Open Folder

Then select the actual folder.

Not a random file inside the folder.

Not the Downloads folder.

Not your entire computer.

The folder.

When the right folder is open, Claude Code has a clear workspace.

This is when the magic starts becoming useful rather than chaotic.

A Simple Folder Structure To Use

Here is a clean starter structure:

Claude_Business_Workflows

SEO_Audits

Website_Reviews

Blog_Content

Email_Triage

Grant_Applications

Team_SOPs

Lead_Research

Client_Onboarding

Inside each folder, add documents, notes, templates and outputs relating to that workflow.

For example, inside Blog_Content, you might store:

• brand voice notes
• blog briefs
• drafts
• SEO checklists
• published article logs
• repurposing prompts

That way, Claude is not just answering random questions.

It is working inside a repeatable business content system.

Step 8: Use Claude To Write Your Own Setup Instructions

This sounds silly until you try it.

One of the best ways to stop drowning in tech steps is to ask Claude to turn the setup into a plain-English checklist.

Use a prompt like this:

“Write me a Claude Code setup checklist for a non-technical business owner. Include how to install Claude Desktop, Claude Code, Node.js if needed, VS Code, the Claude Code VS Code extension, and how to open my first project folder. Make it simple, step by step, with troubleshooting notes.”

This is especially useful if:

• you are tired
• you are helping a study group
• you have a team member setting it up
• you need repeatable instructions
• you are not naturally technical
• you want to document your process once and reuse it

This is how you turn setup chaos into a business asset.

Do it once.

Document it.

Then your team can follow it too.

Step 9: Use /compact When The Conversation Gets Too Long

Claude Code has slash commands that help you manage sessions.

The current Claude Code commands documentation explains that /compact frees up context by summarising the conversation so far, and you can optionally pass focus instructions for the summary.

In plain English:

When a conversation gets too long, use /compact to stop the thread getting fuzzy.

This is useful for longer projects such as:

• SEO audits
• large documentation jobs
• website reviews
• business workflow builds
• grant applications
• system mapping
• multi-page content production

Instead of abandoning the whole conversation, you compact it.

This helps Claude keep the useful context while clearing space.

Step 10: Use /new Or /clear When You Need A Fresh Start

The Claude Code commands documentation lists /clear as a way to start a new conversation with empty context, while keeping the previous conversation available in /resume. It also notes that /new is an alias for /clear.

This is important.

Sometimes you do not need a longer conversation.

You need a clean one.

Use a fresh thread when you are changing tasks.

For example:

• One conversation for an SEO audit
• One conversation for blog writing
• One conversation for grant applications
• One conversation for inbox triage
• One conversation for team SOPs

Do not make one poor AI chat handle your entire business, your life admin, your website, your content strategy and your existential crisis all at once.

That is how messy outputs happen.

Step 11: Connect Your Business Tools Carefully

This is where Claude starts becoming more than “just chat”.

Claude connectors let you connect third-party tools and applications so Claude can access work data and, where approved, take actions in connected tools. Anthropic describes connectors as a way to give Claude access to knowledge in connected tools and desktop files, plus permission to perform actions on your behalf.

Claude’s Google Workspace connector documentation states that Gmail, Google Calendar and Google Drive connectors are available for Claude and Claude Desktop users, and that Claude can search emails, manage calendars, work with documents and save files without leaving the conversation.

But here is the important bit:

Do not connect everything just because you can.

Connect tools based on actual workflows.

Good Connector Use Cases

Use connectors for:

• finding emails related to a client
• summarising unread messages
• drafting Gmail replies
• checking calendar availability
• reading Google Drive documents
• pulling context from project files
• creating folders or saving organised outputs

Claude’s Google Workspace connector documentation also states that actions require explicit approval.

That is good.

You want AI assistance, not AI chaos.

Step 12: Install And Pin Claude In Chrome

The Claude Chrome extension can be useful when you want Claude to work inside browser-based tools.

The Chrome Web Store listing for Anthropic describes Claude in Chrome as an AI assistant that works directly in your browser, automating tasks and taking actions on your behalf. It also mentions browser workflows, scheduled tasks and multi-tab workflows, with availability for paid subscribers.

Once installed, pin it.

In Chrome:

1. Click the puzzle piece icon.
2. Find Claude.
3. Click the pin icon.
4. Keep it visible in your toolbar.

Most people install useful extensions and then immediately lose them.

Pin it so you actually use it.

What To Use Claude In Chrome For

Try browser workflows like:

• summarising a long webpage
• reviewing a sales page
• checking website copy
• pulling key points from an online resource
• triaging messages
• reviewing LinkedIn profile viewers
• extracting information from browser-based dashboards
• assisting with form-heavy admin

Again, use common sense.

If Claude is operating in your browser, supervise it like you would supervise a new assistant on their first week in your business.

Step 13: Understand Cowork And Computer Use Permissions

Claude Cowork and computer-use style features can be powerful because they let Claude work more directly across your apps and computer environment.

But the key word is permission.

Anthropic’s computer use documentation explains that Claude can open apps, click, type and see your screen in supported contexts. It also explains that approvals apply per session, and that Claude asks before controlling specific apps.

The same documentation also highlights safety guardrails, including per-app approval, warnings for apps with broad access, and the ability to stop actions.

For business owners, this is exciting.

But it is not something to treat casually.

Sensible Safety Rules

Use these rules:

• Start with low-risk tasks.
• Watch what Claude does.
• Do not give broad access unless it is necessary.
• Avoid sensitive financial, legal or client data until you understand the workflow.
• Use connected tools before screen control where possible.
• Keep a human approval step for anything important.

AI should reduce admin.

It should not create a governance nightmare.

Practical Business Workflows You Can Build With Claude

Once your setup is working, the real question becomes:

What will you use it for?

Here are practical workflows worth building.

SEO Audit Workflow

Create an SEO_Audits folder.

Store:

• website URLs
• keyword notes
• page copy
• audit checklists
• competitor notes
• final reports

Ask Claude to review a page for:

• title tags
• meta descriptions
• headings
• keyword intent
• readability
• internal links
• calls to action
• FAQ opportunities
• AI search readiness

This turns SEO from a random task into a repeatable process.

Content Production Workflow

Create a Blog_Content folder.

Store:

• raw transcripts
• article drafts
• brand voice instructions
• SEO templates
• CTA blocks
• repurposing prompts

Then ask Claude to turn your raw expertise into:

• blog articles
• email newsletters
• social posts
• YouTube descriptions
• lead magnet outlines
• podcast show notes
• carousel content

The power is not just in creating content.

The power is in having a system.

Grant Application Workflow

Grant applications are a brilliant use case because so many sections repeat.

Create a Grant_Applications folder.

Store:

• company overview
• founder bio
• team details
• business impact
• awards
• revenue notes
• innovation statements
• standard answers
• previous submissions

Then ask Claude to help adapt those details for each grant.

You still need to review the final submission carefully.

But you no longer need to rewrite “about your business” from scratch every time.

Inbox Triage Workflow

With the right connector setup, Claude can help summarise, categorise and draft responses.

Use it for:

• identifying urgent emails
• summarising unread messages
• drafting polite replies
• finding follow-up opportunities
• organising messages by client or project
• preparing a daily inbox briefing

This is where business owners get hours back.

Not because AI is fancy.

Because repetitive admin is finally getting a system.

LinkedIn Lead Research Workflow

If you have access to LinkedIn profile viewer data, especially through Premium, you can use Claude-assisted workflows to review potential leads.

For example:

“Review the people who viewed my profile in the last seven days and list anyone who works at a large food company, training organisation, corporate HR team, learning and development department or consultancy.”

This kind of workflow helps you spot opportunities you may otherwise miss.

Just remember that different LinkedIn plans show different levels of viewer data, so your results depend on what your account can access.

Team SOP Workflow

Create a Team_SOPs folder.

Use Claude to help document:

• how to publish a blog
• how to onboard a client
• how to reply to common enquiries
• how to prepare a workshop
• how to update a sales page
• how to create a lead magnet
• how to process testimonials
• how to send follow-up emails

This is one of the most valuable uses of AI in a growing business.

You are not just creating outputs.

You are capturing how your business works.

What About Smart Shift Email, Euler And Mission Control?

Some training cohorts, partner programs or AI communities use extra tools that are not part of the core Claude setup.

For example, you may be given:

• a Smart Shift AI email
• access to Euler
• access to a Mission Control dashboard
• cohort-specific tracking tools
• partner portal modules

Treat these as access and tracking layers.

They are not the heart of your business workflow.

Your core setup is still:

1. Claude account
2. Claude Desktop
3. Claude Code
4. VS Code
5. Project folders
6. Useful connectors
7. Clear repeatable workflows

If your cohort requires a special email or partner dashboard, follow the current cohort instructions.

But do not confuse “portal access” with “business system”.

The portal may track your learning.

Your folder structure and workflows are what make AI useful in your actual business.

Common Claude Code Setup Mistakes

Mistake 1: Installing Claude Desktop And Thinking Claude Code Is Done

Claude Desktop and Claude Code are related, but they are not the same setup.

You may still need to install Claude Code, configure VS Code or connect the extension.

Mistake 2: Not Opening A Folder

Claude Code needs a workspace.

A folder gives Claude context.

Without it, you are asking a highly capable assistant to work with no desk, no files and no brief.

Mistake 3: Putting Everything In One Folder

One giant folder called “business” will become a mess.

Separate workflows by outcome.

SEO audits go in one folder.

Grant applications go in another.

Content production gets its own home.

Mistake 4: Ignoring Node.js Completely

You do not need Node.js for basic Claude chat.

But if your Claude Code setup or web development workflow relies on npm, Node.js matters.

Use the current official version required by the installation method you choose.

Mistake 5: Giving AI Too Much Access Too Quickly

Connectors and browser automation are powerful.

Start carefully.

Approve deliberately.

Supervise anything sensitive.

Mistake 6: Expecting AI To Know Your Business Without Context

Claude is only as good as the context you provide.

Store your brand voice.

Store your offers.

Store your FAQs.

Store your process notes.

Store your examples.

That is how AI becomes a business assistant instead of a random content generator.

Best Practices For Using Claude As A Business System

Here is the simple version.

1. Start With One Workflow

Do not set up everything at once.

Choose one business area.

For example:

• blog production
• inbox triage
• SEO audits
• grant applications
• team SOPs

Build one clean workflow first.

2. Create A Dedicated Folder

Give that workflow a home.

Add your source material, templates, prompts and outputs.

3. Write A Repeatable Prompt

Create one master prompt for that workflow.

For example:

“Use the files in this folder to complete an SEO audit of the page I provide. Check headings, title, meta description, keyword intent, readability, internal linking, FAQ opportunities and CTA strength. Return a prioritised action list.”

4. Save The Output Format

Tell Claude exactly how you want the output delivered.

For example:

• summary
• issues
• recommendations
• priority actions
• copy suggestions
• next steps

5. Turn The Workflow Into A Skill Or SOP

Once the workflow works, document it.

Then reuse it.

That is where the real value is.

Not in one clever prompt.

In a repeatable business machine.

Key Takeaways

• Claude Desktop, Claude Browser, Claude Code, VS Code and Chrome are different surfaces with different jobs.
• Claude Code becomes more useful when you give it a clean project folder.
• VS Code is not just for developers. It can become a structured AI workspace for business workflows.
• Node.js is not required for basic Claude chat, but it may be required for npm-based Claude Code installs or web development workflows.
• Connectors and Chrome automation are powerful, but should be used with clear permissions and sensible supervision.
• Your folder structure becomes your operating system for AI.
• The goal is not to “learn tech”. The goal is to build repeatable workflows that save time and increase business output.

FAQ

What is Claude Code used for in business?

Claude Code can be used to work inside structured project folders, read files, update documents, assist with website reviews, create documentation, manage technical workflows and support repeatable business systems. Although it is built for coding and development environments, business owners can use it for practical file-based workflows such as SEO audits, SOP creation, content systems and grant application preparation.

Do I need VS Code to use Claude?

You do not need VS Code for basic Claude chat. You can use Claude in the browser or desktop app. VS Code becomes useful when you want Claude Code to work inside a structured project folder or development-style workspace.

Do I need Node.js for Claude Desktop?

No, you do not need Node.js for standard Claude Desktop chat. Node.js matters if you are installing Claude Code through npm or working with web development tools that rely on Node.

What is the difference between Claude Desktop and Claude Code?

Claude Desktop is the app you install on your computer to use Claude outside the browser. Claude Code is a more advanced project and coding assistant that can work with files, folders, commands and development tools.

Why does Claude Code need a folder?

Claude Code needs a working directory so it knows where your project files are. The folder acts as the workspace. It gives Claude context and a place to read, write and organise outputs.

Can I use Claude Code if I am not a developer?

Yes. You do not need to be a developer to benefit from Claude Code, especially if you use it for structured business workflows. You may need some initial setup help, but once your folders and workflows are clear, Claude Code can support non-technical business tasks such as content systems, documentation and audits.

Is the Claude Chrome extension safe to use?

The Claude Chrome extension can be useful, but you should use it thoughtfully. Only install the official Anthropic extension, supervise important tasks, and be careful when granting access to sensitive websites or business systems.

What are Claude connectors?

Connectors allow Claude to access and work with external tools such as Gmail, Google Calendar, Google Drive and other business apps, depending on what is available and approved. They help Claude move from generic chat into more practical business assistance.

What should I set up first?

Start with Claude Desktop, VS Code, Claude Code and one clean project folder. Then choose one workflow, such as SEO audits or blog production, and build from there. Do not try to automate your whole business on day one.

How can business owners use Claude for automation?

Business owners can use Claude to create repeatable workflows for content creation, email triage, lead research, SOP documentation, grant applications, SEO reviews, website audits and internal process mapping. The key is to give Claude clear context, structured folders and repeatable instructions.

Conclusion

Getting Claude Code, VS Code, Node.js, Chrome, Cowork, connectors and extra cohort tools set up can feel ridiculous at first.

But the point is not to become a tech genius.

The point is to stop wasting your brainpower on repetitive admin, scattered systems and messy workflows.

When your AI tools are installed properly, named properly and connected to clean project folders, they become part of your business operating system.

Not a toy.

Not a trend.

Not another tab you forget exists.

A practical assistant that helps you create, review, organise, document and implement faster.

Start simple.

Set up one folder.

Choose one workflow.

Document the process.

Then repeat.

That is how AI becomes useful.

Not by chasing every new shiny tool, but by building business systems that actually save you time.

Call-to-Action

If you want help turning your expertise, content, systems and offers into a proper business engine, come and join us inside Legends Lab.