Skip to content

rampstackco/claude-skills / skills/calculator-design

calculator-design

Verified

Designing 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.

references/calculator-anti-patterns.md

View on GitHub
# Calculator anti-patterns

The patterns that look like calculators but degrade trust. Anti-patterns are easy to ship; the cost shows up in lead quality, downstream conversion, and brand reputation over time.

---

## The lead-trap

The pattern. The user enters inputs, hits Calculate, sees "enter your email to see your result."

The signal. Conversion-rate metric on the email form looks fine; downstream conversion is near zero; the audience that recognizes the pattern bounces immediately.

The cost. The leads captured are unqualified or actively annoyed. The brand earns "lead-trap" reputation; trust erodes across all future interactions.

The cure. Restructure so the result is free and the additional value (PDF, save-and-compare, custom analysis) is gated. Detail in `references/email-capture-decision-tree.md`.

---

## The vanity output

The pattern. A number that looks impressive but does not help any real decision. "Your marketing efficiency score is 87." 87 of what? Compared to what?

The signal. Audiences run the calculator out of curiosity; do not return; do not cite the result anywhere; do not engage with the follow-up sequence.

The cost. The calculator's build cost was wasted. The audience does not associate the brand with useful analysis.

The cure. Anchor the result to a decision the audience actually makes. The output should be a number with units, contextualized against a baseline, with a clear next step.

---

## The hidden-methodology calculator

The pattern. No way to see the math. No methodology page. No assumption list. The audience uses the tool, gets a number, and cannot defend it.

The signal. Sales-team friction; prospects who used the calculator cannot bring its outputs into stakeholder conversations.

The cost. The calculator does not compound credibility. Each user runs it once and does not return; the brand stays invisible in the audience's actual decision conversations.

The cure. Disclose methodology. Detail in `references/calculation-logic-transparency.md`.

---

## The interrogation form disguised as calculator

The pattern. 18 input fields, of which 5 affect the math. The form is collecting sales-qualification data under cover of calculation.

The signal. Conversion rate on the form is poor. The audience self-selects out at the form length.

The cost. The calculator's reach drops dramatically. The leads that do convert are over-disclosed and may resent the friction; the audience the calculator could have served does not get to use it.

The cure. Audit the input set. Remove fields that do not affect the calculation. Capture additional data later in the relationship, not at the form.

---

## The misleading-baseline calculator

The pattern. "Industry Average" or "Typical Customer" baselines that are flattering to the brand and unsourced.

The signal. Audiences with industry knowledge notice the gap. Those audiences do not return; they may post about the bias publicly.

The cost. Trust damage that can be hard to recover. Brand earns "spin" reputation.

The cure. Source the baselines honestly. Use defensible benchmarks; if the brand's data is favorable, disclose that the data comes from the brand's own customer cohort and acknowledge the bias.

---

## The misaligned-units calculator

The pattern. "Estimated savings: 14X" without a base value. Or "60 percent improvement" without saying improvement in what.

The signal. Audiences cannot interpret the result; cannot use it in their decision; do not return.

The cost. The calculator's outputs are uninterpretable; the calculator does not produce decision-grade signal.

The cure. Numbers with units. Percentages with bases. Multipliers with reference values. Contextualization that makes the result interpretable.

---

## The static-assumption calculator

The pattern. Assumptions hardcoded in 2022 that have not been updated. Industry benchmarks from 2 years ago. Tooling references to products that have been deprecated.

The signal. Audiences with current knowledge see the staleness; trust drops; some users may report the inaccuracy.

The cost. The calculator's outputs are unreliable. The brand looks careless or out of touch.

The cure. Quarterly maintenance review. Update assumptions, refresh benchmarks, prune stale references.

---

## The mobile-broken calculator

The pattern. Calculator works fine on desktop; breaks on mobile. Sliders impossible to grab; dropdowns overflow; result hidden below the fold.

The signal. High mobile bounce rate; mobile conversion drops below desktop.

The cost. The mobile audience either bounces or has a worse experience that misrepresents the brand. Mobile is often the majority of traffic; this failure is significant.

The cure. Mobile-first design and testing. Test on actual devices, not just dev tools. Detail in `references/input-design-patterns.md` (mobile section).

---

## The over-precise calculator

The pattern. Result shown as "$14,237.42" when the inputs justify only "$14,000 (estimated)." False precision suggests the calculator knows more than it does.

