Why most people only use 20% of what Claude can actually do

Open Claude for the first time and you're greeted with a model picker showing names like Haiku, Sonnet, and Opus — and no obvious explanation of which one to pick. Most people just click whatever's selected by default, type a question like they would into a search bar, and never touch a single other feature. That's the equivalent of buying a laptop and only ever using the calculator app.

Claude isn't just a chatbot. It's a workspace, a research assistant, a coding partner, and — if you set it up right — a system that can build entire tools for you. This guide walks through the parts of Claude that actually move the needle: which model to use and when, how Projects and Artifacts change the way you work, and how Claude Code lets you build small automations without hiring a developer.

What's the difference between Haiku, Sonnet, and Opus?

This is the first fork in the road, and it trips up almost everyone. The naming looks arbitrary, but the logic behind it isn't.

Anthropic organizes its models into three tiers built around a simple tradeoff: capability versus speed versus cost. Fable 5 is the most capable, Opus is the flagship for hard reasoning, Sonnet is the everyday balance of smart-and-fast, and Haiku is the cheapest and quickest, with the general logic being that bigger names cost more and think harder while smaller names are faster and cheaper.

For everyday use, the practical rule is simpler than the naming suggests: use Sonnet for everything else — it's the right default the vast majority of the time, with near-Opus quality at a fraction of the cost. Save Opus for the moments that actually justify it — multi-step reasoning, complex code, dense analysis, or anything where a wrong answer is expensive. And if you're doing high-volume, low-stakes work, Haiku is built for classifying or tagging at scale, simple extraction, quick lookups, and high-throughput pipelines where speed and cost matter more than squeezing out the last few points of quality.

The takeaway: stop agonizing over the picker. Default to Sonnet, upgrade to Opus when the stakes are high, and check Anthropic's model overview if you want the full technical comparison including context windows and pricing.

How do you actually get set up properly?

Head to claude.ai and create an account. The free tier gets you a real amount of usage, but two features worth paying for immediately are Projects and higher usage limits on Pro — both of which unlock the workflows below.

Before you type a single prompt, go into Settings and turn on Artifacts and code execution — some of the features covered next won't even trigger without them enabled.

What are Claude Projects and why should you use them?

Here's the problem Projects solves: every new chat starts from zero. You re-explain your brand voice, re-upload your style guide, re-paste the same background information — every single time. Projects fix that by giving you a persistent workspace instead of a disposable conversation.

Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases, and within each project you can upload documents, provide context, and have focused chats with Claude. You set this up once. You can also define project instructions for each project to further tailor Claude's responses — for example, instructing Claude to use a more formal tone or answer questions from the perspective of a specific role or industry.

This isn't a small convenience. Teams that build dedicated projects for recurring work — content briefs, meeting notes, competitive research — report measurable gains. Most users report 30-50% time savings on document-heavy workflows and 20-40% improvements in content consistency after switching from one-off chats to Projects.

Setting one up takes about five minutes:

Open claude.ai on web or desktop and click Projects in the left sidebar
Hit New Project and give it a specific name — something like "Q3 content briefs," not just "Content"
Upload your reference documents to the knowledge base (PDF, DOCX, CSV, TXT, and several other formats are supported)
Add custom instructions describing tone, format, and any rules Claude should always follow

Anthropic's own help center article on Projects covers sharing permissions if you're setting this up for a team, and Anthropic's Projects announcement explains the underlying context window mechanics in more detail.

What are Artifacts and when should you use them?

Here's a habit worth building immediately: every time you catch yourself copying text out of a Claude response to paste into another app, stop and ask whether that content should have been an Artifact instead. Usually, it should have been.

Artifacts allow you to turn ideas into shareable apps, tools, or content by simply describing what you need — Claude can share substantial, standalone content with you in a dedicated window separate from the main conversation, making it easy to work with significant pieces of content that you may want to modify, build upon, or reference later.

The trigger conditions aren't mysterious once you know them. Anthropic's own guidance defines an artifact as content that is "significant and self-contained, typically over 15 lines," "something you're likely to want to edit, iterate on, or reuse outside the conversation," and "content you're likely to want to refer back to or use later."

Practical prompts that reliably produce one:

"Build me a working [X]" — a Pomodoro timer, a budget calculator, a flashcard quiz
"Draft a complete [X]" — a pricing page, a project plan, an API spec
"Show me a diagram of [X]" — almost always produces a clean visual instead of a wall of text

Once an artifact exists, refining it is just normal conversation — say "make the colors darker" or "add error handling" and Claude updates it in place. When you're happy with the result, the Publish button generates a shareable link, and anyone can view and interact with a published artifact without signing up, trying all basic functionality without a Claude account. Full details live in Anthropic's artifacts help center article.

What is Claude Code and who is it actually for?

This is the feature most non-developers skip entirely — which is a mistake, because you don't need to already know how to code to get value from it.

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows, all through natural language commands. In plain terms: you describe what you want in normal sentences, and it writes, runs, and fixes the code itself.

Think about the small, annoying task that nobody's built an app for — watching a folder for new files and logging them to a spreadsheet, renaming a batch of images by content, pulling data from three different sources into one report. There's rarely an off-the-shelf tool for the exact workflow you need, but Claude Code can often build a working script for it in well under an hour.

To get started:

Install Claude Code following the steps in the official quickstart guide
Navigate to a project folder in your terminal and run claude
Log in with your Claude subscription when prompted
Start with something low-risk: ask Claude to analyze your files, and it will provide a summary
Move on to an actual task — describe what you want changed in plain language, and Claude Code always asks for permission before modifying files, so you can approve individual changes or enable "Accept all" mode for a session

The best early habit is specificity. Instead of "fix the bug," Anthropic's own docs recommend something closer to "fix the login bug where users see a blank screen after entering wrong credentials." The more precisely you describe the problem, the less back-and-forth you need.

Which workflow should you build first?

Don't try to overhaul everything at once. Pick one recurring task that currently eats your time — a weekly report, a batch of similar emails, a repetitive data cleanup — and build exactly one system around it:

Create a Project with the background context that task always needs
Set custom instructions so you never have to re-explain tone or format
Use Artifacts for anything you'd otherwise copy-paste into another document
Escalate to Claude Code only once you hit something a chat window genuinely can't do — a script, an automation, a recurring pipeline

Most people compare Claude to a search engine with a personality. Once you've set up even one Project and published one Artifact, that comparison stops making sense — you start seeing it as infrastructure instead. The gap between the 20% of users clicking "New Chat" every time and the ones running persistent, reusable systems isn't talent. It's just five minutes of setup most people never bother to do.