What is the '3-year horizon' principle in cost modeling?

The 3-year horizon reveals the true cost of ownership by accounting for long-term maintenance, training, and operational overhead that are often invisible during the initial build phase.

Can this skill help with cloud provider comparisons?

Yes, it is designed to compare per-seat, usage-based, and flat-rate pricing models across different vendors to find the most cost-effective solution.

Why does the model emphasize data egress?

Data egress is frequently the most overlooked cost in cloud architecture; this skill models transfer costs separately to ensure they don't become a surprise expense.

How does it handle scaling costs?

The skill utilizes linear, sublinear, and superlinear growth modeling to project how your expenses will change as your primary cost drivers, such as transactions or users, increase.

Infrastructure Cost Architect

Name: Infrastructure Cost Architect
Author: rnavarych

byrnavarych

•

Infraestructura en la Nube

Models software architecture costs through TCO calculations, build-vs-buy analysis, and long-term ROI projections.

The Cost Modeling skill transforms Claude into a financial architect capable of performing deep economic analysis on software infrastructure. It provides structured frameworks for estimating three-year Total Cost of Ownership (TCO), comparing vendor pricing models, and conducting build-vs-buy evaluations. By incorporating critical factors like data egress surprises, opportunity costs, and maintenance overhead, the skill helps engineering teams make data-driven decisions that align technical strategy with business profitability and scaling sustainability.

Características Principales

013-Year TCO & Maintenance Projections

02ROI Sensitivity & Breakeven Analysis

03Infrastructure Cost Scaling & Growth Modeling

04Quantitative Build vs. Buy Analysis

0511 GitHub stars

06Multi-Model Pricing Comparison (Usage vs. Seat-based)

Casos de Uso

01Evaluating the financial impact of migrating from on-premise to cloud-native architecture.

02Modeling infrastructure expenditure growth relative to user or transaction volume increases.

03Deciding between developing a custom internal tool or purchasing a SaaS solution based on long-term cost.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rnavarych/alpha-engineer cost-modeling

For use in Claude.ai and ChatGPT

Características Principales

013-Year TCO & Maintenance Projections

02ROI Sensitivity & Breakeven Analysis

03Infrastructure Cost Scaling & Growth Modeling

04Quantitative Build vs. Buy Analysis

0511 GitHub stars

06Multi-Model Pricing Comparison (Usage vs. Seat-based)

Casos de Uso

01Evaluating the financial impact of migrating from on-premise to cloud-native architecture.

02Modeling infrastructure expenditure growth relative to user or transaction volume increases.

03Deciding between developing a custom internal tool or purchasing a SaaS solution based on long-term cost.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add rnavarych/alpha-engineer cost-modeling

For use in Claude.ai and ChatGPT