What Claude Is (and Isn't)
The one-sentence version
Claude is a language model: a very capable text tool that predicts useful responses based on patterns in an enormous amount of human writing. It is not magic, not a search engine, and not always right.
What Claude actually does under the hood
You do not need to understand the maths, but this mental model helps. Claude was trained on billions of pages of text — books, articles, code, conversations — and learned the patterns in that writing. When you ask it something, it generates a response by predicting what useful, relevant text should follow your words.
This means Claude is extraordinarily good at tasks that are fundamentally about language: drafting, summarising, explaining, translating, restructuring, brainstorming. It has absorbed enormous amounts of human knowledge and can draw on it fluidly.
It also means Claude has no direct connection to the world. It does not go out and check things. It does not remember your last conversation. It is working entirely from what it learned during training and what you tell it in the current conversation.
What Claude is good at
- Drafting: emails, reports, presentations, proposals, job descriptions — anything that starts as a blank page
- Summarising: long documents, meeting notes, research papers → concise, structured summaries
- Explaining: complex topics in plain language, tailored to a specific audience
- Brainstorming: generating options, alternatives, angles you might not have considered
- First-pass analysis: reading a document and flagging key points, risks, or inconsistencies
- Restructuring: taking rough notes or bullet points and turning them into a coherent document
- Coding assistance: writing, reviewing, and explaining code — useful even if you are not technical
What Claude is NOT
Not a search engine. Claude does not browse the internet when you ask it a question. Its knowledge has a training cutoff date, and it cannot look up current prices, recent news, live regulations, or anything that changes over time. For current information, verify from a live source.
Not a database with memory. When you close a conversation and start a new one, Claude remembers nothing. Every conversation starts fresh. If context matters — "as we discussed last week" — you need to re-provide it. (Your company's Projects feature partly addresses this for shared team contexts, but individual conversation memory does not persist.)
Not infallible. Claude can be confidently wrong. It will state incorrect facts, cite sources that do not exist, or apply rules incorrectly — without any sign that it is uncertain. This is not a bug being fixed; it is a fundamental property of how language models work. You cannot tell from the tone of the output whether it is right.
The brilliant intern mental model
The most useful way to think about Claude: imagine a very capable intern on their first week. They are:
- Fast and willing — they will attempt anything you ask
- Broadly knowledgeable — they have read a lot and can speak intelligently on most topics
- Not reliable on specifics — they can get details wrong without knowing they have
- Only as good as your instructions — vague requests produce vague outputs
- In need of review — you would not send a first-week intern's work to a client without reading it
You would use that intern enthusiastically for drafting, research and first-pass work. You would not ask them for the definitive legal position on a case and send it straight to the client.
Use Claude the same way.
Scenario: good use vs. bad use
Bad use: A manager pastes a supplier contract into Claude and asks: "Does this comply with our standard terms?" Claude responds with a confident yes/no and cites a few clauses. The manager sends the contract back to the supplier with a sign-off. Two weeks later, legal points out that a key liability clause was non-standard and Claude missed it.
What went wrong: Claude performed a first-pass review, which is useful. Treating that first-pass review as a final legal opinion, without human verification, is the error.
Good use: The same manager pastes the contract and asks: "Summarise the key payment, liability and termination terms. Flag anything that looks unusual compared to standard commercial contracts." Claude produces a useful summary and highlights three clauses worth reviewing. The manager sends this summary to their legal contact with the note: "Claude flagged these three — can you confirm they are acceptable?" Legal reviews in 10 minutes rather than an hour.
Claude did the first pass. A human made the call.
Key takeaway
Claude is a powerful first-pass tool, not a final authority. Treat its output as a capable draft that needs a human review before it becomes a decision or goes outside the organisation. Use it freely; verify it before acting on it.
📖 Official Documentation See this in practice in Anthropic's live support docs: