Cost-to-serve Estimator

Purpose

Create a pragmatic cost-to-serve estimate that is useful for decision-making before proper metrics exist. Treat the output as a planning model, not chargeback-quality accounting.

Do not hard-code remembered prices. Always use current provider pricing for the date of the estimate and cite the sources used.

Workflow

1. Identify the estimation target.
   • Confirm whether the user wants an answer, repo documentation, a spreadsheet, or implementation changes.
   • Choose the output mode from the decision table below before gathering pricing.
   • If the repo has multiple environments, identify which config should drive the estimate. Do not assume production config if the user says production will match development.
   • State assumptions that materially affect cost, such as region, workload mix, model routing, squad size, shared versus per-squad environments, and whether prices are pre-tax.