Methodology

How we checked, and what we will not claim

This is a shortlist rather than a census. It started from the tools that come up when a B2B team assembles a sales stack, and was cut to the pairs where at least one side publishes documentation specific enough to check. Everything below is how a fact gets from a vendor's own page to this one, and what moved since.

68integrations checked
323citations
50vendor domains
24corrections of our own
How a fact gets here

Every claim has a document behind it and a date on it

There is one route onto a page in this directory, and it starts at a vendor's own site rather than at anybody's recollection.

A tier requirement, a sync direction or a documented limit is read from the vendor's own knowledge base, developer documentation or pricing page. It is written into a record with the date it was read, and the page renders from that record. 323 citations across 184 distinct documents on 50 vendor domains sit behind the 68 integrations here, and every guide lists the ones it rests on at the foot of the page.

Nothing is taken from a comparison article, a listicle or a vendor's sales deck. Where a page quotes a practitioner rather than a vendor, which it does 340 times across the directory, the quote is transcribed from a linked public thread, the section says when the threads were read, and the claim is never the only source for a number.

The dates are the point of the exercise rather than decoration. Facts here were read between 11 October 2026 and 28 October 2026, the change log records every one that has moved since, and the build refuses to render a changed claim that the log does not mention.

What this will not say

The refusals are the product

A directory is only worth reading if there are things it will not tell you, so these are written down rather than left to judgement.

01

No scores, no stars, no leaderboard

There is no rating out of five anywhere here and no aggregate score, because an integration is not better or worse in the abstract. It is right or wrong for a particular tier, a particular object and a particular direction, and those are published instead. The structured data carries no aggregateRating either, and the build fails if one ever appears.

02

No price per record that a vendor has not published

Reverse Contact publishes what each call costs in credits: nothing for a freshness check, two for a reverse lookup from an email, twenty for a direct phone number when one is found. Those appear on the pages. What is not published is a rate in pounds or dollars behind a credit, so no page prints one. Dividing a pack price by a credit count would be our arithmetic wearing their authority, and the build fails on a currency figure set against a lookup, a record or a call.

03

No estimate where a vendor quotes

ZoomInfo, Outreach, Gong and Sales Navigator Advanced Plus are sold on quotation. Every page that touches them says so rather than printing a number somebody found in a forum thread two years ago.

04

No match rate presented as a promise

Reverse Contact's published identity match rate is a global figure and appears as one, next to the instruction to measure your own on five hundred rows of your own list. No page implies it predicts what you will get.

05

No limit softened in the retelling

Where a vendor documents a limit it appears in the vendor's own terms, including the awkward ones: 315 of them across the directory, and 494 documented failures with the reason each one happens. A directory that lists only what works is a marketing page with a filter on it.

Those five are enforced rather than intended. Three of them fail the build if they are broken, which is the only version of a principle that survives a deadline.

The conflict

Reverse Contact publishes this directory and appears in it

That is a conflict of interest, and the useful thing to do with one is to state it everywhere rather than bury it once.

It is on every page that makes a factual claim, in the author block at the foot, alongside the date and the documents. Reverse Contact's own pages are held to the standard everyone else's are held to, which includes the part nobody enjoys writing: it has no app on any CRM marketplace, no AppExchange package and nothing inside a sequencer, and the pages where that matters say so in the author block rather than in a footnote.

It is also the weaker answer in several rows of the comparison on the directory home, and those rows stayed in. No other vendor pays for placement. Every outbound link in a listing or a citation carries nofollow, Reverse Contact's own included, and the two calls to action do not, because a call to action is not a citation.

The integration matrix is the fastest way to audit that claim: it is the whole dataset in one grid, and the cells where Reverse Contact is absent are as visible as the ones where it is not.

Check it yourself

five ways to audit a page without asking us

A methodology nobody can test is a promise. These are the routes that make this one checkable, and they are all open.

