How to protect free credits in a B2B data enrichment tool
A repeat claim on licensed contact data can replace a paying customer. The arithmetic, why the basic fixes break, and what to change in your free offer.
Say you run a B2B data enrichment tool. A customer uploads a CSV of names and companies, and you send back verified work emails, job titles and direct dials, at one credit per contact. New accounts get 250 free credits so buyers can test your data on their own list, and the Team plan is $299 a month for 5,000 credits. You pay your suppliers about $0.03 per record. This is a scenario, and every number in it is an assumption to replace with your own.
For five weeks you've been working an outbound agency that runs campaigns for six clients. They'd use about 5,000 contacts a month, so they're a Team plan, and you've been counting on that $3,588 a year ($299 × 12) since the second call. At 3:30 on a Thursday their ops lead joins the final call, and they couldn't be nicer about it. Your data's the best they've tried. They've run every client through it for eight months. They won't need a plan, though, because a contractor opens fresh accounts for them at the start of each month.
You thank them, end the call and do the arithmetic:
- 5,000 contacts a month ÷ 250 free credits = 20 new accounts a month
- 5,000 records × $0.03 = $150 a month paid to your suppliers
- 8 months × $150 = $1,200 paid out so far
- 8 months × $299 = $2,392 of data at your own prices
Had they bought, you'd have made $149 a month on them ($299 minus $150). Instead you're $150 down. That's B2B data free credits abuse from one company in your pipeline, and the 40,000 contacts (8 × 5,000) are already in their CRM, where nobody can take them back.
Now say 14 teams are doing the same. That's 70,000 records a month (14 × 5,000). Your supplier contract covers 150,000 records for $4,500, and anything past that costs $0.05. Paying customers use 110,000 and honest free users use 15,000:
- 110,000 + 15,000 + 70,000 = 195,000 records a month
- 195,000 ÷ 30 days = 6,500 a day
- 150,000 ÷ 6,500 = about 23 days
You've set a hard stop at the contract limit, because overage at $0.05 eats nearly all of the $0.06 a Team credit earns ($299 ÷ 5,000). So on the 24th, lookups start coming back empty. A paying customer's campaign list comes back with no emails on it, and by 9:30 the screenshot is in your support inbox. You lift the stop from your phone, and the last 45,000 records add $2,250 to next month's invoice (45,000 × $0.05). Without those 14 teams you'd have used 125,000 and paid no overage at all.
Bars are records used so far. The line is what your contract covers.
Not all 14 would have bought. Say half would have, and the other half would have left:
- 7 × $299 × 12 = $25,116 a year in revenue you didn't get
- Usage drops to 160,000 (195,000 minus 35,000), so overage falls to $500 a month: ($2,250 minus $500) × 12 = $21,000 a year
- $25,116 + $21,000 = $46,116 a year
If you spend $30,000 a month, that's about a month and a half of runway. Your supplier has offered the next tier up, 200,000 records for $5,800. That's $1,300 a month more, which beats the overage, and $15,600 over a 12-month term to serve teams who've told you they won't pay. The other option on your desk is cutting the free credits that brought in every good customer you have.
Why B2B data free credits get claimed again and again
Most free credits buy something that gets used up. A model call is over when it's over. An enriched contact is a row in someone's CRM, useful for as long as that person stays in that job, so your free plan hands over the same thing your paid plan sells.
The people claiming it are businesses, and businesses do the sum. Say the contractor spends three hours a month opening accounts at $15 an hour. That's $45 to avoid $299.
Over a year, a real share of your database leaves this way. If you hold 2 million contacts in the market these teams sell to, 840,000 records a year (70,000 × 12) is 42% of it, before you allow for overlap between their lists. You licensed every one of those records.
The obvious fix is fewer free credits. Cut 250 to 50 and the agency needs 100 accounts a month (5,000 ÷ 50). At 20 accounts in three hours, that's 15 hours, or $225, which is still less than $299. Honest buyers lose more, because the free pack is how they judge your match rate, the share of their list you can fill in. Here's how sure a buyer can be at a 60% match rate:
- 250 contacts: 1.96 × √(0.6 × 0.4 ÷ 250) = about 6 points either way
- 50 contacts: 1.96 × √(0.6 × 0.4 ÷ 50) = about 14 points either way
A buyer who sees 60% on 50 contacts can't tell whether your real rate is 46% or 74%. The agency adds accounts. The honest buyer goes to someone who offers a bigger sample.
The basic fixes, and how each one breaks
Each of these catches something. Three matter most in a data tool.
Work email only. This catches casual repeat signups from personal inboxes, and there are plenty of those. It misses the teams you care about most, because outbound agencies already own spare domains and mailboxes. Sending cold email from secondary domains is a routine part of their job. It also turns away freelancers and founders who use a personal address, and someone has to keep a list of free mail providers up to date.
One free pack per company domain. This catches the second rep at a company that's already had one. It misses those spare domains too. And it blocks the London sales team at a 4,000-person company because someone in Chicago tried you last year, when that team may be your best lead this quarter. Keeping it working takes an allowlist and an inbox of requests. There's more on one company starting trial after trial.
A card on file. This stops more casual repeat use than anything else here. Against $299 a month, though, a second card is a small effort, and buyers at larger companies often can't put a new vendor on a card before procurement signs off. So requiring a card can cost you your biggest deals.
The rest are quicker to judge. Unique-email rules compare text, and one inbox can have many spellings: Gmail ignores dots, and plus-tagged mail reaches the same inbox.
| Basic fix | Catches | Misses | Wrongly blocks | Cost to keep working |
|---|---|---|---|---|
| Email verification | Typos, dead addresses | Any real second inbox | People whose code lands in spam | Deliverability work |
| Unique emails | The same address twice | Every different address | Almost nobody | Very little |
| Disposable-domain blocks | Known throwaway services | New domains, real mailboxes | People using privacy forwarding | A list that's never finished |
| Gmail dots and plus tags | One inbox written several ways | A second real mailbox | People who sort their mail with plus addresses | Upkeep as mail services change |
| CAPTCHA | Simple scripts | A contractor signing up by hand | People using screen readers | Fees and lost signups |
| Phone requirement | Casual second accounts | Anyone with another number | Reps who won't give a sales tool their mobile | A charge per text |
| One per IP address | Repeats on one connection | Any other network | A 40-person sales floor | Tickets and allowlists |
| VPN blocks | Known VPN ranges | Everything off your list | Staff on company VPNs | Another list |
| Rate limits | Bursts from one account | 20 accounts under the limit | Customers enriching big lists | Tuning per endpoint |
| Usage caps | One account going over | The next account's fresh cap | Anyone at the cap | Deciding when lookups stop |
| Shorter trials | Slow, drawn-out use | Fresh accounts | Buyers waiting on a budget | Lost deals |
Manual review gets its own line, because at 1,500 signups a month and three minutes each it's 75 hours a month (1,500 × 3 ÷ 60). Your reviewer will wave these accounts through anyway, because a real job title at a real agency is who you built this for.
These placements are our judgment, and nothing here is measured. The top-left corner is still empty.
What to change in your free offer anyway
Work out your headroom. Write down your contract price, your overage rate and how many records paying customers need.
Give free records their own ceiling. Here, paying customers use 110,000 of 150,000, so you might cap free use at 25,000 a month and keep the rest in reserve. Paying customers stop running out on the 24th. Free demand of 85,000 a month is about 2,833 a day, so the cap goes around day 9, and honest buyers wait three weeks. That's the trade you're making.
Make free credits a test of the data. Show results in your app, and keep CSV export, CRM sync and direct dials on paid plans. A buyer can still measure your match rate, and a table on a screen is much harder to load into a campaign.
Read your data contract. Find what it says about redistribution and about records given away on a free plan. If you can't tell, ask your supplier.
Decide what a no says. The account you turn down may be an agency with a budget, so write a no with a plan price and a person to talk to.
Those steps protect paying customers and make each free pack worth less. They don't change what happens when next month's accounts arrive. Go back to that Thursday call: a real domain, a verified mailbox, a card if you ask for one, and a job title your sales team would love. Each fix above looks at one signup and finds nothing wrong. What's left to ask, every time a free pack is about to go out, is whether this claim should go through.
Evaluate the claim before the records go out
You don't have to build your own abuse prevention system to answer that. AbuseZero uses a proprietary algorithm, with AI that checks the claim again. You get multi-layer AI risk analysis that examines 140,000+ signals, detects linked claims and flags abuse that single checks miss, and a work email rule is one single check. New accounts every month? AbuseZero recognizes repeat devices across new accounts, even when email addresses keep changing. The same card on a new account? AbuseZero detects repeated payment fingerprints across users, even when new accounts and emails hide the connection. Where your lists go stale, it checks mailbox aliases, disposable domains and mail routing. Where an IP limit knows only an address, it 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.
Your server makes one API call before a free pack goes out and gets a clear allow or deny, under eligibility rules you control. Your app still runs signup and meters credits. Observe mode shows you what would be denied before anyone is blocked, which matters when the account in question could be a $299 customer. The quickstart protects your first benefit.
Frequently asked questions
What is B2B data free credits abuse?
It's a business opening account after account to collect your free contact credits instead of buying a plan.
Is an agency with several client accounts abusing my free plan?
Not always. Separate workspaces for clients are normal on a paid plan. Write down what you mean to give each company, and see account sharing vs multi-accounting.
Can I take back contact data after a repeat claim?
No. Once it's exported, it's theirs in practice. You can take back unused credits and stop the next grant.
Keep your free credits for buyers testing your data
Start with Builder
Pay as you go. Evaluate your first claim today.
See pricing
Builder, Pro, Scale and Enterprise.
Talk to us about Enterprise
High volumes and custom terms.