Back to Studio

Studio / Preview

Cost Curve Workbench

A calculator-style tool for converting token pricing into workload cost curves, batch discounts, cache effects, and per-resolution economics.

Live Studio demo

Cost curve workbench

Adjust workload shape and see how token price, retries, cache hits, batching, and review cost change cost per accepted workflow.

Best route

Frontier reasoning

Cost / accepted

$0.08

100k spread

$10,198

Monthly workload curve

USD estimate

Frontier reasoning$20,587 at 250k
Fast mid-tier$22,789 at 250k
Small router$46,081 at 250k
Model routeToken costRetryReview
Frontier reasoning$0.047%17%
Fast mid-tier$0.0212%28%
Small router$0.0024%56%

In this scenario, frontier reasoning has the lowest modeled accepted-output cost. The small router remains useful for triage, but its review and retry drag can make it more expensive than it looks.

How it works

Each Studio surface is designed as a practical operating loop: capture the buyer problem, run measured evidence, and return a decision artifact that can be acted on.

Current demo state

Live calculator surface is available; next release should connect to official provider pricing refresh scripts.

1

Model workload volume, input size, output length, reasoning overhead, retry rate, and review cost.

2

Apply cache, batch, routing, and fallback assumptions to create best/base/worst curves.

3

Compare model classes by accepted workflow rather than token price alone.

4

Export a monthly budget envelope and the levers most likely to bend the curve.

Buyer questions

These are the questions the product needs to answer before someone deploys, buys, or scales the system.

What will this cost at 10k, 100k, or 1M workflows?

How much do retries and human review change the answer?

When does prompt caching materially matter?

Which model class is cheap after quality is included?

Deliverables

What a buyer gets

Cost curve
Scenario table
Savings waterfall
Budget envelope

Connected evidence

Read the benchmark trail

Studio packet

Buyer-ready demo packet.

This generated packet gives Sanjay and Saujas a consistent follow-up artifact for demos, consulting calls, and product conversations.

Next build step

Turn this Studio surface from a populated product brief into a live demo by wiring real run data, screenshots, and client-approved examples into the same page.