Bigger model β better results. The structure of your harness can matter more than the strength of your model.
Here’s a model selection pattern from Anthropic’s developer conference that makes this concrete. A small, fast model β Sonnet or Haiku β does all the execution. A larger, more capable model sits in the tools array, available to be called when the executor gets stuck. This is the advisor pattern: the powerful model is consulted, not driving.
A live demo at Code with Claude London showed what this unlocks. Eve Legal had a legal document analysis pipeline running on Opus alone: roughly Β£110 per run. They restructured: Sonnet executes, Opus sits in the tools array, called only on hard cases. New cost: Β£11. Ten times cheaper β and Opus still caught everything it would have caught before.
Another finding from the same conference: a three-prompt loop on Sonnet (generate β evaluate β repair) beat Opus with adaptive thinking on tokens, latency, and pass rate. Cheaper, faster, better.
The practical takeaway: before reaching for a bigger model, ask if a smarter workflow with a smaller model gets you there. And as billing becomes more usage-based (see tip #41 on tracking AI costs), the economics of this are only getting sharper.
Note: This pays off most on repeatable tasks β document review, code generation loops, CI checks β where you can measure cost per run and tune model choice against outcome quality. One run on Opus can tell you if Sonnet can handle it. If it can, every subsequent run is cheaper.
π‘ Try this: If you have a complex agent task that you run repeatedly and it feels expensive, try adding a “review” step using a stronger model as a tool call β rather than running the whole pipeline on the strong model. Measure the difference over a few runs before committing to either approach.
π Code with Claude London β advisor pattern demo
π Eve Legal case study
How do you choose models for agent tasks?
π’ Match the model to the task complexity
π‘ Haven’t thought about it, I use whatever the tool defaults to
π΄ Always use the best model available
βͺ I rarely do things the same way twice
Tried the advisor pattern? Share what you found π§΅