Get Claude Ready
for Real Work

Most people open Claude and start typing. That's why most people get average results. This setup takes 20 minutes. It changes every session after it.

By the end of this lesson you will have:
  • A Claude account configured for business use
  • Memory enabled so Claude learns your context over time
  • Global instructions that shape every response automatically
  • A response style Claude follows by default
  • Your first project workspace set up
  • Proof it works — a real output from your first structured prompt
1

Create Your Account

The right foundation from day one

Go to claude.ai and create your account. You have two options:

Free Plan

Good for exploring Claude and running occasional prompts. Conversation length and file uploads are limited. Fine to start with — upgrade when you're ready to go deeper.

Desktop App vs Browser

Either works. The Claude desktop app (available at claude.ai/download) opens instantly, stays out of your browser tabs, and makes it easier to build a daily habit. We recommend it for everyday business use.

Action: Create your account at claude.ai before continuing. If you're managing a team, explore claude.ai/teams for shared workspaces and admin controls.
2

Enable Memory

Let Claude learn who you are

Without memory, every Claude conversation starts from zero. You re-explain your role, your business, your preferences — every single time. Memory eliminates that entirely.

What Memory Actually Does

Claude doesn't record or store your full conversations. It extracts useful facts and preferences from them and builds a running summary — things like your role, your communication style, and recurring context. You can view exactly what it stores, edit it, or delete anything at any time.

How to turn it on:

  1. Click your name or avatar in the bottom-left corner of Claude
  2. Go to Settings
  3. Click "Memory" in the left menu
  4. Toggle it on

That's it. From this point forward, Claude builds a profile of you across sessions. The longer you use it, the less setup each conversation requires.

3

Write Your Global Instructions

The standing orders every conversation follows

What Are Global Instructions?

Global Instructions are rules Claude applies to every single conversation — regardless of topic or task. Think of them as the onboarding document you'd give a new employee: your preferences, your communication style, your non-negotiables. Set them once, benefit from them forever.

How to set them:

  1. Go to Settings
  2. Click "Profile" or "Personalization"
  3. Find "What would you like Claude to know about you?"
  4. Paste and customize the template below
Your Global Instructions — Starting Template
My name is [Your Name]. I am [Your Role] at [Your Company Name].

What I primarily use Claude for:
- [Use case 1 - e.g., drafting client-facing communications]
- [Use case 2 - e.g., reviewing contracts and flagging key clauses]
- [Use case 3 - e.g., building automations and internal workflows]

My clients are: [describe in one sentence - industry, size, typical need]
Industry: [your industry]

What I need from you:
- Be direct. No filler phrases like "Certainly!" or "Great question!"
- When you're uncertain, say so explicitly - don't guess and present it as fact
- Format long responses with headers and bullet points
- Match my tone when writing: [professional / concise / conversational]
- Skip disclaimers unless there is a genuine legal or safety reason to include one
4

Set Your Response Style

Control how Claude communicates with you

Why This Matters

Without response style settings, Claude defaults to whatever it thinks is appropriate — which often means long, hedged, over-explained responses you have to trim down. These settings fix that at the source.

How to set it:

  1. Go to Settings → Profile
  2. Find "How would you like Claude to respond?"
  3. Paste and adjust the template below
Response Style Template
Keep responses concise unless I specifically ask for depth.
Use headers and bullet points for anything longer than 3 paragraphs.
Never open a response with "I" or with affirmations like "Sure!" or "Of course!"
When I give you a task, complete it - don't ask clarifying questions unless something is genuinely ambiguous.
If I share a document or paste text, analyze it without summarizing back what I just gave you.
Skip filler transitions and lead with the actual answer.
Customize, Don't Copy Blindly

These templates are a starting point. The most effective global instructions are specific to your real workflow. As you use Claude over the next few days, note what you keep having to correct — then add those corrections to your settings permanently.

5

Create Your First Project

A dedicated workspace for every recurring workflow

What Is a Project?

Projects are Claude's dedicated workspaces. Each project has its own instructions, file library, and conversation history — completely separate from everything else. Use one project per client, per department, or per recurring workflow you manage. Your global instructions still apply; project instructions add a second layer on top.

How to create one:

  1. In Claude's left sidebar, click "New Project"
  2. Give it a specific, descriptive name (e.g., "Client Intake Process" or "Contract Review")
  3. Click "Project Instructions" and add your context
  4. Upload relevant files — SOPs, templates, brand guidelines, past examples
Project Instructions Template
This project is for: [specific workflow, client type, or department]

Background context:
- [Key fact 1 - e.g., client industry, relevant regulations, workflow stage]
- [Key fact 2 - e.g., common deliverable types, recurring challenges]

Output rules for this project:
- Default format: [bullets / prose / email / memo / structured report]
- Tone: [formal / conversational / client-ready]
- Always include: [e.g., a one-sentence summary at the top]
- Never include: [e.g., passive voice, hedging language, legal disclaimers]
6

Run Your First Structured Prompt

See the difference immediately

Most people prompt like this:

"Write me an email to a client about the project update."

That gets you generic output you'll rewrite from scratch. Here is the structure that gets you something immediately usable:

The Structured Prompt Framework
Task: [What you need - be specific about the output type]

Context:
- Who this is for: [audience]
- Background: [1–3 sentences of relevant context]
- Any constraints or history: [deadlines, prior conversations, sensitivities]

Output requirements:
- Format: [email / bullet list / memo / summary / analysis]
- Length: [short / under 200 words / as long as needed]
- Tone: [formal / direct / warm / persuasive]

Deliver the output directly. No preamble.
Why This Works

The difference between a vague prompt and a structured one isn't just output quality — it's the editing time afterward. A structured prompt produces something 80% ready to use. A vague one produces something you'll spend 20 minutes rewriting. At scale, across dozens of tasks per week, that gap compounds into hours saved.