ABM in Practice: A Mini-Playbook for Mid-Market B2B Teams
ABM has a reputation as an enterprise discipline requiring big platforms and bigger budgets. It is not. ABM is campaign architecture applied to a named list of accounts, and a disciplined mid-market team of three can run it better than an under-coordinated enterprise team of thirty.
Most mid-market B2B teams have had the same experience with account-based marketing. They read the case studies, the ones with the enterprise logos and the six-figure platform spend. They priced the dedicated ABM tooling. They looked at their own team of 3 or 4 people, already running demand gen, content, and events, and they concluded, reasonably, that ABM was something other companies did. Companies with more people, more budget, more of everything.
This conclusion is wrong, and it is costing mid-market teams the single highest-leverage play available to them. ABM is not a budget tier or a software category. It is a strategic choice, to concentrate marketing effort on a defined set of high-value accounts rather than spreading it across an undefined market. That choice does not require enterprise resources. It requires the opposite of what most mid-market teams assume: less activity, aimed more precisely.
This article is a working mini-playbook. It builds on the Campaign Blueprint – because ABM is simply that blueprint applied to named accounts instead of a broad audience – and it is scoped deliberately for the team that has discipline but not headcount. Everything in it can be run by a small team that is willing to do fewer things, better.
What ABM Actually Is – and What It Is Not
Account-based marketing inverts the normal funnel logic. Instead of attracting a wide audience and narrowing it down to the few that convert, ABM starts with the few – a named list of high-value accounts – and concentrates the entire marketing effort on moving those specific accounts. The market is not discovered. It is chosen.
This inversion is what makes ABM accessible to mid-market teams, and it is the part most teams miss. Broad-market demand generation requires scale: enough budget and content volume to reach a large audience and convert a small percentage. ABM requires precision, not scale. A team running ABM against 20 accounts is not producing more content than a broad-market team. It is producing more relevant content, aimed at fewer, more valuable targets. Relevance is a discipline. Scale is a budget. Mid-market teams have access to the first regardless of the second.
The ABM principle: Broad-market marketing spends breadth to find the few accounts worth winning. ABM names those accounts first and spends depth on them directly. The mid-market advantage is that depth is a function of focus, not budget, and a small team focused on 20 accounts can go deeper than a large team spread across 20,000.
ABM is not, despite the platform marketing, a technology you buy. The tooling helps at enterprise scale, where the account count runs into the hundreds. At mid-market scale – 10-50 accounts – the playbook runs on a spreadsheet, a CRM you already have, and the discipline to coordinate marketing and sales around a shared list. The technology is optional. The focus is not.
The Five-Step Mid-Market ABM Playbook
This is the playbook scoped for a team without enterprise resources. 5 steps, each runnable with tools you already own. The discipline is in the sequence and the focus, not in the spend.
1. Select the Accounts – Fewer Than You Think
The most important decision
Account selection is the entire foundation of ABM, and the most common place mid-market teams over-reach. The instinct is to name a hundred accounts. The discipline is to name ten to thirty. Selection is built from your ICP, but at the account level: which specific companies match the profile, have a plausible trigger to buy, and are large enough to justify concentrated effort?
The list must be agreed jointly by marketing and sales, because an account marketing pursues that sales will not work is a wasted account.
Mid-market scope: 10-30 named accounts. If the list is over 50, it is not an ABM list, it is a segment, and it should be run as broad-market demand gen instead.
2. Map the Buying Committee – Real People, Not Roles
Per account
In B2B, the account does not buy, a committee of people inside the account buys. For each named account, map the actual humans involved: the economic buyer, the champion, the technical evaluator, the likely blocker.
This is the ICP work from earlier in this series, applied to named individuals rather than a persona archetype. A mid-market team can do this manually: LinkedIn, the company website, a single sales conversation. The enterprise tooling automates this; the small team does it by hand, and often understands the committee better as a result.
Mid-market scope: 3-5 named individuals per account, each with their likely role in the decision and their likely concern. A spreadsheet column per person.
3. Build the Account Narrative – 1 Story Per Account Cluster
The leverage point
Here is where mid-market teams gain their real advantage. ABM content does not need to be produced fresh for every account; that is the enterprise myth that scares small teams off. It needs to be produced for clusters of accounts that share a situation. The Hero's Journey applies directly: the account is The Hero, their shared industry challenge is The Ordinary World, and the narrative carries them toward The Special World.
1 strong account narrative, lightly personalised per account, beats 50 generic personalised tokens.
Mid-market scope: 2-4 account clusters by shared situation. One Hero Asset per cluster, personalised at the account level with specific detail, not just a merged company name.
4. Coordinate Marketing and Sales – The Shared Cadence
Weekly ritual
ABM fails most often not in the content, but in the coordination. Marketing warms an account; sales does not follow up. Sales pushes an account; marketing has nothing to support it. The fix is a shared cadence: a short, regular ritual where marketing and sales review the named accounts together and align the next action on each.
This is where the mid-market team genuinely beats the enterprise: a team of 3 in 1 room can coordinate in 15 minutes what a team of 30 across departments cannot coordinate in a month.
Mid-market scope: A weekly 30-minute marketing-and-sales account review. One shared document. One agreed next action per active account.
5. Measure by Account, Not by Volume
Ongoing
ABM cannot be measured with broad-market metrics. Lead volume is meaningless when the whole point is 20 specific accounts. The measurement is account progression: how many named accounts moved from cold to engaged, from engaged to in-conversation, from in-conversation to opportunity.
The unit of measurement is the account, not the lead, and the metric is movement through the stages, not the count of clicks. This is the measurement layer of the blueprint, scoped to a named list.
Mid-market scope: A simple stage tracker per account – Cold / Engaged / In Conversation / Opportunity / Won. Reviewed in the weekly cadence. No platform required.
The mid-market advantage, made explicit: Enterprise ABM wins on scale and tooling. Mid-market ABM wins on focus and coordination, and against the right account list, focus and coordination beat scale and tooling more often than the case studies admit. A team of three that knows its twenty accounts intimately and acts on them weekly is a genuinely formidable competitor to a team of thirty that knows its two thousand accounts statistically.
Why Mid-Market Teams Win at ABM
The enterprise ABM advantages are real but narrow: more budget, more tooling, more people. These advantages matter when the account list runs into the hundreds and coordination must be automated because it cannot be done in a room. At mid-market scale, those advantages largely evaporate, and a set of mid-market advantages takes their place that enterprise teams cannot easily replicate.
A mid-market team can hold its entire account list in working memory. Every person on the team knows the 20 accounts, who is on each committee, where each one stands. That shared, intuitive knowledge is something enterprise teams pay platforms to approximate and still do worse. A mid-market team can coordinate marketing and sales in a single weekly conversation, because the 2 functions are often a few desks apart. And a mid-market team can personalise genuinely – not with merge tokens, but with real, specific knowledge of the account – because 20 accounts is a number a human can actually know.
The mistake is for the mid-market team to try to run ABM the way the enterprise case studies describe it: with the tooling, the volume, the automation. Run that way, the small team loses, because it is competing on the enterprise's terms. Run on focus and coordination, the small team wins, because it is competing on its own.
Three Mistakes That Sink Mid-Market ABM
Mistake #1: Naming too many accounts
The single most common mid-market ABM failure is a target list of 80 accounts when the team has the capacity to genuinely pursue 20. A list that exceeds the team's capacity to personalise and coordinate is not an ABM list – it is a broad-market segment with an ABM label. The effort spreads thin, the personalisation degrades to merge tokens, the coordination breaks down, and the program produces broad-market results at ABM cost. The discipline is brutal subtraction: name the smallest list the team can pursue with genuine depth, and resist every pressure to expand it.
Mistake #2: Treating ABM as a marketing-only program
ABM is the one marketing motion that cannot succeed without sales as an equal partner. A marketing team that builds an account list, produces account content, and warms the accounts – without sales agreeing to the list and working it in parallel – has built an expensive content program that generates engagement nobody acts on. The shared cadence in Step 4 is not optional infrastructure. It is the difference between ABM and an account-themed content campaign that quietly fails because the handoff never happened.
Mistake #3: Buying the platform before building the discipline
The temptation, when starting ABM, is to buy the tooling first – it feels like progress and it looks like commitment. But a platform does not create focus or coordination; it only scales them once they exist. A team that buys an ABM platform before it has run a disciplined program on a spreadsheet ends up with an expensive tool enforcing a process it never built. Run the playbook manually first. Earn the right to the platform by outgrowing the spreadsheet, not by hoping the platform will supply the discipline you have not yet developed.
How to Use GenAI as Your ABM Account Researcher
The most time-consuming part of mid-market ABM is the per-account research, understanding each account's situation well enough to personalise the narrative genuinely. This is where GenAI earns its place in the playbook: not generating the outreach, but accelerating the research that makes the outreach specific.
Use this Prompt:
I will share a named target account and what I already know about it. Help me build the account intelligence needed to personalise our ABM narrative genuinely, not with merge tokens, but with real specificity.
THE ACCOUNT:
- Company: [Name]
- Industry and size: [Describe]
- What I already know: [Paste any notes, public information, or sales context]
- Our ICP and positioning: [Paste from your existing strategy]
HELP ME BUILD:
1. THE ACCOUNT'S LIKELY ORDINARY WORLD: Based on the industry, size, and context, what is the specific business challenge this account is most likely facing that our offer addresses? State it as the account would experience it, not as we would pitch it.
2. THE LIKELY BUYING COMMITTEE: What roles are most likely involved in a decision like this at a company of this size? For each, what is their probable primary concern?
3. THE ACCOUNT CLUSTER: Based on this account's situation, what other accounts likely share the same Ordinary World, so we can build one narrative for the cluster rather than one per account?
4. THE PERSONALISATION ANGLES: Identify 3 specific, genuine personalisation points: real aspects of this account's situation we could reference that would signal we understand them, beyond inserting their company name.
5. THE RESEARCH GAPS: List what we would need to verify with a real sales conversation or further research before acting; flag anything you are inferring rather than knowing.
Rules:
- Distinguish clearly between what is reasonable inference and what would need verification. Never present inference as fact.
- Personalisation angles must be genuine and specific; reject anything that is just a dressed-up merge token.
- Keep it scoped for a small team. Do not recommend research that requires enterprise tooling.
Validate every output against real account knowledge before acting. GenAI infers the account's likely situation from public patterns; it does not know this specific account. The research gaps it flags are the most valuable part of the output: they tell you exactly what to confirm in the next sales conversation before you personalise on an assumption. Use it to accelerate the research, never to replace the verification.
Final Thought
ABM is not an enterprise discipline that mid-market teams should aspire to once they are bigger. It is a strategic choice available to any team willing to do fewer things with more focus, and in many ways it suits the mid-market team better than the enterprise, because focus and coordination come naturally to a small team and expensively to a large one.
The mistake is to look at the enterprise case studies and conclude that ABM requires their resources. It requires their discipline, not their budget. Name a small list. Know the accounts genuinely. Coordinate marketing and sales weekly. Measure by account movement. None of that needs a platform. All of it needs the willingness to concentrate, which is the one resource a mid-market team has in abundance, if it chooses to use it.
Are you avoiding ABM because you lack the budget or because committing to twenty named accounts means admitting which ones actually matter?
Recommended Use Cases:
Diana Socaciu