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.
Who it is for
Teams who already know the application is expensive and need a reading of one specific week or month, not a full ninety-day review.
What you leave with
A short briefing note that names what changed in that window: new traffic, a longer context, a forgotten replica, or a training job that leaked into the inference bill.
Scope
One billing period of up to thirty-one days, one application.
- Duration
- Usually eight to ten working days from a complete pack.
- Where
- Video by default; a KL sitting if you prefer to spread invoices on the table.
- Fee basis
- From RM 4,800 per window.
- Who leads
- Priya Nair writes the briefing. Farah joins if the window includes a training run mixed with inference.
Included
- One ninety-minute working session
- A two-to-four page briefing note
- A list of questions finance is likely to ask about that window
Not included
- A full ninety-day cost review
- Allocation across more than one product team
How the sitting runs
-
Name the window
You pick the dates and send the invoice plus any usage extract for those days.
-
Session
We read the period together and mark the lines that moved.
-
Note
You receive the briefing note within five working days.
Preparation
The invoice for that period, a sentence on what you think happened, and anyone who ran a campaign or a model change in those dates.
Limits we keep
We will not stretch a window briefing into a full review without a new fee. If the period is messy enough to need ninety days of context, we will say so and point you to the compute cost review.
Next step
Send the dates and the invoice. We confirm whether a window briefing is the right sitting.