SaaS Feature Gating: How to Decide What's Free vs. Paid

Most SaaS founders get feature gating wrong in one of two directions. They make the free tier so restrictive that new users never see real value — sign up, hit a wall immediately, leave. Or they make it so generous that nobody has a reason to upgrade — the product is effectively free forever, and paid plans exist on paper. Both failures are expensive. The first kills activation. The second kills revenue. The goal of good SaaS feature gating is more precise than either extreme: make free feel complete but limited. Users should be able to experience the core value of your product without restriction — and hit friction exactly when they want more.

Getting that balance right is a product strategy decision with direct revenue implications. It's also one of the most overlooked leverage points in early SaaS growth. A well-designed free tier doesn't just reduce churn — it becomes your most effective sales motion, showing users exactly what they're missing at exactly the right moment. That visibility is multiplied when your [SaaS dashboard](/blog/saas-dashboard-sells-upgrades) surfaces limits in context, right where users feel them.

The Three Gating Levers

There are three fundamental models for SaaS pricing tiers, and the choice between them shapes everything downstream: how users experience the product, when they hit friction, and what prompts them to upgrade.

Volume limits let users do the core thing — just not at scale. They can create projects, send API calls, onboard seats, or store records, but only up to a threshold. Notion gates storage and guest access. Linear gates the number of active issues on free. Airtable gates rows and attachments. Volume gating works best when the core workflow is identical at every tier and the value scales with usage. Users don't feel blocked from trying the product — they feel incentivized to grow into a paid plan as their needs grow.

Feature gating reserves the core workflow for free and puts power features behind the paywall. Advanced analytics, export/download capabilities, integrations with third-party tools, automation at scale, custom branding — these aren't the thing the product does, they're extensions that amplify it. Feature gating works best when the core product is genuinely useful in a lightweight form and the paid features serve a more sophisticated user or a more mature use case. The free tier isn't a demo — it's a complete product for a specific user profile.

Time limits — the free trial model — add urgency that the other two models don't. You get full access for 14 days, then the decision. Time-limited trials work best when activation is fast and the product's value is obvious within days. The downside is that users who haven't fully activated by the time the trial expires often churn rather than convert — which is why a [trial conversion playbook](/blog/saas-trial-conversion-playbook) matters as much as the gating decision itself. Freemium vs free trial SaaS is a genuine strategic fork: freemium optimizes for breadth of adoption and long-term conversion; trials optimize for high-intent conversion in a compressed window. Both are valid — but the choice should be deliberate, not a default.

Most successful SaaS products layer all three models. A freemium base (volume limits on core usage) with feature gating on advanced capabilities and a time-limited trial on the Pro tier covers the full spectrum of user intent.

The Aha Moment Rule

There's one rule that overrides all others in SaaS plan gating strategy: never gate the feature that delivers the aha moment.

The aha moment is the specific experience that makes users understand why your product exists — the moment the value clicks. For Slack, it's sending a message to your team and getting an instant reply. For Dropbox, it's opening a file on a different device. For Momentum, it's watching a failed payment automatically recover without touching it. Gate that moment and users never get sold. They evaluate the product without experiencing it, which is like test-driving a car with the engine off.

If your product's core magic is automation, make a basic version of automation free. Gate the number of automations, the complexity of automation workflows, or the integrations available — not automation itself. If your core magic is analytics, give users a real dashboard with real data. Gate historical depth, export capabilities, or advanced segmentation — not the dashboard.

The concrete examples from products people actually use are instructive. Notion gates storage and external guest access, not pages. You can have as many pages as you want on the free tier — that's the product's core value, and restricting it would mean users never build the habits that make the product sticky. Slack gates message history, not messaging. You can use Slack's core product — real-time communication with your team — on a free plan indefinitely. The paid tier unlocks the depth (message history, compliance exports, advanced administration) rather than the breadth.

This principle applies regardless of what your aha moment is. Find it, protect it from your pricing model, and gate everything else.

What Almost Always Belongs on Pro

