Fable 5, Opus, or Sonnet: which Claude for client work

Revised July 24, 2026. Rewritten after Anthropic settled Fable 5's plan availability (July 20) and shipped Claude Opus 5 (July 24). Earlier versions of this article tracked a deadline that moved three times; that stretch is over and the picker is stable again. The revision history is kept with the article's source.

For six weeks the honest answer to "which Claude model should I use" was wait, it'll change again. It changed four times. It's now settled, and the settled version has a twist worth knowing before you read the rest of this: which model sits at the top of your picker depends on which plan you pay for.

Two things happened in the same week. On July 20, Anthropic made Fable 5 a permanent part of Max plans — up to half your weekly usage at no extra charge — while Pro and Team-standard seats reach it only through pay-as-you-go usage credits. Four days later, Claude Opus 5 arrived as the default model on Max and the strongest model available on Pro.

So the picker is a real decision again, but not the one it was in June. Most of the content answering "Opus 5 vs Fable 5" is written for developers: benchmark charts, per-token prices, context-window trivia. None of it tells you which model should write Friday's client update. Here's the consultant version. One rule, then defaults, task by task.

What's actually in the picker

Skip the spec sheets. Here's the working translation.

Fable 5 is Anthropic's most capable model — a tier above the Opus line. Its differentiating strength is long, multi-step work: it holds an entire deliverable coherent from start to finish instead of drifting in the middle, and it reasons before it answers, every time. The trade is time — hard asks take noticeably longer, because the model is doing more before it speaks. Whether it's in your picker at all now depends on your plan (see the dated block below). We covered what the top tier changes for consulting work; this piece is about when to choose it.

Opus 5 is the new arrival and, for most consultants, the one that matters. Anthropic describes it as coming close to Fable 5's frontier intelligence at half the price, and it ships as the default model on Max and the strongest model available on Pro. Strong judgment, strong writing, fast enough for genuinely interactive work. It also has an adjustable effort setting — more on that below, because it's the most useful new lever in the picker.

Sonnet is the speed-and-intelligence balance: noticeably snappier in conversation, and more than smart enough for work whose shape you already know.

If your picker shows a lighter option such as Haiku, file it under instant answers — lookups, quick transformations, "make this a bullet list." Most consultants will rarely choose it deliberately, and that's fine.

Which of those you can actually reach is the one thing here that depends on what you pay, so it gets its own dated block — and it is the only paragraph in this article that names a plan:

As of July 24, 2026. Fable 5 is a standard part of Max plans (and premium Team/Enterprise seats), usable for up to half your weekly limits at no extra charge; past that you continue on usage credits or switch models. On Pro and standard Team seats it isn't included at all — reaching it means pay-as-you-go usage credits on top of your plan. On Free it isn't available. Opus 5 is the default on Max and the strongest model available on Pro. Anthropic's own plan page is the authority — check it before acting on this paragraph, because this is the fifth time the answer has changed since June.

Two practical notes before the rule. First, cost: the models in your picker draw on the subscription you already pay for, plans meter that usage, and the bigger models draw the allowance down faster. Spending your top model on a subject line is paying caviar prices for toast. Second, names: Anthropic ships new versions on its own schedule, and the labels keep changing — this article has been rewritten twice for exactly that reason. The tiers persist: a top model for the hardest work, a strong default, a fast one. Learn the tiers and the rule below survives every release. That's the narrow version of a broader point we've made about not building your practice on one model, which this summer tested about as thoroughly as anyone could ask.

The rule: match the model to the leash

Forget capability rankings. The question that actually picks the model is this: how long is the leash on this task, and what does wrong cost you?

Leash length is how much work you hand over between check-ins. A subject-line rewrite is a ten-second leash — you see the output immediately, a miss costs nothing, you iterate without thinking about it. A "here's the transcript, my services file, and my rate floor — draft the proposal" run is a long leash: the model works through many steps before you see anything, and a failure in the middle compounds quietly until the end.

Put those two on the same model and you've made an error in one direction or the other.

The second half of the rule — what wrong costs — decides the borderline cases. Cheap wrongness gets caught for free: you were reading the output anyway, and the fix is one more message. Expensive wrongness is the kind that survives your review because the artifact looks finished — a proposal with a plausible-but-off price, a case study citing a detail the client never said. The polish of a long-run output is camouflage. The more finished a draft looks, the stronger the model you should have used to make it, and the harder your read should be before it leaves your desk.

Short leash, low stakes → the fast model. You're in a tight loop. Latency is the dominant cost, and you personally inspect every output anyway. Depth has nowhere to earn its keep.

Medium leash, judgment-gated → the strong model you steer. The work happens in stages and your judgment gates each one — scope before price, price before draft. You want maximum sharpness per stage and a loop fast enough not to break your momentum between them.

Long leash, whole deliverable → the strongest model you can reach. Delegation runs reward the model that can hold the entire job in its head — and the middle of a long run is exactly where weaker models used to drift. This is the one row where the plan question actually bites, and where Fable 5 earns its slot if you have it.

Concrete contrast: the Friday client update is a short-leash task wearing business clothes — known shape, your inputs, your proofread before it sends. The proposal built from a discovery transcript is a long-leash task wearing the same clothes — a dozen quiet decisions about scope, sequence, and emphasis happen between your brief and the draft. Same client, same week, opposite ends of the picker.

That's the whole rule. Everything below is the rule applied.

