Which Claude model should your business use?
Compare Claude Fable 5.1, Opus 5.5, Sonnet 5.5 and Haiku 5.5, see how DLVX routes Claude, and plan a safe business setup.
A starting point
Anthropic's current Claude API comparison spans four models, while availability in Claude apps, Claude Code and partner platforms varies. This guide explains what changed, how we route Claude alongside other systems, and how to add it to a real business without granting more access than the job needs.
The short answer
Start with the job, not the model name. Anthropic's current API comparison lists four models: Fable 5.1, Opus 5.5, Sonnet 5.5 and Haiku. Anthropic recommends Opus 5.5 for most workloads. In our own use the split looks like this:
- Fable 5.1 for the hardest, longest running work, where a wrong answer is expensive.
- Opus 5.5 as the default when you are unsure.
- Sonnet 5.5 for well scoped, repeated production work, often at lower cost.
- Haiku for fast, simple, high volume tasks such as sorting or tagging.
Access inside the Claude apps, Claude Code and partner platforms depends on your plan and rollout, so check what your own account can use before you plan around a model.
Pick the simplest surface
Use chat or Cowork for one person's knowledge work. Use Claude Code when the task lives in a code repository. Use the API when a repeated workflow needs structured inputs, tools, logging and access rules. Most businesses start in chat and only move to the API once the workflow is stable.
Worked example
A Bangkok property agency wants first replies to Thai and English enquiries drafted faster. This is an illustration, not a client result.
- Collect 20 real past enquiries with the replies that were actually sent. Remove names and phone numbers.
- Run the same 20 through Sonnet 5.5 and Opus 5.5 with the same instructions. Our guide to comparing AI outputs blind explains how to score without knowing which model wrote which draft.
- Score each draft on three questions: does it keep every promise in the policy, does it read naturally in Thai, and would a manager send it with only small edits?
- If Sonnet passes, use Sonnet. If only Opus passes, use Opus and accept the cost. Keep a human approving every reply for the first month.
The result is a decision backed by your own enquiries, not a leaderboard. Re-run the same 20 whenever a new model arrives, keep a way out if a vendor changes terms with an AI vendor exit plan, and compare other model families in Grok, Kimi, Gemini and Codex compared.
The full guide covers the September 2026 changes, three setup patterns, a thirty day rollout and the approval rules we apply before Claude touches any business system.
The current Claude model line
Current lineAnthropic's current comparison page recommends starting most workloads with Opus 5.5, moving to Fable 5.1 for the hardest long-running work, using Sonnet 5.5 when speed and capability need a better balance, and using Haiku 5.5 for the fastest current option. All four accept text and images and return text; their context, thinking controls, output limits, latency and price differ. (Anthropic model overview, checked 4 November 2026)
| Model | Claude API ID | Best starting use | Context and output | API list price per million tokens | Important detail |
|---|---|---|---|---|---|
| Claude Fable 5.1 | claude-fable-5-1 | Demanding reasoning and long-horizon agent work | 1M input context, 128K output | USD 10 input, USD 50 output | Always-on adaptive thinking, high default effort. Public release: 1 September 2026. |
| Claude Opus 5.5 | claude-opus-5-5 | Long-running coding and knowledge work | 1M input context, 128K output | USD 4 input, USD 20 output | Always-on adaptive thinking, medium default effort. Public release: 22 September 2026. |
| Claude Sonnet 5.5 | claude-sonnet-5-5 | Well-scoped production work where speed and cost matter | 1M input context, 128K output | USD 2 input, USD 10 output | Adaptive thinking, fast relative latency. Public release: 28 September 2026. |
| Claude Haiku 5.5 | claude-haiku-5-5 | Fast, high-volume, lower-complexity work | 1M input context, 128K output | From USD 0.10 input, USD 0.50 output | Adaptive thinking, medium default effort, fastest relative latency. Active; retirement not sooner than 7 October 2027. |
Prices above cover Claude API input and output tokens. Prompt caching, Batch API and any separately priced tools use their own published rates. Fable, Opus, Sonnet and Haiku 5.5 all list a June 2026 reliable knowledge cutoff. A large context window also does not supply current facts. Current work still needs search, retrieval or a connected source. (Anthropic model overview) (Anthropic, Sonnet 5.5 pricing details) (Anthropic, training-data recency)
Claude Mythos 5.1 shares Fable 5.1's specifications and pricing but is limited to verified access programmes. It is not part of the normal public choice for most businesses. Haiku 5.5 is now released and active. Claude Haiku 4.5 (claude-haiku-4-5-20251001) is no longer the newest small model, and its deprecations entry lists retirement not sooner than 15 October 2026, so plan to move any workflow still on it. Claude Sonnet 4.5 is deprecated with retirement on 30 November 2026. (Anthropic, model deprecations, checked 4 November 2026) (Anthropic, Fable 5.1 and Mythos 5.1) (Anthropic, Sonnet 5.5 announcement)
Which Claude model fits which job?
Route by jobUse the least expensive model that passes a real task test, then escalate for complexity or risk. Do not choose by job title. One marketer may use Haiku for classification, Sonnet for a first production draft and Opus for a difficult exception. A developer can plan with Opus, implement with Sonnet and use deterministic tests before accepting either result. Anthropic itself describes planning with Opus and executing with Sonnet as a common Claude Code pattern. (Anthropic, models and limits in Claude Code)
| Workflow | Start here | Escalate when | Proof before acceptance |
|---|---|---|---|
| Everyday coding and implementation | Sonnet 5.5 | Use Opus for cross-cutting architecture or difficult debugging. Use Fable for unusually long sessions. | Tests, reviewed diff, security checks and a working build. |
| Ambiguous strategy or architecture | Opus 5.5 | Use Fable if a higher-effort Opus run still fails the task rubric. | Decision record, constraints, counter-case and accountable owner. |
| Large document extraction | Sonnet 5.5 | Use Opus for judgement-heavy synthesis and Fable for long research that must become a finished artefact. | Citations, source checks and sampled extraction accuracy. |
| Research | Opus 5.5 | Use Fable for long multi-step work; use Sonnet for bounded retrieval and synthesis. | Dated primary sources and a separate fact check. |
| Browser or computer work | Sonnet 5.5 for bounded tasks | Use Opus when navigation or exception handling needs more judgement. | Site allowlist, action log and confirmation before consequential writes. |
| Operational routines | Sonnet 5.5 | Use Opus for exceptions and Fable only for the hardest long-running cases. | Allowed-action policy, approval points, replay log and fallback. |
| High-volume triage | Haiku 5.5 | Move edge cases to Sonnet when the eval shows judgement failures. | Sampled human review and an edge-case queue. |
| Quality review | Opus 5.5 | Add a specialist or second provider for contested, high-impact decisions. | Independent rubric. Do not let the same run create and certify the work. |
How we actually use Claude at DLVX
DLVX methodWe do not send every task to Claude, and we do not send every Claude task to the same model. Our working method routes by task. Claude is most useful to us where context, voice, trade-offs and difficult judgement matter. Kimi or Codex can take implementation or long-context work when they fit it better, while separate checks cover facts, code, security and rendered output.
There is an important date boundary. Our internal routing method was last verified in July 2026, before Fable 5.1, Opus 5.5 and Sonnet 5.5 launched. It supports the routing principle, but it does not prove that DLVX benchmarked those September releases or migrated every internal route to a new pinned model. This guide therefore separates current Anthropic product facts from our established operating method.
In practice, we keep four things portable: the source pack, instructions, acceptance test and output format. That lets us change a model without rebuilding the business process. On client work, we also separate research, implementation and review when the consequence warrants it. A strong builder should not be its only judge.
We have built private AI workflows inside wider business systems, but the model name is not the product. The useful part is the controlled connection between source data, the job, permissions and the person responsible for the result. Our work archive documents projects with connected business systems.
Inside this guide: what comes next
- Find the answer you need.
- Claude models and Claude products are different choices
- What changed in September 2026
- Choose the simplest Claude surface that solves the job
- Three practical setup patterns
- A safe thirty-day rollout
- The approval and evidence framework
- Common mistakes
- Five questions businesses ask about Claude
- Download the one-workflow checklist
- Update policy
- Sources
Read the full guide
A free Academy account opens the full guide and practice lessons.
Create a free account Already a member? Sign in
No newsletter subscription. We use your email for sign-in and account messages.