What is a capacity gate?
A paywall placed on how much someone can use a product, such as items stored or scans per month, rather than on which features they can see.
A capacity gate limits how much of a product a free user can use, not which parts they can use. Examples: up to a set number of books, locations, projects or AI scans, after which a paid plan removes the limit.
The alternative is a feature gate, where some features are visible but locked.
What the data showed
On Plumerie, feature gates for two advanced tools were shown 52 times in June 2026 and got zero clicks. The conversions came from capacity gates and from Shelf Scan, a photo feature with a small free allowance. The first paying customer converted at the Shelf Scan gate.
The lesson: people need to feel a feature's value before a paywall means anything. A capacity gate only appears once someone has already used the product enough to care.
Why it suits small products
- It's honest. Free users get the whole product, just less of it, so the free tier is genuinely useful.
- It times itself. The upgrade prompt appears when someone is most invested.
- It's easy to explain. "Free up to 500 books" beats a feature matrix.
How to choose the limit
Set the limit above what a casual user needs and below what a committed user reaches in their first weeks. Watch where people hit it, and whether they upgrade or leave. Give everyone a small free taste of any premium action, so they know what they'd be paying for.
Watch your gates
Track every gate as an event: shown, clicked, converted. A gate that's shown often and never clicked is noise, and it's teaching users to ignore your prompts. That habit of measuring before deciding is the same one behind a validation gate.
For one-person products, a capacity gate works well alongside product loops: the loop brings people in free, and the gate catches them once they're hooked. Picking your gates is part of the Build subtrack in our indie cohort.