Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Overloop (formerly Prospect.io) · overloop.com

Report an error on this page Is this your product? →

Link to this page

Overloop: AI-assisted analysis on whats-best.ai Overloop: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Overloop at a glance

Vendor
Overloop (formerly Prospect.io)
Headquarters
Incorporated in Belgium source, captured 17 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Overloop 1.5/5, the mean of 6 judges. Overloop (formerly Prospect.io) is a lead generation product built on a database of over 450 million B2B contacts, with email verification, multichannel email-and-LinkedIn sequences and CRM sync. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Overloop alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Overloop (formerly Prospect.io) is a lead generation product built on a database of over 450 million B2B contacts, with email verification, multichannel email-and-LinkedIn sequences and CRM sync. Its strongest showing is CRM sync and export, scored 6, on two-way sync every 10 minutes with Salesforce, HubSpot and Pipedrive, email-based matching, CRM-wins conflict precedence and a public API. Pricing transparency scored 4 on two published tiers, Starter at 69 USD and Growth at 99 USD, each per user per month, with a free trial. The weakness is the data layer: data provenance scored 2, with no public information on source categories, the vendor's lawful basis or removal routes for people in the database, and visitor identification spans 1-2, since the only intent signals documented are job changes and funding events. Sovereignty scored 3: the contracting entity is Overloop SRL in Brussels, but we found no public information on where the database is hosted. Persona-weighted totals ran 3.1-4.1 — the SDR persona highest at 4.1, the data-protection and ABM personas lowest at 3.1 — with no material disagreements computed.

Report an error

Speaks for it

  • CRM sync and export scored 6, on two-way sync every 10 minutes for Salesforce, HubSpot and Pipedrive with CRM data winning conflicts and blank fields never overwriting
  • Pricing transparency scored 4, with Starter at 69 USD and Growth at 99 USD, each per user per month, published with a free trial
  • Email verification sorts results into valid, uncertain and invalid before campaigns, with catch-all domains held for a separate decision
  • Prospecting compliance scored 4-5, on sourcing from the database, CSV import and a Chrome extension into fixed lists and dynamic segments
  • The contracting entity is fully named — Overloop SRL, Rue des Pères Blancs 4, 1040 Brussels, Belgium, VAT 0645.917.753 — alongside terms of use, a privacy policy and a GDPR page

Report an error

Held against it

  • Data provenance scored 2: we found no public information on source categories for the contact data, the vendor's own lawful basis, or a self-service removal route for people in the database
  • Visitor identification scored 1-2: we found no public information on identifying companies behind website visits, and the documented signals are job-change and funding triggers
  • Data coverage scored 3-4, with the vendor's own caveats that coverage varies by role and market and that records guarantee neither current position nor deliverability
  • The sync is documented never to delete records, so an objection or erasure on one side will not propagate
  • We found no public information on credits included per tier, per-item credit costs, credit expiry or overage rates

Report an error

Best for

  • You run Salesforce, HubSpot or Pipedrive and need documented two-way sync every 10 minutes that keeps CRM data authoritative in conflicts and never overwrites existing values with blanks
  • Your SDR team sources prospects from database search, CSV import and a Chrome extension, then runs email-plus-LinkedIn sequences from fixed lists and dynamic segments
  • You want email addresses verified into valid, uncertain and invalid buckets before a campaign launches, with catch-all domains held for a separate decision
  • You budget by seats and want two published tier prices, Starter at 69 USD and Growth at 99 USD per user per month, with a free trial to start

Report an error

Avoid if

  • You need to identify the companies behind website visits — the documented signals are job-change and funding triggers for prospects already known to you, and visitor identification scored 1-2
  • Your procurement requires provenance documentation — the published GDPR material covers the customer's use of the product (team training, supplier reviews, exclusion lists), not the sources of the contact data, and data provenance scored 2
  • Your CRM hygiene depends on deletions propagating — the sync is documented never to delete records, so an objection or erasure on one side stays put
  • You must compute a total annual budget — ask the vendor: the public pages we read do not show it

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Coverage, accuracy & freshness

Show reasoning
How this is scored

How much of the target market the database actually covers — judged on DACH and EU coverage as much as North American — and what the vendor documents about verification and refresh, because accuracy claims cannot be checked from outside.

