Gemma and Phi-3 made small models feel serious again.
small models get to start the workflow
The shift was not that small models suddenly became magical. It was that the product question around them got sharper.
They started to look like pieces of architecture: a local classifier, a preprocessor, a cheap first pass, a narrow router, a verifier with a small blast radius.
That is the part I care about. A small model is useful when it owns a small job and does not pretend otherwise. The bigger model can stay on the hard reasoning lane.
a route that stays local
I like the local-first version because it gives the system a cheap first pass and a clear escalation path. For a secret-scanning workflow, the model can do this:
result = model.predict_entities(
text=note,
labels=["api_key", "token", "password", "private_key"],
threshold=0.35,
)
if result.confidence < 0.7:
route = "review"
else:
route = "redact"
That kind of setup is interesting because the small model does one thing well and escalates when it is unsure. It is not trying to be a general assistant. It is trying to keep the bigger system calmer.
You can use the same pattern for intake. A small model tags the document, strips obvious secrets, or routes the message to the right queue. The larger model only sees the cleaned result or the hard cases. That is where open weights matter: you can run the model locally, test it on your hardware, and see the memory cost instead of guessing.
The route looks more honest when you write it down:
input: local note under 20 KB
labels: api_key, token, password, private_key
threshold: 0.35
fallback: deterministic scan + human review
route: local first
That makes the role of the model legible. It is one stage with a narrow job and a defined failure path.
Open weights changed the debugging loop too. Once you can run the model locally, measure memory, quantize it, and point it at your actual hardware, the experiment stops feeling like an API demo. It becomes a system choice.
I think of Gemma and Phi as a reminder that size is not the identity. Placement is.
Related posts

About Jeremy London
Engineering leader and builder in Denver. I write about AI platforms, agents, security, reliability, homelab infrastructure, and the parts of engineering work that have to survive production.