FA-301c · Module 2

Packaging Strategy

3 min read

Packaging is what you sell. Pricing is what you charge. They are separate decisions with separate optimization criteria. Packaging determines which features and services are bundled together and which are sold separately. Good packaging creates bundles that align with buyer use cases — not with your product architecture. Buyers do not think in modules. They think in problems. Package for the problem, not the module.

Do This

  • Package by buyer persona and use case: "everything a marketing team needs" vs. "Module A + B + C"
  • Include features that drive adoption in every package — removing them creates activation barriers
  • Create add-ons for features with variable demand: premium support, advanced analytics, custom integrations
  • Test packaging separately from pricing — the bundle matters as much as the number

Avoid This

  • Package by product module — "analytics package, automation package, reporting package"
  • Gate essential features behind premium tiers — you create resentment, not upgrade motivation
  • Bundle everything into one SKU with no modular expansion — you lose the ability to segment pricing
  • Change packaging and pricing simultaneously — you will not know which change drove the result
Packaging Decision Matrix:
──────────────────────────────────────────────────────
Feature               Include   Gate    Add-On   Why
──────────────────────────────────────────────────────
Core workflow           All       —       —     Drives adoption
Basic analytics         All       —       —     Proves value
Advanced reporting       —      Pro+      —     Upgrade trigger
Custom dashboards        —      Ent       —     Premium value
Premium support          —        —      Yes    Variable demand
Custom integrations      —        —      Yes    Per-customer
Dedicated CSM            —      Ent       —     Justifies price
API access             All       —       —     Drives stickiness
SSO/SAML                —      Pro+      —     Enterprise need
SLA guarantee            —      Ent       —     Enterprise need
──────────────────────────────────────────────────────

All tiers include what drives adoption.
Gated features create upgrade triggers.
Add-ons monetize variable demand.