What you want to checkWhere to look
Whether a claim matches the vendorThe sources at the foot of every guide, with the date each was read
Whether a page has gone stale/changes
What the page says without the pageAny URL plus .md, which is that page as plain text
The whole dataset at once/data.json
A specific question, answered by machine/api/mcp

The MCP server answers the same records the pages are built from, which means an assistant can be asked to check a claim here against a vendor's own documentation without being handed our summary of it first. That is the test this directory would rather be judged on.

When we are wrong

24 of the 96 log entries are our own corrections

A change log that only ever shows other companies moving their goalposts is marketing, so ours records the times the mistake was here.

27 entries record a vendor changing something: a tier requirement moving, an endpoint being replaced, a plan being withdrawn. 24 record a correction of our own, including the one where a sync table shipped with every row pointing the wrong way on the single field this directory exists to get right.

The log is enforced rather than maintained by goodwill. Every claim a reader could act on is fingerprinted at build time, and if one moves without an entry naming the records it affects, the build stops. That is why the dates here can be trusted more than the usual "last updated" stamp: nothing can quietly change underneath one.

The hard part is not checking it once. It is checking it again.

Every figure here carries the date it was read, because a contact record goes stale continuously and a tier requirement changes a few times a year. Reverse Contact is the half of that problem you can automate: one API that resolves an email, a domain or a profile URL into a verified people and company record, with the freshness check costing nothing.

Free trial, no card required, and 500 credits to start.

FAQ

The method, asked and answered

The questions a sceptical reader asks first.

Who wrote this directory?

Reverse Contact publishes it and Eugene Suslov did the research, named and linked in the author block on every page that makes a factual claim. An organisation cannot be held to an account and a person can, which is why both are there rather than one.

Why should I trust a directory published by a vendor in it?

You should not trust it; you should check it. Every page names the vendor documents it rests on and the date each was read, the whole dataset is downloadable, and the conflict of interest is stated on every page rather than in a footer nobody opens. A directory that cannot survive being checked is not worth publishing.

How do you decide which integrations to include?

A pair is included where at least one side publishes documentation specific enough to check: a tier requirement, a sync direction, a rate limit, an object list. Pairs that exist only as a logo on a partner page are left out, because there is nothing to verify and nothing useful to say.

What happens when a vendor changes something?

It goes in the change log with what it was, what it is now, and which records it affects. The build enforces that: every claim a reader could act on is fingerprinted, and a claim that moves without a log entry naming the affected records stops the build rather than shipping quietly.

Why are there no ratings?

Because an integration is not better or worse in the abstract. It is right or wrong for a particular tier, a particular object and a particular direction, and publishing a number out of five would hide exactly the detail that decides it. The structured data carries no rating either, and the build fails if one appears.

Can I reuse the data?

Yes. The whole dataset is at /data.json with absolute URLs and open CORS, every page has a plain-markdown twin at its own path plus .md, and there is a read-only MCP server at /api/mcp with no key. Attribution is appreciated and the sources are cited so you can check them yourself rather than taking ours.

Checked by

Reverse Contact

We sell B2B people and company data, and we publish this directory. Every number on this page is derived from those records rather than typed, and each record was read from a vendor's own knowledge base, developer documentation or pricing page on the date below. Nothing on it is restated from a press release or a third-party listing.

Where a vendor publishes no public figure, this page says so rather than estimating, which is why no page here prints a cost per enriched record. Reverse Contact appears in this directory as a data provider and publishes it. No other vendor pays for placement, and every link out of a listing or a citation carries nofollow, including the ones that point at Reverse Contact. The only followed links on this page are the two calls to action and the reviewer.

Tier requirements, sync behaviour and documented limits change without notice. Confirm against your own contract before you budget. What has changed since · How we checked, and what we will not claim

Researched and written by

Eugene Suslov

Researched and wrote every page in this directory, and checked every tier requirement, sync direction and documented limit against the vendor's own knowledge base, developer documentation or pricing page.

Verified
2026-10-28
Sources
2 vendor documents
Paid placement
None

Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.

Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.

Ask an assistant