Cold outreach that
runs on a loop.
Scrapeloop sources fresh leads every month — scraped live or pulled from the database — cleans them in tables and flows, sends them to Instantly, GoHighLevel and Aimfox, then routes whoever didn't reply into the next channel. You pick the states. It does the rest.
- contacts in the database
- 56M
- states, pick any subset
- 50
- outreach channels
- 3
One lead, one month. Scraped on a schedule, cleaned in a table, then routed by the contact data it actually has — and moved to the next channel when it doesn't reply.
Four moves, then it repeats
Most stacks give you one of these and leave the other three to you and a CSV. Scrapeloop is the loop itself — which is why the leads keep coming and the campaigns stay full.
- 01Source
Leads arrive every month
Schedule a scrape — Google Maps, Yelp, Apollo, LinkedIn — or pull straight from the 56M-contact database. Choose the states you sell to and a monthly cap; the coverage map keeps track of what has already been pulled so each run finds new businesses.
- 02Clean
Tables and flows do the filtering
Every lead lands in a table with enrichment columns — find the owner, verify the email, check the line type — and rules that run on their own. Duplicates collapse, catch-alls are held back, bad rows never reach a campaign.
- 03Send
Straight into your outreach apps
Clean rows push into Instantly, GoHighLevel or Aimfox with the sequence and daily cap you set. Verification gates the send, so a campaign never burns a domain on an address nobody checked.
- 04Return
And the data comes back
Replies, bounces, unsubscribes and no-shows flow back onto the same lead row. No reply to email? It moves to SMS. Still nothing? A LinkedIn lookup and a DM. One lead, several chances — without you touching a spreadsheet.
Pick the states you actually sell to
Nobody needs all fifty. Select a territory, set a monthly volume, and Scrapeloop only spends against those tiles — then remembers what it already covered so next month's run brings new businesses, not the same ones again.
Coverage, not guesswork
The map records every platform × territory × category tile you've pulled and how fresh it is, so you can see the untapped pockets instead of re-scraping a city you finished in March.
Or skip scraping entirely
56M B2B contacts and a local-business index sit behind the same filters. Search by title, industry, geography and headcount, then send the result into a table — no vendor, no wait.
On a schedule, hands off
Set the run to monthly and it fills the table on its own. The rules that clean it and the campaigns that consume it are already wired, so a full pipeline is a calendar entry, not a Monday morning.
Click a state to add or remove it.
A table that enriches and filters itself
Columns are enrichers: find the owner, verify the email, check whether that number takes SMS. Rules watch the rows and act — hold back a catch-all, suppress a hard bounce, push a verified row into the campaign. You write them once.
- whenRow createdthenFind owner email → verify it
- whenEmail is catch-allthenHold back from sending
- whenEmail verifiedthenSend to Instantly · Sequence A
- whenReplied · not interestedthenSuppress for 180 days
Verification gates the send. A row whose email hasn't passed verification cannot enter a campaign — the guard lives in the sender, not in your memory.
Three channels, and the data comes back
Push a clean table into the tools you already send from. What matters is the return leg: replies, bounces and silence land back on the lead, so a rule can move it to the next channel instead of it dying in an export.
Verified emails only. Sequences, daily caps and sending accounts stay in Instantly — Scrapeloop keeps the list full and pulls the replies back.
Leads with a mobile number but no address get an SMS campaign, and the conversation syncs back into the CRM contact.
No email, no number, no problem: a profile lookup matches the person, then a connect-and-DM sequence runs on LinkedIn.
Nothing gets one shot. A lead that ignores four emails drops to SMS. If SMS goes quiet too, it gets looked up on LinkedIn and DM'd. Same lead, same table, no re-import — that is the loop.
No $400 surprises
Scraping and enrichment cost real money, so Scrapeloop treats spend as a first-class object rather than an invoice you read later.
One ledger, every vendor
Scrapes, enrichments, verifications and proxy bytes all write to a single spend ledger — attributed to the workspace, the credential and the job that caused them.
Caps that actually stop a run
Set a ceiling per credential, per integration and per workspace. When one is reached the job halts and tells you; it does not quietly keep spending.
Estimated before it runs
Every scrape and every enrichment column shows what it will cost before you press go, and the cost sits on the row and the node where the spend happens.
One console, every client
Sub-accounts get their own workspace, users, roles and credit meter. You get a console that shows volume and spend per client — and a sub-account never sees anything about the others.
Flat subscription, metered overage
Bring your own vendor keys in v1 — you pay the scrapers and verifiers directly, at their list price, with nothing added on top. Managed keys come later.
- 1 workspace
- 10K leads / month
- BYOK scrapers + enrichers
- 1 connected sender
- Email support
- 3 workspaces
- 50K leads / month
- Custom enricher recipes
- 3 connected senders
- Coverage map
- Slack + email notifications
- Unlimited sub-accounts
- 200K leads / month
- White-label (v2)
- CRM sync (HubSpot, GoHighLevel)
- Priority support
Prices in USD, billed monthly. Overage is metered per lead and shown in the same ledger as everything else.
Join the early-access waitlist
Scrapeloop is invite-only at launch. Leave your email and we'll send a code in the next batch.