Your First Real Claude Conversation

If you took our first course, you already know how AI works. You know about prompting. You've tried ChatGPT.

Now it's time to go deeper with one specific tool. And the tool we're going to spend the next two weeks on is Claude.

Why Claude? A few reasons.

First, it's genuinely good at the things knowledge workers actually do. Writing, analysis, research, working through complex problems. Not parlor tricks. Real work.

Second, it has features that most people don't know exist. Features that turn it from "a chatbot I ask questions" into "an actual system that runs parts of my work." That's what this course is about.

Third, it's the tool I use every day. Not because I have a sponsorship or affiliation. Because I've tried everything and it's the one I keep coming back to.

If you don't have a Claude account yet, go to claude.ai and sign up. The free tier works for the first few days of this course. By the end of the second week, you'll want a paid plan - not because I'm upselling you, but because the features we'll cover in Week 2 require it. You'll see why.

The prompting formula (refresher + Claude-specific)

You remember the basics. Be specific. Give context. But let's apply the formula to Claude specifically.

Every great Claude prompt has three parts:

Set the stage. Tell Claude who you are and what you're working on. Claude is designed to be steerable - it adapts its personality, tone, and depth based on what you tell it.

Define the task. What do you actually want? Not "help me with marketing" but "write a 200-word LinkedIn post announcing our new product feature, targeting small business owners."

Specify the rules. Format, length, tone, what to include, what to avoid. Claude follows constraints well - much better than leaving it to guess.

Here's the difference in practice.

Bad: "Help me write an email about a project delay."

Good: "I need to email a client (enterprise SaaS company, we've worked together 8 months) that our integration project will be delayed by two weeks. This is the second delay. They've been patient but I'm worried about losing their trust. Keep it under 150 words. Professional but genuinely apologetic - not corporate-speak apologetic."

That second prompt takes 30 extra seconds to write. The output saves you 20 minutes of editing.

What makes Claude different from ChatGPT

I'm not going to do a feature-by-feature comparison. That stuff changes every month. But there's one thing that matters at a fundamental level.

Claude is designed to be collaborative, not performative. It doesn't try to impress you with how smart it is. It tries to actually help you get work done. When it doesn't know something, it tends to say so instead of making something up.

That sounds subtle. In practice, it changes how you work with it. You start treating it less like a magic 8-ball and more like a coworker who's really good at research and writing.

The iteration mindset

Here's the thing nobody tells beginners: your first prompt almost never produces the final result. And that's fine.

The people who get the most out of Claude treat every conversation as iterative:

• First response too generic? Say "This is too vague. I need specific examples from the B2B SaaS space, not general advice."
• Tone is off? Say "This sounds like a corporate press release. Make it sound like I'm explaining this to a friend over coffee."
• Too long? "Cut this in half. Keep only the parts that would matter to a CFO."

Specific feedback beats vague feedback every time. "Make it better" gives Claude nothing to work with. "The opening is weak - start with the revenue impact number instead of the background context" gives it everything.

Think of it like managing a smart junior employee. The clearer your feedback, the faster they improve.

Try this today

Open claude.ai and do this:

1. Pick a real work task you need to do this week. Not a test. Something real.
2. Write a prompt using the three-part formula (stage, task, rules).
3. Read Claude's response. Don't accept it.
4. Give it specific feedback on what to change.
5. Repeat once more.

Notice how the third version compares to what you'd have gotten from a one-shot prompt. That gap - that's the skill we're building.

Claude rewards specificity and iteration. The more clearly you communicate what you want, the less editing you do after.