Client: Pix2Code · Partner: BlueBear · Business problem: Get more value from AI spending without lowering the quality of customer-facing work
If your AI bill is growing, the problem may be how work is assigned
Many businesses begin with one strong AI model connected to every workflow. It is simple, it works, and it helps the team move quickly. Then usage grows. More employees use AI, more customer experiences depend on it, and the monthly bill starts climbing.
The natural response is often to negotiate a lower price or switch to a cheaper model. But that misses the larger opportunity. The real question is: does every task need the same level of intelligence, speed, and cost?
Usually, it does not. Summarizing a short document is different from planning a complex project. Extracting a few structured fields is different from analyzing video frames. A routine background job should not automatically receive the same expensive model as a high-value, customer-facing decision.
Model routing is work assignment for AI
Think of model routing the way an operations leader thinks about assigning work to a team. You would not give every task to the most senior, expensive specialist. You would match the work to the person with the right skills, availability, speed, and cost.
BlueBear's software applies that operating principle to AI. For each request, it can consider:
- What kind of work is this? Planning, extraction, visual analysis, generation, coding, or a routine background task.
- What capabilities are required? For example, understanding images, handling a long history, using tools, or returning a precise format.
- What matters most here? Highest quality, fastest response, lower cost, or a deliberate balance.
- What has worked before? Which models produced outcomes that users accepted for similar work.
The goal is not to route everything to the cheapest model. It is to stop overpaying for routine work while protecting the tasks where quality has the greatest business value.
The Pix2Code example: one customer request contains several different jobs
Pix2Code provides AI-assisted creative and video-editing workflows. A request that looks like one action to the customer can contain several jobs behind the scenes: understanding the request, planning an edit, analyzing visual material, generating an asset, producing structured instructions, and applying changes.
Those jobs have different needs. Visual analysis requires a model that can understand images. Planning may need more context and stronger reasoning. Extracting a small set of fields may be predictable enough for a faster, lower-cost option.
BlueBear helped Pix2Code make those differences visible to the routing software. Instead of hard-coding one model everywhere, the workflow describes the job and its priorities. The routing layer can then recommend an appropriate model while keeping a record of why that recommendation was made.
How we built it without disrupting the existing workflow
Changing model selection can affect cost and customer experience, so BlueBear used an observation-first rollout. The routing software can make a recommendation in the background while Pix2Code's existing execution path continues to run.
This allows the team to compare the recommended model with the model that actually performed the work before handing over control. It also records when a fallback was needed. Operators gain evidence before making a policy change instead of betting production quality on an untested rule.
In practical terms, the rollout follows four stages:
- Describe the work: define the task, required capabilities, and business priority.
- Observe recommendations: see what the router would choose without changing the customer experience.
- Compare outcomes: connect each recommendation to quality, speed, cost, and user response.
- Apply proven policies: allow routing decisions to take control where the evidence supports them.
The part most routing systems miss: what happened afterward?
A routing decision is only useful if the business can tell whether it worked. BlueBear connected Pix2Code's model choices to the outcome of the creative work.
The software can learn from signals the product already creates:
- Did the output pass the product's quality checks?
- Did the user accept it, reject it, or keep correcting it?
- Which of two alternatives did the user prefer?
- What rating did the completed experience receive?
- How long did it take, how many tokens did it use, and was a fallback required?
This changes routing from a purchasing rule into an improvement loop. The system is not simply asking which model is cheapest. It is learning which model creates a successful result for a particular kind of work at an appropriate cost.
A simple way for operators to measure value
Cost per model call is easy to see, but it can be misleading. A cheap response that must be redone three times may cost more than a strong first result. A premium response used for a routine task may deliver no additional value.
A better operating measure is cost per successful outcome. Pair it with a small set of supporting measures:
- User acceptance and rework rate
- Time to a completed result
- Model cost and token use
- Fallback and failure rate
- Performance by task type, team, or customer workflow
This gives finance, operations, and product leaders a shared view. Finance can see where premium-model spend is justified. Product can protect quality. Operations can identify workflows that create rework or unnecessary waiting.
What BlueBear's software solves
The BlueBear approach gives operators control without asking them to become model experts. The software provides a consistent way to describe AI work, compare model choices safely, trace what actually ran, and feed business outcomes back into future decisions.
For Pix2Code, that means the foundation to:
- Use premium models where their capabilities create real value.
- Move suitable routine work to faster or more economical options.
- See the relationship between model choice and customer experience.
- Improve routing policy with evidence instead of vendor claims or guesswork.
- Keep feedback privacy-aware and avoid interrupting the creative workflow if reporting is unavailable.
We are not attaching an invented savings percentage to this case study. The meaningful outcome is that Pix2Code now has the measurement and control loop required to improve quality and AI economics over time.
Questions to ask about your own AI spending
- Are we using the same model for simple and complex work?
- Can we explain why a particular model handled a request?
- Do we know which model actually ran when a fallback occurred?
- Can we connect model cost to acceptance, rework, and completed outcomes?
- Can we test a new routing policy before it changes the customer experience?
If the answer to most of these is no, reducing the price of individual calls will only solve part of the problem. The higher-value move is to build a routing and feedback system around the work your business actually performs.
Ready to get more value from your AI budget?
BlueBear helps businesses turn growing AI usage into a governed, measurable operating capability. Talk with BlueBear about model routing for your workflows.