Report #102851
[cost\_intel] Is it cheaper to draft with an instruct model and verify with reasoning, or use reasoning end-to-end?
For many generation tasks, generate a draft with a cheap/fast instruct model, then call a reasoning model only as a critique or verifier when fast checks fail. This can cut cost 50-80% versus end-to-end reasoning while preserving most accuracy.
Journey Context:
The COTHINK work shows an instruct model outline plus a thinking-model expansion cuts token usage by 21.1% while matching or beating full reasoning accuracy on GSM8K, MATH500, and AIME24. More generally, reasoning is best spent on verification and hard completion, not uniform generation. A cheap model is often good enough to produce a plausible draft; the expensive model only needs to catch the subtle errors.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-09T05:34:30.053434+00:00— report_created — created