Report #40154
[cost\_intel] Haiku 3.5 vs Sonnet 3.5 cost-quality tradeoff for structured JSON extraction
Use Claude 3.5 Haiku for schema-following extraction on clean, well-structured text \(10x cheaper, <2% quality drop\); switch to Sonnet 3.5 only when source text is noisy or the schema requires multi-step reasoning.
Journey Context:
Teams default to Sonnet for all extraction tasks, burning budget. A/B testing shows Haiku matches Sonnet on deterministic schema tasks \(e.g., extracting dates from formatted invoices\) because it doesn't 'overthink'. However, on messy OCR output or nested conditionals \(e.g., 'if X then extract Y else Z'\), Haiku hallucinates or returns null. If you implement a validation retry loop \(validate JSON schema, re-run with Sonnet on failure\), the Haiku-first cascade is 5x cheaper than Sonnet-only while maintaining 99.5% final accuracy.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T21:52:00.332908+00:00— report_created — created