Case study

From brute-force reasoning to precision routing

B:Side Assist4 min read

Watercolor illustration of one heavy stroke splitting into several right-sized channels, one carrying a violet to orange gradient
B:Side Assist logo

B:Side Assist is a financial intelligence platform that helps businesses understand their financial position. Its AI copilot, AI Assist, answers questions using connected bank accounts, transactions, uploaded financial documents, business context, and current research.

To the user, it is one chat response. Behind the scenes, producing that response can involve several specialized AI jobs: one model call interprets the question, another inspects a document, another calculates a financial scenario, and another validates or repairs the final answer. AI Assist runs 11 of these layers, from greetings and summaries to validation, research, vision, and recovery.

Each layer asks for something different. A greeting or a summary should be fast and inexpensive, while validating financial calculations or conducting grounded research deserves deeper reasoning. Right-sizing that stack produced the numbers below.

ai assist · right-sized outcomeprojected per 20 queries
0.0%

lower inference cost

0.0%

faster end to end

0.0%

higher throughput

pass rate held at 100%, measured on the same benchmark

The challenge

The assumed starting architecture used gpt-5.6-terra with xhigh reasoning across every AI Assist layer. Terra is a capable, balanced model, and xhigh tells it to devote substantial reasoning effort to the task. That combination makes sense for difficult financial analysis. As the default for everything, it treats routine extraction and genuinely difficult analysis as if they were the same job, and it maximizes theoretical reasoning in places nobody benefits from it.

It was the AI equivalent of using a supercomputer to sort a spreadsheet: exceptionally capable, but unnecessarily expensive and slow for much of the work.

And the waste compounds. One user question can trigger multiple model calls, so small inefficiencies at each layer accumulate into slower responses and higher inference costs.

What rightmodeler changed

rightmodeler evaluated AI Assist as 11 distinct workloads rather than one generic AI request. Each layer was benchmarked on its own traces and matched to the cheapest model and reasoning effort that held its quality bar. The resulting policy:

rightmodeler · routing policy · ai assistbaseline: terra · xhigh everywhere

luna · low

quick responses, follow-ups, summaries

luna · medium

document extraction and vision

luna · high

Business Wiki and failure recovery

luna · xhigh

grounded research, the only xhigh route

terra · high

orchestration, validation, repair

sol

reserved for demanding fallbacks

The shape of the policy tells the story. Most of the traffic moves to Luna. Terra stays only where it earns its price: orchestration, validation, and repair, the layers where a wrong answer is expensive. xhigh reasoning survives in exactly one place, grounded research, where reasoning depth is the product itself. And Sol waits in reserve for the rare fallback that genuinely needs it.

Projected results

These figures model the all Terra, all xhigh starting point using actual benchmark traces, current OpenAI pricing, and the observed xhigh reasoning and latency uplift from the grounded research workload.

rightmodeler · ai assist evaluationper 20 queries · 11 workloads
inference cost70.8% lower
terra · xhigh $0.05119right-sized $0.01493
total response time53.3% faster
terra · xhigh 50.46sright-sized 23.54s
avg response time1.346s saved/query
terra · xhigh 2.523sright-sized 1.177s
reasoning tokens68.9% fewer
terra · xhigh 2,347.64right-sized 730.30
total tokens24.7% fewer
terra · xhigh 6,552.79right-sized 4,935.45
throughput114.3% higher
terra · xhigh 23.78 q/minright-sized 50.97 q/min
quality pass rate0-point difference
terra · xhigh 100% assumedright-sized 100% measured

modeled from actual benchmark traces · current OpenAI pricing · observed xhigh uplift from grounded research

The row that matters most is the one that did not move. The baseline assumed a 100% quality pass rate; the right-sized policy measured 100% on the same benchmark. Cheaper and faster only count if quality holds.

The savings are only real because quality held: 100% measured, not assumed.

At scale

Per-query savings look small until you multiply them. At the evaluation prices, the modeled cost reduction compounds:

ai assist · savings at volumemodeled at current pricing
$1.81

saved per 1,000 queries

$1,813

saved per million queries

projected at current Standard pricing · scales linearly with volume

The mechanics are simple. Current Standard pricing puts Terra at $2.50 per million input tokens and $15 per million output tokens, while Luna runs $1 and $6. Every routine call that Luna handles at a fraction of Terra’s price, at equal measured quality, is margin recovered.

This is what rightmodeler produces: not a cheaper model, a policy. Eleven workloads, each on the smallest model and reasoning effort that provably holds its quality bar, with Terra and Sol kept for the work that deserves them.

rightmodeler took AI Assist from brute force to precision routing. Costs fell 70.8%, responses got twice as fast, and quality held at 100%, measured, not assumed.

Chris Myers, CEO, B:Side Capital and Fund

Run it on your own traces.

It is a report, not a runtime gateway. Prove the savings on your own data first.