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/tiered-value-structures.md

View on GitHub
# Tiered value structures

Tier 1 free, Tier 2 email-gated, Tier 3 account-gated. Worked examples.

The architecture that lets calculators capture leads honestly. The user gets immediate value (free tier) and is offered progressively richer value at each tier with proportional friction. Each tier earns its gate.

---

## The tier-design principle

Each tier should add real value over the previous. Tiers that gate the same content at higher friction destroy trust.

**Tier 1 (no gate).** Immediate, complete result. The audience gets what they came for. The free tier is not a teaser; it is the substantive output of the calculator.

**Tier 2 (email-gated).** Additional value the user might want for sharing, persistence, or depth. Email is the appropriate friction level for this value.

**Tier 3 (account-gated).** Persistent, multi-session, collaborative, or product-integrated value. Account creation is the appropriate friction level for this value.

Each tier's friction matches its value-add. Tiers that ask for more friction than they justify destroy conversion.

---

## Tier 1: free immediate result

What lives at Tier 1.

**The calculator's primary output.** The headline result the user came for. Annual savings, recommended plan, monthly cost, time to payback.

**The breakdown.** Components that show how the headline was calculated.

**Basic visualization.** A chart or comparison that helps the user see the relationship.

**Methodology disclosure.** Either inline formulas or a methodology link.

**Assumption list.** What the calculator assumes about the user's situation.

**Source citations.** Where the calculator's benchmarks come from.

The Tier 1 set is complete. A user who never opts into Tier 2 still got the calculator's full value. The brand still earns trust; the audience still associates the brand with the topic.

**What Tier 1 should NOT include.**

- A teaser version of the result that withholds the actual answer.
- A "preview" of the analysis that requires email to see in full.
- Marketing copy that displaces the result itself.

---

## Tier 2: email-gated additional value

What lives at Tier 2.

**A formatted PDF report.** The Tier 1 content packaged in a shareable format. The PDF has to be genuinely better than a screenshot, or the gate is not justified.

**A saved scenario.** The user's inputs and result persist; they can return to the calculator and see their previous calculation.

**A custom analysis.** A deeper second-pass calculation, often delivered by email after submission.

**Notification opt-in.** Updates when benchmarks change, when new calculator versions launch, or when the brand publishes related content.

**Tier 2 design discipline.**

- Each Tier 2 offering must clearly justify the email exchange. "Get a PDF that you can share with your CFO" is justifiable; "Get the same content in a PDF" is not.
- The email-capture form should appear in context with the offer, not as an interruption to the Tier 1 viewing.
- The follow-up email should deliver the promised value immediately, not delay it.

---

## Tier 3: account-gated persistent value

What lives at Tier 3.

**Save-and-compare across multiple scenarios.** The user models 5 different configurations and compares them side-by-side. Account-level persistence supports this.

**Historical tracking.** When the calculator is used periodically (monthly projection, quarterly review), the user's historical inputs and results are tracked over time.

**Collaboration features.** Multiple users on the same account can model scenarios together.

**Product integration.** The calculator's output flows into the user's account on the brand's platform; the calculation becomes part of an ongoing workflow.

**Tier 3 design discipline.**

- Account creation is significant friction. Tier 3 features must justify it.
- Tier 3 is often unnecessary. Many calculators serve their purpose with Tier 1 and Tier 2 alone; do not add Tier 3 unless the use case warrants it.
- Account-creation friction can be reduced (social login, magic link) but not eliminated.

---

## Worked example: SaaS pricing calculator

A B2B SaaS platform considering a tiered pricing calculator.

**Tier 1 (free).**

- The user enters team size, role distribution, and use case.
- Sees the recommended plan and the estimated monthly cost.
- Sees a breakdown showing per-seat cost, included features, and any add-ons.
- Sees a comparison against the next-tier-up plan with a brief explanation of when it would be worth it.
- Sees a methodology link explaining how recommendations are made.

**Tier 2 (email-gated).**

- A PDF showing the recommended plan, the breakdown, the next-tier comparison, and 2-3 customer case studies of similar teams using similar plans.
- The PDF is shareable and contains enough context for an internal stakeholder to evaluate.

**Tier 3 (account-gated).**

- The user can save the scenario and adjust inputs over time as the team grows.
- The user can model alternative scenarios (different team size, different use case) and compare side-by-side.
- The user can receive an email when their team size threshold suggests a tier change.

Each tier earns its gate. The user can stop at Tier 1 and still get value. Tier 2 is offered as a way to share with stakeholders. Tier 3 is offered for users who want ongoing tracking.

