Setting up an environment to run Claude/Claude Code for non-engineers

About this Series

I'm Jinno from the Account Sales Department at Classmethod. In my daily job, I work as an account sales representative for public cloud services like AWS and cloud services like Claude.

Recently, Claude has been attracting a lot of attention, and within our company, we've been individually advancing the use of Claude. While it's certainly demonstrating great power in design and development processes by engineers, it's also showing efficiency and productivity improvements when used by non-engineers, which makes me feel there's great potential here.
So, with the hope of providing useful references for non-engineers using Claude, I'd like to start writing a blog series called "Claude/ClaudeCode Series for Non-Engineers." This series will be written in rotation by non-engineers at Classmethod, so we plan to share experiences from members in various roles. I hope this will be helpful to many people.

Why should non-engineers use Claude Code?

If you thought, "Isn't Claude Code meant for engineers?", I initially thought so too.

However, after actually trying it, my perception changed. Claude Code isn't a "tool for writing code," but rather "an agent that autonomously performs file operations and data processing when you communicate what you want to do in natural language."

As a salesperson, here are some things I've actually been able to do:

• Automatic generation of sales materials (PowerPoint, Word)
• Integration with Google Calendar
• Automation of attendance management (King of Time) operations
• Automation of customer research

If you thought, "Couldn't you do this with Claude chat too?", you're perceptive. In fact, looking at individual tasks, many can be accomplished with Claude.ai's chat or Cowork features.

So why Claude Code specifically? After using it, I found two decisive differences.

The first is "autonomy." While chat basically provides "one response to one instruction," Claude Code thinks through multiple steps on its own and executes them autonomously. For example, if you tell it to "summarize last week's sales activities in PowerPoint," it will find the necessary files on its own, organize the data, structure the slides, and save the file. It will proceed through this entire sequence without requiring multiple instructions from you.

