Skill

role-architect:cost-modeling

Models infrastructure costs, calculates 3-year TCO, analyzes build-vs-buy decisions, compares pricing models, projects ROI with sensitivity analysis, simulates cost growth, and performs breakeven analysis.

infrastructure

devops

npx claudepluginhub rnavarych/alpha-engineer --plugin role-architect

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/role-architect:cost-modeling

User invocable

Model invocable

Inline context

Default effort

Tool Access

This skill is limited to the following tools:

ReadGrepGlobBash

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

- Estimating infrastructure costs before committing to an architecture

Supporting Files

references/estimation-tco-build-vs-buy.mdreferences/roi-growth-breakeven.md

SKILL.md

31 lines · ~527 tokens

Similar Skills

cost-estimator

Estimates infrastructure, development effort, and TCO for technical projects. Use for budgeting, build vs buy decisions, and architecture cost projections.

cto-team

business-case

172

Generates business case analyses with ROI, NPV, IRR, payback period, TCO calculations, and sensitivity analysis for financial justification, build-vs-buy, and investment decisions.

6 files5 tools

ork

financial-modeling

Builds financial models for business cases including ROI, NPV, IRR, scenario analysis, TCO, DCF, break-even, and EVA. Useful for investment recommendations, strategic decisions, and cost-benefit analysis.

management-consulting

Stats

LanguageShell

Parent stars13

Parent forks1

MaintenanceGood

Last CommitMar 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Cost Modeling

When to use

Estimating infrastructure costs before committing to an architecture

Calculating 3-year TCO to compare two architectural approaches or vendors

Deciding whether to build a capability in-house or buy an existing solution

Comparing per-seat, usage-based, flat-rate, and hybrid pricing models for a tool

Projecting ROI on a proposed investment with sensitivity analysis

Modeling how costs will scale as the primary cost driver (users, transactions, data) grows

Performing breakeven analysis for a migration or build-vs-buy decision

Core principles

Egress is always the surprise — model data transfer costs separately before everything else

3-year horizon reveals the truth — build looks cheaper in year 1; maintenance changes that by year 3

Cost per unit, not total cost — if cost per user is rising, there is a scaling architecture problem

ROI needs a pessimistic scenario — if the investment goes negative under realistic downside assumptions, it is risky

Opportunity cost belongs in the model — time spent building is time not spent on revenue features

Reference Files

references/estimation-tco-build-vs-buy.md — compute/storage/network/managed service cost estimation, 5-category 3-year TCO structure (license + infrastructure + operations + training + migration), build vs. buy decision criteria and 3-year quantification, and per-seat/usage-based/flat-rate/hybrid pricing model comparison

references/roi-growth-breakeven.md — ROI formula and time-to-ROI calculation, sensitivity analysis (+/- 20% assumptions), linear/sublinear/superlinear cost growth modeling, cost-per-unit trending, cost optimization checkpoint thresholds, and breakeven crossover chart methodology for build-vs-buy and migration decisions

Cost Modeling

When to use

Estimating infrastructure costs before committing to an architecture
Calculating 3-year TCO to compare two architectural approaches or vendors
Deciding whether to build a capability in-house or buy an existing solution
Comparing per-seat, usage-based, flat-rate, and hybrid pricing models for a tool
Projecting ROI on a proposed investment with sensitivity analysis
Modeling how costs will scale as the primary cost driver (users, transactions, data) grows
Performing breakeven analysis for a migration or build-vs-buy decision

Core principles

Egress is always the surprise — model data transfer costs separately before everything else
3-year horizon reveals the truth — build looks cheaper in year 1; maintenance changes that by year 3
Cost per unit, not total cost — if cost per user is rising, there is a scaling architecture problem
ROI needs a pessimistic scenario — if the investment goes negative under realistic downside assumptions, it is risky
Opportunity cost belongs in the model — time spent building is time not spent on revenue features

Reference Files

references/estimation-tco-build-vs-buy.md — compute/storage/network/managed service cost estimation, 5-category 3-year TCO structure (license + infrastructure + operations + training + migration), build vs. buy decision criteria and 3-year quantification, and per-seat/usage-based/flat-rate/hybrid pricing model comparison
references/roi-growth-breakeven.md — ROI formula and time-to-ROI calculation, sensitivity analysis (+/- 20% assumptions), linear/sublinear/superlinear cost growth modeling, cost-per-unit trending, cost optimization checkpoint thresholds, and breakeven crossover chart methodology for build-vs-buy and migration decisions

role-architect:cost-modeling

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

role-architect:cost-modeling

Popularity

Invocation

Tool Access

Context Preview

Supporting Files

SKILL.md

Cost Modeling

When to use

Core principles

Reference Files

Similar Skills

Help us improve

Cost Modeling

When to use

Core principles

Reference Files