0% helpful
0 likes 0 dislikes
Inputs Required
Model/vendor pricing; token usage assumptions or average request size; traffic forecasts; latency targets; caching/retry policies; tooling costs (vector DB, reranker, storage); infra costs; human review costs (if HITL); gross margin target.
Output Artifact
Cost model showing: cost per request/session, cost per active user, monthly run-rate at traffic scenarios, margin impact by tier, and cost levers (caching, routing, smaller model, rate limits).
When to use this
When you’re pricing/packaging an AI feature or approaching launch and need to ensure margins won’t get destroyed by inference/tooling costs.
Link copied