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 is Part 1 of Learn Claude from scratch. No ranking wars. No “this will change everything” fog. Just enough structure that the rest of the series has somewhere to hang.
What you’ll learn
- How to separate Anthropic (company), Claude models (engines), and Claude products (where you actually click)
- What Claude tends to be useful for at work, and where it fails loudly
- How people access Claude on web, desktop, and mobile (light tour only)
- What model names like Haiku, Sonnet, Opus, and Fable mean in plain English
- How Claude relates to ChatGPT and Gemini without a fan-club fight
- Common first-week mistakes, plus a short practice you can finish today
If you want the broader vocabulary first (LLM, generative AI, why these systems predict text), 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 layers: company, model, product
When someone says “Claude,” they might mean any of three stacked things. Mixing them is how office chat gets confusing fast.
Layer 1: the company. Anthropic builds Claude. Anthropic is 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 partners) ship.
Layer 2: the models. A model is the trained system that turns your words (and sometimes images or files) into a response. Model families get names and version numbers. As of writing, consumer and platform docs talk about names such as Haiku 4.5, Sonnet 5, Opus 5, and Fable 5. Names and generations change. Treat the labels as map pins, not eternal brands.
Layer 3: the products and surfaces. These are the places you actually open: 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. Same family name. Different doors.
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.
Also: liability stays with humans. Claude is not a source of 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 and the products built around them. You type (or speak, or upload), and Claude generates a response based on patterns learned during training plus whatever context you give 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 surface supports tools. It is software that predicts useful next text under guardrails and product limits. It is not a person, a database of your private company facts, or a magic truth machine.
That map is enough to start. The rest of this post fills in “good at,” “bad at,” “how people open it,” and “how it sits next to other AI assistants.”
What Claude is good at
Think in jobs, not vibes. Here are jobs where a careful human plus Claude usually beats a careful human alone.
Turning rough notes into readable drafts
Meeting notes, bullet lists from a whiteboard, a half-finished email you hate. Claude is strong at structure: outlines, subject lines, section headers, and tone shifts (“make this firmer but not rude”). You still need to check names, dates, and claims. The win is speed from mess to first readable draft.
Explaining dense material in plainer language
Policy PDFs, vendor docs, error logs, academic abstracts. Ask for a summary for a specific audience (“for 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 live 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. 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, regex, and “why is this query wrong” conversations. That is useful. It is also where overtrust hurts. If you use AI-written SQL in production, treat it like code from a junior colleague: read it, run it on a safe sample, check joins and filters. We keep a practical habit guide on how to check AI-written SQL for that exact reason.
Long-context work when the product allows it
Paste or attach a long report and ask for themes, 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 skill is not “dump everything.” The skill is packaging context so the model sees what matters.
Role-play for practice, not for truth
“Interview me as a skeptical CFO.” “Red-team this launch plan.” Role-play is a gym. It is not a substitute for talking to the real CFO.
Notice what these share: Claude shines when the output is revisable and you can verify it. Drafts, explanations, options, code samples you will test. Weak when the output must be an authoritative fact you cannot check.
What Claude is not
Clear boundaries save embarrassment.
- Not a source of record. Do not cite Claude as the origin of revenue, headcount, clinical results, or legal interpretation. Cite systems of record, contracts, and humans with authority.
- Not your company’s memory by default. Unless you connect approved systems and follow policy, Claude does not “know” last quarter’s closed pipeline. It may invent plausible-sounding numbers if you pressure it to sound sure.
- Not a person. It has no ongoing life between sessions beyond what the product stores as chat history, memory features, or project files. Warm tone is design and training, not friendship.
- Not always up to date. Training cutoffs and product tools (like web search when available) matter. 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. Later in this series we cover 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. You supply the accountability.
How people access Claude (light tour)
You do not need every surface on day one. Know the doors so later posts do not surprise you.
Web: claude.ai
Most people start here. Create an account, open a chat, type. Free and paid plans both live in this world (with different limits and features). Browser access 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. 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. Awkward for long file work. Same account ecosystem as web for many features, subject to plan and app version.
Specialized products (names, not deep tutorials)
Paid consumer plans often unlock more than plain chat. As of writing, Pro-tier marketing highlights tools such as Claude Code (coding-oriented workflows, including terminal-style work), Claude Cowork (agent-style computer work depending on product definition that month), Claude Design, Claude Science, Research-style features, Projects, and a Microsoft 365 path. Exact packaging changes. Part 2 of this series covers Free vs Pro vs Max. Later series parts map each specialized product without forcing you to buy everything on day one.
API and Console (separate from “I just chat”)
If you build apps, you may use the Claude API through Anthropic’s developer Console (or cloud partners). That is a different billing and auth story from a personal claude.ai subscription. Mixing them in your head is a classic confusion. Part 2 calls this out again when plans and usage come up.
Age and account basics
Claude consumer products are for users 18 and older (confirm current terms when you sign up). Work accounts may sit under Team or Enterprise with 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 UIs often let you pick a model or default one for you. Think of models as different engines in the same brand garage.
As of writing (mid-2026), 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: the most capable widely released tier in Anthropic’s lineup, aimed at long-running agent-style work. Availability and plan access can differ; treat it as a distinct model tier, not a synonym for Opus.
- Mythos 5: a limited-availability sibling of Fable 5 in the same capability class, offered through a restricted program rather than the normal chat menu. Listed here only so the name is not a mystery if you see it.
Older generation numbers (4.5, 4.6, 4.8, and so on) 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. The skill that lasts is: know you are choosing a capability and cost tradeoff, not a personality cult.
Claude, ChatGPT, and Gemini: siblings, not twins
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, get generated text (and increasingly tools: code execution, browsing, file creation). All can hallucinate. All need human review for high-stakes work. All sit behind accounts, plans, and usage limits.
Different companies and ecosystems. Claude comes from Anthropic. ChatGPT comes from OpenAI. Gemini comes from Google. Ecosystems matter: 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. Those strengths move. 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 (“does this email sound passive-aggressive?”). Switching every day because Twitter said a new model dropped is a great way to learn nothing about prompting and everything about FOMO.
This series teaches Claude specifically. The same verification habits apply everywhere: check numbers, check SQL, check citations, keep secrets out of the box.
A small table of “when someone says Claude…”
Use this as a decoding key in meetings.
| They say | They might mean | What to ask |
|---|---|---|
| “Put it in Claude” | claude.ai chat | Work account or personal? Any data rules? |
| “Claude wrote the SQL” | A model draft in chat or Claude Code | Who reviewed joins and filters? |
| “We’re on Claude” | Company contract / Team / Enterprise | SSO? Retention? Which products enabled? |
| “Call the Claude API” | Developer Console / app integration | Whose API key and budget? |
| “Switch to Opus” | A specific model tier | Does our plan include it, and is the task hard enough to care? |
Common mistakes in week one
- Treating fluent answers as true. Fluency is the product. Truth is your job. Ask for sources, then open the sources. 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. Reply with “shorter,” “more skeptical,” “add a table of assumptions,” “list what you are unsure about.” 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. Part 2 explains Free, Pro, and Max without FOMO cosplay.
- Assuming one brand must win forever. Tools change. Your verification habits and data hygiene transfer.
- 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 answers in a notes app, not only in your head.
- Map the three layers on paper: company name, two model names you have heard, two product surfaces you might use. If you cannot fill two of each, re-read the layers section.
- Open claude.ai (or your company Claude portal). Start a new chat. Paste a non-sensitive paragraph you wrote last week. Ask: “Rewrite for a busy manager in 120 words. Keep all numbers exactly. Flag anything that looks like a claim without evidence.”
- Stress-test honesty. Ask: “What might be wrong or incomplete in your rewrite?” Read the answer. Notice whether you still want to paste the draft into email unchanged.
- Name one off-limits category for your job (for example customer phone numbers, unpublished revenue, passwords). Write it as a personal rule.
- Schedule Part 2 before you upgrade anything. Plans make more sense once you know what you actually open every day.
Optional stretch: take a short SQL snippet you understand and ask Claude to explain it line by line, then to propose a change. 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 Learn Claude from scratch, “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.
Recap checklist
- Separate Anthropic (company), Claude models (engines), and Claude products (where you click).
- Claude is strong at drafts, explanations, options, and revisable technical help. Weak as a source of record.
- 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. Names change.
- ChatGPT and Gemini are sibling tools in the same broad category, not identical products.
- You are 18+ for consumer terms as of current Anthropic rules; work use may require a company plan.
- Liability stays with humans. Verify numbers, SQL, and anything that ships.
- Next up in this series: Free vs Pro vs Max, what you actually get, without upgrade panic.
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/tutorials/how-to-check-ai-written-sql/
