Route by quality need, not by habit.

Start with evals that match real workflows, not generic benchmark scores.

Keep hard, high-risk tasks on stronger models until there is evidence to move them.

Route simple, repetitive, and structured tasks to cheaper models or cached paths.

Track quality, latency, and cost together so savings do not hide regressions.