Report #102306
[cost\_intel] When does fine-tuning beat prompting on cost per quality point?
Fine-tune the smallest capable base model for stable, high-volume tasks with 500\+ labeled examples, once the monthly bill for prompting a frontier model exceeds the amortized training and inference cost. A fine-tuned small model typically costs several-fold to an order of magnitude less per inference call than a prompted frontier model and removes the token overhead of long few-shot prompts.
Journey Context:
Prompt engineering wins on iteration speed and multi-task flexibility; fine-tuning wins on token efficiency and unit cost at scale. The crossover depends on training cost, data-labeling cost, and how often distributions drift. Studies on code-review automation show that a small fine-tuned model can close most of the gap to a prompted frontier model for a narrow task. The risks are vendor lock-in, catastrophic forgetting, and the need to retrain when the base model updates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:19:21.421358+00:00— report_created — created