Skip to content

How we verify

Human verification, or none at all.

Every contact is cross-checked by a person against LinkedIn and the company website before delivery, and the date of that check is recorded on the row. Records that cannot be confirmed are removed, not shipped as Pending.

How we verify

Brief, Source, Verify, QA and deliver.

Stage What happens Artifact produced
01 Brief A 30-minute Project Brief call with a senior analyst — not an SDR — to scope the ICP, territory, titles, volume and timeline. Ten fields, all required before research begins. If the brief shows we are not a fit, we say so before any work starts. The signed research brief
02 Source Analysts map the territory across twenty-plus sources — ZoomInfo, Apollo, Clay, LinkedIn Sales Navigator, Cognism, Lusha, Crunchbase, PitchBook and company websites — triangulated rather than exported. Accounts outside the brief are dropped here. The raw master source sheet
03 Verify Every contact is cross-checked by a person against LinkedIn and the company website: current role confirmed, employer matched, email format validated. The date of that check is recorded on the row. SMTP-only verification is the floor, not the ceiling. The LinkedIn cross-check log
04 QA and deliver A 10% spot-check by a second person, with zero QA failures permitted — anything that fails goes back to the analyst. Records that cannot be confirmed are removed, not shipped as Pending. Then a CRM-ready XLSX and CSV with a count summary. The QA spot-check sheet

What we exclude

The honest half of the method.

A list is only as good as what was taken out of it. These records are flagged and removed before delivery, and the Method sheet in your workbook names how many.

Removed Why
Generic inboxes info@, sales@ and hello@ reach a queue, not a person. They inflate a count and answer nothing.
Unconfirmed employers If the profile and the company site disagree about where someone works, the record comes out.
Retired titles A title that no longer exists at the company means the org chart moved and the record is stale.
Out-of-brief accounts Outside the employee band, the sector or the geography you specified. Close enough is not in the brief.
Prior removal requests Anyone who has asked us or a client to be removed stays on a suppression list and is not rebuilt.

Quality benchmarks

The targets we hold ourselves to.

These are targets, not audited results, and the difference is the point. Each one carries its source and date below. A measured figure replaces the target here the moment our bounce reports produce one — a QA rate invented to look good is exactly the vendor behaviour this page exists to contradict.

Measure Figure Source
Client-reported bounce rate Under 8% Target · 2026
Internal QA failure rate Under 3% Target, measured before delivery · 2026
On-time delivery within agreed TAT 100% Target · 2026
QA spot-check sample, every project 10% Delivery SOP stage 5 · 2026

What you receive

One workbook, four sheets, and a CSV that imports cleanly.

Delivered as QD_[Client]_[Package]_[YYYYMMDD].xlsx with a matching UTF-8 CSV for direct CRM import. Phone columns are formatted as text, so long numbers do not arrive as scientific notation.

1 · Read Me

Client, package, ICP summary, delivery date, record counts, the verification method, and the guarantee stated verbatim.

2 · Verified Leads

One row per person. Company, contact, exact title, LinkedIn URL, verified email, confirmation date, status.

3 · Companies

One row per company. Domain, employee band, HQ country, sector, and the accounts we excluded.

4 · Method

Sources used, the verification steps applied, the exclusions, and the QA sample size.

Sheet 2 · Verified Leads — redacted specimen
Company Contact Title Confirmed Status
N•••••• Systems D. R••••• VP Engineering 2026-07-28 Verified
C•••••• Labs R. M••••• Head of Infrastructure 2026-07-29 Verified
A••••••• Digital S. T••••• Director, Service Delivery 2026-07-29 Verified
V•••••• Cloud J. P••••• Chief Technology Officer 2026-07-30 Verified

FAQ

Questions we are asked before the first call.

How is a contact actually verified?

A researcher opens the person’s LinkedIn profile and the company website, confirms the name, the exact title and the current employer, validates the email format, and records the date of that check on the row. A second analyst spot-checks 10% of the file before it ships. Anything that cannot be confirmed is removed rather than delivered as Pending.

What happens if the leads bounce?

Every delivery is covered for 7 days. If your campaign records a hard-bounce rate above 8% — the rate our 92%+ deliverability target implies — send us the bounce report within that window and we replace every bounced record free, re-verified, within 5 working days. Soft bounces, out-of-office replies and spam-filter blocks are sending problems rather than data problems, so those we help you read rather than replace.

Do you charge a retainer?

No. Pilot and Growth are one-time projects, quoted whole before they start. Scale is a monthly subscription with a three-month minimum, then cancel any time. No seat licences, no credits, no tool subscriptions.

What format is the delivery?

A CRM-ready XLSX workbook plus a matching UTF-8 CSV with a BOM. It drops straight into HubSpot, Salesforce, Apollo, Instantly, Smartlead or any outbound stack, with field mapping agreed before delivery.

Which markets do you research?

Primarily the United States, United Kingdom, Europe and the Middle East. Our clients are based in India, the US, the UK, the GCC and the EU. The research team is in Kochi.

Do you run the outbound campaigns too?

No, and that is deliberate. We hand off a cleaned, structured, ready-to-use list. Sequencing, cold calling and appointment setting stay with your team — we are better at our part because we only do our part.

Will you sign a DPA?

Yes, for any engagement where we handle records you already hold. Ask on the Project Brief and we send it for signature.

Book a project brief

Send us one ICP. We will show you what survives verification.