Cloud service and infrastructure cost analysis toolkit. Research current pricing, estimate costs across scenarios, calculate ROI projections, and identify cost optimization opportunities for software projects.
Analyzes cloud service costs, estimates infrastructure expenses, and identifies optimization opportunities for software projects.
/plugin marketplace add flight505/claude-project-planner/plugin install claude-project-planner@claude-project-plannerThis skill is limited to using the following tools:
Service cost analysis is a systematic process for estimating infrastructure and operational costs for software projects. Research current pricing, model costs across usage scenarios, calculate ROI projections, and identify optimization opportunities. Use this skill to make informed budget decisions backed by real pricing data.
This skill should be used when:
When documenting cost analysis, include visualizations.
Use the project-diagrams skill to generate:
python .claude/skills/project-diagrams/scripts/generate_schematic.py "diagram description" -o diagrams/output.png
| Category | Examples | Variability |
|---|---|---|
| Compute | VMs, containers, serverless | Usage-based |
| Storage | Object storage, block storage, databases | Capacity + operations |
| Networking | Data transfer, load balancers, CDN | Traffic-based |
| Databases | Managed databases, caching | Capacity + throughput |
| Third-Party | APIs, SaaS tools, services | Usually usage-based |
| Development | CI/CD, monitoring, logging | Often fixed + usage |
| Personnel | Development, operations, support | Fixed (but critical) |
For every service, follow this protocol:
Find Official Pricing
WebFetch or WebSearch to get current pricingIdentify Cost Drivers
Document Assumptions
Calculate Scenarios
service_cost:
# Identity
service_name: "string"
provider: "aws | gcp | azure | other"
category: "compute | storage | database | networking | third_party | development"
# Pricing
pricing_model: "per_hour | per_request | per_gb | per_user | flat_rate | tiered"
pricing_source: "URL to official pricing"
pricing_date: "YYYY-MM-DD"
# Cost Estimates
monthly_cost:
low: number
mid: number
high: number
# Assumptions
assumptions:
- "string - assumption 1"
- "string - assumption 2"
# Usage Estimates
usage:
metric: "string (e.g., requests, GB, hours)"
low: number
mid: number
high: number
# Notes
notes: "string - important considerations"
optimization_opportunities:
- "string - potential optimization"
Common Services:
| Service | Pricing Model | Key Cost Drivers |
|---|---|---|
| EC2 | Per-hour + data transfer | Instance type, hours, data out |
| RDS | Per-hour + storage + IOPS | Instance type, storage, multi-AZ |
| S3 | Per-GB + requests | Storage class, requests, data transfer |
| Lambda | Per-request + duration | Invocations, memory, duration |
| ECS/Fargate | Per-vCPU-hour + memory-hour | Task size, hours running |
| CloudFront | Per-request + data transfer | Requests, data out, regions |
AWS Pricing Research:
# Use WebSearch to find current pricing
WebSearch: "AWS [service] pricing 2025"
WebFetch: "https://aws.amazon.com/[service]/pricing/"
Example AWS Cost Specification:
service_costs:
- service_name: "AWS RDS PostgreSQL"
provider: "aws"
category: "database"
pricing_model: "per_hour"
pricing_source: "https://aws.amazon.com/rds/postgresql/pricing/"
pricing_date: "2025-01-06"
monthly_cost:
low: 50 # db.t3.micro, 20GB, single-AZ
mid: 250 # db.t3.medium, 100GB, multi-AZ
high: 800 # db.r5.large, 500GB, multi-AZ, provisioned IOPS
assumptions:
- "US East (N. Virginia) region"
- "Reserved instances not applied (on-demand pricing)"
- "Low: Development environment"
- "Mid: Production with moderate traffic"
- "High: Production with high availability requirements"
usage:
metric: "instance hours + storage GB"
low: "730 hours db.t3.micro + 20GB"
mid: "730 hours db.t3.medium + 100GB + multi-AZ"
high: "730 hours db.r5.large + 500GB + multi-AZ + 3000 PIOPS"
notes: |
Consider Aurora for better scalability above 500GB.
Reserved instances can reduce costs by 30-60%.
Multi-AZ doubles compute cost but is recommended for production.
optimization_opportunities:
- "Reserved instances for predictable workloads"
- "Aurora Serverless for variable workloads"
- "Read replicas instead of larger instance"
Common Services:
| Service | Pricing Model | Key Cost Drivers |
|---|---|---|
| Compute Engine | Per-second (min 1 min) | Machine type, sustained use |
| Cloud SQL | Per-hour + storage | Instance type, HA configuration |
| Cloud Storage | Per-GB + operations | Storage class, operations |
| Cloud Functions | Per-invocation + compute time | Invocations, memory, duration |
| Cloud Run | Per-request + vCPU-second | Requests, CPU, memory |
| BigQuery | Per-TB scanned + storage | Query bytes, storage |
GCP Pricing Research:
WebSearch: "GCP [service] pricing 2025"
WebFetch: "https://cloud.google.com/[service]/pricing"
Common Services:
| Service | Pricing Model | Key Cost Drivers |
|---|---|---|
| Virtual Machines | Per-hour | VM size, hours, data transfer |
| Azure SQL | DTU or vCore model | Compute tier, storage |
| Blob Storage | Per-GB + operations | Access tier, redundancy |
| Azure Functions | Per-execution + duration | Executions, memory |
| Container Apps | Per-vCPU-second | vCPU, memory, requests |
| Cosmos DB | RU/s + storage | Provisioned RUs, storage |
Common Categories:
| Category | Examples | Typical Pricing |
|---|---|---|
| Authentication | Auth0, Clerk, Firebase Auth | Per-MAU |
| Payments | Stripe, PayPal | % of transaction |
| SendGrid, Postmark, SES | Per-email | |
| Search | Algolia, Elasticsearch Cloud | Per-search + records |
| Monitoring | Datadog, New Relic | Per-host + features |
| Error Tracking | Sentry, Bugsnag | Per-event |
| Analytics | Mixpanel, Amplitude | Per-MTU |
Example Third-Party Cost:
service_costs:
- service_name: "Stripe Payment Processing"
provider: "stripe"
category: "third_party"
pricing_model: "per_transaction"
pricing_source: "https://stripe.com/pricing"
pricing_date: "2025-01-06"
monthly_cost:
low: 150 # $5,000 GMV
mid: 750 # $25,000 GMV
high: 3000 # $100,000 GMV
assumptions:
- "Standard pricing: 2.9% + $0.30 per transaction"
- "Average transaction: $50"
- "Low: 100 transactions/month"
- "Mid: 500 transactions/month"
- "High: 2000 transactions/month"
notes: |
Volume discounts available above $100K/month.
Additional fees for international cards (+1.5%).
Subscription billing may have different rates.
monthly_cost_summary:
project: "[Project Name]"
date: "YYYY-MM-DD"
currency: "USD"
scenarios:
low:
description: "MVP / Development"
users: "< 100"
total: 0
mid:
description: "Initial Production"
users: "1,000 - 10,000"
total: 0
high:
description: "Scale / Growth"
users: "> 10,000"
total: 0
by_category:
compute:
services: []
low: 0
mid: 0
high: 0
storage:
services: []
low: 0
mid: 0
high: 0
database:
services: []
low: 0
mid: 0
high: 0
networking:
services: []
low: 0
mid: 0
high: 0
third_party:
services: []
low: 0
mid: 0
high: 0
development:
services: []
low: 0
mid: 0
high: 0
totals:
monthly:
low: 0
mid: 0
high: 0
annual:
low: 0
mid: 0
high: 0
roi_analysis:
project: "[Project Name]"
investment:
development_cost: 0
infrastructure_setup: 0
training_and_onboarding: 0
total_initial_investment: 0
ongoing_costs:
monthly_infrastructure: 0
monthly_third_party: 0
monthly_personnel: 0
total_monthly_operating: 0
annual_operating: 0
revenue_projections:
year_1:
monthly_revenue: 0
growth_rate: "% per month"
annual_revenue: 0
year_2:
annual_revenue: 0
year_3:
annual_revenue: 0
metrics:
payback_period_months: 0
year_1_roi: "percentage"
year_3_roi: "percentage"
break_even_users: 0
assumptions:
- "Revenue assumption 1"
- "Cost assumption 2"
- "Growth assumption 3"
| Strategy | Savings | When to Use |
|---|---|---|
| Reserved Instances | 30-60% | Predictable, steady workloads |
| Spot/Preemptible | 60-90% | Fault-tolerant, batch jobs |
| Right-sizing | 20-40% | Over-provisioned resources |
| Auto-scaling | Variable | Variable traffic patterns |
| Serverless | Variable | Sporadic, unpredictable loads |
| Strategy | Savings | When to Use |
|---|---|---|
| Tiered Storage | 40-80% | Infrequently accessed data |
| Lifecycle Policies | Variable | Data with known access patterns |
| Compression | 20-50% | Compressible data types |
| Deduplication | Variable | Redundant data |
| Strategy | Savings | When to Use |
|---|---|---|
| Reserved Capacity | 30-60% | Predictable workloads |
| Read Replicas | Variable | Read-heavy workloads |
| Serverless | Variable | Variable traffic |
| Query Optimization | 20-50% | Pay-per-query models |
| Strategy | Savings | When to Use |
|---|---|---|
| Annual Contracts | 10-30% | Committed usage |
| Volume Discounts | Variable | High volume |
| Alternative Providers | Variable | Comparable services |
| Self-hosting | Variable | High volume, DevOps capacity |
# Cost Analysis Report: [Project Name]
## Executive Summary
- Total estimated monthly cost: $X - $Y
- Primary cost drivers: [List top 3]
- Key optimization opportunities: [List top 3]
## Cost Breakdown by Category
### Compute ($X/month)
[Service details and cost justification]
### Storage ($X/month)
[Service details and cost justification]
### Database ($X/month)
[Service details and cost justification]
### Third-Party Services ($X/month)
[Service details and cost justification]
## Scenario Analysis
### Low Scenario (MVP)
- Users: X
- Monthly cost: $Y
- Suitable for: [Use case]
### Mid Scenario (Production)
- Users: X
- Monthly cost: $Y
- Suitable for: [Use case]
### High Scenario (Scale)
- Users: X
- Monthly cost: $Y
- Suitable for: [Use case]
## ROI Analysis
[If applicable]
## Optimization Recommendations
1. [Recommendation with potential savings]
2. [Recommendation with potential savings]
3. [Recommendation with potential savings]
## Assumptions and Risks
- [Key assumption 1]
- [Key assumption 2]
- [Cost risk 1]
## References
- [Pricing source 1]
- [Pricing source 2]
Before completing cost analysis:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.