0 — Not a data product: the tool supplies no contact or company data and only manages leads the customer brings.

3 — Total record counts for the database with the data types offered (email, phone, company data) and email verification mentioned.

5 — Coverage stated by country or region with Europe or DACH included, email verification described, firmographics beyond name and domain (industry, size, revenue), and a refresh cadence or last-verified date stated.

8 — Coverage broken down by country, industry and data type (email, direct dial, mobile), verification method and refresh cadence documented, company data drawn from official registers where available, and a bounce or credit-back guarantee with stated terms.

10 — The vendor is accountable for its data: per-country coverage and accuracy methodology published, every field carrying a last-verified date visible to the user, register-sourced company data, and credit-back terms that make inaccuracy the vendor's cost rather than the buyer's.

Report an error

The SDR Team Lead

Over 450 million B2B contacts is the headline, with email finder, verification and a phone finder as the data types on offer, and verification is properly described — valid, uncertain and invalid results with catch-all domains kept in a separate bucket before a campaign starts. But I found no public information on coverage by country or industry for my DACH patch, no firmographics beyond the contact record, and no refresh cadence or last-verified dates; the vendor itself says coverage varies by role and market and that records guarantee neither current position nor deliverability. 2 3 4

Report an error

The RevOps Manager

Total database size is stated as over 450 million B2B contacts, with email finding, email verification and a phone number finder as the data types, and verification described down to valid/uncertain/invalid results with catch-all domains flagged separately. Coverage comes only with the vendor's own caveat that it varies by role and market, and we found no public information on coverage by country or region, firmographic fields, a refresh cadence or last-verified date, or a bounce or credit-back guarantee. 2 3 4

Report an error

The Data Protection Officer

The vendor claims more than 450 million B2B contacts and describes email verification in valid, uncertain and invalid categories with catch-all domains flagged separately, plus a phone finder that spends credits only on a match. Coverage is qualified only as varying by role and market, with no country or regional breakdown, refresh cadence or last-verified date, and the vendor itself warns that records prove neither a person's current position nor deliverability. 2 3 4

Report an error

The ABM Marketer

Over 450 million B2B contacts is the headline number, with email verification separating valid, uncertain and invalid results and a phone finder that spends credits only on a match — and the pages are blunt that coverage varies by role and market and that records guarantee neither current position nor deliverability. I found no coverage by country or region, nothing on DACH or Europe, no verification method, refresh cadence or bounce guarantee. Working a fixed account list, I cannot tell from these pages whether my German and Austrian targets are even in this database. 2 3 4

Report an error

The DACH Sales Director

A total of 450 million contacts plus email verification with valid, uncertain and invalid categories is the honest but thin extent of it: coverage "variiert je nach Rolle und Markt", and I found no public information on per-country figures for Germany, Austria or Switzerland, on verification method, or on any refresh cadence or last-verified date. For a Mittelstand pipeline that is a database size and a disclaimer, not a coverage statement I could defend to a customer. 2 3 4

Report an error

The Skeptic

The headline is 450 million-plus B2B contacts, with email verification that sorts results into valid, uncertain and invalid before campaigns — the verification triage is the honest part. But the only coverage statement beyond the count is that it varies by role and market: we found no public information on a country or DACH/Europe breakdown, a verification method, a refresh cadence or last-verified date, and the vendor's own pages state records guarantee neither current position nor deliverability. A count plus a caveat is not coverage a buyer can plan a territory around. 2 3 4

Report an error

Data sources & lawful basis

Show reasoning
How this is scored

Where the personal data in the database comes from and on what legal basis it is processed — as evidenced on the vendor's own pages. Covers Art. 6(1)(f) legitimate interest, the Art. 14 notice to the people in the database, and whether they can find, object to and remove their record.

0 — The vendor states that it leaves the legal basis for the personal data it sells entirely to the buyer, or that records are collected without the people in them being able to object.

3 — Sources described in general terms (public sources, partners), a GDPR legal basis named, and an opt-out or removal route for people in the database.

5 — Source categories named (registers, company websites, contributory networks, licensed partners), legitimate interest under Art. 6(1)(f) stated as the basis for EU records, a privacy notice addressed to the people in the database, and a self-service opt-out or removal process.

8 — The above plus an Art. 14 notification practice described (people informed when added), contributory or browser-extension collection disclosed as such, a legitimate-interest assessment summarised publicly, and EU records handled differently from US records where the law differs.

