Three ways to start
Three ways to start
From least access to a live pilot. Pick the one your security function will sign this quarter; each produces a record you keep, and none takes purchasing authority, sees payload data, or takes money from any compute seller.
A · Back-cast first
Give us one purchase you have already made: the invoice extract, the rate card, the redacted job facts. We re-run the decision as it stood at the time — the baseline, the alternatives, what could and could not have been known. Historical alternatives are unobserved, so it is a diagnostic, not a saving. Free for design partners. No credentials.
B · Sandbox record
Give us redacted contracts, sample billing exports, and your budget structure, offline. We return the first position, the schema, the coverage report, and the reconciliation gaps — before anything touches a live system. You see what the record would hold and what it could not match, with nothing connected.
C · Read-only, in your tenancy
After your security review: scoped read-only credentials, SSO, an audit log, deletion terms, no write path. Two weeks to a first position with its coverage stated. Then the job logs and an hour with your engineers, and ninety days of watching — what it would have bid, where, at what cost, the running total, and the days it says stay put. Nothing changes until you approve it.
Whichever you choose, we agree the subscription and the baseline in writing before anything connects: what a competent team with a second supplier and a router would do without us, on a route that holds your deadlines. Put the people who run your scheduler in the first meeting. If a reservation or a renewal is coming, the record sees it first, and that purchase gets its own fixed fee.
A mutual non-disclosure agreement and a minimal export specification go out before you send us anything. Deletion terms are in the engagement letter.
What we need
Read access to the bill, the contracts, and the budgets, under scoped credentials your security function issues, in your own tenancy. We write to nothing. Or, for the two smaller starts, redacted exports and nothing else
When ready — read access to the scheduler’s job logs, and an hour with your engineers, so deadline and interruption tolerance are written down rather than guessed
1 panel — the suppliers you would actually accept, approved by your security function
90 days from the first job-log print to a running total you can hold the subscription against
When not to call us
You want one counterparty and one invoice and do not need the baseline or the record — hand it to a managed platform. Nothing runs above your commitment, nothing can move, and nothing is coming due, in which case the record would print nothing to do every day. Your work is latency-bound or regulated end to end. Or your utilization is low, in which case fix scheduling first.