Stop 1 of 6 · Read once
What Claude is, and is not
What is actually behind the chat box, why the first answer was bland, and why a confident answer is not the same as a correct one.
What it is
Lina runs the office for a nine-person engineering firm. Invoices, the shared inbox, proposals, scheduling, the owner's calendar. She opened the free chat once, typed "write a professional email", got something bland, and closed the tab.
That is the normal first experience, and it is not her fault. Claude is not a search box and it is not a button that produces finished work. It is closer to a very fast, very well read assistant who started this morning: excellent with language, blank on your specifics, and willing to guess when it should ask.
The picker at the top
Every chat has a dropdown at the top that chooses which model answers you. A faster model suits a quick rewrite or a two-line reply. A more capable model suits a long document, a contract, or anything with numbers in it. Start on the default. Move up when an answer feels thin, move down when you only want speed. Model names and plan details change, so check claude.com/pricing rather than trusting a number you read somewhere.
Claude only knows what it can see
This one sentence explains most disappointing first answers. Claude cannot open Lina's shared inbox unless she connects it. It cannot read the Henderson proposal unless she uploads it. It does not remember Tuesday's chat on Wednesday unless she is working inside a Project. When the answer is generic, the question usually arrived with nothing attached to it.
It can be confidently wrong
Claude writes a wrong sentence in exactly the same steady tone as a right one. There is no wobble in the voice to warn you. That matters most on the things Lina's firm gets held to: dates, dollar amounts, permit rules, insurance limits, who agreed to what in a meeting.
So the habit is simple. Verify before it leaves your hands. Anything going to a client, the bank or the owner gets one read from you first, and any outside fact gets traced to a source you open yourself.
You can also ask for honesty directly. "If you do not know, say you do not know" is a real instruction, and Claude follows it. An answer that says "I am not sure, here is what I would check" is a good answer, not a failure.
Try this
I run the office for a nine-person engineering firm. I handle invoices, the shared inbox, proposals, scheduling and the owner's calendar. Before we start working together, ask me the five questions you most need answered so you can help me well. Ask them one at a time and wait for my answer before the next one.
Answer the question below. At the end, add two short lists: what you assumed, and what you were not sure about. If you do not know something, say you do not know rather than guessing. [paste your question]