Feature Packaging Decision Matrix: A Founder’s 1‑Page Framework to Choose Charge vs. Free (and What to Ship First)

Start with a single row per capability and score it on four dimensions: Value to the user (how much it improves Time‑to‑Value), Competitive differentiation (is it a unique hook or table stakes), Cost to serve (engineering and ongoing infra), and Revenue optionality (how plausible is it someone will pay). Use a 1–5 scale and total the scores. This simple arithmetic separates obvious frees (high user value, low revenue optionality) from obvious charge candidates (high differentiation, low cost to serve, high revenue optionality).

Convert totals into actions with clear rules: 15–20 = Charge (standalone or micro‑price); 10–14 = Bundle in a paid tier; 6–9 = Keep free but instrument heavily; 4–5 = Kill or postpone. Print the matrix, fill it with your top 6 candidate features, and iterate with product, sales, and one customer interview to validate the subjective scores.

If you choose Charge: define a minimum viable monetization (MVM) test. MVM acceptance criteria should include an expected free‑to‑paid conversion lift (e.g., >2% within 30 days of exposure for self‑serve SaaS), a minimum ARPU delta (e.g., $X incremental ARPU per paying account), and at least one paying customer segment that finds the feature indispensable. Track trial‑to‑paid and conversion by cohort immediately after release.

If you choose Bundle: success is measured by attach rate inside the target tier and net expansion over 90 days. Define a targeted attach rate (for example, 20% of new signups on the tier adopt the feature within 30 days) and verify it improves ACV or retention vs. a control cohort. For Free (instrument heavily): require an activation and retention lift for the core funnel before you even consider gating.

Don’t rely on vanity metrics. Instrument the product to capture both outcome events (did the user reach X — e.g., exported report, completed workflow) and entitlement context (was the feature shown but blocked, partially allowed as a trial, or fully available). Key signals: feature impression, attempted use when blocked, successful use, repeat use frequency, time to first value (TTFV), free→paid conversion, and churn within 30/90 days.

Use these signals to run simple experiments: if many blocked users attempt the feature and churn immediately after seeing the block, that’s strong evidence to micro‑price or bundle. If usage among free users shows frequent adoption and long‑term retention benefit, the feature might be strategically better offered free to grow the top of funnel. Tools and playbooks from product analytics vendors help align metrics to the product‑led growth funnel and reduce guesswork.

Example A — Micro‑price for power users (clone for a consumer SaaS tool): Make the capability free for the first N uses, then offer a micro‑purchase (one‑time or credit pack). Acceptance criteria: >5% of heavy users convert to micro‑purchase within 14 days; incremental ARPU covers marginal cost. Telemetry to watch: attempted uses beyond N, micro‑purchase conversion, repeat micro‑purchases.

Example B — Tiered bundle for SMBs (clone for B2B tools): Put the capability in a 'Pro' tier that also includes two complementary features. Acceptance: 15–25% attach rate among trialing SMBs within 30 days and measurable increase in close rate or ACV for accounts that use the feature. Telemetry: attach rate by segment, expansion MRR, and retention differential vs lower tiers.

Example C — Free with progressive disclosure (clone for product‑led onboarding): Ship the feature free but hidden until the user crosses a milestone; this drives activation and retains the option to gate later. Acceptance: lift in Time‑to‑Value and Day‑7 retention vs a control. Telemetry: milestone reach rate, feature discovery event, and retention by discovery cohort.

1) Fill the 1‑page matrix and prioritize the top 3 features. 2) Define acceptance criteria and test windows for each. 3) Add telemetry events (impression, attempt when blocked, success, repeat). 4) Implement feature flags and entitlements so you can change packaging without code deployments.

5) Launch to a small cohort with a control group. 6) Collect quantitative signals and 3–5 qualitative interviews. 7) If revenue signals are promising, run a pricing A/B for micro‑price or tier placement; if activation/retention signals are promising, keep free and invest in discovery. 8) Revisit the matrix monthly; move features across buckets when evidence accumulates.