---

## Worked example: ROI calculator for a B2B service

A B2B service company considering an ROI calculator.

**Tier 1 (free).**

- The user enters current cost, team size, and process maturity.
- Sees estimated annual savings.
- Sees a breakdown across cost reduction, productivity gains, and implementation savings.
- Sees the methodology disclosed inline.

**Tier 2 (email-gated).**

- A PDF showing the calculation in defensible form, with industry-context comparison and a worked-example case study from a similar customer.

**Tier 3.** Not offered. The calculator is single-use; account creation would be unnecessary friction.

The two-tier structure fits the use case. Adding Tier 3 would add friction without value.

---

## Worked example: financial calculator (mortgage, refinance, savings)

A financial services company considering a savings calculator.

**Tier 1 (free).**

- The user enters current loan details, target rate, and timeline.
- Sees estimated monthly savings, total savings over the loan term, and break-even point on closing costs.
- Sees the breakdown and methodology.

**Tier 2 (email-gated).**

- A PDF analysis with comparison across multiple lender scenarios.
- A personalized rate quote (which requires underwriting based on user inputs).

**Tier 3.** Optional. An account that tracks the user's loan over time and notifies them when refinance opportunities emerge as rates change.

The Tier 2 includes genuine value-add (personalized quote requires underwriting). The Tier 3 is optional for users who want ongoing monitoring.

---

## Tier-design failures

Patterns that look like tiered value but degrade trust.

**Teaser-tier-as-Tier-1.** The free tier shows a partial result; the email tier shows the full result. This is lead-trap dressed as tiered value.

**Same-content-different-format.** Tier 1 is the result on screen; Tier 2 is the same result in a PDF. The PDF is not value-add; the gate is not justified.

**Inverted tiers.** Tier 1 is thin; Tier 2 is what should have been Tier 1; Tier 3 is what should have been Tier 2. The audience that gets Tier 1 sees nothing useful; conversion drops.

**Tier-3 friction without Tier-3 value.** Account creation required for features that could have been email-only or free. Friction without value-add destroys the gate.

**Surprise upsells.** The user opts into Tier 2; the email follow-up reveals additional gates the user did not anticipate. Trust drops.

---

## The flat-tier alternative

Some calculators do not need tiers.

**When flat is right.**

- Simple calculators where the result is the only output worth offering.
- Calculators built for SEO or brand authority where lead capture is secondary.
- Calculators where account creation does not match the use case.

**The flat structure.** Tier 1 (free, complete result). Optional email opt-in for newsletter or related content (no gate, no friction).

This structure works when the calculator's primary value is the calculation itself and the lead-capture motion is secondary or absent.

---

## Tier transitions

How the user moves from tier to tier.

**Tier 1 to Tier 2.** The user sees the free result. Below or alongside, an offer: "Want this as a PDF you can share?" or "Save this scenario for later." Email-capture in context.

**Tier 2 to Tier 3.** After the user has engaged with Tier 2 (downloaded the PDF, returned to the saved scenario), an offer: "Want to track this over time? Create an account." The friction increase is justified by the additional value.

**The discipline.** Tier transitions should feel natural, not pushy. The user gets value at each tier; the next tier is offered, not demanded.

---

## Tier maintenance

Tiers decay along with the calculator.

**Tier 1 maintenance.** Update defaults, refresh sources, update methodology as benchmarks shift.

**Tier 2 maintenance.** Update PDF templates as the brand evolves; refresh case studies; update comparison data.

**Tier 3 maintenance.** Maintain the account-side functionality; ensure persistence works; update integrations.

**The retire-tier decision.** Tier 3 features that are not used can be retired. Tier 2 PDFs that no one downloads can be simplified. Periodic audit of tier usage informs maintenance.

---

## Common tier failures

**Tier 1 is a teaser.** Lead-trap pattern.

**Tier 2 does not justify the email.** Same content, repackaged.

**Tier 3 is offered but unused.** Friction without payoff; sometimes the right answer is to retire Tier 3.

**Tier transitions are pushy.** Aggressive popups at each transition; the user feels pressured.

**Tier maintenance lapses.** Stale PDFs, broken account features, outdated comparison data.

---

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

The tier-design principle. What lives at each tier. Tier-design discipline at each level. Worked examples across calculator types. The flat-tier alternative. Tier transitions. Tier maintenance. Common failures.

## Implementation choices that stay internal

Specific tier structures for specific calculators. Specific PDF templates and account-creation flows. Specific tooling for tier transitions. The team's tier-usage measurement and audit calendars. 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