10 — Provenance is traceable per record: the source and collection date available for each contact, Art. 14 notices sent and documented, the balancing test published, objections honoured across the whole dataset and suppressed permanently, and no data sourced by scraping behind logins or from contributors' address books without their contacts' knowledge.

Report an error

The SDR Team Lead

The phone finder "searches multiple sources" and there is a dedicated GDPR page, user-facing compliance articles and GDPR training for the team, but I found no public information on source categories for the contact database, the legal basis the vendor relies on to sell EU records, or an opt-out and removal route for the people in it. The vendor is upfront that a record is not consent and that the lawful basis is mine to own — honest, but it leaves the provenance question open. 2 4 5 6

Report an error

The RevOps Manager

There is a GDPR page (team trained, suppliers contacted for their own GDPR compliance, better export, exclusion lists) plus help articles on being GDPR compliant and on prospects' rights, and the vendor is candid that a database record is not consent. But we found no public information on where the contact data is sourced from, the legal basis for the EU records sold, or a self-service route for the people in the database to find and remove their record. 2 5 6

Report an error

The Data Protection Officer

Beyond a phone finder said to search multiple sources, the captured pages name no source category for the database records, state no legal basis for the vendor's own collection, and show no route by which the people in the database can be found, object or be removed; the GDPR material addresses the customer's use of the product, not the data subjects. The vendor's own words that a record is not consent and that compliance depends on the buyer's lawful basis leave the Article 6 question with whoever exports the list. A help article on prospects' rights exists by title, but its content is not shown. 2 3 5 6

Report an error

The ABM Marketer

The GDPR material is aimed at the customer — a guide to using the tool compliantly, team training, supplier reviews — and it states plainly that a database record is not consent and that audience, lawful basis and opt-out handling are the customer's to manage. I found no public information on where the 450 million contacts come from, the vendor's own legal basis for them, or a self-service removal route for the people in the database beyond the title of a help article on prospects' rights. 2 4 5 6

Report an error

The DACH Sales Director

The vendor is frank that a record is not consent and that campaign compliance depends on the buyer's lawful basis, but we found no public information on where the contact data comes from beyond phone numbers found by "searching multiple sources", on a named legal basis such as legitimate interest, or on an opt-out route for the people in the database. The GDPR page documents team training and supplier checks instead of source categories or a notice to data subjects. 2 4 5

Report an error

The Skeptic

The GDPR page documents the vendor's housekeeping — team training, contacting suppliers about their own GDPR compliance, exclusion lists with minimal data — and the help centre carries articles on prospects' rights, but we found no public information naming a source category for the contact data, the vendor's own lawful basis such as legitimate interest, an Art. 14 notice to the people in the database, or a self-service removal route for them. The published guidance that a record is not consent addresses the buyer's lawful basis for outreach, not the basis on which Overloop sells the records. Provenance of the database itself is undocumented on these pages. 4 5 6

Report an error

Visitor identification & intent signals

Show reasoning
How this is scored

Identifying companies behind website visits and surfacing buying intent — scored on what is identified (company or person), how the tracking works, and whether the vendor states that its script needs consent under §25 TDDDG and how it behaves without it.

0 — No visitor identification or intent data; the product does not look at website visits.

3 — Reverse-IP identification of the companies behind website visits through a tracking script, with visits listed per company.

5 — Company-level identification with filters and visit history per company, alerts or CRM handover of identified companies, and a stated position on consent for the script or a consent-mode option.

8 — Company-level only for EU traffic by design, cookieless operation documented, integration with common consent management platforms and the §25 TDDDG position stated, intent topics or page-level signals with the source of third-party intent data named, and alerts routed to owners.

10 — Identification that survives a DPO review: no personal data of visitors stored, the TDDDG and GDPR position published and specific, third-party intent data sourced from a named co-op or panel with its consent basis stated, and scoring on intent that the user can trace back to the underlying visits.

Report an error

The SDR Team Lead

The only intent-style signals on the captured pages are job changes, funding events and similar triggers used for prioritizing outreach. I found no public information on identifying companies behind website visits, any tracking script, or the vendor's position on consent for such a script. 3

Report an error

The RevOps Manager