The second is "context accumulation." Claude Code automatically reads files in the working folder and CLAUDE.md (which I'll explain later). In other words, you don't have to repeatedly explain "I'm in sales" or "use this format" - it can infer the situation from past files and settings. The more you use it, the more context accumulates in the folder, and you'll need fewer instructions.

I feel like I have an extremely competent secretary, and I can see the actual effects of this. (Though I've never actually worked with a personal secretary...) Moreover, this secretary doesn't need explicit instructions - it can infer context from materials on the desk and past interactions, thinking "This is what you mean, right?" That's what I feel is Claude Code's greatest strength.

I hope more people, regardless of their job responsibilities or positions, will benefit from using Claude Code in their work!

How to Use Claude Code

Before getting into the steps, there's one important thing to mention.

When you hear "Claude Code," you might imagine typing the claude command in a terminal. That's how engineers actually use it.

But for non-engineers, the "Code" tab in the Claude Desktop app is recommended.

Using the "Code" tab means:

• No terminal needed. No need to remember commands
• Access Claude Code features directly from the chat interface
• Directory (folder) specification possible through GUI

Honestly, I thought "Isn't Claude Code something you use in the terminal?", but I was able to use it normally from the "Code" tab in the Claude Desktop app. If you're uncomfortable with terminals, start here.

In this series, we'll proceed with the assumption that you're using the "Code" tab in Claude Desktop.

Installation Steps

Here are the steps to start using Claude Code, in order.
You can just follow them in sequence. Each step includes considerations, so please don't skip reading them.
I personally use a Mac, so the screenshots will be from Mac, but I've included information for Windows based on official sources as well.

Step 1: Install Claude Desktop

First, install the Claude Desktop app.

1. Access the download page

Open the download page from the URL below.

https://claude.ai/download

2. Download the installer for your OS

Mac users should click "macOS" and Windows users should click "Windows" to download.

3. Install

• Mac: Open the downloaded file and follow the prompts to install. When completed, Claude will be added to your Applications folder
• Windows: Run the downloaded file and follow the prompts to install. Claude will be added to your Start menu
  

4. Launch and sign in

Launch the Claude app and sign in with your account. If you don't have an account yet, create one at claude.ai.

At this point, the Claude Desktop installation is complete. However, you cannot use Claude Code (the "Code" tab) with the free plan. In the next step, we'll subscribe to a paid plan.

Step 2: Subscribe to a paid plan

To use Claude Code, you need to subscribe to a paid plan. The free plan only allows chat functionality, and the "Code" tab is not displayed.

Plan selection criteria

Since "Which plan should I choose?" is likely the first hurdle, I'll explain how to choose from a non-engineer's perspective. This is based on information as of today, so please check Claude's official page for the latest information.

Recommendation for non-engineers: Start with the Pro plan ($20/month).

The reason is simple: you won't know how much usage you need until you try it. If Pro isn't enough, you can upgrade to Max, and if you want to implement it across your organization, you can switch to the Team plan. There's no need to start with a higher-tier plan.

💡 Understanding usage limits: Claude's paid plans have "usage limits." When you reach the limit, you temporarily can't use it, but it resets after some time. In my experience, the Pro plan is sufficient for general sales tasks. If you find yourself "hitting the limits often," consider Max at that point. You can check your usage from Settings -> Usage in Claude Desktop.

Subscription process

1. Open Claude Desktop app or claude.ai in your browser

2. Select a plan from the settings screen
In the Claude Desktop app, you can access this from the screen below.

3. Select the Pro plan and enter payment information

You can choose between monthly and annual payments, but personally, since you don't know how much you'll use it, I think it's better to start with the monthly plan.

4. Restart the Claude Desktop app after completing the subscription

When you switch to a paid plan, the "Code" tab will appear at the top of the app. This is the entry point to Claude Code.

Step 3: Create a working directory (folder)

After installing Claude Desktop and subscribing to a paid plan, you might want to launch Claude Code right away. But there's something you should do first: prepare a working folder.

Why create a folder first?

Claude Code operates based on the folder you specify. It reads files in that folder and creates new files there.

This means that if you launch it on your desktop, all files on your desktop become potential targets for Claude Code operations. This creates a risk of affecting unrelated files.

By creating a dedicated folder and launching from there, you can limit Claude Code's scope of action.

Actual steps

1. Open Finder and navigate to your home directory

Your home directory is your user name folder on Mac. You can open it from the Finder menu bar by selecting "Go" -> "Home".

2. Create a working folder

Right-click in your home directory -> "New Folder" to create a folder. In this case, we'll name it claude-work.

~/claude-work/    ← This will be your home base for future Claude Code work

Considerations: Avoiding folder design mistakes

This may seem trivial but is important for future use. I'll write based on my own mistakes.

Places to avoid

To explicitly specify Claude's operating environment, first create a folder for Claude.
I initially deployed without explicit specification, which allowed Claude to access more than I intended, creating a situation that wasn't great for security. I've fixed it now, but it's much harder to correct after extensive use, so it's better to specify the operating environment from the beginning.

Create subfolders for each project

As you use Claude Code for multiple tasks, files will accumulate. Organizing by project from the start will save you trouble later.

~/claude-work/
├── CLAUDE.md              ← We'll create this in the next step
├── projects/
│   ├── sales-report/      ← For sales report creation
│   ├── kintone-agent/     ← For kintone integration automation
│   ├── blog-drafts/       ← For blog drafts
│   └── sandbox/           ← For testing (a folder where breaking things doesn't matter)
├── scripts/               ← Repository for scripts created by Claude Code
└── archive/               ← Storage for completed projects

You don't need to create this full structure at the beginning. Just having the claude-work folder is enough. Subfolders will naturally develop as you use it.

Step 4: Create CLAUDE.md

After creating the folder, the next step is to create CLAUDE.md. This might be the most important step for non-engineers.

What is CLAUDE.md?

CLAUDE.md is a configuration file that Claude Code automatically reads at startup. You can write it in plain Japanese (or any language).

Think of it as a "handover document" for a new team member.

• What kind of professional you are
• What you want to accomplish
• What tools you normally use
• How you want Claude to respond

When you write this down, Claude Code will automatically read it every time, so you won't have to give the same explanations every time you start a new conversation.

Conversely, without CLAUDE.md, Claude Code starts with a blank slate every time.

• It doesn't know you're a non-engineer → It explains things using technical terms
• It doesn't know what tools you use → It makes irrelevant suggestions
• It doesn't know what you want it to confirm before creating files → It generates files immediately

If you assign work to a new subordinate without a handover, you'll be asked the same questions every time. It's the same principle.

Actual creation steps

There are three ways to create CLAUDE.md, but having Claude Code create it for you is the easiest.

Let's try the recommended method.

1. Open the "Code" tab in Claude Desktop

2. Specify the claude-work folder you created earlier as the project directory

3. Enter the following as your first message

Please create CLAUDE.md. I'm in sales (non-engineer) at Classmethod Inc. (https://classmethod.jp/), and I want to automate AWS and Claude-related sales tasks. Please explain code in simple terms. If there are errors, please tell me both the cause and solution. Please confirm what you're going to create before creating files.

When asked if you trust the workspace, it's fine to proceed with "Trust workspace" since we created this folder specifically as Claude's operating environment.

4. Claude Code will generate CLAUDE.md for you
It will ask if this is good, so let it know to proceed.

That's it. Claude Code will automatically create a CLAUDE.md tailored to your situation.

Considerations: Important points about CLAUDE.md

The best timing is "right after first launch"

CLAUDE.md is loaded when Claude Code starts up. So if you create it during your first conversation, you'll benefit from it starting with your second launch. It's best to do it right away rather than "later," which you might forget.

Start minimal and build it up over time

You don't need to write a perfect CLAUDE.md from the beginning. You can add things as you realize "I should have written this" while using it. Here's the CLAUDE.md that was created with the prompt we used:

# Project: Sales Task Automation (AWS & Claude related)

## Overview

Workspace for automating AWS and Claude-related sales tasks at Classmethod Inc.

Design with top priority on non-engineers being able to operate and maintain.

## Coding Rules  

### Clarity is the highest priority

- Write Japanese comments explaining "what is being done" in the code

- Each function/script should have just one role

- Use meaningful English variable/function names (e.g., `customer_list`, `send_email`)

### When introducing libraries/tools

- Explain why the library is necessary before introducing it

- Provide installation instructions as well

## Error Handling Rules

When an error occurs, present these three points together:

1. **Cause**: Why the error occurred (explain technical terms in simple language)

2. **Solution**: Specific steps to fix it (at a level that can be executed by copy-paste)

3. **Prevention**: Points to prevent the same error from recurring

## File Creation Rules

- Before creating new files, confirm "what to create and why"

- Don't create new files if editing existing ones will suffice

- Don't write sensitive information (API keys, customer data, etc.) directly in code; manage them with environment variables or `.env` files

## Explanation Style

- Add supplementary explanations to technical terms in parentheses

- Use metaphors and concrete examples as needed

- Add summaries like "In other words, ○○"

## Directory Structure
claude-work/

├── CLAUDE.md # This file (project rules)

├── scripts/ # Automation scripts

├── data/ # Input/output data (CSV, etc.)

├── docs/ # Documents and notes

└── templates/ # Email templates, etc.

※ Create directories when needed (don't create empty folders in advance)

Currently, the one I actually use has much more content, but you can update that through interactions with Claude, so starting minimal is fine.

Place CLAUDE.md directly under the claude-work folder

Claude Code reads the CLAUDE.md file located directly under the startup folder. If you put it in a subfolder, it won't be read. With the creation method we used, it should automatically be created in the correct location.

~/claude-work/
├── CLAUDE.md       ← ✅ Place it here
├── projects/
│   └── CLAUDE.md   ← ❌ Won't be read at startup if placed here
└── ...

Summary

In this article, we've gone through the entire process of setting up Claude Code for non-engineers. Let's review the steps:

It takes only about 15 minutes to set up an environment to start using Claude Code.

To reiterate, steps 3 and 4 are especially important:

• Create and launch from a dedicated folder (not directly on the desktop)
• Create CLAUDE.md right after first launch (having Claude Code create it for you is easiest)

These two steps significantly affect how user-friendly Claude Code will be. If you start using it without a proper environment, files will be scattered, you'll have to give the same explanations repeatedly, and folders and files will spread beyond expectations, making it difficult to use.

On the other hand, by actively experimenting with it, you'll generate ideas for potential use cases and efficiency improvements, and you'll see increasing benefits!
Once the environment is set up, non-engineers can use Claude Code normally, so use these steps to get started!

In future articles, I'll share experiences, successes, and failures from a non-engineer's perspective, which I hope you'll find helpful!

Reference Links

• Claude Desktop Download
• Claude Desktop Installation Guide (Official)
• Claude Plans and Pricing
• How to Use Claude Code Desktop (Official)
• Claude Official - Pro Plan Details
• Claude Official - Team Plan Details
• Claude Official - Max Plan Details
• Claude Official - Differences Between Usage and Context