Almost every form builder meters responses rather than forms. You can build as many forms as you like; what you are really buying is permission to receive answers. That makes the response cap the single most consequential number on a pricing page, and the one people read last.
It is also the failure that hurts most, because it lands at the worst possible moment: the form is live, the campaign is running, and the limit is reached by strangers you cannot see.
The three things a cap can do
When an account runs out of allowance, tools take one of three approaches. Worth knowing which one you have bought.
The form closes. New respondents see a message saying the form is not accepting responses. Nothing already collected is lost, but everyone who arrives after the ceiling is gone, and you find out when someone emails to ask why your link is broken.
The responses are collected but withheld. The form keeps working and the answers land in your account, locked behind an upgrade prompt. Better for the respondent, worse for your leverage. The data exists, and you have to pay to read it.
Overage billing. The form keeps working and the invoice grows. Fine if you are watching it, expensive if the traffic was a bot or an unexpectedly successful post.
None of these is dishonest. They are just very different risks, and the pricing page rarely says which one you are getting.
Why the cap exists at all
A response costs the vendor something real: storage, a database row, an email, sometimes a file upload. But that is not why the number is where it is. Responses are the closest available proxy for how much value you are getting, so it is the number that makes people upgrade, which is exactly why free-tier allowances are set low enough to run out during your first real form.
Ten responses is a demo. A hundred is a small survey. A thousand is a working channel.
The questions to ask before you pick a plan
- What happens on the response after the last one? Closed form, withheld data, or an invoice. Get this in writing from the docs, not from a sales page.
- Does the meter reset, and when? A calendar-month reset behaves very differently from an annual allowance you can exhaust in March.
- Is the cap per form or per account? Per account means one popular form can starve the other nine.
- Are partial or duplicate submissions counted? A form that counts abandoned starts burns allowance on people who never answered.
- What is the cheapest plan with no cap at all? Frequently the honest answer to the whole question, and frequently not the plan the pricing page pushes.
How this works on Questionful
The free plan allows 100 responses per calendar month. When that is used up the form shows respondents a neutral “not accepting responses at the moment” message until the month rolls over. It does not collect quietly, and it does not bill you. Everything already collected stays where it is.
Every paid plan is unlimited, from €19 a month. There is no overage, no per-form ceiling, and no allowance to run down mid-campaign: the cap is a free-plan boundary, not a pricing lever applied to customers.
Forms, questions and sections are unlimited on every plan, including the free one.
The short version
- Response caps, not form counts, are what you are actually buying.
- Find out which of the three behaviours your tool has before you go live.
- Check whether the meter is per form or per account, and when it resets.
- Ask what the cheapest uncapped plan is: often the only number that matters.
- On Questionful the free plan closes the form at 100 a month; paid plans have no cap. See pricing or the Typeform comparison for how that differs from a per-tier allowance.