When to activate
- Estimating total cost of ownership (TCO) for proposed solutions
- Comparing build vs buy costs for architectural decisions
- Creating cloud cost projections for solution proposals
- Optimizing existing solution costs through right-sizing
When NOT to use
- For personal financial planning
- For simple pricing page calculations
- For procurement negotiations
Instructions
- Inventory components. List all infrastructure, services, licenses, and personnel needed.
- Estimate usage. Project traffic, storage, compute requirements at launch and at scale.
- Model costs. Use provider pricing calculators. Include data transfer, API calls, support tiers.
- Compare options. Build vs buy, different providers, different architectures.
- Present TCO. 3-year projection with growth assumptions. Include hidden costs (migration, training, maintenance).
- Optimize. Identify reserved instances, spot opportunities, right-sizing candidates.
Example
Solution Cost Model: Microservices migration
Year 1:
Compute (EKS): $8,400/mo → $100,800/yr
Database (RDS): $3,200/mo → $38,400/yr
Storage (S3): $800/mo → $9,600/yr
Data transfer: $1,200/mo → $14,400/yr
Monitoring: $600/mo → $7,200/yr
Personnel (0.5 SRE): $90,000/yr
Total Year 1: $260,400
Year 3 (at 5x scale):
Total: $580,000/yr (with reserved instances: $490,000/yr)
vs Monolith (current): $180,000/yr (hitting scaling limits at ~10x)
1---2name: cost-modeling3description: Model solution costs — cloud infrastructure, licensing, personnel, and total cost of ownership analysis4allowed-tools: [Read, Write, Grep]5effort: medium6metadata:7 source: https://skillmd.com/skills/uitbreidenos/cost-modeling8---910## When to activate1112- Estimating total cost of ownership (TCO) for proposed solutions13- Comparing build vs buy costs for architectural decisions14- Creating cloud cost projections for solution proposals15- Optimizing existing solution costs through right-sizing1617## When NOT to use1819- For personal financial planning20- For simple pricing page calculations21- For procurement negotiations2223## Instructions24251. **Inventory components.** List all infrastructure, services, licenses, and personnel needed.262. **Estimate usage.** Project traffic, storage, compute requirements at launch and at scale.273. **Model costs.** Use provider pricing calculators. Include data transfer, API calls, support tiers.284. **Compare options.** Build vs buy, different providers, different architectures.295. **Present TCO.** 3-year projection with growth assumptions. Include hidden costs (migration, training, maintenance).306. **Optimize.** Identify reserved instances, spot opportunities, right-sizing candidates.3132## Example3334```35Solution Cost Model: Microservices migration3637Year 1:38 Compute (EKS): $8,400/mo → $100,800/yr39 Database (RDS): $3,200/mo → $38,400/yr40 Storage (S3): $800/mo → $9,600/yr41 Data transfer: $1,200/mo → $14,400/yr42 Monitoring: $600/mo → $7,200/yr43 Personnel (0.5 SRE): $90,000/yr44 Total Year 1: $260,4004546Year 3 (at 5x scale):47 Total: $580,000/yr (with reserved instances: $490,000/yr)4849vs Monolith (current): $180,000/yr (hitting scaling limits at ~10x)50```