Buying signals from job changes and financing are documented for prioritising outreach, and campaign events including page visits are written into the CRM as notes. We found no public information on identifying the companies behind website visits, cookieless operation, or any stated position on consent for a tracking script under the German Telekommunikation-Digitale-Dienste-Gesetz. 3 8

Report an error

The Data Protection Officer

We found no public information on identifying the companies behind website visits, on a tracking script, or on any consent position for one; the intent signals documented are job changes and funding events for prioritisation, with outreach engagement events such as page visits written back to the CRM as notes. We also found no public information on a consent-mode option or a position on the German tracking-consent rule. 3 8

Report an error

The ABM Marketer

This is the heart of my job — knowing which of my three hundred accounts are in market — and I found no public information on identifying companies behind website visits, a tracking script, a consent position for one, or third-party intent data with a named source. The closest the pages come is buying signals from job changes and funding rounds for prioritisation, and a page-visit event logged as a note against a prospect already in a sequence — decent triggers, but not de-anonymised account visits with alerts reaching the account owner while the signal is warm. 3 8

Report an error

The DACH Sales Director

Buying signals such as job changes and funding rounds are documented for prioritisation, and tracked campaign events can note when a prospect visits a page, but we found no public information on identifying the companies behind anonymous website visits, on any tracking script's behaviour, or on a TDDDG consent position. This is trigger data for known prospects, not visitor identification. 3 8

Report an error

The Skeptic

What the pages show are buying signals for prioritisation — job changes, funding — and campaign tracking of opens, clicks, replies and page visits written into CRM notes; these are third-party triggers and email-event tracking, not website-visit identification. We found no public information on identifying the companies behind website visits, any tracking script and how it behaves, or a stated position on consent for such a script. I can only score the intent-adjacent signals that are actually documented. 3 8

Report an error

Prospecting workflow & outreach rules

Show reasoning
How this is scored

Search, list building and outreach — and whether the product helps the buyer stay within UWG §7 and the GDPR once the list exists, rather than leaving the legal risk entirely with the customer.

0 — No search, list building or outreach; the product only stores leads entered or captured elsewhere.

3 — Search with filters on firmographics and job title, saved lists, and export of the contacts found.

5 — Advanced filters (technographics, hiring or funding triggers), saved searches with alerts, a suppression or do-not-contact list, and guidance on GDPR or cold-outreach rules for EU contacts.

8 — Country-aware handling (for example German contacts flagged where cold calls and emails require consent under UWG §7), phone numbers checked against national do-not-call registers where they exist, and opt-outs from outreach synced back to the database.

10 — Compliance is part of the workflow: outreach channels restricted or flagged per country and contact type by default, suppression shared across the whole account and every export, the Art. 14 notice supported at first contact, and a documented record of how each contact entered the buyer's pipeline.

Report an error

The SDR Team Lead

Sourcing runs from the database, CSV import and a Chrome extension into one workspace with lists, dynamic segments and bulk edit, and there is a documented exclusion-list practice plus GDPR guidance that tells me straight that a record is not consent and that audience, lawful basis and opt-out handling are mine to manage. Job-change and funding triggers feed prioritization, but I found no public information on saved-search alerts or country-aware flagging of German contacts. 2 3 5 6

Report an error

The RevOps Manager

Database search, CSV import, a Chrome extension, fixed lists, dynamic segments, bulk edit, and job-change and funding triggers are documented, together with an exclusion-list feature positioned as a GDPR-friendly measure. The vendor also gives real guidance — a record is not consent, compliance depends on your lawful basis and how you handle outreach and opt-outs — but we found no public information on country-aware flagging of German contacts, checks against do-not-call registers, or opt-outs syncing back to the database, so the legal risk in outreach sits with the buyer. 2 3 5 6

Report an error

The Data Protection Officer

Fixed lists and dynamic segments, job-change and funding triggers, and multichannel email and LinkedIn sequences are documented, and the GDPR page credits the product with exclusion lists holding the minimum amount of data — a genuine suppression mechanism. The vendor publishes customer-facing guidance, including articles on GDPR compliance and prospects' rights, and states plainly that a record or a verification result is not permission to contact anyone. We found no public information on country-aware handling, do-not-call register checks, or opt-outs synced back into the database, so the outreach risk stays with the buyer. 3 4 5 6

Report an error

The ABM Marketer

