What is Claude? A plain-English guide

Last month a teammate opened a meeting with “I asked Claude,” then spent five minutes arguing with finance about whether that meant a website, a model, a company, or a bot that lives inside Slack. Nobody was wrong in the way people are wrong about sports teams. They were using one word for three different things, the way people once said “Google” when they meant search, the company, or “whatever is on my phone.”

If you only need one clean map before you try the product, this post is that map. It skips the ranking wars and the “this will change everything” hype, and it gives you just enough structure so the rest of what you read about Claude clicks into place.

If you want the broader vocabulary first, meaning terms like LLM and generative AI and why these systems predict text at all, start with our plain-English overview of what LLMs, ChatGPT, and generative AI are. This series sits next to the Practical AI series when you want workflow habits, not product tours.

Three things people mean by Claude

When someone says “Claude,” they might mean any of three stacked things, and mixing them up is how office chat gets confusing fast.

Layer 1 is the company. Anthropic builds Claude and is itself a company with employees, research, policies, pricing pages, and legal terms. You do not “install Anthropic” the way you install an app; you use products that Anthropic and its partners ship.

Layer 2: the models. A model is the trained system that turns your words, and sometimes your images or files, into a response. Model families get names and version numbers, and right now consumer and platform docs talk about names such as Haiku 4.5, Sonnet 5, Opus 5, and Fable 5. Names and generations change often, so treat the labels as map pins, not eternal brands.

Layer 3: the products you actually open. These are the places you click: claude.ai in a browser, desktop apps for Mac, Windows, and Linux, mobile apps for iOS and Android, plus specialized tools such as Claude Code, Claude Cowork, Claude Design, Claude Science, and API access through the developer Console, all under the same family name but reached through different paths.

A useful analogy: a car company designs engines (models), sells cars and apps that use those engines (products), and remains the legal entity you sue or praise (company). You do not need engine blueprints to drive to the grocery store. You do need to know which key goes in which car.

Why the split matters at work

IT policies often ban “the free consumer chatbot” while allowing a vendor-managed enterprise seat. Finance may approve API spend and refuse personal Pro subscriptions. Your manager may say “use Claude” and mean “paste into the web chat,” while an engineer means “run Claude Code in the terminal.” If you keep the three layers straight, those conversations stop sounding like people are talking past each other.

Liability also stays with humans: Claude is not the official record for company numbers, legal commitments, or board materials. If a draft is wrong and you ship it, that is on you. The tool can be excellent and still not own the outcome.

What Claude is, in one paragraph

Claude is Anthropic’s family of large language model assistants, plus the products built around them. You type, speak, or upload something, and Claude generates a response based on patterns it learned during training, plus whatever context you give it in the conversation, files, or connected tools. It can draft, summarize, explain, critique, brainstorm, write code, and work through multi-step tasks when the product you’re using supports tools. It is software that predicts useful next text within safety rules and product limits, not a person, a database of your private company facts, or a magic truth machine.

That’s enough of a map to get going. Next: what Claude is actually good at, and where it falls flat.

What Claude is good at

Focus on the job, not the vibe. Here are jobs where a careful person working with Claude usually beats a careful person working alone.

Turning rough notes into readable drafts

Meeting notes, bullet lists from a whiteboard, a half-finished email you already hate: Claude is strong at structure, meaning outlines, subject lines, section headers, and tone shifts such as “make this firmer but not rude.” You still need to check names, dates, and claims yourself. The win is speed, going from a mess to a first readable draft.

Explaining dense material in plainer language

Policy PDFs, vendor docs, error logs, academic abstracts: ask Claude for a summary written for a specific audience, such as “a sales manager who has ten minutes.” Ask what is ambiguous. Ask what questions a skeptic would raise. This is where Claude earns its keep for analysts and operators who spend their days in long documents.

Brainstorming options, then narrowing them

Product names, interview questions, A/B test ideas, ways to structure a dashboard narrative: Claude will flood you with options, and your job is taste and constraints. “Give me five options under 40 characters” works better than “be creative.”

