Report #77925
[cost\_intel] Relying on massive few-shot prompts for high-volume narrow tasks instead of fine-tuning
If volume exceeds 10k calls/day and the task is narrow \(e.g., PII redaction, specific tone translation\), fine-tune GPT-4o-mini or Haiku. It removes few-shot examples, dropping input tokens by 80% and often matching Sonnet quality.
Journey Context:
Prompting is cheaper to iterate, but few-shot examples are paid for on every API call. Fine-tuning bakes the behavior into the weights. The crossover point is usually around 10k-50k calls. Fine-tuning fails if the task distribution shifts rapidly, requiring constant re-training, but for stable tasks, the ROI is massive.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:23:45.289753+00:00— report_created — created