There is genuine workflow — sourcing from the database, CSV or a Chrome extension, fixed lists and dynamic segments, exclusion lists holding a minimum of data, and job-change and funding triggers — alongside a GDPR compliance guide and help articles including one on prospects' rights. But the captured pages put the lawful basis and opt-out handling squarely on the buyer, and I found no public information on country-aware flagging for German contacts under UWG §7 or checks against do-not-call registers. 2 3 5 6

Report an error

The DACH Sales Director

Database search, static lists and dynamic segments, multichannel email and LinkedIn sequences, buying signals as triggers and exclusion lists with minimal data make a real workflow, and the vendor publishes GDPR help articles on compliance and prospects' rights plus the reminder that verification is not permission. What I miss selling into Germany is country-aware handling: we found no public information on flagging German contacts where cold calls need consent under UWG §7, and no do-not-call register check. 2 3 5 6

Report an error

The Skeptic

The workflow is real: search the database, import a CSV, add contacts via a Chrome extension, save lists and dynamic segments, run email-and-LinkedIn sequences, and export — and there is genuine posture, with a dedicated GDPR page, a help article titled 'How to Be GDPR Compliant When Using Overloop', exclusion lists built on minimal data, and plain statements that a record and a verification result are not permission to contact anyone. Job-change and funding signals also function as hiring and funding triggers for prioritisation. We found no public information on saved-search alerts, country-aware flagging of German contacts under UWG §7, checks against do-not-call registers, or opt-outs synced back into the shared database. 2 3 4 5 6

Report an error

CRM sync, enrichment & export

Show reasoning
How this is scored

Getting the data into the systems where sales works — CRM sync, enrichment of existing records, API — and what happens to exported data, and to the buyer's access to it, when the subscription ends.

0 — Data can only be viewed inside the product; the vendor states no export and no integration.

3 — CSV export and a push of contacts to at least one named CRM.

5 — Native integrations with the major CRMs (Salesforce, HubSpot or similar) with field mapping or deduplication, enrichment of existing CRM records, and a documented API.

8 — Bidirectional sync with scheduled re-enrichment, update and deletion propagated when a record changes or a person objects, webhook or API access with stated limits and credit costs per call published, and data retention rights after cancellation stated plainly.

10 — The vendor treats the buyer's CRM as the system of record: objections and corrections propagated into synced records automatically, full change history per field, a versioned API with a deprecation policy, and exit terms that say exactly which data the customer may keep and for how long.

Report an error

The SDR Team Lead

Two-way sync every ten minutes with Salesforce, HubSpot and Pipedrive — matching on email, field mapping, CRM data winning conflicts, blank fields never overwriting, engagement events written back as notes — plus a public API keeps the CRM authoritative, which is exactly what I want. The sync will never delete records by design, and I found no public information on API limits or credit costs per call, or on retention of my data once I cancel. 7 8

Report an error

The RevOps Manager

This is the strongest part of the evidence: two-way sync every 10 minutes for Salesforce, HubSpot and Pipedrive with user and field mapping, records matched by email so an existing record is updated instead of duplicated, CRM data taking precedence on conflict, blank values never overwriting existing data, engagement events added as notes, a Salesforce API-call cap, and a documented public API. The sync will never delete records, so an objection or erasure will not propagate out of Overloop, and we found no public information on published API limits and credit costs per call or on data retention rights after cancellation. 5 7 8

Report an error

The Data Protection Officer

Two-way sync every ten minutes with Salesforce, HubSpot and Pipedrive, email-based matching, field mapping, CRM-wins conflict precedence and a documented public API form a solid integration story, and improved data export is confirmed on the GDPR page. But the vendor states the two-way sync will never delete records, so an objection honoured in the database is not propagated to the CRM — and we found no public information on retention rights or export terms after cancellation. 5 7 8

Report an error

The ABM Marketer

Two-way sync every ten minutes with Salesforce, HubSpot and Pipedrive, matching by email, CRM data taking precedence in conflicts, blank fields never overwriting existing data, and email opens, clicks and page visits written into the CRM as notes — plus a documented public API with Zapier. Two things give me pause: the sync is documented to never delete records, so an objection or removal on one side will not propagate, and I found no public information on API rate limits, credit costs per call, or what data I could keep after cancelling. 5 7 8

