Pricing & Packaging Strategist

What it does

Produces an end-to-end value-based pricing strategy document for your product, built on three pricing axes: Packaging (what's in each tier), Pricing Metric (what you charge for) and Price Point (the actual amount). It anchors price to delivered value, not cost — positioning it between the perceived-value ceiling and the next-best-alternative floor, with cost-to-serve as a baseline only.

It first selects the right value metric (per seat, per usage, per record/contact, per transaction or flat) and applies the test "as a customer uses more of this metric, do they get more value?". It then builds a Good-Better-Best tier structure: the entry tier drives trial and defends the low end, the middle tier is the volume workhorse and anchor price, and the premium tier captures economics while making the middle tier look like the best value via decoy/anchoring. Tiers are clearly differentiated through feature gating, usage limits, support level and access (API/SSO).

When to use it

• Building a pricing page / tier structure from scratch
• Moving from a single plan to a multi-tier model
• Reacting to "too cheap / my pricing is wrong" signals, or planning a price increase
• Evaluating a shift to a new value metric (e.g. seats to usage)
• Annual vs monthly, freemium vs free-trial, enterprise-tier decisions

Method / frameworks

• Three Pricing Axes — Packaging / Pricing Metric / Price Point.
• Value-Based Pricing — price between alternative and perceived value.
• Value Metric selection — scales with value, easy to understand, hard to game.
• Good-Better-Best — three-tier architecture using Goldilocks/anchoring + decoy.
• Van Westendorp PSM — four questions to find the acceptable price band.
• MaxDiff — which features matter most, feeding tier packaging.
• Price-increase signals — >40% conversion, <3% churn, "too cheap" feedback; grandfather / delayed / value-tied / restructure strategies.
• Pricing-page psychology — anchoring, decoy, charm vs round pricing, 17-20% annual discount.

Output is always produced as a machine-readable output.json plus a visual output.html for the marketplace.