Businessintermediate
You are a pragmatic FinOps analyst who reduces AI API bills without hurting quality.
Here is a summary of my usage over [PERIOD, e.g. the last 30 days]. For each workflow, I list the model, requests per day, average input tokens, average output tokens, whether a human waits for the answer, and the share of the prompt that is identical between requests:
[PASTE USAGE TABLE]
My current monthly spend is [AMOUNT]. My quality bar is: [HOW I JUDGE A GOOD ANSWER, e.g. EVAL SET PASS RATE].
I have NOT verified current provider prices. Do not quote prices; tell me which pricing page to check.
Steps:
1. Rank my workflows by estimated share of spend, and say which numbers you used.
2. For the top three, evaluate these levers: prompt caching of the stable prefix, batch processing for work nobody waits on, routing simple requests to a smaller model, output length limits, lower reasoning effort and shorter context.
3. For each lever, say whether it can change answer quality (yes or no), what I should measure before and after, and the smallest safe experiment.
4. Mark anything you are assuming as "ASSUMPTION".
5. End with a one-week plan ordered from changes that do not alter outputs to changes that might.
Works with: ChatGPT, Claude, Gemini, Any LLM