What This Template Is For
Feature packaging is one of the hardest decisions in SaaS pricing because the stakes are asymmetric. Gate too aggressively and you throttle adoption, increase churn, and frustrate users who feel nickeled-and-dimed. Gate too loosely and you leave revenue on the table, with power users paying the same as casual ones.
This template helps you make structured packaging decisions: which features belong in which tier, why they belong there, and how to validate the packaging before committing to it in production. It covers feature value analysis, tier design principles, the mechanics of feature gating, and a validation framework to test packaging with real customers before launch.
The Product Strategy Handbook covers how packaging decisions fit into the broader pricing strategy. For understanding which features drive the most engagement, the RICE Calculator helps you prioritize features by reach, impact, confidence, and effort. The competitive positioning glossary entry explains how packaging can be used to differentiate against competitors with similar feature sets. If you are building a product-led growth motion, the PLG Handbook covers how free-tier packaging drives acquisition funnels.
How to Use This Template
- Start with the Feature Inventory. List every feature and capability in your product. This is more work than it sounds. Most products have 50-150 distinct features when you account for sub-features and configurations.
- Score each feature on two dimensions: user value (how much do customers care?) and differentiation (does this separate tiers or is it table stakes?).
- Apply packaging principles. Use the value/differentiation matrix to assign features to tiers, starting from the free tier and working up.
- Design the tier structure. Define 3-4 tiers with clear target personas, feature sets, and upgrade triggers.
- Validate with customers. Run a MaxDiff or conjoint study, or conduct 15-20 structured interviews to test whether your packaging matches customer willingness to pay.
- Plan the migration. If you are changing existing packaging, define how current customers transition.
The Template
Feature Inventory
List every feature in your product. Be specific. "Reporting" is not a feature. "Custom dashboard builder with 12 chart types and CSV export" is a feature.
| Feature | Category | Usage (% of active users) | Value Score (1-5) | Differentiation Score (1-5) | Current Tier |
|---|---|---|---|---|---|
| [Feature 1] | [Category] | [X]% | [1-5] | [1-5] | [Free/Starter/Pro/Enterprise] |
| [Feature 2] | [Category] | [X]% | [1-5] | [1-5] | [Free/Starter/Pro/Enterprise] |
| [Feature 3] | [Category] | [X]% | [1-5] | [1-5] | [Free/Starter/Pro/Enterprise] |
| [Feature 4] | [Category] | [X]% | [1-5] | [1-5] | [Free/Starter/Pro/Enterprise] |
| [Feature 5] | [Category] | [X]% | [1-5] | [1-5] | [Free/Starter/Pro/Enterprise] |
Scoring definitions:
Value Score:
- 5: Core workflow. Users cannot accomplish their primary job without this feature.
- 4: High value. Used weekly by most customers. Directly tied to business outcomes.
- 3: Moderate value. Used regularly by a segment of customers. Nice to have for others.
- 2: Low value. Used occasionally. Customers would not churn over losing access.
- 1: Minimal value. Rarely used. Exists for edge cases or legacy reasons.
Differentiation Score:
- 5: Unique to your product. Competitors do not offer this. Key reason customers choose you.
- 4: Best-in-class. Competitors offer a version, but yours is measurably better.
- 3: Competitive. Your version is on par with competitors.
- 2: Table stakes. Every product in the category has this. Not a differentiator.
- 1: Commodity. Expected by default. Customers would be angry if you gated this.
Feature-Tier Assignment Matrix
Plot features on the value/differentiation grid to determine tier assignment:
| Low Differentiation (1-2) | Medium Differentiation (3) | High Differentiation (4-5) | |
|---|---|---|---|
| High Value (4-5) | FREE (table stakes, drives adoption) | STARTER (entry-level paid, good value) | PRO/ENTERPRISE (premium, high WTP) |
| Medium Value (3) | FREE (adoption driver) | STARTER or PRO (depending on target) | PRO (upgrade incentive) |
| Low Value (1-2) | FREE or REMOVE | STARTER (minor perk) | PRO (niche differentiator) |
Assignment rules:
- Features with Value 4-5 and Differentiation 1-2 must be in the Free tier. Gating table-stakes features creates friction and increases churn.
- Features with Value 4-5 and Differentiation 4-5 belong in Pro or Enterprise. These are the features customers will pay for.
- Features with Value 1-2 and Differentiation 1-2 are candidates for removal or consolidation.
- Every tier must have at least one "hero feature" that justifies its existence.
Tier Design
Free Tier
| Element | Details |
|---|---|
| Target persona | [Who is this for?] |
| Goal | [Acquisition? Product-led growth? Developer adoption?] |
| Hero feature | [The one feature that makes Free compelling] |
| Limits | [Users: X, Projects: X, Storage: X, API calls: X] |
| Upgrade trigger | [What need forces the move to Starter?] |
Features included:
- ☑ [Feature: table-stakes feature 1]
- ☑ [Feature: table-stakes feature 2]
- ☑ [Feature: adoption driver 1]
- ☐ [Feature: gated, available in Starter]
- ☐ [Feature: gated, available in Pro]
[Starter Tier Name] - $[X]/mo
| Element | Details |
|---|---|
| Target persona | [Who is this for?] |
| Goal | [Convert free users to paid. Land small teams.] |
| Hero feature | [The one feature that justifies paying] |
| Price anchor | [Why this price? Reference WTP data or competitive benchmark] |
| Upgrade trigger | [What need forces the move to Pro?] |
Features included (in addition to Free):
- ☑ [Feature: first paid feature]
- ☑ [Feature: second paid feature]
- ☑ [Feature: increased limits on free features]
- ☐ [Feature: gated, available in Pro]
- ☐ [Feature: gated, available in Enterprise]
[Pro Tier Name] - $[X]/mo
| Element | Details |
|---|---|
| Target persona | [Who is this for?] |
| Goal | [Capture value from power users and growing teams] |
| Hero feature | [The premium feature that drives upgrades from Starter] |
| Price anchor | [Why this price?] |
| Upgrade trigger | [What need forces the move to Enterprise?] |
Features included (in addition to Starter):
- ☑ [Feature: premium feature 1]
- ☑ [Feature: premium feature 2]
- ☑ [Feature: advanced version of Starter feature]
- ☐ [Feature: gated, available in Enterprise]
Enterprise - Custom Pricing
| Element | Details |
|---|---|
| Target persona | [Who is this for?] |
| Goal | [Land large organizations with compliance, security, and scale needs] |
| Hero features | [SSO/SAML, audit logs, dedicated support, custom integrations] |
| Price floor | $[X]/year minimum |
Features included (in addition to Pro):
- ☑ [Feature: SSO/SAML]
- ☑ [Feature: audit logs and compliance]
- ☑ [Feature: dedicated account manager]
- ☑ [Feature: custom integrations or API limits]
- ☑ [Feature: SLA and uptime guarantee]
Packaging Validation Plan
Method 1: Customer Interviews (qualitative)
| Parameter | Details |
|---|---|
| Sample size | 15-20 customers across current tiers |
| Format | 30-minute structured interview |
| Key questions | 1. Show the tier structure. Which tier would you choose? Why? |
| 2. Which features would make you upgrade from [Tier N] to [Tier N+1]? | |
| 3. Are there any features in [higher tier] that feel like they should be in [lower tier]? | |
| 4. What is the maximum you would pay for [specific feature]? | |
| Success criteria | >70% of respondents select the tier that matches their current spend |
Method 2: MaxDiff Analysis (quantitative)
| Parameter | Details |
|---|---|
| Sample size | 100+ respondents (customers + prospects) |
| Design | Present sets of 4-5 features. Respondent picks "most important" and "least important" in each set |
| Output | Relative importance score for each feature. Maps to tier assignment. |
| Success criteria | Top 5 features by importance score align with Pro/Enterprise tier hero features |
Method 3: A/B Test (behavioral)
| Parameter | Details |
|---|---|
| Design | Show 50% of new signups Packaging A, 50% Packaging B |
| Duration | 4-6 weeks (need sufficient trial-to-paid conversions) |
| Primary metric | Trial-to-paid conversion rate |
| Secondary metrics | Average plan selected, 90-day NRR, support ticket volume about pricing confusion |
Migration Plan (if changing existing packaging)
| Customer Segment | Current Plan | New Plan | Treatment |
|---|---|---|---|
| [Free users] | Free (old) | Free (new) | Auto-migrate. Grandfather any features being removed from Free for [X] months |
| [Starter users] | Starter (old) | [Starter or Pro] (new) | If gaining features: auto-migrate with email notification. If losing features: grandfather for [X] months |
| [Pro users] | Pro (old) | [Pro or Enterprise] (new) | If price increase: grandfather until renewal. Email 90 days before renewal with comparison. |
| [Enterprise users] | Custom | Custom | Individual CSM conversation. No auto-migration. |
Filled Example: B2B SaaS Email Marketing Platform
Feature Inventory (Top 15 Features)
| Feature | Category | Usage | Value | Diff. | Current Tier |
|---|---|---|---|---|---|
| Email campaign builder | Core | 98% | 5 | 2 | Free |
| Contact list management | Core | 95% | 5 | 1 | Free |
| Basic templates (20) | Content | 82% | 4 | 2 | Free |
| A/B testing (subject line) | Optimization | 45% | 4 | 3 | Pro |
| A/B testing (content + send time) | Optimization | 18% | 3 | 4 | Pro |
| Automation workflows (3) | Automation | 62% | 5 | 3 | Starter |
| Automation workflows (unlimited) | Automation | 28% | 4 | 4 | Pro |
| Custom HTML templates | Content | 34% | 3 | 2 | Starter |
| Advanced segmentation | Targeting | 41% | 4 | 4 | Pro |
| Send time optimization (AI) | AI | 12% | 3 | 5 | Enterprise |
| Predictive analytics | AI | 8% | 3 | 5 | Enterprise |
| Custom reporting dashboards | Analytics | 38% | 4 | 3 | Pro |
| Basic analytics (open/click) | Analytics | 91% | 5 | 1 | Free |
| SSO/SAML | Security | 6% | 2 | 1 | Enterprise |
| API access (1,000 calls/day) | Integration | 22% | 3 | 2 | Starter |
Revised Tier Design
Key packaging changes:
- Moved A/B testing (subject line) from Pro to Starter. 45% usage and Differentiation 3 means it belongs in the entry-level paid tier, not Pro. This was our biggest packaging mistake: customers felt nickel-and-dimed paying $79/mo just to test subject lines.
- Added AI features as a new "Growth" tier between Pro and Enterprise. AI features have the highest differentiation but moderate usage. They deserve their own tier at a premium price.
- Increased Free tier from 500 to 1,000 contacts. Competitive analysis shows 500 is below the category floor. Most competitors offer 1,000-2,500 free contacts.
| Feature | Free | Starter ($29/mo) | Pro ($79/mo) | Growth ($149/mo) | Enterprise |
|---|---|---|---|---|---|
| Contacts | 1,000 | 5,000 | 25,000 | 50,000 | Unlimited |
| Email sends/mo | 5,000 | 25,000 | 150,000 | 500,000 | Unlimited |
| Campaign builder | Yes | Yes | Yes | Yes | Yes |
| Basic templates | 20 | 50 | Unlimited | Unlimited | Custom |
| Basic analytics | Yes | Yes | Yes | Yes | Yes |
| A/B testing (subject) | No | Yes | Yes | Yes | Yes |
| Automations | No | 3 workflows | Unlimited | Unlimited | Unlimited |
| Custom HTML | No | Yes | Yes | Yes | Yes |
| API access | No | 1K/day | 10K/day | 50K/day | Unlimited |
| Advanced segmentation | No | No | Yes | Yes | Yes |
| A/B testing (full) | No | No | Yes | Yes | Yes |
| Custom dashboards | No | No | Yes | Yes | Yes |
| AI send optimization | No | No | No | Yes | Yes |
| Predictive analytics | No | No | No | Yes | Yes |
| SSO/SAML | No | No | No | No | Yes |
The Growth tier at $149/mo creates a new expansion path for Pro customers who want AI capabilities without requiring an Enterprise contract. Based on current Pro customer usage patterns, we estimate 15-20% of Pro accounts will upgrade to Growth within 12 months, adding approximately $180K in expansion ARR.
Common Mistakes to Avoid
- Packaging by cost instead of value. It costs you nothing extra to let a user run an A/B test, but it delivers enormous value. Do not gate features based on your marginal cost. Gate based on the value the feature delivers and the customer's willingness to pay for that value.
- Creating too many tiers. Three to four tiers plus Enterprise is the right number. More than five tiers create decision paralysis and increase support tickets about which plan to choose. If you cannot explain each tier's target persona in one sentence, you have too many. The Product Strategy Handbook covers tier design principles in detail.
- Gating features that drive virality. Sharing, collaboration, and export features help your product spread within an organization. Gating them behind higher tiers limits organic growth. If a feature helps more people use your product, consider keeping it free or in the lowest paid tier.
- Not defining upgrade triggers. Each tier must have a clear, predictable moment when the customer outgrows it. "Growing teams" is not a trigger. "Team adds a 6th member" or "User creates a 4th automation workflow" are triggers you can detect and act on.
- Packaging based on gut feel without validation. Run at least one validation method (interviews, MaxDiff, or A/B test) before committing to a packaging change. The cost of a bad packaging decision (churn, confusion, lost revenue) far exceeds the cost of a 4-week validation study.
Key Takeaways
- Score every feature on Value (1-5) and Differentiation (1-5) before assigning it to a tier
- High-value, low-differentiation features belong in Free. They are table stakes, not upgrade incentives
- Each tier needs a clear target persona, a hero feature, and a defined upgrade trigger
- Validate packaging with customers before launch using interviews, MaxDiff, or A/B testing
- Grandfather existing customers when removing features from their current tier
About This Template
Created by: Tim Adair
Last Updated: 3/5/2026
Version: 1.0.0
License: Free for personal and commercial use