# Setting Freemium Limits: Examples and Rules of Thumb > How to set freemium limits for a SaaS product, with common limit types, illustrative examples and rules of thumb that balance free value with upgrade pressure. Source: https://comppound.com/blog/setting-freemium-limits-examples-and-rules-of-thumb (published 2026-07-25) A freemium plan only works if its limits are set well. Set them too generously and nobody needs to upgrade. Set them too tightly and free users never get enough value to care about your product. The limits are where freemium succeeds or fails, and the freemium limits examples SaaS teams usually copy from better-known products don't always fit their own customers. This guide covers what limits are for, the common types and when each works, illustrative combinations, rules of thumb for choosing your own and how to tell when your limits need to change. ## What limits are for Freemium limits have two jobs, and they pull in slightly different directions. The first is to let free users succeed at a small scale. They should get real value from the product, form a habit and come to depend on it. The second is to create a natural reason to upgrade when their needs grow. A free plan that only does the first job produces many happy users who never pay. A free plan that only does the second produces frustrated users who leave before they get anywhere. The best limits are reached because a customer is succeeding, not because the product is deliberately crippled. A team that hits the seat limit has grown its use of the product. A form builder user who hits the response cap has a form that's working. In both cases, the upgrade prompt arrives at a moment when the customer has just experienced the value they'd be paying for. ## Common types of limits ### Usage limits Usage limits cap how much of the core action a free user can do. That might be the number of projects, documents or boards, the number of contacts or records, the number of emails sent, tasks run or reports generated each month, or the amount of storage. Usage limits work well when usage grows naturally as customers succeed. A team that sends more campaigns because its email marketing is working will reach a send limit at the right time. They work less well when heavy usage doesn't correlate with value, or when a single user can reach the limit on day one simply by importing existing data. ### Seat limits Seat limits cap the number of users on a free account, often at three or five. They work well when value increases with team adoption, so growing teams reach the limit as the product spreads. Collaboration tools often rely on seat limits because the product becomes more useful the more teammates join, and a team that has grown past the limit has usually built real dependence on it. The risk is that seat limits can discourage the very adoption you want. If inviting a fourth teammate means paying, some teams will share logins or keep the product within a small group. Watch for those patterns and consider whether the limit is stopping the spread that drives long-term value. ### Feature limits Feature limits reserve certain capabilities for paid plans. Common examples are integrations, advanced reporting, automation and administrative features such as permissions and single sign-on. Feature limits work well when some features clearly matter more to larger or more serious customers. A freelancer rarely needs audit logs. A company with an IT team often won't buy without them. The danger with feature limits is gating something that free users need to experience the core value. If your product's main benefit depends on an integration, locking that integration away means free users never see why the product is worth paying for. ### History or retention limits History limits restrict how far back data is kept or visible, such as only the last 30 or 90 days, or search limited to recent items. They work well when customers accumulate valuable history over time. A team that has been using the product for months starts to care about finding last quarter's work, which creates a natural reason to upgrade without restricting day-to-day use. ### Branding limits Branding limits mean free outputs carry your product's name, such as a "Made with [Product]" line on forms, pages or emails. They work well when outputs are seen by other people. The branding drives awareness among the people who see the output, and professional users often want it removed, which gives them a reason to pay. ### Support limits Support limits give free users community or self-serve support, while paid customers get direct help. This is common and sensible, since direct support costs money. It rarely drives upgrades on its own, but it keeps the cost of serving free users manageable. ## Illustrative combinations These are common patterns rather than recommendations for any specific product. A collaboration tool might be free for small teams, with limited history. Growing teams reach the seat limit, while established teams start to want access to older work. Each limit catches a different kind of success. A form builder might cap responses per month and add branding to free forms. Successful forms reach the response cap, and professional users want the branding removed so the form looks like their own. A reporting tool might limit the number of dashboards and data sources, with integrations to key paid tools reserved for paid plans. Small users can get value from a couple of dashboards, while teams building a broader reporting setup need more. An email tool might combine a contact limit with a monthly send limit and keep automation for paid plans. A small list can be managed on the free plan, while growth in the list or the need for automated sequences prompts an upgrade. Notice that each combination pairs a limit tied to growth with a feature or condition that matters to more serious customers. That pairing is often more effective than relying on a single limit. ## Rules of thumb ### Keep the core value free If free users can't experience what makes the product useful, they'll leave before ever considering an upgrade. Identify the single result your product delivers best and make sure free users can reach it. Everything else is negotiable. ### Limit what grows with success Pick limits on things that increase as customers get more value, such as team size, volume, history or the number of projects. That way upgrades feel earned rather than forced, and the customer understands why they're paying more. ### Put company-scale needs in paid plans Features like permissions, single sign-on, audit logs and advanced admin controls matter mostly to larger organizations. Gating them rarely hurts individual free users, and it gives larger buyers clear reasons to pay. ### Make limits visible before they're reached Show usage meters and gentle warnings as users approach a limit. A user who sees they've used eight of their ten projects can plan for the upgrade. A user who hits an unexpected wall in the middle of their work feels punished, and that frustration often turns into churn rather than payment. ### Avoid limits that break workflows Cutting off a feature mid-task or making existing data inaccessible creates frustration and support tickets. Prefer limits that block new activity while keeping existing work accessible. A user who can't create an eleventh project but can still open the other ten is far more likely to upgrade calmly than one who suddenly loses access to their work. ### Consider your cost to serve If free users cost real money in infrastructure or third-party services, such as storage, compute or paid APIs, set limits that keep that cost sustainable. A free plan that loses money on every active user becomes a problem as you grow, however good it is for acquisition. ### Look at real usage data Check what typical free users actually do. A good limit sits above what a casual or small user needs but below what a growing, successful account will need. If you're launching freemium for the first time, use trial data or conversations with early customers to estimate where those thresholds are, and expect to adjust. ## How to test limits Changing limits affects existing users, so be careful. Test new limits on new signups first, so existing users aren't surprised. Track free-to-paid conversion, but also activation and free user retention, because a tighter limit can increase short-term conversions while reducing the number of users who stick around long enough to pay later. Watch support volume and the tone of support conversations. A sudden rise in tickets about limits suggests users are reaching them earlier than expected or don't understand them. Compare revenue per signup rather than conversion rate alone, since a change that converts slightly fewer users to a more valuable plan may be the better outcome. If you tighten limits for existing free users, give plenty of notice and consider grandfathering them on the old limits. Free users who built habits on your product are a source of word of mouth, and treating them badly can cost more than the revenue you gain. ## Signs your limits need adjusting Limits are probably too generous if very few free users ever approach any of them, or if large, clearly successful teams stay on the free plan for a long time. In that case, the free plan is doing the first job well and the second job poorly. Limits are probably too tight if free users churn before forming a habit, if there are many support tickets about reaching limits early or if activation among free users is low. In that case, users aren't getting enough value to see why the paid plan matters. ## Write helpful upgrade prompts When users reach a limit, the message they see matters. > You've reached 3 projects on the free plan. Upgrade to Team for unlimited projects and shared templates. This message explains what happened, names the plan that solves it and describes what the user gains. That last part is important. Explain what they get, not just what they're blocked from. A prompt that only says "Limit reached" leaves the user frustrated. One that describes the next plan in terms of what it lets them do turns the limit into a decision. ## The takeaway Good freemium limits let free users become successful small customers and then make the upgrade the obvious next step as they grow. Keep the core value free, limit what grows with success, reserve company-scale features for paid plans and make every limit visible before it's reached. Test changes on new signups, watch retention as well as conversion and review your limits at least once a year as your product and customer base change. ## Frequently asked questions ### What are freemium limits? Restrictions on a free plan, such as usage caps, seat limits or reserved features, designed to create reasons to upgrade. ### What should be free in a freemium SaaS plan? Enough core value for users to succeed at a small scale and form a habit. ### How do I know if my freemium limits are too generous? If few free users approach limits and successful teams stay free for a long time, limits may be too generous. ## About Comppound Comppound runs SEO and AI search for B2B SaaS companies: a person sets the plan and reviews samples and every high-risk page, and AI speeds up production. - [See SEO Growth](https://comppound.com/services/seo-growth): Buyers compare before they book a demo. Are your pages there when they do? - [Book a call](https://comppound.com/contact): Most of this works better when buyers can find you first