Mapping the Pareto frontier
Every LLM system sits on a tradeoff between cost and quality. Evaluation tells you exactly where on the curve you are — and where you could go.
The Pareto-frontier exercise
- Pick a representative eval set.
- Run the same eval against multiple models / prompts / configurations, capturing both quality (eval pass rate) and cost (per-1k-call dollar cost).
- Plot quality vs cost. Each (model, config) is a point.
- The "Pareto frontier" is the set of configurations where you can't improve quality without increasing cost. Points off the frontier are dominated — strictly worse on both axes.
What the chart usually shows
For most product tasks the curve is steep at the bottom (cheap models barely work, even modest cost increases buy big quality jumps) and flat at the top (frontier models cost 10x more for marginal quality). The right point on the curve is where your product's quality threshold meets the smallest acceptable cost.
Model routing for advanced systems
Don't pick one model for everything. Route easy queries to cheap models, hard queries to expensive ones. A simple router (regex on query length / topic / classifier) plus a quality classifier can reduce inference cost 3-10x while preserving quality. RouteLLM, Martian, and the OpenAI Routing API are the standard tools.