← ClaudeAtlas

pricing-calculator-builderlisted

Build a live, interactive pricing calculator or decision model as a spreadsheet — toggle-driven scenarios, cost/price curves, a hard floor clamp, and a capped lever stack. ALWAYS use this skill when Farhan is building a pricing MODEL, CALCULATOR, decision model, interactive pricing spreadsheet, margin/floor calculator, a per-unit rate card with volume bands, or a toggle between pricing scenarios (per-game vs per-league, per-seat vs usage, monthly vs annual). Trigger on "build a pricing calculator", "a model where I can toggle X vs Y", "a sheet that clamps to the floor", "margin calculator", "rate card with volume discounts", or when he's iterating on the numbers in an existing model. This produces the WORKING SPREADSHEET. When he wants the recommendation, memo, or comp plan (the argument), use pricing-proposal-builder instead — the two pair, and the calculator feeds the proposal.
f13i/pricing-calculator-builder · ★ 0 · AI & Automation · score 70
Install: claude install-skill f13i/pricing-calculator-builder
# Pricing Calculator Builder This builds the *tool*, not the argument. `pricing-proposal-builder` produces the recommendation a CEO reads; this produces the live spreadsheet Farhan (and often the client's operator) drives — the one with a toggle cell, a cost/price curve, and a floor that can't be breached no matter what discounts stack. They pair constantly: on the AirPLAi rec-league deal he built a 7-tab decision model *and* a strategy memo in the same session. When both are needed, build the calculator first — its numbers feed the proposal. The reason a calculator is its own deliverable: a memo asserts a price; a calculator lets someone *move the levers and watch what breaks*. Its whole value is exposing the margin squeeze that a static table hides. If the model quietly protects the user from ever seeing the floor get hit, it has failed at the one thing it exists to do. ## Before you build: load the context 1. **The deal file** — `30-deals/<client>/index.md` (obsidian tools). Prior pricing decisions, current cost basis, what the client actually sells, who decides. 2. **Any prior model** — if you're iterating, read the existing sheet's structure before changing it, so you don't strand cell references (see the modeling laws). 3. **The lessons log** — `20-agents/07-lessons.md`, section `client-intel / pricing-models`. These are hard-won corrections from past model builds; read them as pre-flight checks. 4. **Pricing philosophy** — `10-brain/02-business.md` if the client's