Where Google and open-weight models fits on a long engagement.

The most useful property of open weights is the size range. Many production tasks — classification, extraction, routing, summarisation of short text — are handled well by a small model that runs cheaply, and using a frontier model for them is paying substantially more for capability the task does not need.

Licensing needs reading rather than assuming. "Open weights" covers a range from genuinely permissive to licences with usage restrictions, scale thresholds or field-of-use limits. A model chosen without checking can become a commercial problem well after it is embedded in a product.

What an assigned team does with Google and open-weight models.

Model selection should be empirical. A small model evaluated on the actual task frequently matches a much larger one at a fraction of the cost and latency, and that comparison takes days rather than the weeks teams assume.

Running that evaluation properly, rather than defaulting to the largest available, is part of what AI capacity is for under ai engineering services.

What we use Google and open-weight models for.

  • Small models for bounded tasks Classification and extraction handled at a fraction of frontier-model cost.
  • Licences checked before adoption Usage restrictions understood, because they are a commercial problem once embedded.
  • On-device and edge inference Models small enough to run where no connection or no data egress is permitted.

How Google and open-weight models capacity is assigned.

Model evaluation is assigned as explicit scope, with size matched to the task by measurement rather than by defaulting to the largest option.

Tell us what your roadmap needs Google and open-weight models for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

Loading the contact form… You can also email hello@azendo.co.

We reply within one working day. No obligation, and no newsletter.