Coding help and technical explanation

Many people use Claude for SQL drafts, Python snippets, regular expressions, and “why is this query wrong” conversations, and that’s genuinely useful. It’s also where trusting the tool too much hurts you. If you use AI-written SQL in production, treat it like code from a junior colleague: read it, run it on a safe sample, and check the joins and filters. We keep a practical habit guide on how to check AI-written SQL for exactly that reason.

Long-context work when the product allows it

Paste or attach a long report and ask for the themes, the contradictions, or a one-page brief. Paid plans and certain modes expand what you can do with files, research-style browsing, and project folders. The real skill is packaging the context so the model can see what actually matters, not dumping in everything at once.

Role-play for practice, not for truth

“Interview me as a skeptical CFO.” “Red-team this launch plan.” Role-play works like a practice gym: useful for rehearsal, and no substitute for talking to the real CFO.

Notice what these share: Claude shines when the output is revisable and you can verify it, such as drafts, explanations, options, and code samples you will actually test. It is weaker when the output has to be an authoritative fact you cannot check yourself.

What Claude is not

Clear boundaries save embarrassment.

• Not your official record. Do not cite Claude as the origin of revenue, headcount, clinical results, or legal interpretation, and instead point to the real system where that number lives, such as your CRM or your finance ledger, plus the contracts and the people who actually have authority over it.
• Not your company’s memory by default. Unless you connect approved systems and follow policy, Claude does not “know” last quarter’s closed pipeline, and if you press it to sound sure anyway, it may invent a plausible-looking number instead.
• Not a person, even though it can feel like one. It has no ongoing life between sessions beyond what the product stores as chat history, memory features, or project files, and its warm tone is design and training, not friendship.
• Not always up to date. Training cutoffs and product tools, such as web search when it’s available, matter, so for breaking news or live prices, verify outside the chat.
• Not a license to paste secrets. Customer PII, credentials, unpublished earnings, health data, and anything under NDA need a policy answer before they hit a consumer chat box. A later post in this series covers memory and privacy habits in more depth.
• Not a replacement for judgment. It can propose a chart title. It cannot own the decision to ship a metric definition that will get gamed.

If you remember only one line: Claude is a fast junior collaborator with infinite patience and no accountability, so you are the one who supplies it.

How people access Claude (light tour)

You don’t need to use every path on day one. Getting familiar with the paths now means later posts won’t catch you off guard.

Web: claude.ai

This is usually where people start: create an account, open a chat, and type. Free and paid plans both live here, with different limits and features. Browser access alone is enough for writing, explaining, and light analysis work.

Desktop apps

Anthropic ships desktop clients for Mac, Windows, and Linux. Desktop is handy if you want a dedicated window, local integrations, or workflows that feel less like “another browser tab.” Features can lag or lead the web depending on release timing, so check the download page when you set up.

Mobile: iOS and Android

Good for quick questions, voice-to-text ideas on a commute, and catching a draft between meetings, though it is awkward for long file work. It shares the same account as the web for many features, subject to your plan and app version.

Specialized products (names, not deep tutorials)

Paid consumer plans open up more than plain chat. Pro-tier marketing currently highlights tools such as Claude Code (coding-oriented workflows, including terminal-style work), Claude Cowork (agent-style computer work, though the exact definition shifts month to month), Claude Design, Claude Science, research-style features, Projects, and a Microsoft 365 path, and the exact packaging changes often. A later post in this series covers Free, Pro, and Max plans in detail and maps each specialized product, so you don’t have to buy everything on day one.

API and Console (separate from “I just chat”)

If you build apps, you might use the Claude API through Anthropic’s developer Console, or through a cloud partner. That is a different billing and login story from a personal claude.ai subscription, and mixing the two up in your head is a classic mistake. A later post in this series calls this out again once plans and usage come up.

Age and account basics