Once you've protected the aha moment, there's a predictable set of capabilities that should live behind the paywall in almost every SaaS product.

Export and download almost always belongs on paid. Users who need to get their data out of your product are typically power users or enterprise buyers — the exact customers who should be paying. Free users building habits rarely need bulk exports.

Advanced analytics and reporting should be paid. Dashboards showing aggregate trends, cohort analysis, revenue attribution — these are tools for decision-makers who have enough data to need them. That user profile maps to paid.

API access belongs on paid tiers. API users are builders and integrators — they're embedding your product into their own workflows, which means they're deeply committed and extracting significant value. That commitment justifies a paid relationship.

Third-party integrations — connecting your product to Salesforce, HubSpot, Zapier, Slack — are almost universally a paid feature. Integrations serve users who've made your product central enough to their workflow to connect it to everything else. That's a paid user.

Custom branding and white-labeling serve agency buyers and enterprise customers who won't pay for a product they can't put their brand on. It belongs on the highest tiers.

Team features beyond two or three seats are the natural expansion revenue lever. Let individuals and small teams start free. Gate the full collaboration suite — advanced permissions, team-level analytics, workspace administration — behind paid plans.

Automation at scale — not basic automation, but high-volume or complex workflows — belongs on Pro. This is what separates hobbyist use from business-critical use.

Priority support is a paid differentiator that costs you relatively little but signals a real commitment to the customers who need it most.

What Almost Never Belongs on Pro

The inverse matters just as much as the pro feature list.

The feature that makes users "get it" should never be paid. If there's one thing your product does that makes a user say "oh, that's what this is for" — that feature is your most important acquisition tool. Paywalling the aha moment is the same as charging users to see your best sales pitch.

The core action users came to do should be free. Your product exists to do something specific. If that specific thing requires a paid plan, you've turned your product into a demo — and demos don't build habits or generate word-of-mouth.

Anything that blocks sharing or inviting others should be free. The viral loop — a user inviting a teammate, sharing a workspace, sending a link — is the cheapest customer acquisition channel you have. Gate it and you're paying to block your own growth. Referral mechanics, sharing features, and invite flows should always be free.

Account setup and basic configuration should never be paywalled. Anything a user needs to do to get started — connecting an account, configuring basic settings, importing existing data — should be completely free. Friction at setup is the most expensive friction in SaaS.

The Upgrade Trigger Framework

Good SaaS upgrade triggers aren't designed. They emerge from well-calibrated gating — when the free tier is set up correctly, the upgrade moment appears naturally.

The pattern looks like this: the user gets access to enough of the product to experience real value. They build a workflow, hit an activation milestone, rely on the product for something meaningful. Then, at exactly the moment they want to do more — more automations, more seats, deeper analytics — they hit the limit. The wall appears right after they've experienced value, not before.

That sequence is critical. Users who hit friction before they experience value churn. Users who hit friction after they experience value upgrade. Bad gating hits them at signup, before they've seen anything. Good gating — the kind that drives what to put on free plan SaaS for maximum conversion — lets users get 80% of the value, then surfaces friction precisely when they want the last 20%.

The practical implication: your free tier should be designed with the upgrade moment in mind, not as an afterthought. What's the last thing a user will want to do before they're ready to pay? That's where the paywall should be. Everything before that moment should be frictionless.

For a freemium model SaaS, this is the core design challenge: the upgrade moment has to be real, proximate to value, and feel like a natural next step rather than a punishment for using the product. Nail that sequence, and conversion follows without aggressive sales tactics — and your [pricing page](/blog/saas-pricing-page-optimization) just needs to confirm a decision the user has already made. Miss it, and you're either giving the product away or blocking people before they understand why they'd pay.

---

Momentum automates the entire subscription layer — free tier tracking, upgrade triggers, plan enforcement, and billing lifecycle — so you can focus on building the product, not the billing plumbing. When a user hits a limit, the right prompt appears. When they're ready to upgrade, the flow runs itself. [Start free →](/sign-up)