Skip to content

rampstackco/claude-skills / skills/product-configurator-design

product-configurator-design

Verified

Designing build-your-own product configurators (Tesla-style, custom-pricing, plan-builders) with constraint logic, real-time pricing, validation, and save-and-share mechanics. Honest about infinite-options (decision paralysis), canned-bundles-only (no real customization), and guided-configuration (smart defaults plus meaningful constraints plus escape hatches) patterns. Triggers on configurator design, build-your-own, custom configuration, plan builder, product customizer, configuration tool. Also triggers when users abandon mid-configuration, when configurator conversion is poor, or when a configurator is being scoped for the first time.

references/configurator-decision-criteria.md

View on GitHub
# Configurator decision criteria

When configurators earn the build vs when bundles serve.

A configurator is meaningful work. Constraint logic, real-time pricing, validation, save-and-share, cart handoff, ongoing maintenance. The configurator earns this investment only when specific conditions are present.

---

## When configurators earn the build

Five conditions that, when present, make a configurator a strong investment.

**The product has genuinely customizable parameters that affect outcome and cost.** Not just cosmetic options; real parameters that change what the user gets.

**The audience values customization beyond what bundles offer.** Some audiences want choice; others prefer curated bundles.

**The team can support the configuration logic.** Validation, pricing, fulfillment for variable configurations.

**The combinatorial space is meaningful but constrained.** Not literally infinite; not so small that bundles would suffice.

**The success metric is defined.** Configuration completion rate, configuration-to-purchase rate, average configuration price.

When all five are present, a configurator is strong investment. When two or fewer are present, bundles often serve better.

---

## When configurators do NOT earn the build

Funnels where configurators add complexity without lift.

**The product is essentially bundles.** Calling them configurations is marketing.

**The audience prefers curated options.** Some audiences resent customization friction.

**The combinatorial space is too large.** No audience can navigate.

**Customization produces invalid combinations.** Team cannot prevent; users hit failures.

**A simpler tool would serve.** Comparison, calculator, or selection tool.

The honest assessment matters. Configurators are sometimes the wrong tool.

---

## Configurators vs bundles

When each fits.

**Bundles strengths.** Simple; clear; no decision paralysis. Easy to maintain.

**Bundles weaknesses.** Audiences that need customization underserved.

**Configurators strengths.** Match real customer needs; capture revenue from edge cases.

**Configurators weaknesses.** Build cost; complexity.

**The combined approach.** Some products offer bundles AND a configurator for users who want custom.

---

## The opportunity-cost frame

Configurators are significant work.

**Build cost.** Constraint logic, pricing engine, save-and-share, validation, cart integration. 60-200 engineering hours typical.

**Maintenance cost.** Product changes trigger configurator updates. 4-12 hours per quarter.

**Opportunity cost.** Better bundles, comparison tool, calculator. The configurator has to clear those alternatives.

The decision frame. Configurators earn investment when they produce more revenue than bundle-only or alternative formats.

---

## Decision worked example

A B2B SaaS with seat-based + add-on pricing.

**Conditions check.**

- Genuinely customizable: yes (seats, add-ons, integrations).
- Audience values customization: yes; team size and add-ons vary.
- Team can support: yes.
- Combinatorial space: meaningful but constrained.
- Success metric: defined.

**Decision.** Build the configurator.

The decision was deliberate.

---

## Decision worked example: when bundles serve

A consumer SaaS with three plans.

**Conditions check.**

- Genuinely customizable: no; plans are bundles.
- Audience values customization: no; users pick plans.
- Combinatorial space: trivial.

**Decision.** Bundles. No configurator needed.

The decision was right-sized.

---

## When to retire a configurator

Configurators can become wrong over time.

**Retire when:**

- Conversion declined and refinements have not moved it.
- Most users default-and-purchase; customization unused.
- Product changed; configurator no longer matches.

The retire-or-redesign discipline frees capacity.

---

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

The five conditions for configurators. The five against. Configurators vs bundles. Opportunity-cost frame. Decision worked examples. The retire decision.

## Implementation choices that stay internal

Specific configurator decisions for specific products. Capacity benchmarks. Tooling. 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: 323kUpdated 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