Problem
Companies typically evaluate models based on visible intelligence: reasoning, writing, vision, coding, or precision. But when an organization starts deploying agents in real workflows, another tougher variable emerges: the cost of waiting.
A model can be excellent and still be useless for an operation that requires fast cycles, many calls, continuous feedback, and controlled cost.
Thesis
Gemini 3.5 Flash matters because it shifts the conversation from “most capable model” to “model capable of acting at scale.” Latency stops being a technical metric and becomes a strategic decision: which tasks can be delegated, which agents can be sustained, and which workflows can operate without breaking margins.
The future of model routing won’t be about choosing the most intelligent model. It will be about choosing a model that’s reliable enough for each decision, at a cost and speed the system can govern.
Framework
In an agent-based operating model, the model is evaluated by four tensions:
- Quality: can make or prepare decisions with sound judgment.
- Speed: can complete cycles within real operational time.
- Cost: can be executed many times without destroying margins.
- Supervision: can sustain logs, scaling, and evaluation without excessive friction.
Mini-case: a finance agent reviews invoices, detects anomalies, and proposes actions. If it uses a slow and expensive model for every micro-decision, the initiative seems brilliant in pilot but absurd in production. If it uses a fast model for triage and reserves more expensive models for exceptions, the system starts to achieve operational economy.
Measurable signal: cost per accepted decision, not cost per token or cost per prompt.
Posture: latency is a business policy when the workflow depends on agents.
Breathing: not everything needs the strongest model. Everything needs the right model at the right point.
The New Routing Question
Before: which model responds better.
Now: which model allows the system to decide better without triggering cost, wait, or rework.
This shift forces designing routes:
- fast model for classification
- strong model for ambiguous cases
- specialized agent for repeatable action
- human for high-risk exceptions
Common Error
The anti-example is using a single “premium” model for everything. It seems safe, but often introduces latency, cost, and false confidence. It also blocks learning: if everything goes through the same model, you don’t know where the real bottleneck is.
An expensive model doesn’t replace a decision architecture.
Protocol (3 steps)
- Classify decisions by risk and frequency. Frequent and reversible decisions need economy; rare and critical decisions need depth.
- Define routes by threshold. Triage, normal decision, exception, human escalation.
- Measure cost by outcome. Accepted decision, avoided rework, saved time, reversed error.
| Task type | Ideal model | Design risk |
|---|---|---|
| Mass triage | fast and cheap | low filter quality |
| Ambiguous decision | stronger | excessive latency |
| Repeatable action | stable and auditable | lack of rollback |
| Critical exception | human + model | late scaling |
Related
- Model Routing as Governance: model politics, not intuition
- AI Evaluation Stack 2026: measuring without theater
- AI Budget Allocation: investing in use cases vs infrastructure
Sources consulted
- Gemini 3.5: frontier intelligence with action
- Google I/O 2026: News and announcements
- Google unveils Gemini 3.5 models focused on agentic work
Next step
If your AI strategy still chooses models based on intuition or prestige, you’re going to overpay and underlearn. Start by mapping decisions and routes. We can do this in a diagnostic.
Translated from the Spanish original with AI assistance and reviewed for accuracy. Read the original in Spanish.