Claude consumer products are for users 18 and older; confirm the current terms when you sign up. Work accounts may sit under Team or Enterprise plans with single sign-on (SSO) and admin controls. If your employer provides Claude, use that path for work content unless policy says otherwise.

Models in plain English (no hype ranking wars)

Product screens often let you pick a model, or pick a default one for you. Think of models as different engines in the same brand garage.

Right now, in mid-2026, the names you are likely to see include:

• Haiku 4.5: the faster, lighter option. Good for short tasks, high volume, lower cost in API settings. Quality is strong for many everyday jobs; it is not always the best choice for the hardest multi-step reasoning.
• Sonnet 5: the workhorse label in many coding and agent marketing materials. Balance of speed and capability for a lot of real work.
• Opus 5: the heavier, more capable end of the classic lineup for tough agentic and complex tasks. Often slower or more usage-heavy depending on plan metering.
• Fable 5: a newer generation name in Anthropic’s lineup, aimed at long-running agent-style intelligence, according to wording on the official site. Availability and plan access can differ, so treat it as a distinct model tier, not a synonym for Opus.

Older generation numbers, such as 4.5, 4.6, and 4.8, may still appear in API docs or cloud marketplaces while consumer chat pushes newer defaults. That is normal; software versions overlap.

Practical rule for beginners: use the default model until you hit a wall. If answers feel shallow or you need deeper multi-file reasoning, try a higher tier when your plan allows. If you are burning through limits on simple rewrites, try a lighter model. Do not pick a model because a social post said it “crushes” another brand last Tuesday.

Model names will change again, and the skill that lasts is knowing you are choosing a capability and cost tradeoff, not joining a personality cult.

Comparing Claude with other AI assistants

People love tournament brackets. For learning, a calmer frame works better.

Shared family traits. All three are modern AI assistants built on large models. You chat, attach context, and get generated text, and increasingly tools such as code execution, browsing, and file creation. All three can hallucinate and need human review for high-stakes work, and all three sit behind accounts, plans, and usage limits.

Different companies and ecosystems. Claude comes from Anthropic, ChatGPT comes from OpenAI, and Gemini comes from Google. Ecosystems matter here: Google Workspace vs Microsoft 365 connectors, mobile defaults, enterprise contracts your company already signed, data residency options, and which tool your team already documents.

Different product shapes. One product may feel better at long document work this quarter. Another may feel better at image generation or a specific plugin store, and those strengths move around from quarter to quarter. Buying decisions for companies often hinge on security review and admin features more than a one-off demo.

What to do as a learner. Pick one primary assistant for a month so your habits stick. Use a second only when you need a second opinion on a sensitive draft, such as “does this email sound passive-aggressive?” Switching every day because a social post said a new model dropped is a great way to learn nothing about prompting and everything about the fear of missing out (FOMO).

This series teaches Claude specifically, but the same verification habits apply everywhere: check numbers, check SQL, check citations, keep secrets out of the box.

What people usually mean when they say “Claude”

Use this as a decoding key in meetings.

Where people trip up with Claude

• Treating fluent answers as true. Fluency is the product; truth is still your job, so ask for sources and then open them yourself. For internal facts, open the warehouse or the finance system, not only the chat.
• Pasting confidential data into a personal account. Even if “everyone does it,” policy and regulation do not care about everyone. Use approved tools for approved data.
• One giant vague prompt. “Write a strategy” without audience, length, constraints, or success criteria produces generic mush. Give role, reader, length, must-include facts, and must-avoid claims.
• Never iterating. First drafts are clay, so reply with “shorter,” “more skeptical,” “add a table of assumptions,” or “list what you are unsure about,” because conversation is the feature.
• Confusing Free limits with “Claude is broken.” Hitting a usage wall is a plan and metering issue, not a moral failure of the model. A later post explains Free, Pro, and Max plans without the upgrade panic.
• Assuming one brand must win forever. Tools change, but your verification habits and data hygiene transfer with you.
• Skipping the human-readable goal. If you cannot say what “good” looks like in one sentence, Claude will invent a shiny wrong target.

