Claude Model Family Best Practices
Guidelines for choosing and managing which Claude model tier to use, so your team gets the right balance of capability, speed, and cost across everyday work.
//
Search across all documentation pages
Guidelines for choosing and managing which Claude model tier to use, so your team gets the right balance of capability, speed, and cost across everyday work.
Defaulting to Claude Sonnet 5 for everyday work and only deliberately escalating or stepping down when a task's complexity, latency needs, or volume clearly calls for it - most other practices build on that habit.
When the task is ambiguous, multi-step, or requires weighing several factors carefully - not simply because the task feels important or the input is long.
Rarely - Fable 5's premium pricing and always-on adaptive thinking are best reserved for tasks that specifically need maximum context, output length, or reasoning depth, not as a blanket team default.
Because they don't always point to the same tier - a task can be simple but latency-critical (favoring Haiku 4.5), or complex but not time-sensitive (favoring Opus 4.8 or Fable 5); treating them as one dimension leads to the wrong tier choice.
At minimum after any major model launch or pricing change, and periodically otherwise - capability gaps between tiers can narrow over time, as shown by Sonnet 5 edging past Opus 4.8 on some tasks.
Use a mixed-tier pipeline: route simple, high-volume steps to Haiku 4.5, everyday work to Sonnet 5, and only escalate the smaller subset of genuinely hard steps to Opus 4.8 or Fable 5.
Output tokens are priced roughly 4-5x higher than input tokens across every tier, so a workflow's expected output length has an outsized effect on total cost.
Consistently defaulting to the most expensive tier regardless of task, or consistently underpowering genuinely hard tasks on the cheapest tier to save money - both waste resources, just in opposite directions.
In most cases yes, since Haiku 4.5 is specifically tuned for speed, but if the feature also requires nuanced judgment that Haiku's lighter reasoning doesn't reliably deliver, Sonnet 5 may be a better fit despite the latency trade-off.
Because it's a concrete, dated example of how model pricing shifts over a model's lifecycle - a reminder to build budget assumptions that account for known future changes, not just current rates.
Some flexibility is reasonable, but setting a deliberate team-wide default and documenting when to deviate from it avoids the drift and inconsistency that comes from ad hoc, per-person choices.
Stack versions: Written against the Claude model lineup current as of ~June 2026 - Claude Fable 5, Claude Opus 4.8, Claude Sonnet 5 (the default), and Claude Haiku 4.5. Model names, pricing, and product features move quickly - verify current specifics at platform.claude.com/docs before relying on them.
Reviewed by Chris St. John·Last updated Jul 18, 2026