The signal. Analytical audiences see the false precision and discount the result. The calculator earns "fake math" reputation among the audience that matters most.

The cost. Trust erosion specifically among the audience the calculator was designed to serve.

The cure. Round to honest precision. Use "estimated" or "approximately" framing. Disclose the precision the inputs support.

---

## The marketing-disguised-as-methodology calculator

The pattern. The methodology page exists but contains marketing copy ("our proprietary algorithm draws on industry-leading data") rather than actual formulas, sources, or assumptions.

The signal. Audiences who click through to verify find no real verification; trust drops.

The cost. The calculator's credibility is performative rather than real; the audience that interrogates discovers the gap.

The cure. Real methodology. Formulas, assumptions, sources. Brand voice can frame the methodology page; brand voice cannot replace the methodology itself.

---

## The orphan-result calculator

The pattern. The result loads; no next step is offered. The user gets the number and leaves.

The signal. Conversion to next step (PDF, save, contact, demo) is near zero because no next step is offered.

The cost. The calculator captures attention without converting it. The brand has the audience's moment of intent and does nothing with it.

The cure. Offer a clear next step at the result. PDF, save scenario, talk to team, related resource. Detail in `references/result-presentation-patterns.md` (result-to-action transitions).

---

## The popup-interrupted calculator

The pattern. The result loads; the user starts reading; a popup appears asking for email or offering a different magnet. The user's flow breaks.

The signal. Bounce rate spikes at the popup moment; users complain about the interruption.

The cost. The calculator's user experience is hostile. The brand earns "annoying" reputation.

The cure. Offers in context with the result, not as popups that interrupt. Detail in `references/result-presentation-patterns.md`.

---

## The cookie-cutter calculator

The pattern. The calculator looks and behaves like every other calculator from a template platform. Generic UI, generic assumption set, generic output styling.

The signal. The calculator does not differentiate; the audience does not associate it specifically with the brand.

The cost. The calculator becomes commodity; the brand's investment does not compound credibility because the tool does not stand out.

The cure. Custom design that reflects the brand. Methodology that reflects the brand's specific authority. The calculator should look like it could only have come from this brand.

---

## The pessimistic-default calculator

The pattern. Defaults set to make the brand's outputs look favorable through pessimistic baselines. "Current cost" defaults to the high end; "savings" defaults to the optimistic end.

The signal. Audiences who notice (often analytical audiences) discount the result. The audience the calculator was built for stops trusting it.

The cost. Same as misleading-baseline. Trust damage; brand earns "spin" reputation.

The cure. Honest defaults sourced from data; let the user adjust to their actual context.

---

## The form-without-calculator

The pattern. A "calculator" that is actually a form. No real calculation; the result is generic ("based on your inputs, our team will reach out") or static ("your estimated savings: 30 percent").

The signal. Audiences expecting a real calculation get a sales form; bounce rate spikes; the audience perceives bait-and-switch.

The cost. The calculator's framing was a lie; trust collapses.

The cure. Either build a real calculator with real math, or do not call the form a calculator.

---

## How to detect anti-patterns in a portfolio

Audit cadence. Quarterly review of every active calculator, looking specifically for these anti-patterns.

**Audit questions per calculator.**

- Is the result accessible without email gate (anti-pattern check: lead-trap)?
- Is the methodology disclosed in a way the audience can verify (anti-pattern check: hidden-methodology)?
- Are the inputs all necessary for the calculation (anti-pattern check: interrogation-form)?
- Are the baselines and benchmarks sourced and current (anti-pattern check: misleading-baseline, static-assumption)?
- Does the calculator work on mobile (anti-pattern check: mobile-broken)?
- Is the result actionable, with a clear next step (anti-pattern check: orphan-result)?
- Does the calculator differentiate from other calculators on similar topics (anti-pattern check: cookie-cutter)?

**The retire decision.** Anti-pattern calculators often warrant retirement. Maintaining them costs more than the diminishing returns they produce.

---

## Methodology-level choices that stay in the public skill

The catalog of anti-patterns. Signal-pattern-cost framing for each. Cures matched to anti-patterns. The audit cadence and audit questions. The retire decision.

## Implementation choices that stay internal

Specific anti-patterns the team has shipped historically and the lessons learned. Specific portfolio audit results. Specific retirement decisions and successor-tool plans. The team's audit calendar and reviewer list. These vary by team.
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: 322kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall