Skip to content
scsiwyg
sign insign up
get startedmcpcommunityapiplaygroundswaggersign insign up
Wiki/Skills Reference/Strategy/

/infrastructure-cost-audit

High confidence

Updated 25 Apr 2026 by David Olsson

/infrastructure-cost-audit

Full infrastructure, cost, and scaling audit. Maps service topology, projects costs from MVP to 10K users, and produces a vendor-agnostic requirements spec plus recommended stack.

Trigger: infrastructure audit, cost audit, scaling audit, how much does this cost to run, cost to scale, infrastructure report Output: docs/02-infrastructure-cost/ Reports: 8 (00–07) · Self-contained

Reports

#FileWhat it covers
0000-executive-summary.mdKey metrics, total costs per tier, top risks, next investment
0101-infrastructure-services-map.mdService topology, data flows, dependencies, failure modes
0202-cost-analysis-scaling.mdPer-service pricing tiers: MVP → 100 → 1K → 10K users
0303-loc-complexity-costing.mdLOC benchmarking, complexity scoring, development cost estimation
0404-technology-roadmap-costs.mdStage-by-stage progression from idea through scale
0505-executive-report.mdFull synthesis of 01–04 with charts and recommendations
0606-technology-requirements-spec.mdVendor-agnostic capability requirements
0707-recommended-stack.mdRecommended stack + key findings

Workflow

  1. Scan codebase for infrastructure dependencies (package.json, docker-compose, env files, config)
  2. Map service topology with data flow directions
  3. Research current pricing tiers for each identified service
  4. Project costs across four scaling tiers
  5. Analyze codebase complexity and development cost
  6. Produce technology roadmap with migration plan
  7. Generate vendor-agnostic requirements + opinionated recommendation

See also