A practical guide to the models, your usage, and the habits that make Claude go further.
This is a short, practical guide — not a deep technical talk. By the end you'll know which Claude model to pick, why some habits use up your access faster than others, and a few simple changes that let you get more done before you ever hit a limit. Everything here reflects our Claude Team plan — what you'll actually see when you log in.
There are a few, built for different kinds of work. We'll cover what each one is actually good at.
A simple rule of thumb makes the choice easy once you know it.
A handful of everyday habits dramatically change how much you can get done before you hit a limit.
Your Team plan gives you a usage budget that refills automatically. Two limits work together to govern it. You rarely need to track the numbers; you just need to know what spends the budget faster.
A short window that resets frequently.
A larger cap that resets once a week, on top of the rolling window.
There's no fixed number — it varies by seat type and model, and it shifts over time. If someone asks "exactly how much do I get?", don't guess: check your real, current standing in Settings → Usage. Source: Anthropic Help Center — support.claude.com
Our organization has usage credits turned on. That makes the distinction below specific to us: your allowance is already paid for, but once it runs out, the company starts paying real money for continued use — and you won't feel any difference while you're working. That's exactly why the habits in this guide matter.
You won't see or feel the difference while chatting — it looks exactly the same whether you're on your free allowance or spending credits. The habits below keep you inside the free allowance longer, before the company is paying real money without anyone realizing it.
Three models, three jobs. You wouldn't take the truck to grab milk. Match the vehicle to the trip.
Fast answers and simple tasks — quick questions, short summaries, tidying text. Easiest on your budget.
Strong all-rounder for most work — writing, analysis, email, research. Default to this for almost everything.
Most capable for genuinely complex work. The most powerful of the three — and it uses your budget the fastest.
| When the task is… | Reach for |
|---|---|
| Quick question, short summary, cleaning up text | 🚲Haiku 4.5 |
| Everyday writing, analysis, email, research | 🚗Sonnet 5 (default) |
| Complex reasoning, long documents, tricky problems | 🚛Opus 4.8 |
Heavier model = faster budget burn. Defaulting to Opus "just in case" quietly eats your weekly allowance. Start with Sonnet; step up to Opus deliberately, only when you truly need it.
There's a fourth model in the picker called Fable 5, and yes, it's switched on for us. It's Anthropic's most powerful model — but it's a specialist tool for enormous, multi-day, hands-off projects, not day-to-day chat.
Fable 5 draws on paid usage credits, not your normal plan allowance — so casual use runs up real cost.
For ordinary tasks, Sonnet or Opus are just as good.
For certain subjects (security, science), Fable 5 hands the answer to Opus instead — and you'll be told when that happens.
Its strength is huge, multi-day projects that run with little supervision — not quick chats.
Default to Sonnet or Opus. Use Fable 5 only for approved, large-scale work — check with your manager or admin first.
This is the single most useful habit. Every message you send makes Claude re-read the entire conversation so far — so the longer a single chat gets, the more each new reply costs, and the sooner you hit the limit.
People tend to keep one giant chat open all day and pour every unrelated task into it. By message twenty, each reply is dragging nineteen messages of history along, every time. The fix is trivial: when you switch to a new, unrelated task, start a new chat.
"One task, one chat" does not mean firing off ten one-line messages. Each of those is a full round-trip that re-reads the history. Group related questions into one clear message instead.
…six tiny back-and-forth messages, each re-reading everything above it.
One message. All the context. Fewer round-trips.
Rule of thumb: new chat when the task changes; one rich message within a task.
On the Team plan, Projects are shared. Think of a Project as a shared workspace with its own documents and instructions. Upload the documents your team reuses once — they're cached, so referencing them again doesn't keep spending your budget.
Everyone works from the same context — no more inconsistent background.
Reused content doesn't re-charge your usage each time Claude refers back to it.
No more dropping the same three-page brief into every new chat.
For anything recurring — a style guide, a report format, reference docs — put it in a shared Project once and point everyone at it.
A Word doc or PDF looks like plain text to you, but underneath it's dense markup — headings, styles, and formatting metadata wrapped around your actual words. Claude has to read all of it. Plain text or Markdown carries almost none of that overhead.
<?xml version="1.0"?> <w:document xmlns:w="..."> <w:body><w:p><w:pPr> <w:pStyle w:val="Heading1"/> </w:pPr><w:r><w:rPr><w:b/> <w:sz w:val="32"/></w:rPr> <w:t>Q3 Highlights</w:t> </w:r></w:p>... </w:document>
# Q3 Highlights Revenue grew **12%** over last quarter.
Rule of thumb: for anything Claude will read again and again, store it as plain text or Markdown. But don't pre-convert everything — the conversion itself spends tokens, so it only pays off for documents you'll genuinely reuse. The numbers above are illustrative; the real ratio depends on the document, but the direction is always the same.
None of these are dramatic on their own — together they add up.
Great for hard problems, overkill for routine asks. Leave it off unless a task really needs deep reasoning.
Clear context now means fewer clarifying round-trips later.
Don't dump huge files you won't actually use — a big attachment costs you even if you barely reference it.
Pull up earlier context instead of re-pasting a wall of text.
"New task, new chat" and "default to Sonnet" alone will get you most of the benefit. Bookmark this page.
Check your usage anytime under Settings → Usage. Questions about the Team plan? Ask your Claude admin. Pick one habit from the cheat sheet and try it this week.