How to stop free response limit abuse in a form builder
One business, four free accounts, one copied form. Why free response limits get stepped around, which basic fixes break and what to do this week.
You have four tabs open now, and all four are the same rental application. The same 14 fields sit in the same order, with "Prefered move-in date" spelled with one r in every copy and the logo stretched a little too wide on each. The forms sit in four different free accounts, and last month those accounts took 340 responses between them and paid you $0.
This is form builder free responses abuse at its most ordinary, and for this post it's a scenario: a made-up product and a made-up customer, with numbers you should replace with your own. Say a property manager wrote to your support inbox in March. They loved the product, they said, and they'd move to your $49 plan as soon as their form outgrew the free limit of 100 responses a month. It outgrew it in April, seven months ago. You waited for the upgrade, got busy and forgot. Today you clicked Apply on their website for no real reason and saw a form ID you didn't recognize. You searched your forms for the company's name, and three more came back.
An illustrative month for that customer, at about 11 responses a day:
So every month they meet your upgrade prompt three times, and every time they move the form instead. Over seven months that's 21 prompts (3 × 7), and those prompts are the whole reason a response limit exists. A form that fills up has just proved it works, with real applicants in it. That's the day a free customer turns into a paying one, and this customer has had 21 of those days.
Your costs won't warn you. Assume a response costs you $0.003 in storage and notification email:
- 340 responses × $0.003 = $1.02 a month to serve them
- $49 × 12 months = $588 a year you were counting on
Nothing on your dashboard goes red over $1.02. And you found this one by accident, so you don't know how many more there are. Say it's 40 businesses. Say you also have 210 paying customers at $49, spend $14,000 a month and have $60,000 in the bank:
- 40 × $49 = $1,960 a month, or $23,520 a year
- Today: 210 × $49 = $10,290 in, $3,710 short each month, about 16 months of runway
- With those 40 paying: $1,750 short each month, about 34 months of runway
Forty businesses that already rely on your product are the difference between 16 months and 34. Somewhere in your 210 there may well be a property manager across town, paying $49 a month for what this one gets for nothing.
Now you have to decide something about a form that's live on someone's website. Close the three extra accounts and 240 applications a month hit a closed page, and the customer you hoped would pay hears about it from their own applicants. Cut the free limit to 50 and every honest free user pays for it, like the yoga teacher whose 60-person retreat signup now closes early. Or say nothing, and $49 a month keeps not arriving.
Why a free response limit is so easy to step around
Your limit counts responses inside an account, but the form does its work outside the account, on someone's website, behind a link nobody looks at. Applicants don't know which account owns it. When one fills up, the business copies the form somewhere else, changes one link and carries on, and nothing their applicants see is any different.
In this scenario, the person doing it is a busy property manager with a real company address, who has signed up by hand four times in seven months. Most of the tools you'd reach for were built for scripts, and there's no script here.
The first fix everyone thinks of is taking away the copy button. That turns one click into ten minutes of retyping 14 fields, once, and honest users lose the button too. The second is counting responses per account instead of per form, which is worth doing and stops someone running ten forms inside one account. The copy was never in the same account, though, so its count starts at zero.
That leaves the limit itself. This is the same customer at different free limits, illustrative:
Halving the limit takes them from 4 accounts to 7 (340 ÷ 50 = 6.8). That's a nuisance, and it may push some businesses to pay. You've also halved the plan for everyone else to add three more copies of one form to someone's month.
The basic fixes for free response limit abuse, and how each one breaks
Each of these catches something, and the cheap ones are worth keeping.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Verified, unique emails | Typos, dead addresses and the same address twice | Any real second inbox | People whose code lands in spam | Sending and deliverability work |
| Disposable-domain blocks | Known throwaway services | Company domains and ordinary mailboxes | People using privacy forwarding | A list someone updates forever |
| Gmail dots and plus addressing | One Gmail inbox written several ways | A second real mailbox | Real users, if the rule misfires | Upkeep as mail services change |
| CAPTCHA | Simple scripts | Anyone signing up by hand | People using screen readers or privacy tools | Fees and lost signups |
| Phone or card requirement | Casual second accounts | Anyone with another number or card | People who want to try first | Text charges and fewer free forms out in the world |
| One per IP address, VPN blocks | Repeat signups on one connection, known VPN ranges | Any other network | Two departments in one building, staff on company VPNs | Exceptions, tickets and a list to maintain |
| Rate limits | Bursts from one account | Four signups spread over months | Real teams in a busy hour | Tuning per endpoint |
| Usage caps | One account overrunning | Each new account's fresh cap | A form that suddenly gets popular | Deciding what response 101 sees |
| Manual review | What a person can spot | Anything without a telltale typo | Whoever looks odd to a tired reviewer | Hours every month |
A business can create leasing@, rentals@ and office@ on its own domain in a minute, and each is a real mailbox that passes verification. Gmail ignores dots and plus-tagged mail reaches the same inbox, so one personal address can be written many ways, but a company with its own domain doesn't need any of that.
Stack everything in the table and someone building a three-question RSVP form has to verify an email, solve a puzzle, enter a phone number and add a card. Each step also costs you signups.
Manual review is the only row that caught the property manager, and it did that by luck. Say you have 8,000 free accounts. At two minutes each that's 16,000 minutes, about 267 hours, more than six working weeks, and it's out of date the day you finish. Comparing forms won't settle it either. "Rental application" is probably one of your own templates, so hundreds of unconnected businesses have the same 14 fields.
What to do about it this week
Write down what the free plan is. For example, one free plan per business, 100 responses a month, in your terms.
Warn at 80, with their real numbers. "You took 340 responses last month. The $49 plan covers 1,000." Put the price in front of them before the form closes, because a closed form is when copying starts.
Give agencies a plan. An agency running 12 clients on 12 free accounts may never have been offered anything else. One plan with client folders turns those into one paying account.
Talk to the businesses you've found. Close nothing on a live form until they've had a chance to answer.
What to send the property manager
Hi, your rental application took about 340 responses last month across four free accounts. Our free plan covers 100 a month for one business, so we'd like to move you to one account on the $49 plan, which covers 1,000. We'll bring your forms and past responses across for you, and your link won't change.
Those steps deal with the businesses you already know about. The next one arrives with a new address and nothing in your records. What's left is the claim itself: when a new free account is about to publish its first form, should it go through, or does it look like a repeat?
Evaluate each free plan claim before a form goes live
You don't have to build your own abuse prevention system to get that answer. AbuseZero starts where those table rows ran out. Your server makes one API call as the free plan is claimed, and you get a clear allow or deny, under rules you control. Every row above is a single check. AbuseZero's multi-layer AI risk analysis examines 140,000+ signals, detects linked claims and flags the abuse those single checks miss. A unique-email rule saw a new address, but AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. Where your domain list went stale, it checks mailbox aliases, disposable domains and mail routing. And an IP limit stops at the address, while AbuseZero sees beyond it with VPN, hosting, network reputation, Tor and proxy intelligence. You also get a proprietary algorithm, with AI that checks the claim again. Creating a fresh account isn't enough to erase previous activity.
Your application still counts responses and closes forms. You set eligibility for the free plan, and Observe mode shows you what would be denied before anyone is blocked. The quickstart gets your first benefit protected.
Frequently asked questions
How do I stop people copying a form to a new account for more free responses?
Count responses per account, warn before the limit with the real price, and put a decision at the moment a new free plan starts. Removing the copy button alone only adds ten minutes of typing.
Is every second account on a form builder abuse?
No. Agencies and separate departments can both have good reasons. Write down what you mean to give each business, and be fair when you say no.
Should I lower my free response limit?
Only if the free plan costs more than it brings in. A lower limit hits every honest user, and a business that needs 340 responses can still open more accounts.
Keep your response limit worth paying for
Start with Builder
Pay as you go. Protect your free plan today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.