Report an error

The DACH Sales Director

Two-way sync every ten minutes with Salesforce, HubSpot and Pipedrive, matching by email so existing records update instead of duplicating, field mapping, CRM precedence on conflict, tracked events written as notes and a public API with Zapier is solid, documented work, and data export is named in the GDPR efforts. But the sync is stated to never delete records, and we found no public information on API limits or per-call credit costs, webhooks, or what data a customer may keep after cancelling. 5 7 8

Report an error

The Skeptic

Two-way sync with Salesforce, HubSpot and Pipedrive runs every 10 minutes, matching records by email address, with field mapping, explicit precedence rules (CRM data always wins conflicts, blank fields never overwrite), tracked events written into CRM notes, Salesforce API-limit protection, plus a documented public API and Zapier. But the vendor states the sync will never delete any records, so a deletion or objection on one side does not propagate; we found no public information on API rate limits, credit costs per call, or what data the customer keeps after cancellation. Strong plumbing, silent on the endings that matter. 5 7 8

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where a database of EU residents' personal data is held, who the contracting entity and controller are, and which subprocessors see it. Independently sourced by the sovereignty pipeline; weighted heavily here, because the product itself is personal data about people who never chose the vendor.

0 — Vendor, contracting entity and processing of EU residents' contact data all shown to be outside the EU, with no transfer basis stated.

3 — A named contracting entity and a privacy policy or data processing agreement; a non-EU entity with an EU representative under Art. 27, or EU hosting offered while the hosting location of the database is not stated.

5 — EU hosting stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.

8 — EU contracting entity and controller, EU hosting on named infrastructure, subprocessor and data-partner list published, and any non-EU transfer named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, controller, hosting, data partners and every subprocessor European, certification published, and a DPA covering both the customer's data and the database records the customer exports.

Report an error

The SDR Team Lead

The contracting entity is named and European — Overloop SRL at Rue des Pères Blancs 4, 1040 Brussels, with a VAT number — and terms of use, a privacy policy and a GDPR page exist, with the vendor stating it reviewed all suppliers processing personal data on its behalf for GDPR. I found no public information on where the database is hosted, a subprocessor list, or a data processing agreement, so the residency question stays open. 4 5

Report an error

The RevOps Manager

The contracting entity is named and placed in Brussels — Overloop SRL with street address and VAT number — and terms of use, a privacy policy and a GDPR page exist. We found no public information on where the database of EU contacts is hosted, a data processing agreement, a subprocessor list, or any non-EU transfer and its legal basis. 4 5

Report an error

The Data Protection Officer

The contracting entity is Overloop SRL with a Brussels address and VAT number, and privacy policy, terms of use and a GDPR page are published — an EU vendor by entity. We found no public information on where the database is hosted, on a data processing agreement, or on a subprocessor list; only Intercom for support and a general statement that suppliers were reviewed for GDPR appear. 4 5 6

Report an error

The ABM Marketer

The contracting entity is named and European — Overloop SRL, Rue des Pères Blancs 4, 1040 Brussels, Belgium, VAT 0645.917.753 — with a privacy policy, a GDPR page and a supplier GDPR review on record. I found no public information on where the database of EU contacts is hosted, a data processing agreement, or a published subprocessor list. 4 5

Report an error

The DACH Sales Director

The contracting entity is Overloop SRL with a Brussels address and Belgian VAT number, an EU jurisdiction, and terms, a privacy policy and a GDPR page exist — though the company details appear only in a page footer. The hosting location of the database is not stated anywhere captured, and we found no public information on a data processing agreement, a subprocessor list or any transfer basis, only that suppliers were contacted to confirm their own GDPR compliance. 4 5

Report an error

The Skeptic

The contracting entity is named and checkable — Overloop SRL, Rue des Pères Blancs 4, 1040 Brussels, Belgium, VAT 0645.917.753 — with a privacy policy, a GDPR page, and support named as running on Intercom. We found no public information on where the database of EU residents' contact data is hosted, a data processing agreement, a subprocessor or data-partner list, or any transfer basis — an EU address in a footer is where the evidence starts and stops. 4 5 6

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone — including credits per email, phone number and mobile, credit expiry, seat pricing, visitor-identification tiers and the API — in a category where the unit of billing is often invented by the vendor.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price, a free tier or one priced tier, while what a credit buys or the other tiers are not stated.