Practice: thirty minutes to place Claude in your head

Do this once. Write your answers in a notes app, not only in your head.

1. Map the three layers on paper: company name, two model names you have heard, two product paths you might use. If you cannot fill two of each, re-read the layers section.
2. Open claude.ai (or your company Claude portal), start a new chat, and paste a non-sensitive paragraph you wrote last week. Ask: “Rewrite for a busy manager in 120 words. Keep all numbers exactly, and flag anything that looks like a claim without evidence.”
3. Stress-test honesty. Ask: “What might be wrong or incomplete in your rewrite?” Read the answer, and notice whether you still want to paste the draft into email unchanged.
4. Name one off-limits category for your job, for example customer phone numbers, unpublished revenue, or passwords. Write it as a personal rule.
5. Read the next post first. It walks through Free, Pro, and Max plans, so understand your options before you upgrade anything.

Optional stretch: take a short SQL snippet you understand and ask Claude to explain it line by line, then to propose a change, and run both versions yourself. Keep the habit from checking AI-written SQL even when the explanation sounds perfect.

How this series will use the word Claude

For the rest of this series, “Claude” usually means the assistant products you chat with, unless we say “model,” “API,” or a specific product name like Claude Code. When pricing or limits matter, we will say Free, Pro, or Max. When company policy matters, we will say Anthropic’s terms or your employer’s rules.

We will also keep linking outward when the topic is bigger than one vendor. Generative AI basics live in the LLM explainer. Workflow discipline lives in Practical AI. Vendor-specific depth stays here, so you are not juggling five mental models at once.

Quick recap

• Separate Anthropic (company), Claude models (engines), and Claude products (where you click).
• Claude is strong at drafts, explanations, options, and technical help you can check yourself. It is the wrong place to look for your official numbers.
• Access paths: web (claude.ai), desktop (Mac, Windows, Linux), mobile (iOS, Android), plus specialized tools and a separate API Console story.
• Model names (Haiku, Sonnet, Opus, Fable, with version numbers) are capability and cost tradeoffs, and they change over time.
• ChatGPT and Gemini are sibling tools in the same broad category, built by different companies with different strengths.
• Claude’s consumer products require users to be 18 or older, and work use may need a separate company plan; check Anthropic’s terms if you are unsure.
• Liability stays with humans, so verify numbers, SQL, and anything that ships before you send it.
• Next up in this series: Free vs Pro vs Max, what you actually get, without upgrade panic.

Series notes

This is Part 1 of Learn Claude from scratch. The next post in this series covers Free vs Pro vs Max plans.

Sources

• Anthropic / Claude product overview: https://claude.com/product/overview
• Claude plans and pricing (verify current numbers before you buy): https://claude.com/pricing
• Claude download (desktop and mobile entry points): https://claude.com/download
• Anthropic company site: https://www.anthropic.com/
• Claude Platform model and API pricing docs: https://platform.claude.com/docs/en/about-claude/pricing
• Usage limit best practices (session and weekly style limits): https://support.claude.com/en/articles/9797557-usage-limit-best-practices
• Consumer terms of service (age and legal baseline; read the live page): https://www.anthropic.com/legal/consumer-terms
• AMS: What are LLMs, ChatGPT, generative AI, and more: https://analyticsmadesimple.com/analytics/what-are-llms-chatgpt-generative-ai-and-more/
• AMS Practical AI series: https://analyticsmadesimple.com/series/practical-ai/
• AMS: How to check AI-written SQL: https://analyticsmadesimple.com/how-to-check-ai-written-sql/

More definitions in Key Terms →

Merch on Etsy

Open store →

You're On Mute Coffee Mug View on Etsy → Git Version Control Shirt View on Etsy → You're On Mute Coffee Mug – Data Science Gift View on Etsy → Mean Squared Error Shirt View on Etsy →