Task by task

Default assignments for the recurring work of a solo practice. Adjust to your taste — the point is to have defaults instead of re-deciding at every blank conversation.

The column that matters is the tier, not the model name — names change every few months and this table shouldn't.

As of today those tiers read: Sonnet fast, Opus 5 the strong default, and Fable 5 the top tier — if your plan includes it, per the block above. Names change; open your own picker rather than trusting the ones printed in any article, including this one. When they change again, which model you get on which plan is the page we update first — the tiers in the table above are what actually survive the renames.

Three patterns worth noticing. Everything routine routes to the fast tier. Everything judgment-steered routes to the strong default. Everything delegated-whole routes to the top tier you can reach — which is the one row where your plan decides for you. When a task doesn't fit a row, ask the leash question and it sorts itself.

The effort setting is the new lever, and it maps onto the leash rule exactly. Opus 5 lets you dial how much work the model does before it answers. Short leash, low stakes: leave it low and enjoy the speed. Long leash, expensive wrongness: turn it up and let it verify itself. The practical effect is that the gap between "the strong default" and "the top model" narrowed for most consulting work — a well-briefed Opus 5 run at high effort covers the deliverable work that used to require reaching for the tier above.

The Friday-update default surprises people — surely the better model writes the better update? Marginally, maybe. But a good weekly update comes from its shape and its inputs, not from model depth, and you proofread it regardless. Save the depth for where wrongness is expensive.

The proposal row is the one that actually moved this summer. A year ago the proposal was a steered task — you chained the stages because no model could be trusted with the whole thing at once. With models built for long runs, it becomes a delegated task for consultants who can write a complete brief: objective, inputs, constraints, what done looks like. If your handoffs aren't that complete yet, keep steering — a long leash on a vague brief just produces a longer wrong document, and no amount of effort setting fixes a missing rate floor.

And the discovery debrief deserves its own note, because it's the highest-stakes steered task on the list: what you extract from that call feeds the scope, the price, and the proposal that follows. If you want a tested starting point rather than a blank page, our free Discovery Debrief is a single-prompt workflow with a Claude skill and a worked example — it runs the same whichever model you pick, and it costs nothing.

When the top model is the wrong choice

Reaching for the most capable model available deserves a section of honest no.

When you need the loop, not the leash. Interactive drafting — reacting line by line, talking a document into shape — wants the fastest model that's good enough. Deeper reasoning shows up as wait time, and waiting breaks the rhythm of steered work. A brilliant answer ninety seconds late is a worse partner than a very good answer now. This is also what the effort setting is for: turn it down rather than switching models.

When the shape is known. A weekly update, a meeting recap, an invoice reminder: structure plus your inputs solves the task. Extra capability has nowhere to go, so you're paying its costs — time, usage — for nothing.

When you're rationing usage. Heavy top-tier runs draw down plan allowances faster than the smaller models do, and where the top tier is included at all it is capped rather than unlimited. If month-end finds you bumping into limits, audit whether routine tasks crept up-model out of habit. They usually have.

When it isn't in your plan — which is most readers. If reaching the top tier means buying usage credits, then every long run is a line item you chose, and that is a perfectly workable way to operate: keep the plan-included model as your default and spend deliberately on the one deliverable a month that genuinely warrants it. What you should not do is treat a credit balance as a general-purpose upgrade — the leash rule still says most of your week belongs on the fast tier and the strong default. Whether the jump is worth changing plans over comes down to your billing rate rather than any benchmark — the dated block above and your own picker are the only inputs that decision needs.

One footnote so it doesn't surprise you: the top-tier models ship with safety classifiers around a handful of research-heavy topics — security research, biology — and Anthropic says fewer than five percent of sessions ever encounter them. Consulting work essentially never goes near the triggers. If a conversation ever behaves oddly, the companion piece covers the practical response: fresh conversation, plainer ask, move on.

Set your defaults this week

Three moves now, one for the calendar. None longer than a coffee.

Write the defaults down. List your five most frequent Claude tasks. Assign each a tier from the table above, then write today's model name next to it. Put the list somewhere you'll see it. The win isn't the assignments — it's never re-deciding at a blank conversation again.

Run one honest A/B. Take a deliverable you produce regularly. Same inputs, same brief, two models — your current habit and the table's recommendation. Read both drafts cold and pick the one you'd actually send. That's your evidence, from your practice, not a stranger's benchmark screenshot. If you want a ready-made deliverable to run it on rather than improvising one, our free Friday Update Brief is a complete handoff with a sample week of notes and a reference output — it costs an email address, and it makes the comparison honest because both runs work from identical inputs.

Re-route the routine work down. If everything has been running on the biggest available model out of habit, move the known-shape tasks to the fast tier for a week. You'll notice the speed immediately, you almost certainly won't notice a quality drop, and the usage headroom comes back for the long runs that genuinely need it.

And the calendar one: put an expiry on your defaults. Models change under you, and assignments go stale quietly — the table above would have read differently a month ago and may read differently by fall. When the next release lands, re-run the A/B on your highest-stakes task before believing anyone's writeup, including this one. Ten minutes, evidence refreshed.

The deeper question underneath all of this — which work to hand over at all, and which work stays yours no matter how capable the models get — doesn't change with the picker. That's the operating frame of The Solo Consultant's AI Playbook, and it's deliberately model-agnostic. Pick the model per task. Keep the judgment on retainer.