Services · Account-based
ABM starts with the account, not the contact.
You already know which companies matter. What the campaign needs is the people who sign, evaluate and can block inside each one — verified, dated, and grouped to the account rather than listed flat.
$895 · 500 accounts · 2,500 verified contacts · 10–14 days
- 92%+
- Deliverability target
- Stated guarantee · 2026
- 750
- Verified leads, Pilot
- 250 companies · 3 contacts each · 2026
- 5–7d
- Turnaround
- From a confirmed brief · 2026
Why a flat list breaks ABM
A flat list cannot express an account.
Named-account selling needs the buying centre inside each company — who owns the budget, who runs the evaluation, and who can stop it. One contact per company gives you a coin toss on which of those three you reached.
- 5 contacts per company on Growth, across three seniority levels. 3 on Pilot, if you are testing the approach first.
- The workbook carries a Companies sheet as well as a Verified Leads sheet, so contacts arrive grouped to their account rather than as loose rows to reassemble in your CRM.
- Accounts we cannot map to the agreed depth are reported as unmapped, with the reason — never padded with a generic inbox to hold the number up.
Depth per account
4.1 verified contacts per account, across every engagement we have published.
We have never delivered a one-contact-per-company list. The shallowest of the seven still ran 3.6 per account. This table is generated from the case studies, so it cannot disagree with them — and it moves when the next engagement lands.
| Engagement | Accounts mapped | Verified contacts | Per account |
|---|---|---|---|
| Technology and SaaS | 100 | 500 | 5.0 |
| Venture-backed startups | 110 | 480 | 4.4 |
| Healthcare and pharma | 60 | 240 | 4.0 |
| EdTech | 75 | 300 | 4.0 |
| Fintech and payments | 40 | 150 | 3.8 |
| Manufacturing and industrial | 120 | 450 | 3.8 |
| E-commerce and retail | 90 | 320 | 3.6 |
| All seven engagements | 595 | 2,440 | 4.1 |
What arrives per account
Columns, not benefits.
The same fields as any lead generation delivery, on every row, with the account as the organising key rather than an afterthought.
- Company name, domain, employee band, HQ country and sector
- Contact name, exact job title and LinkedIn URL
- Verified work email, and direct line where available
- The date the LinkedIn cross-check was completed
- Verification status: Verified, Pending or Bounced
How we verify
Four stages. A person at every one.
| 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 |
How it is priced
This is the Growth package, scoped to named accounts.
Not a separate product with its own rate card. Growth is the tier written for this — its published best-fit line reads “Full campaign launch · ABM rollouts · multi-persona outreach” — so an ABM engagement is scoped, priced and delivered as one.
- Price
- $895 · ₹75,000
- Accounts
- 500 verified companies
- Contacts
- 2,500, at 5 per account
- Turnaround
- 10–14 days
- Before the list
- Market research first where the account list does not exist yet — $300 per territory
Every tier and what each includes is on the pricing page.
What buyers ask first
Three trade-offs we do not make.
We already have the account list.
Then we start at the committee
Send it on the brief and we skip selection entirely — no re-litigating accounts you have already agreed internally. The work becomes mapping the buying centre inside each one, and reporting the accounts where we could not reach the depth you asked for.
We need 50 accounts, not 500.
Depth and width are different asks
Fifty accounts mapped deep is a different file from 500 mapped wide, and the packages are sized for the second. Say which you need on the call. We will tell you which tier fits or scope it as a project, rather than sell you a tier that does not.
Our enrichment tool already does this.
Enrichment fills fields
It completes rows you already have, from what a provider happens to hold. It does not read a company website to work out who owns the programme, and it cannot find the person who moved into the role last month and is not in any database yet. That reading is what you are buying here.
FAQ
What ABM teams ask before briefing us.
Do you choose the accounts, or do we?
Either. If you have the list, send it and we go straight to mapping the committee. If you do not, the market research brief builds it first — 100+ companies mapped against a stated segment definition, with the boundary written down rather than implied, at $300 per territory. Most ABM engagements that go well start there.
How deep can you go inside a single account?
Five contacts per company on Growth, across three seniority levels. Deeper is a scoping conversation, not a package: at some point an org chart runs out of people who genuinely touch the decision, and padding past that point is how a list stops being useful. We would rather name the ceiling on the call.
What happens to an account you cannot map?
It is reported as unmapped, with the reason. We do not substitute a generic inbox, a contact at a different company, or a title we could not confirm against a live profile and the company site. The count you receive is the count that survived verification.
Can you flag when a mapped contact changes role?
Job changes inside 90 days are flagged on the row at delivery. For an account list you intend to work for a quarter or more, database hygiene re-checks it before the next wave and finds the successor in the same role at the same company.
Book a project brief