5 — Prices public per tier with the billing period and the credits or contacts included per tier; extras such as mobile numbers, additional seats or API access may still be on request.

8 — Every tier priced publicly with credits per data type, credit expiry and rollover, per-seat costs, overage rates, minimum term and VAT treatment stated.

10 — Complete price computability: the annual invoice derivable for a given number of seats, exported contacts by data type, identified companies and API calls, with every credit cost and the refund rule for inaccurate data published.

Report an error

The SDR Team Lead

Two tiers are public — 69 USD per user per month for Starter and 99 USD for Growth, with a free trial — and the phone finder confirms a credit system where credits are spent only on a match. But I found no public information on credits included per tier, the credit cost of an email or a phone number, credit expiry, or overage rates, so I can budget seats but not a year of actual prospecting. 1 2 4

Report an error

The RevOps Manager

Two tiers are priced publicly — Starter at $69 and Growth at $99, each per user per month in USD — alongside a free trial, and credits are the billing unit at least for phone matches. We found no public information on the credits or contacts included per tier, credit expiry or rollover, overage rates, minimum term, VAT treatment, or current API pricing beyond a restriction of API access to the Business plan under an old pricing model. 1 2 7

Report an error

The Data Protection Officer

Starter at 69 USD and Growth at 99 USD, each per user per month, are public alongside a free trial. We found no public information on what credits each tier includes, credit expiry, overage or VAT treatment, and the public API is described as tied to a plan on the old pricing model — so the annual cost of a given workload cannot be computed from the captured pages. 1 2 7

Report an error

The ABM Marketer

Two tiers are priced publicly — Starter at 69 USD and Growth at 99 USD, each per user per month — alongside a free trial, and the phone finder notes spending credits only on a match. The credit economy itself is not on the captured pages: how many credits a tier includes, what each costs, expiry, overage, further tiers or VAT treatment are all unstated, so I cannot compute a real annual cost for my team. 1 2 7

Report an error

The DACH Sales Director

Two tiers are public and clearly unit-priced — Starter at "99"… correction, Starter at "69" and Growth at "99", each USD per user per month — plus a free trial, which beats a bare "from" price. But we found no public information on the credits or contacts included per tier, on credit expiry, overage rates, VAT treatment or any tier beyond Growth, so an annual cost for a DACH team is not computable from the public pages. 1 2

Report an error

The Skeptic

Two tiers are public — Starter at 69 USD and Growth at 99 USD, each per user per month — with a free trial, and the phone finder says you spend credits only on a match, so at least the currency of billing is disclosed. But we found no public information on the credits included per tier, the credit cost of an email, phone or mobile number, credit expiry, overage, minimum term or VAT treatment, and the public API was restricted to the Business plan under the old pricing model. A buyer cannot compute the annual cost from these pages. 1 2 7

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Overloop

Is Overloop European?

Not determined: the vendor’s pages as captured do not say where Overloop is based. Its vendor, Overloop (formerly Prospect.io), is incorporated in Belgium, per the vendor’s page captured 17 Nov 2026.

Where does Overloop store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

Does Overloop have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

What are the best alternatives to Overloop?

As of 18 Nov 2026, the panel rates Dealfront (3/5), Lusha (2.5/5) and Vainu (2.5/5) highest among the other 48 Lead Generation products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Dealfront (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Overloop alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (8)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page overloop.com Checked 17 Nov 2026 Details →
  2. 2 Coverage, accuracy & freshness — found from sitemap overloop.com Checked 17 Nov 2026 Details →
  3. 3 Coverage, accuracy & freshness — found from sitemap overloop.com Checked 17 Nov 2026 Details →
  4. 4 Data sources & lawful basis — found from sitemap overloop.com Checked 17 Nov 2026 Details →
  5. 5 Prospecting workflow & outreach rules — found from sitemap overloop.com Checked 17 Nov 2026 Details →
  6. 6 Prospecting workflow & outreach rules — found from sitemap support.overloop.com Checked 17 Nov 2026 Details →
  7. 7 CRM sync, enrichment & export — found from sitemap support.overloop.com Checked 17 Nov 2026 Details →
  8. 8 CRM sync, enrichment & export — found from sitemap support.overloop.com Checked 17 Nov 2026 Details →