rampstackco/claude-skills / skills/calculator-design
calculator-design
VerifiedDesigning interactive calculators (ROI calculators, pricing estimators, savings projections, mortgage calculators, custom assessments) that deliver real decision-support value while serving as lead magnets and qualified-traffic generators. Honest about vanity-calculator (no real value), lead-trap (hides the answer behind email), and transparent-decision-tool (gives the result and earns the email through tiered value) patterns. Triggers on calculator, ROI calculator, pricing estimator, savings calculator, custom calculator, interactive tool, decision tool, financial calculator. Also triggers when an audience needs a calculation-driven lead magnet, when a vanity calculator is producing leads but no qualified ones, or when a calculator is being scoped for the first time.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 358 B |
| SKILL.md | skill md | 23.2 KB |
| references/calculation-logic-transparency.md | markdown | 11.4 KB |
| references/calculator-anti-patterns.md | markdown | 10.1 KB |
| references/calculator-investment-criteria.md | markdown | 9.8 KB |
| references/common-calculator-failures.md | markdown | 9.1 KB |
| references/email-capture-decision-tree.md | markdown | 10.6 KB |
| references/input-design-patterns.md | markdown | 10.7 KB |
| references/methodology-disclosure-templates.md | markdown | 10.4 KB |
| references/result-presentation-patterns.md | markdown | 10.6 KB |
| references/tiered-value-structures.md | markdown | 10.3 KB |
references/calculation-logic-transparency.md
View on GitHub# Calculation logic transparency
Methodology disclosure options. Inline formulas, methodology pages, source citations, assumption lists. The defensibility of the result is the calculator's credibility currency.
A calculator's output is only as trustworthy as the audience's ability to inspect how it was computed. Calculators that hide methodology produce numbers; calculators that disclose methodology produce defensible numbers. The difference shows up in whether the audience cites the calculator in stakeholder conversations.
---
## The transparency principle
The audience should be able to inspect the methodology if they care.
Three levels of transparency, in increasing depth.
**Level 1: Inline.** The methodology appears in the calculator itself, near the result. "Your annual savings: $14,200 = (current cost x 12) - (estimated new cost x 12) + first-year implementation savings of $X."
**Level 2: Methodology page.** A linked page explaining the formulas, assumptions, and sources in detail. The result page links to it; users who want depth find it.
**Level 3: Spec on request.** The team is willing to share the underlying spec, customer-data sources, or formula derivations on request. Useful for analytical or enterprise audiences who want full inspection.
A calculator should at minimum support Level 1 or Level 2. Level 3 is optional and signals analytical credibility.
---
## Inline formulas
Show the math near the result.
**The pattern.** Below or alongside the headline result, show the formula that produced it.
**Example: ROI calculator inline formula.**
```
Annual savings: $14,200
Calculation:
Current annual cost: $36,000 ($3,000 / month x 12)
Estimated new annual cost: $24,000 ($2,000 / month x 12)
Annual savings: $36,000 - $24,000 = $12,000
+ First-year implementation savings: $2,200
Total: $14,200
```
**The win.** The audience can verify the math. They can adjust their inputs and predict how the result will change. They can defend the result to a stakeholder by citing the formula.
**When to use inline formulas.** When the calculation is straightforward enough to display in a few lines. Most ROI, savings, and pricing calculators fit this pattern.
**When inline formulas hurt.** When the calculation is so complex (multi-stage, with branching) that the formula display overwhelms the result. In those cases, link to a methodology page instead.
---
## Methodology page
A linked page explaining the calculation in depth.
**The pattern.** The result page includes a "How this is calculated" or "Methodology" link. The link opens a page with formulas, assumptions, and sources.
**What a methodology page should include.**
- The central formulas in plain text (not just images).
- Each variable defined.
- Each assumption listed plainly. "We assume a 3-month implementation period." "We assume the user is comparing month-over-month."
- Sources for any external benchmarks. "Industry Average: 14 percent. Source: [Industry Benchmark Report 2025]."
- Worked example. A specific scenario with input values and the resulting calculation.
- Caveats. "This calculator does not account for [X]; for that, see [other resource]."
**The methodology page test.** A skeptical reader of the methodology page should come away thinking "this is reasonable" or "I disagree with assumption Y, here is why." Either response is a sign the methodology is real and the audience can engage with it.
**Methodology pages and SEO.** Methodology pages can themselves rank for search terms ("how is X calculated"), bringing additional traffic to the calculator. The page is not just transparency; it is also a content asset.
---
## Source citations
When the calculator uses external benchmarks or data, cite the source.
**The pattern.** "Industry Average: 14 percent. Source: [Industry Benchmark Report 2025, page 23]."
**Why source citations matter.** They signal that the benchmark is real, not invented. They let the skeptical user verify. They protect the brand if the benchmark is later disputed.
**Citation discipline.**
- Cite the most authoritative source available (industry report, academic paper, published study).
- Date the source. Benchmarks decay; an undated source could be from any year.
- Link to the source where possible. Inaccessible sources (paywalled reports cited from memory) are weaker than linked sources.
- If the source is internal customer data, say so. "Source: [Brand]'s customer cohort, n=200, 2024-2025." Internal sources are valid; honesty about their origin matters.
**The uncited-benchmark failure.** "Industry Average: 14 percent" with no source. The audience that knows the industry sees the gap; the audience that does not know rolls the dice on whether to trust. Either way, credibility leaks.
---
## Assumption lists
A plain-language list of what the calculator assumes.
**The pattern.** Either inline (near the result) or on the methodology page, list the assumptions in plain English.
**Example assumption list for a SaaS pricing calculator.**
- "We assume your team will use the platform daily."
- "We assume implementation takes 4-6 weeks."
- "We assume the productivity gains compound through year 1 and stabilize in year 2."
- "We assume your current solution costs include licenses, hosting, and 1 FTE for maintenance."
- "We do not account for [specific factors] in this estimate."
**Why assumption lists matter.** They make the calculator's worldview visible. The audience can see whether the assumptions match their situation. If the assumptions diverge, the audience knows to discount the result accordingly.
**Honest assumptions vs flattering assumptions.** Honest assumptions reflect the typical case; flattering assumptions reflect the case that produces the most attractive output. Audiences that catch flattering assumptions stop trusting the calculator.
**The assumption-decay problem.** Assumptions need updating as the world changes. A calculator with assumptions from 2022 may have outdated benchmarks; review quarterly.
---
## The methodology-authority spectrum
Calculators sit on a spectrum from "fully transparent" to "fully opaque." Each position has tradeoffs.
**Fully transparent.** All formulas, all assumptions, all sources visible. The audience can fully reconstruct the calculation. Trust is maximum; competitive risk (others copying the methodology) is highest.
**Largely transparent.** Major formulas visible; minor weighting or proprietary elements glossed. The audience trusts the result; the brand keeps some IP. Common middle ground.
**Methodology-page transparent.** The result is shown without inline formulas; the methodology page has the depth. The audience that cares finds the depth; the audience that does not, does not have to.
**Opaque.** No methodology shown. The audience either trusts the brand or not; there is no inspection path. High competitive protection; low audience trust.
The right position depends on the audience and the goal. Analytical audiences (engineers, finance teams, technical buyers) need transparency to trust. Less-analytical audiences may accept opacity if the brand has earned trust through other means. Most calculators benefit from at least Level 2 (methodology page) transparency.
---
## When the calculation cannot be fully disclosed
Some calculations include proprietary IP. Honest framing matters.
**The honest framing.** "The output combines public benchmark data with proprietary insights from our customer cohort. Public elements are detailed in the methodology page; the proprietary weighting reflects our own data and is not detailed here."
**The dishonest framing.** Hiding the proprietary nature; presenting opaque outputs as if they came from public methodology.
**The audience's reaction.** Honest framing about proprietary IP is usually accepted. The audience understands that some IP is protected; they appreciate the honesty about what is shown and what is not. Dishonest framing breaks trust when the audience tries to interrogate and finds nothing.
**The discipline.** Disclose what can be disclosed. Honestly label what cannot. The combination earns more trust than full opacity or false transparency.
---
## Methodology display patterns
How to integrate methodology into the calculator's UI.
**Pattern A: Always-visible inline formulas.** The result and the formula appear together. Best for short calculations where the formula is digestible.
**Pattern B: Expandable methodology details.** The result appears prominently; "How this was calculated" is an expandable section below. The user opens it if they want depth.
**Pattern C: Methodology link to a separate page.** The result is shown; the methodology page is linked. Good for complex calculations that need full discussion.
**Pattern D: Hover-revealed assumption tooltips.** Each variable in the result has a tooltip explaining how it was derived. Useful when the calculation has many components.
**Pattern E: Methodology in PDF report.** The free result shows the headline; the gated PDF contains the full methodology. This pattern works when the PDF is genuinely the value-add and the headline result is enough for free users.
The choice depends on calculator complexity, audience analytical depth, and the brand's transparency posture.
---
## Common transparency failures
**No methodology shown.** Result is a number; user has no way to verify or defend it.
**Hidden assumptions.** Inputs and outputs visible; assumptions baked into the math without disclosure.
**Uncited benchmarks.** "Industry Average: 14 percent" with no source.
**Stale assumptions.** Methodology written in 2022, never reviewed.
**Flattering defaults.** Defaults set to produce favorable outputs; the audience that catches the bias stops trusting.
**Methodology page that hides more than it reveals.** Marketing copy disguised as methodology; no actual formulas or sources.
**Inconsistent precision.** Result shown as "$14,237" when the inputs justify only "$14,000 (estimated)." False precision erodes trust.
**No version history on methodology.** Methodology page changed over time without record; users who relied on previous outputs cannot tell what changed.
---
## The credibility compounding effect
Transparent calculators compound credibility.
**The mechanism.** The audience uses the calculator, gets a defensible result, cites it in their decision-making conversation. The brand is in the conversation. The audience returns to the calculator for related decisions. The brand's authority on the topic deepens.
**The opposite.** Opaque calculators do not compound. The audience uses the calculator, gets a number they cannot defend, leaves it out of their stakeholder conversation. The brand is invisible. The audience does not return.
**The metric.** Track whether the calculator is being cited. Mentions in customer conversations, references in industry discussions, backlinks from other content all signal compounding credibility.
---
## Methodology-level choices that stay in the public skill
The transparency principle and the three levels. Inline formulas, methodology pages, source citations, assumption lists. The methodology-authority spectrum. Honest framing for proprietary calculations. Methodology display patterns. Common transparency failures. The credibility compounding effect.
## Implementation choices that stay internal
Specific methodology pages for specific calculators. Specific source citations and benchmark relationships. Specific tooling for methodology display. Specific brand-voice methodology copy. The team's update calendars and version control for methodology. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies 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. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |