cost-estimator
Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.
What this skill does
# Cost Estimator
Provides frameworks for estimating infrastructure costs, development effort, and total cost of ownership (TCO) for technical projects.
## When to Use
- Planning infrastructure budgets
- Evaluating build vs. buy decisions
- Projecting costs at different scale points
- Comparing technology options by cost
- Creating business cases for technical investments
## Cost Categories
### Total Cost of Ownership (TCO)
```
TCO = Infrastructure + Development + Operations + Opportunity Cost
┌─────────────────────────────────────────────────────────────────┐
│ TOTAL COST OF OWNERSHIP │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Infrastructure Development Operations Opportunity │
│ ──────────────── ──────────── ────────── ──────────── │
│ • Compute • Engineering • Support • What else │
│ • Storage • QA • Monitoring • could team │
│ • Network • DevOps • On-call • be building? │
│ • Third-party • Management • Training │
│ APIs/SaaS • Contractors • Incidents │
│ │
└─────────────────────────────────────────────────────────────────┘
```
---
## Infrastructure Cost Reference
### Cloud Compute Pricing (2024-2025)
#### AWS EC2 On-Demand (US regions)
| Instance | vCPU | RAM | Monthly Cost | Best For |
|----------|------|-----|--------------|----------|
| t3.micro | 2 | 1GB | $8 | Dev/test |
| t3.medium | 2 | 4GB | $30 | Small apps |
| t3.large | 2 | 8GB | $60 | Light production |
| m6i.large | 2 | 8GB | $70 | General production |
| m6i.xlarge | 4 | 16GB | $140 | Medium workloads |
| m6i.2xlarge | 8 | 32GB | $280 | Heavy workloads |
| c6i.2xlarge | 8 | 16GB | $250 | CPU-intensive |
| r6i.2xlarge | 8 | 64GB | $370 | Memory-intensive |
#### GPU Instances
| Instance | GPU | VRAM | Monthly Cost | Best For |
|----------|-----|------|--------------|----------|
| g4dn.xlarge | T4 | 16GB | $380 | Inference |
| g5.xlarge | A10G | 24GB | $730 | ML training/inference |
| p4d.24xlarge | 8x A100 | 320GB | $23,000 | Large model training |
#### Savings Options
| Plan | Savings | Commitment |
|------|---------|------------|
| On-Demand | 0% | None |
| Reserved (1yr) | 30-40% | 1 year |
| Reserved (3yr) | 50-60% | 3 years |
| Spot Instances | 60-90% | Can be interrupted |
### Database Pricing
#### Managed Database (AWS RDS PostgreSQL)
| Instance | vCPU | RAM | Monthly Cost | Connections |
|----------|------|-----|--------------|-------------|
| db.t3.micro | 2 | 1GB | $15 | 50 |
| db.t3.medium | 2 | 4GB | $50 | 100 |
| db.m6g.large | 2 | 8GB | $120 | 200 |
| db.m6g.xlarge | 4 | 16GB | $240 | 400 |
| db.r6g.xlarge | 4 | 32GB | $350 | 500 |
| db.r6g.2xlarge | 8 | 64GB | $700 | 1000 |
**Add for storage**: $0.115/GB/month (gp3)
**Add for IOPS**: $0.02/IOPS/month (over 3000 baseline)
#### Redis/ElastiCache
| Node Type | RAM | Monthly Cost |
|-----------|-----|--------------|
| cache.t3.micro | 0.5GB | $12 |
| cache.t3.medium | 3GB | $50 |
| cache.m6g.large | 6.4GB | $100 |
| cache.r6g.large | 13GB | $175 |
### Storage Pricing
| Service | Cost | Use Case |
|---------|------|----------|
| S3 Standard | $0.023/GB | Frequently accessed |
| S3 Infrequent | $0.0125/GB | Backups, archives |
| S3 Glacier | $0.004/GB | Long-term archive |
| EBS gp3 | $0.08/GB | Block storage |
| EBS io2 | $0.125/GB + IOPS | High performance |
### Network Costs (Often Overlooked!)
| Traffic Type | Cost |
|--------------|------|
| Data IN | Free |
| Data OUT (first 10TB) | $0.09/GB |
| Data OUT (next 40TB) | $0.085/GB |
| Inter-AZ transfer | $0.01/GB each way |
| Inter-region transfer | $0.02/GB |
| CloudFront to internet | $0.085/GB |
---
## Development Cost Estimation
### Engineering Cost Framework
```
Development Cost = (Hours × Hourly Rate) × Complexity Factor × Risk Buffer
Hourly Rate (Fully Loaded):
- Junior Engineer: $75-100/hr
- Mid-level Engineer: $100-150/hr
- Senior Engineer: $150-200/hr
- Staff/Principal: $200-300/hr
Complexity Factors:
- Greenfield, known tech: 1.0x
- Existing codebase, known tech: 1.2x
- New technology for team: 1.5x
- Complex integrations: 1.3x
- Regulatory/compliance: 1.4x
Risk Buffer:
- Well-defined requirements: 1.2x
- Ambiguous requirements: 1.5x
- Experimental/R&D: 2.0x
```
### Story Point to Cost Mapping
| Size | Story Points | Hours | Cost (Mid-level) |
|------|-------------|-------|------------------|
| XS | 1 | 2-4 | $200-400 |
| S | 2 | 4-8 | $400-800 |
| M | 3 | 8-16 | $800-1,600 |
| L | 5 | 16-32 | $1,600-3,200 |
| XL | 8 | 32-64 | $3,200-6,400 |
| XXL | 13+ | 64+ | $6,400+ |
### Team Cost Calculator
```markdown
## Monthly Team Cost
Engineering Team:
- 2 Senior Engineers × $15,000 = $30,000
- 3 Mid-level Engineers × $10,000 = $30,000
- 1 Engineering Manager × $18,000 = $18,000
Overhead (benefits, tools, etc.): 30%
Monthly Burn: ($78,000) × 1.3 = $101,400
Annual Team Cost: ~$1.2M
```
---
## Build vs. Buy Analysis
### Decision Framework
```
Build vs Buy Decision Matrix:
LOW Differentiation HIGH Differentiation
┌────────────────────┬────────────────────┐
HIGH Volume/ │ │ │
Usage │ Consider │ BUILD │
│ Build │ (competitive │
│ (cost savings) │ advantage) │
├────────────────────┼────────────────────┤
LOW Volume/ │ │ │
Usage │ BUY │ BUY │
│ (no question) │ (then consider │
│ │ build if scales) │
└────────────────────┴────────────────────┘
```
### TCO Comparison Template
```markdown
## Option A: Build Custom Solution
### Initial Development
- Engineering time: X months × $Y/month = $Z
- Infrastructure setup: $A
### Ongoing Costs (Annual)
- Infrastructure: $B
- Maintenance (20% of dev time): $C
- On-call/support: $D
### 3-Year TCO
Year 1: $Z + $A + $B + $C + $D
Year 2: $B + $C + $D
Year 3: $B + $C + $D
Total: $XXX
---
## Option B: Buy SaaS Solution
### Initial Costs
- Implementation/integration: $X
- Training: $Y
### Ongoing Costs (Annual)
- License fees: $Z/year
- Per-user costs: $A × users
- API costs: $B
### 3-Year TCO
Year 1: $X + $Y + $Z + $A + $B
Year 2: $Z + $A + $B
Year 3: $Z + $A + $B
Total: $XXX
```
### Common Build vs Buy Scenarios
| Capability | Build When | Buy When |
|------------|------------|----------|
| **Authentication** | Unique security requirements | Standard OAuth/OIDC works |
| **Payments** | Core business differentiator | Standard e-commerce |
| **Search** | Domain-specific relevance | Generic search needs |
| **Analytics** | Proprietary insights needed | Standard dashboards work |
| **Email** | High volume, custom delivery | Standard transactional |
| **ML/AI** | Proprietary models needed | Pre-trained models work |
---
## Cost Projection by Scale
### SaaS Application Cost Model
| Scale | Users | Monthly Infra | Notes |
|-------|-------|---------------|-------|
| **Startup** | 0-1K | $200-500 | Single server, managed DB |
| **Growth** | 1K-10K | $500-2,000 | Load balancer, caching |
| **Scale** | 10K-100K | $2,000-10,000 | Horizontal scaling |
| **Enterprise** | 100K-1M | $10,000-50,000 | Multi-region, HA |
| **Large** | 1M+ | $50,000+ | Global, custom CDN |
### Cost Per User Benchmarks
| Application Type | Cost/User/Month | Notes |
|------------------|-----------------|-------|
| Simple web app | $0.05-0.20 | Static + API |
| Data-intensive | $0.20-0.50 | Analytics, storage |
| Real-time | $0.50-2.00 | WebSockets, streaming |
| ML-powered | $1.00-5.00 | Inference cRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.