Purpose and test conditions
Could RocketReach match the tester’s own LinkedIn profile and return usable contact data? Jimmy opened a self-service account on October 20, 2026. Its subscription row displayed Free, $0.00, monthly and Active. Usage showed five Lookups remaining and five Company Exports remaining. These were separate account allowances; Company Exports did not establish contact-export rights.
We fixed the sample at one identity before matching and did not substitute a more discoverable person. This differs from our Lusha workflow test, which used a filtered prospect sample. Neither test supports a direct accuracy comparison with the other.
The account’s Email Type setting displayed All emails available. We did not change it or verify a work-email-only setting. No email was sent, no contact was enrolled in outreach and no paid upgrade was purchased. No new mailbox or CRM connection was part of this test.
The evidence consists of dated account checkpoints, screenshots and inspection of the downloaded CSV. This is one self-profile case, not a representative database-coverage or deliverability test. For broader buying context, read our RocketReach review.
Search: zero URL results and eleven name candidates
RocketReach interpreted the supplied LinkedIn URL as a Social Link query. All Results, Net New and My Contacts each displayed zero. The page showed both a no-results message and a message that matching results could not be displayed. We did not establish why this query returned no visible result.
A separate name query for Jimmy Dwyer displayed eleven candidates and zero My Contacts. Jimmy reported that he could not find his own record. A name match alone would not establish the right identity, and we did not retrieve a namesake’s contact details to force a positive result. The eleven candidates were not eleven confirmed matches to the tester.
An account checkpoint after the URL search still showed five Lookups and five Company Exports remaining. This establishes no observed decrease at that checkpoint, rather than a general rule that every search route is free.
Native URL submission: completed with no match
Upload a List offered People and Companies routes. Within People, we inspected the CSV and pasted-LinkedIn-URL options, then used the native paste route for the same single profile. The form counted one profile URL and estimated one lookup. Its statement that only accurate matches would be charged was RocketReach’s description of the operation.
The task subsequently showed Completed, with these counts:
| Task counter | Result |
|---|---|
| Submitted Contacts | 1 |
| Matched Contacts | 0 |
| Verified Matched Contacts | 0 |
The generic heading said the list had been created and contacts were ready. That wording did not mean a contact had been found: the specific completed-task counters remained zero. We downloaded the result of that existing task rather than submitting another request.
We prepared a one-row CSV as an alternative input but did not upload it. Inspecting the CSV instructions does not establish that CSV import, column mapping or enrichment worked.

CSV inspection: a preserved input, not a discovered contact
The downloaded CSV was 526 bytes, comma-delimited UTF-8 without a BOM. It contained 34 unique column headings and one data row of 34 fields, with no exact duplicate data rows.
| Exported content | Observed result |
|---|---|
Input - linkedin_url |
The exact submitted tester-owned URL |
| Name and Profile ID | Blank |
| Email fields and Email Lookup Status | Blank |
| Phone fields | Blank |
| Employer, title and other output fields | Blank |
Only the input URL was populated; the other 33 fields were empty. The file therefore was not header-only, but its one row did not represent one contact found. We retained the original file privately and report only its structure and aggregate contents.
The subsequent My Contacts view displayed All Contacts (0), no contact rows and a No Results Found message. Its filter panel was collapsed, so we did not audit its contents. The view was consistent with the task’s zero matches; it did not demonstrate successful saving or persistence of a populated list.
Allowances: no observed decrease for this unmatched request
| Recorded checkpoint | Lookups remaining | Company Exports remaining |
|---|---|---|
| Initial Usage & Billing | 5 | 5 |
| After the URL-search checkpoint | 5 | 5 |
| After the completed matching task | 5 | 5 |
The completed unmatched request caused no observed decrease in these displayed allowances. That is consistent with the task’s match-contingent charge statement for this case. It does not verify successful-match charging, every export route or a universal refund policy. We did not spend the remaining allowance on replacement targets.
The account displayed a next lookup issue date of November 20, 2026. This was an account-specific label, not proof of guaranteed future issuance or a universal Free-plan entitlement.

Pricing evidence: monthly and annual billing differ
On October 22, we inspected screenshots of RocketReach’s pricing cards and comparison table. The seat selector displayed one; the cards used a dollar sign. The screenshots establish those displayed offers, rather than a universal country-to-currency mapping or a completed checkout.
| Plan | Monthly billing | Displayed monthly equivalent with annual billing | Annual bill | Monthly-plan lookups / exports per month | Annual-plan lookups / exports per year |
|---|---|---|---|---|---|
| Essentials, email only | $69 | $33 | $399 | 100 / 100 | Unlimited / 1,200 |
| Pro, email and phone | $119 | $75 | $899 | 250 / 250 | Unlimited / 3,600 |
| Ultimate, email and phone | $209 | $142 | $1,699 | 1,000 / 1,000 | Unlimited / 20,000 |
Use the explicit annual bill for budgeting. The headline monthly equivalents are rounded: $399 divided by twelve is $33.25; $899 divided by twelve is about $74.92; $1,699 divided by twelve is about $141.58. Multiplying the displayed $33, $75 or $142 by twelve will not reproduce each annual bill exactly.
Against twelve monthly payments, the annual bills save approximately 51.8%, 37.0% and 32.3%, respectively. The page’s Save 50% badge is not an exact uniform discount across these plans. Billing choices also change allowances, so this compares bills rather than identical usage bundles.
The important buying distinction is that annual Unlimited lookups do not mean unlimited exports. The page still lists annual export caps, and those caps differ from the monthly plans’ annualized export counts. Unlimited, verified-contact and accuracy wording are vendor claims; we did not test paid-plan capacity or fair-use terms.
The selector also advertises a discount for adding a seat, and custom team plans start at $6K annually. We did not capture a multi-seat quote, enter checkout or verify taxes, renewal, cancellation, rollover, API-specific limits or detailed unlimited-use conditions. Multiplying a one-seat price does not establish the actual discounted team quote.
View the pricing screenshots inspected October 22



What the findings change in our review
Our review now includes this completed, bounded self-profile matching attempt and the checked result file. Contact discovery and enrichment did not succeed in this case: neither the task, contact list nor CSV returned contact data for this identity. A completed job and a downloadable row are insufficient evidence of a usable contact.
For buyers, our practical recommendation is to test known, authorized identities before committing to a paid plan, inspect which output fields are populated and reconcile the actual allowance change. Match your export requirement to the chosen billing plan separately from its lookup headline. This case does not establish that RocketReach will fail for another person, industry or account.
Limitations
- One tester-owned profile; no representative sample or cross-vendor accuracy ranking.
- The reason for the missing match remains unresolved. We did not establish that the profile was absent from the underlying database.
- No successful email or phone retrieval, ownership validation, employment check or delivery test.
- No executed CSV import, populated-list persistence, repeat lookup, duplicate-handling or CRM/API test.
- Paid-plan features and marketing performance claims were inspected as page descriptions, not exercised.
- The pricing evidence was inspected on October 22; it does not constitute another matching test or a checkout audit.
Re-test and correction history
| Date | Record |
|---|---|
| October 20, 2026 | Original single-profile search and matching test; zero matches, input-only result CSV and unchanged displayed allowances recorded. |
| October 22, 2026 | Monthly/annual pricing screenshots inspected and report drafted. No new target, matching request or contact reveal; the original test date remains October 20. |
