Packaging architecture

What is packaging architecture?#

Packaging Architecture (sometimes called product configuration) is the strategic design of what you sell, distinct from price setting, which determines how much you charge. It is the process of grouping features, services, and commercial terms into sellable units (offers) that align with specific customer segments and their willingness to pay (WTP).

• Packaging architecture vs Pricing:

  • Packaging determines what the customer gets, while pricing determines how much they pay.
  • It is important to distinguish the price (the number) and the architecture (how you organize what you sell). For founders, the money is often found not in optimizing the price point, but in optimizing the architecture.

• Packaging vs Offer:

  • While "packaging" is the "design" phase and the internal strategy, the "offer" is the external presentation.
  • The offer is the final, market-facing proposition presented to the customer. It is the combination of the package (features), the price model, and the price point.

Key definitions#

• Leader/Filler/Killer Features: To design a package, you must classify every feature into one of three categories. Never put a "Killer" in a mass-market package. Use "Leaders" to differentiate tiers.

  • Leaders: Must-have features that drive the purchase decision and high willingness to pay.
  • Fillers: Nice-to-have features that add perceived value/bulk but don't drive the sale.
  • Killers: Features that actively turn customers away or devalue the offer (e.g., forcing a complex enterprise feature on a small business).

• Good/Better/Best (G/B/B) Tiers: The gold standard for packaging. It involves creating three (sometimes four) distinct tiers: "Good" (entry-level/price-sensitive), "Better" (mass market), and "Best" (premium/specialized). It utilizes the "compromise effect" and the "decoy effect" to encourage customers to settle on the middle option, maximizing revenue.

• Pricing metric / value metric: The unit by which you charge (e.g., per user, per gigabyte, per transaction, per API call, per $ processed). It is the single most consequential decision in pricing. It must align with how the customer derives value. If the metric is wrong (e.g., charging per user when value is derived from data usage), it creates friction and limits growth.

• Plan/Tier/Version vs Bundle:

  • Plan/Tier/Version (Vertical Segmentation) is designed to separate customers based on their needs and WTP for essentially the same core value proposition. Customers typically select one tier. This strategic process is often referred to as Product Configuration or Laddering.
  • Bundle (Horizontal Aggregation) is selling multiple distinct products or services together as a single package to increase total profit and simplify the purchase decision. While a tier technically "bundles" features, true bundling usually refers to combining separate standalone offerings (e.g., Microsoft Word + Excel = Office Bundle, or Pizza + Breadsticks = Meal Deal).
  • Distinction: Plan/Tier/Version is a vertical strategy to segment customers based on willingness to pay (WTP) for a single product, while Bundling is a horizontal strategy to aggregate distinct products or features to maximize total revenue or simplify purchasing. A typical structure of Plan/Tier/Version is Good/Better/Best, while Bundle is Core + Add-ons or Multi-product Suite.

• Plan/Tier/Version vs Add‑on/Module:

  • Add‑on/Module: Optional, logical groupings of features that solve a specific "Job to be Done." Modular features sold outside the core packages to increase expansion revenue without bloating the base price.
  • Distinction: Plan/Tier/Version is a vertical configuration (Gold vs. Silver) where customers typically select one. A Module is a flexible grouping of features that can be added to a base package. Use modules for heterogeneous markets where customers have vastly different needs.

• Fencing vs Laddering:

  • Fences are the rules, metrics, or feature limitations used to separate customers with different willingness-to-pay (WTP). They prevent high-value customers from buying the low-cost version intended for price-sensitive buyers.
  • Laddering is the design of product tiers (e.g., Good/Better/Best, or Starter/Pro/Enterprise) to guide a customer's journey upward over time. It provides a clear path for a customer to enter at a lower price point and "expand" to higher tiers as their needs grow.
  • Distinction: Fencing is about separation. While Fencing is about keeping segments apart (e.g., "Student Discount" is a fence based on identification; "10-user limit" is a fence based on usage quantity.), laddering is about moving customers up. It is the structural foundation of a "Land and Expand" strategy.

Mental model#

Refer to The "Fence and Ladder" in Segmentation by Willingness to Pay (WTP) / Use Case page.

When should you use packaging architecture?#

Decision criteria#

Rules of thumb#

Use as starting hypotheses:

• Start with 3 core tiers (or 2 + enterprise) unless your segmentation is extreme.
• Keep add-ons <5 initially; make them big, unambiguous, and widely applicable.
• Ensure the "middle" tier is the default for your ICP (copy + limits + CTA).
• Gate by outcome/complexity/risk (e.g., security, compliance, scale), not by "random features."
• The 10x Rule: For every move up a tier, the customer should ideally perceive at least 10x the value, even if the price only triples.

Why does packaging architecture matter?#

Most founders fall into "The Kitchen Sink Syndrome"—adding every new feature to the same plan. Over time, this creates two predictable problems. First, value leakage: your most advanced customers pay roughly the same as your smallest ones, despite deriving far more value. Second, analysis paralysis: prospects struggle to understand the differences between plans, delaying or abandoning the purchase altogether.

Well-designed packaging solves this by aligning offers with willingness to pay and operational reality:

• Monetization leverage: Changes to packaging and pricing drive a 12.7% improvement to the bottom line on average, compared to just 3.3% from improving customer acquisition alone. Packaging is one of the highest-ROI levers founders control.
• Unlocking hidden revenue: A single package for the "average" customer inevitably over-serves the low end (giving away value) and under-serves the high end (leaving money on the table). Thoughtful packaging captures more of the demand curve by matching distinct value propositions to distinct segments.
• Operational velocity: Clear packaging standardizes how products are sold. Without it, sales teams default to custom deals and exceptions, slowing deal cycles, increasing discounts, and creating long-term technical and roadmap debt.

How do you implement packaging architecture step-by-step?#

Inputs you need#

• Usage telemetry: Behavioral data showing which features are actually used by high-value versus low-value customers, informing which capabilities should move up or down tiers, paired with cost-to-serve data such as support load, infrastructure cost, and risk.
• MaxDiff analysis: A survey method that forces customers to trade off features, helping you identify true Leaders (purchase drivers) versus Fillers (nice-to-haves).
• Willingness-to-pay (WTP) data: Quantitative inputs (e.g., Van Westendorp surveys) that reveal price sensitivity and acceptable price ranges for different packages.
• Jobs-to-be-Done (JTBD) research: Qualitative interviews that clarify the specific "job" customers hire your product to do (e.g., Predictive Maintenance vs. Operational Reporting).
• Competitor benchmarks: Visibility into competitors' tiers, add-ons, and usage limits—not to copy them, but to understand the pricing and packaging mental anchors your customers already bring to the decision.

Risks & anti-patterns (and fixes)#

References & Links#

Sources:#

• McKinsey & Company. (2023, June 2). The art of software pricing: Unleashing growth with data-driven insights. McKinsey & Company.
• Mohammed, R. (2018). The Good-Better-Best Approach to Pricing. Harvard Business Review, 96(5), 118-125.
• Forth, S. (2022, February 14). Core Concepts: Tiered Pricing Architecture. Ibbaka Market Blog.
• Ramanujam, M., & Tacke, G. (2016). Monetizing Innovation: How Smart Companies Design the Product Around the Price. Wiley.
• Lehrskov-Schmidt, U. (2023). The Pricing Roadmap. Independently published.