What does an ABM agency cost? Scope accounts, tiers and roles

What drives the cost of an ABM agency?

Three counts set it: how many target accounts sit in each tier, how many buying-group roles each account needs at your deal size and how much routing and CRM work has to happen before a campaign can work. Retainers, programme names and platform licences are how those counts get packaged. Agency price guides quote monthly fees by programme type (a pilot, 1:many, 1:few or 1:1) and by list size, with ad spend on top. Platform guides price the software: an annual contract, plus onboarding, data and integration. Neither says what work the fee buys.

Each count changes a different part of a proposal:

The roles count needs the most care, because buying groups are large. Forrester’s State of Business Buying 2026 puts 13 internal stakeholders and 9 external influencers in a typical buying decision.^↗ Engaging all 22 at every account is out of reach, so the count that matters is the roles your deals can’t close without. Panelhop’s starting point, an illustration until your own won and lost deals replace it, is 3 roles under €50k (champion, budget owner, IT or security), 4 at €50–150k (adding finance) and 5 above €150k (adding the executive who signs).^↗ Engaging those roles is the work worth paying for: in deals over $50k, multi-threading lifts win rates by 130% on average.^↗

Media and software belong in the comparison too. Ask every agency to list ad spend, contact data and platform licences apart from its fee, because a proposal that includes them can’t be compared with one that doesn’t.

How do you scope your ABM needs before comparing proposals?

Fill in a one-page scope sheet before any agency pitches: your sellers and deal size, the tiers they can carry, the roles per account, the engagement each role needs and a readiness test for routing. Then every agency prices the same work. Here it is worked for a fictional seller, as an illustration: 4 AEs, deals of about €80k a year, a 9-month sales cycle and 1,800 accounts in the CRM that match its industry codes.

Size the tiers to the sellers who will work them. Panelhop’s audit working ranges are 5–15 Tier 1 accounts per AE, 20–60 in Tier 2 and 100–500 in Tier 3.^↗ At 10, 30 and 100 per AE, this seller gets 40 Tier 1 accounts (1:1), 120 in Tier 2 (1:few) and 400 in Tier 3 (1:many): 560 of the 1,800.^↗ The other 1,240 stay in the CRM outside the paid scope, and a dated buying signal at a fit account moves it in.^↗

Then count the roles. At €80k, a Tier 1 account needs all 4 roles and a Tier 2 account needs 2: the champion and the budget owner. A Tier 3 account needs none until a buying signal moves it up. That makes 160 roles in Tier 1 (40 × 4) and 240 in Tier 2 (120 × 2): 400 in all.^↗

Then the cadence. A role counts as engaged when its holder has had a two-way exchange with you in the last 90 days: a call, a meeting or a written reply to a question you asked.^↗ Holding 400 roles takes at least 400 exchanges a quarter, about 31 a week (400 ÷ 13), or about 8 per AE if the AEs hold every role.^↗ Over a 9-month sales cycle, that is at least 12 exchanges at each Tier 1 account (4 roles × 3 quarters).^↗

Deal size moves these numbers. For the same 40 Tier 1 accounts, 3 roles at €30k means 120 roles to hold and about 9 exchanges a week; 4 roles at €80k, 160 and about 12; 5 roles at €200k, 200 and about 15.^↗

Run the same sheet on all 1,800 accounts at 4 roles each and you get 7,200 roles and about 554 exchanges a week, 138 per AE.^↗ No team of 4 AEs can hold that, so a proposal priced on 1,800 “ABM accounts” is pricing reach: ads and emails to contacts, while the buying groups stay unengaged.

The brief that goes to every agency is the sheet’s output:

• 40 Tier 1 account plans, with 160 roles mapped and a play for each
• 120 Tier 2 accounts in a few clusters, with 240 roles named and reached
• 400 Tier 3 accounts in 1:many programmes, moved up on a dated buying signal
• The routing and CRM fixes the readiness test found, as their own line
• Media, data and software, listed apart from the fee

Ask each agency to price those lines, name who does each one and say which exchanges it leaves to your reps.

B2B demand generation agency vs ABM agency: deal size decides

Deal size and the size of the buying group decide which help you need first. A demand generation agency builds interest across a broad market and is usually judged on leads and pipeline volume. An ABM agency works a named target account list, and we’d judge it on engaged buying groups at those accounts. Lead generation is the step after demand generation: it turns that interest into named prospects and first sales conversations.

When a single buyer signs, reach and inbound pay back, and a demand generation agency fits. Once a deal needs 3 or more roles engaged, reach alone leaves most of the buying group untouched, and the work moves account by account.^↗

Treat the bands as a starting point and replace them with the roles that show up in your own won and lost deals. Check procurement as you do: Forrester finds it is a decision-maker in 53% of buying cycles, so look for it in those deals before you leave it out.^↗ And if your list has a wide Tier 3 and a market beyond it, demand generation still has a job there, while ABM help belongs on Tiers 1 and 2.

A tight target account list with working routing costs less

We think a tight, well-fit target account list with routing that works needs less spend than a long, loose list sitting on top of a new platform. Our reasons:

• Attention is the budget. Rep hours and signal spend are both fixed. Spread across more accounts than the team can research and multi-thread, both get thinner, and the fee pays for work on accounts nobody will follow up.
• A padded list costs more than its fee. Every extra account needs its data kept fresh and a place in the ad audiences, whether or not anyone works it.
• A platform only adds signals. An ABM or intent platform surfaces more accounts in market. If today’s buying signals don’t reach a named owner the same day with an action attached, more signals meet the same leak, and the subscription pays for alerts nobody works.
• A shorter list scores better. There is less noise to average over, and with a short Tier 1 the team sees each week where the score was wrong.

We don’t say platforms are never worth buying, or that one list size suits every team: the size follows your sellers and your deal size. We say the order matters. Build the list and fix the routing first, then add a platform once the team acts on the signals it already has.

Does a long sales cycle need a RevOps agency first?

It does when the readiness test fails. If buying signals wait days for a rep, alerts go unworked or accounts carry no tier and owner, fix those first: campaigns and signals feed the routing and CRM you already have. Run the test on the last 30 days, at your target accounts only:

• Speed: the median time from a buying signal or a request to the first human touch. Panelhop’s audit gives its top score only under 24 hours.^↗
• Ownership: the share of alerts followed by an activity within 7 days. The top score needs over 75%, with a named owner and a weekly review.^↗
• Fields: a tier, an owner and a fit score on every target account; a buying-group role on every contact.

Expect work here: 76% of CRM users say less than half of their CRM data is accurate and complete.^↗ A failed line goes into the scope sheet as the first item, priced before any campaign.

A long sales cycle raises the stakes. Buyers are 61% of the way through their buying journey before they first contact a seller.^↗ The signals before that contact are the earliest view a team gets. Then the deal runs for quarters, with every required role needing a two-way exchange in each. If the CRM can’t show the last exchange per role, nobody can tell whether a deal is still multi-threaded.

So when you hire a RevOps agency for a B2B company with a long sales cycle, ask it to show you, in your own CRM:

1. Accounts modelled the way the buyer is organised (a parent with its sites or business units) and a buying-group role on every contact
2. Routing that turns each buying signal into a task for the account’s named owner the same working day, with a fallback and an escalation
3. Stage exit criteria tied to the roles engaged and a reason recorded for every close-date move
4. A report of engaged roles ÷ required roles per target account, against a baseline taken before the work starts
5. A runbook and an owner for every automation, so the system outlives the people who built it

If you need both kinds of help, buy them in that order: RevOps until the readiness test passes, then ABM help that has working routing to run on.