From bill shock to an operating model
Analect Forecast is the AI cost modeling and forecasting workflow in the Analect platform. It captures your workloads in plain language or from your provider bill, prices each one across roughly 200 models from 27 providers, and produces the report finance signs off, with the reasoning behind every recommendation shown.
The problem finance actually has
AI spend arrives as one line on a provider invoice. Nobody can say which workload drove it, whether the model was the right one for the job, what caching would have saved, or what next quarter looks like. 73 percent of enterprises exceeded their AI cost projections last year, and 98 percent of FinOps teams now manage inference spend, most of them from that single line. That is not a pricing problem. It is an operating-model problem.
What Forecast does
Describe the work
Workloads captured in plain questions or full detail: volumes, context, tool calls, budgets.
Start from your bill
Import the provider CSV. See what you actually paid against what the work should cost, and your effective discount.
Recommendation
Which of roughly 200 models across 27 providers can do each job, what every scenario costs, and what your budget ceiling would buy.
Report
One row per workload with the reasoning behind each pick and caching as its own lever. The version finance signs off. Prints to PDF.
Ingestion and routes
What the corpus costs to make answerable before anyone asks it a question, and the fragment route priced against the document route.
The Forecast loop
Measure
Import the bill or describe the workloads. Establish what is actually being asked, how often, at what size.
Model
Price every workload across the catalog. Run scenarios. Set the ceiling and see what it buys.
Decide
Route each workload to the best-fit model. Choose fragment or document per job. Switch caching on where it pays.
Govern
Publish the report. Own the budget. Re-forecast as prices, models and volumes change.
Step four feeds step one. Every re-forecast starts from the bill you just paid.
From an invoice to an operating cost
Per workload, not per invoice
Cost attaches to the job that caused it, with an owner and a reason.
A ceiling that means something
The budget planner shows what your number buys, so trade-offs are explicit before the spend.
A forecast that stays current
Catalog pricing updates as the market moves; the plan re-prices with it.
Forecast turns AI from a black-box invoice into a managed operating cost. It is also the tool that prices the fragment route against the document route, which is how you see the saving before you buy it.
See your workloads priced.
A pilot prices your real workloads across the catalog and puts the fragment route next to the document route, so the saving is a number before it is a decision.