How to stop repeat free exports in an AI resume builder
A repeat free export costs model spend you can't recover and removes the only reason to pay. What each basic fix catches in a resume builder, and where it breaks.
Say you run an AI resume builder. A new account gets one tailored resume for free, downloaded as a clean PDF, and after that it's $24 for a 30-day pass. This is a made-up scenario and every price in it is an assumption, so swap in your own. Keep your eye on the second click on Download, because your whole business sits behind it.
One free export costs you this much in model calls:
- Reading the old resume: $0.02
- Four drafts against the job ad, at $0.09 each: $0.36
- Cover letter: $0.07
- Match report: $0.05
- Total: $0.50
In a normal month, 6,000 free exports cost $3,000. Five percent of those people buy a pass, so 300 passes bring in $7,200. Each pass holder makes about 12 exports, which adds $1,800 in model spend (300 × 12 × $0.50). You keep $2,400 for hosting, ads and yourself.
Then a post goes up in a big job seekers' forum on a Tuesday evening. It says your free resume is excellent and that a new email gets you another one. Over the next 14 days, 1,100 people open one new account a day and download one more tailored resume a day, one for each job they're applying to. That's AI resume builder free download abuse, and on your signup graph it looks like the best two weeks you've ever had.
- 1,100 people × 14 accounts = 15,400 free exports
- 15,400 × $0.50 = $7,700 in model spend
- $7,700 ÷ 14 days = $550 a day on top of your usual $160
Your provider bills that as it happens. On a normal day you take in $240 from passes and spend $160 on the model. For these two weeks, the model takes $710 a day.
If your prepaid balance reloads $500 at a time, your card used to get charged about every three days. Now it's charged about every 17 hours ($500 ÷ $710 × 24). None of that comes back. The model ran, and the PDF is on someone's laptop, already attached to an application. A credit balance can at least be taken away. A downloaded resume has nothing left to take.
Say your billing month began the day that post went up. On day 12, your $8,000 monthly spending cap runs out ($8,000 ÷ $710 = 11.3 days). At 9:40 p.m. every Generate button in your product starts returning an error. A customer who paid you $24 last week writes in: "This job closes at midnight and your tool won't generate. I paid for this." You see it an hour later and raise the cap from your phone. By then 38 pass holders have hit the error, and you refund them all, which is $912.
Say you had $9,000 in the business account when this started. Two weeks of model spend took out $9,940, two weeks of normal sales put in $3,360, and the refunds took $912. You've got $1,508 left, and the next reload is 17 hours away.
The sales you never made are on top of that. If one in four of those 1,100 people would have bought a pass at the second download, that's 275 passes, or $6,600. Add the $7,700 and the two weeks cost you $14,300, nearly two months of revenue. You're now deciding whether to pull the free export, the one thing that sells all 300 of your passes.
Why resume builders get hit this way
Most software hopes you'll stay. A resume builder gets used in a burst, for the length of a job hunt, and then sits unopened until the next one. The PDF is the entire product, and once it's downloaded it works with no account at all.
That leaves your paywall one moment to work: when someone who's just seen a great resume needs a second one for the next job. A free export at that moment costs you $0.50, and it removes the only reason they had to pay.
A pass holder leaves you $18 after model costs ($24 minus 12 exports at $0.50). Someone running 14 free accounts costs you $7 and pays nothing. Some of those accounts aren't job seekers either. A freelancer charging $30 to rewrite a resume can run each client through a new free account, so 10 clients a week earns them $300 and costs you $5.
The obvious fix is a watermark, or a blurred preview with the download behind the paywall. That protects the file and leaves the bill where it was, because the four drafts already ran by the time anyone sees a preview. And a resume with a watermark can't go to an employer, so the free user never gets the moment where your product proves itself.
The basic fixes, and how each one breaks
Every one of these catches something. Your usual repeat claimer, though, is one job seeker making one account by hand.
| Basic fix | What it catches | What it misses | Who it wrongly blocks | What it costs to keep working |
|---|---|---|---|---|
| Email verification | Typos and dead addresses | Any real second inbox | Job seekers whose code lands in spam | Sending and deliverability work |
| Unique emails | The same address twice | Every different address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains and ordinary mailboxes | People who keep job mail behind a forwarding alias | A list someone updates forever |
| Gmail dots and plus addressing | One inbox written several ways | A second real mailbox | Two people sharing one inbox | Upkeep as mail services change |
| CAPTCHA | Simple scripts | A person signing up by hand | Screen reader users and old phones | Lost signups, sometimes fees |
| Phone requirement | Casual second accounts | Anyone with another number | People on shared or lapsed plans | A charge for every text |
| Card requirement | Casual second accounts | Anyone with another card | People between jobs and watching every dollar | Fewer people reach the free export |
| One per IP address | Repeats on one connection | Any other network | Libraries, campus career centers, job clubs | Exceptions and tickets |
| VPN blocks | Known VPN ranges | Everything off your list | People job hunting quietly behind a VPN | Another list to maintain |
| Rate limits | Bursts from one account | One export a day | Someone regenerating before a deadline | Tuning per endpoint |
| Usage caps | One account overrunning | Each new account's fresh cap | Anyone at the cap mid-application | Deciding when your product stops |
| Manual review | What a person can spot | Every PDF already downloaded | Whoever looks odd to a tired reviewer | Hours every week |
A unique-email rule compares text, and one mailbox can go by many addresses: Gmail ignores dots, and plus-tagged mail reaches the same inbox. A second plain mailbox takes a minute to open, and your code will reach it fine, because verification only proves an inbox exists.
CAPTCHA waves through nearly all 1,100 people, since it's built to let humans in. Rate limits don't notice one export a day. Turn on one free export per IP address and your first ticket comes from a library job club, where 15 people share a connection and the second one sees a paywall. Require a card and you've put a wall in front of people who just lost their income. Manual review would mean 15,400 accounts at a minute each, about 257 hours, or 18 hours a day for those two weeks, and every PDF would already be gone.
Stack enough of this and it costs you the sales too. If the extra steps turn away 20% of the people who'd reach the free export, that's 60 fewer passes a month, or $1,440. That's 60% of the $2,400 you keep.
One fix really does shrink the bill, so start there.
Make the free export cheap. One draft and no extras costs $0.11 ($0.02 + $0.09). The same 15,400 exports now cost $1,694 instead of $7,700, which saves $6,006. The $6,600 in missing sales stays, because a new account still gets a free file.
Give free exports their own budget and a hard cap, separate from pass holders, so a bad week stops the free step before it stops someone's application.
Hold the model calls until the account is verified, so expensive work doesn't run on signups that go nowhere.
Decide how often a real person gets a free export. People lose jobs twice. Once ever may be too strict, and once a year may suit you better. Write it down before you enforce anything.
Write a kind no. Whoever reads it may be out of work. Offer a cheap single export, and word it carefully.
All of that keeps the damage smaller. A new account still arrives with a clean record and a free export waiting. What's left is one question, asked before any money is spent: should this claim go through?
Ask before the first draft runs
You can keep rebuilding that table, or you can hand the question to AbuseZero. One API call, placed before your first model call, returns a clear allow or deny under rules you control. AbuseZero puts 140,000+ signals through multi-layer AI risk analysis, which detects linked claims and flags abuse that single checks miss. There's also a proprietary algorithm, with AI that checks the claim again.
Your unique-email rule gave up at the first new address, and AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. Your domain list went stale, and AbuseZero checks mailbox aliases, disposable domains and mail routing. Your IP limit landed on a library job club, and AbuseZero sees beyond an IP address with VPN, hosting, network reputation, Tor and proxy intelligence. Creating a fresh account isn't enough to erase previous activity. You don't have to build your own abuse prevention system, or keep one running through every hiring season.
Eligibility can be once, or once every set number of days, up to 365, so next year's job hunt can still get a free export. Observe mode shows you what would be denied before anyone is blocked, and the quickstart walks you through your first benefit.
Frequently asked questions
Should I remove the free export from my resume builder?
Only if it isn't selling passes. In this scenario it sells all 300 a month, so make it cheaper and cap its budget first. See should you remove your free tier?
Is it abuse when someone comes back for a new job hunt?
Usually not. Someone returning a year later with the same account is the customer you want. Set a window that treats them fairly.
How do I stop a second free resume from a new email?
A unique-email rule can't do it alone, because a new email is a different address. Keep the free step cheap, then evaluate each claim before the first draft runs. AbuseZero's evaluation returns allow or deny.
Keep the free export for the next real job hunt
Start with Builder
Pay as you go. Protect your free export today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.