Key Takeaways

• Feature-based pricing uses capability access as the billing axis, so two customers on identical seat counts and usage can pay different amounts.

• The model takes three shapes: bundled feature plans, per-module purchase, and per-feature add-ons, and each renews differently.

• Notion gates SAML SSO behind its $20 per seat Business plan, so a 200-seat buyer who needs SSO pays $48,000 a year instead of $24,000 on Plus (verified 2026-09-18).

• Pricing by feature works only when a capability has a buyer who wants it and a buyer who doesn't, which is why security features gate well and core workflow features don't.

• The running cost lands on entitlements, not the pricing page: every gated capability needs a real-time access check, a grandfathering rule, and an upgrade path.

What are the types of feature-based pricing?

The types of feature-based pricing differ by what the customer actually buys: a bundled plan, a standalone module, or an add-on.

Notion's public pricing shows the bundled shape with real numbers: Free at $0 per seat per month, Plus at $10, Business at $20, Enterprise quoted. SAML SSO and private teamspaces sit on Business. Audit logs and SCIM provisioning sit on Enterprise. Page history steps 7, 30 and 90 days before going unlimited, the same idea applied to a limit instead of an on-off capability.

These shapes mix. Notion also sells Workers and Custom Agents as metered credits at $10 per 1,000 monthly credits, which puts a consumption axis on top of the capability axis. That combination is a hybrid pricing model.

When should you price by feature?

Price by feature when a capability splits your base into people who badly want it and people who won't notice it's missing. That split is what makes a gate survive renewal.

Capabilities that carry a price step:

• Security and compliance controls: SSO, audit logs, data residency, retention

• Administrative scale: user provisioning, role hierarchies, multi-workspace admin

• Integration depth: premium connectors, bidirectional CRM sync, warehouse export

• Support and service levels: named contacts, response-time commitments

The Notion gate prices out cleanly. A 200-seat company that needs SAML SSO can't buy SSO on its own, so it moves from 200 x $10 x 12, which is $24,000 a year, to 200 x $20 x 12, which is $48,000. One capability carries a $24,000 annual step, and the buyer pays it because their security review won't clear the purchase otherwise.

The model fails in the opposite case. Gating something the daily user needs produces support tickets rather than upgrades, and I'd rather meter that capability than gate it. When value scales with volume, consumption-based pricing fits better, and when it tracks headcount, per-seat pricing does.

What does feature-based pricing cost to run?

The cost is operational, and it lands on the systems behind the pricing page.

What the model adds to your build:

• An entitlement check on every gated capability, evaluated at request time, since a plan change takes effect immediately, not at the next invoice

• A price record per sellable capability, which multiplies once modules and add-ons combine with regions and currencies

• A grandfathering rule for every repackaging, because customers who bought a capability under an old bundle keep it while new ones don't

• A mid-term upgrade path with proration, so a customer adding a module in week three of a quarterly term pays for the remainder

• Reporting that attributes revenue to capabilities, or you can't tell which gate earns its keep

Most of this is feature gating work, and it's the part teams underestimate. The pricing decision takes an afternoon. The entitlement layer that enforces it and keeps legacy customers correct is permanent engineering.

One guardrail we use: cap the independently sellable capabilities at what a salesperson can explain in one call. Past that, gates stop driving upgrades and start driving discount requests.

Related terms

The neighbouring pieces of a packaging decision:

• Feature gating is the enforcement layer that makes a feature-based price real in the product.

• Per-seat pricing charges by user count, the axis feature-based pricing most often sits beside.

• Consumption-based pricing charges by volume, and it fits capabilities whose value scales smoothly.

• Hybrid pricing model combines capability, seat and usage axes on one invoice.

• Subscription pricing models sets out the full menu of recurring structures.

• Feature flag vs entitlement explains why a release toggle can't do an entitlement's job.

FAQ

Is feature-based pricing the same as tiered pricing?

No. Feature-based pricing is the axis, and tiering is one way to arrange it. You can price by feature with no tiers at all by selling modules or add-ons independently, and you can tier on usage volume without gating a single capability.

What is an example of feature-based pricing?

Notion is a clear one. Its Business plan at $20 per seat per month carries SAML SSO, granular database permissions and private teamspaces, none of which the $10 Plus plan includes. Price tracks capability access, not usage.

How do you decide which features to gate?

Pick capabilities that a defined segment needs and the rest of your base doesn't, then check that the segment can say why. Security, administration and integration depth pass that test. Anything in the core workflow fails it, because gating it blocks the job the customer came to do.

What are the disadvantages of feature-based pricing?

The price stops tracking value delivered once a customer's usage grows inside a bundle they've already paid for. The other cost is operational: every gate needs an entitlement check, a grandfathering rule and a proration path, and that compounds with each repackaging.