Flagship
Compute cost review
A three-week reading of one AI application’s invoices, usage windows, and idle capacity, delivered as a findings memo you can take to finance.
Reviews
Readings of compute cost and usage, scoped to a named application
Each sitting is a piece of writing and a set of conversations. Nothing to log into. Pick the review that matches the question finance is actually asking.
Most first-time teams start with the compute cost review. A window briefing is for one noisy period. Allocation mapping is for a shared endpoint. A retainer follows a review; it does not replace one.
Rooms used for invoice sittings, Kuala Lumpur
Short reading
Usage window briefing
A focused sitting with one billing period — a campaign week, a model swap, or a month that jumped — so you can explain that window to finance.
Shared endpoints
Cost allocation mapping
A mapping of one shared model endpoint or GPU pool onto the product teams that actually call it, so the bill is no longer a single unexplained number.
Retainer
Recurring spend briefing
A monthly or quarterly written briefing on the same application, so finance sees the same shape of note each period instead of a scramble after every invoice.