Marketing Automation and Agents
Accounts: ABM Lists, Scoring, and Routing Playbook
Accounts aren’t a CSV - they’re your revenue OS. Learn how to build ICP-driven lists, score and route with SLAs, and run ABM plays that create MQAs and pipeline.
“Accounts” isn’t a CSV you bought last quarter. It’s the operating system of your B2B revenue motion. If you sell to businesses, your product-market fit lives inside named accounts, and your pipeline quality depends on how you choose, score, route, and work those accounts. This playbook shows how to build an account engine that moves from guesswork to repeatable growth - practical, technical, and measurable.
What “accounts” actually means in B2B revenue
When people say “accounts,” they mix three concepts: (1) account entities in your CRM (the Company/Account object, with firmographics), (2) account programs (ABM orchestration across channels), and (3) the go-to-market system (how accounts move from unknown to opportunity to revenue). If you don’t separate these, you end up with fluffy ABM buzz and no pipeline.
In a healthy system, accounts are the source of truth. Contacts, activities, and opportunities are associated to them. Your ICP lives at the account level; personas live at the contact level; pipeline lives at the opportunity level. Your reporting rolls up from contact to account to revenue.
Precision matters because sales cycles happen inside buying committees, not inboxes. If you only score contacts, you miss the big picture. If you only target accounts, you miss human activation. The work is to connect both.
Define a sharp ICP: firmographic, technographic, and trigger layers
Stop at “mid-market SaaS” and you’ll drown in noise. You need layered criteria that tell you why an account will move now. Start with firmographics: industry, employee bands, revenue bands, geo, funding stage, multi-location vs single, regulatory context. Use this to draw a hard line: who is in, who is out.
Next, add technographics and ecosystem. Your product sits beside other tools, payment rails, data stores, or channels. If your best customers run HubSpot + Stripe + NetSuite, and your product integrates cleanly, that stack is signal. If a prospect’s stack is custom, that’s friction. Map signal tools, neutral tools, and blockers.
Finally, include trigger events: hiring patterns, open roles, tech migrations, vendor renewals, domain events (new clinic opening, new territory, M&A), or public OKRs. Triggers convert a good-fit account into a time-sensitive one. If your ICP ignores triggers, your outbound becomes generic and your paid targeting burns cash.
Turn ICP into a curated account list (not a giant dump)
The fastest way to kill ABM is a 20,000-account list no one will touch. Build in concentric rings: Tier 1 (100–300 must-win), Tier 2 (1,000–2,000 strong-fit), Tier 3 (expansion/unverified). Each tier has different play intensity and channel mix.
Start with a seed set of your top 30 closed-won customers. Reverse-engineer their shared traits across firmographics, technographics, and triggers. Use data providers and your own enrichment to expand - but enforce governance: deduplicate by domain, standardize industries, enforce clear owner rules. Every net-new account gets a source, a confidence score, and a date stamped.
Governance beats volume. Establish a monthly intake process: add candidates, review against ICP, promote or park. A small, accurate Tier 1 that the team believes in will outperform a sprawling database every time.
Score accounts to focus effort where it converts
Account scoring is not magic; it’s math and iteration. Use a 0–100 rubric that blends fit (static) and intent/engagement (dynamic). Keep it transparent so sales trusts it and ops can tune it.
Start with a simple model: Fit (60% weight) includes industry match, employee range, revenue band, region, tech stack presence, and disqualifiers. Intent/Engagement (40% weight) includes your site visits from the company’s IP, high-intent pageviews (pricing, integrations), ad interactions, outbound replies, event attendance, and third-party intent if you have it. Disqualifiers subtract aggressively: competing tech hard blocker, tiny TAM, or unserviceable geo.
Operationalize thresholds: 70+ becomes Marketing Qualified Account (MQA), auto-route to an owner, and trigger a play. 40–69 goes into nurturing with lighter touches. Under 40 returns to research. Publish the math so SDRs can quickly rationalize why an account is hot and choose the next action.
Map buying committees and contact plans
Accounts don’t buy; people do - together. For each segment, define your roles: economic buyer, technical evaluator, end user champion, procurement/IT, and blocker. List their core pains, desired outcomes, and common objections. This isn’t persona theater; it’s routing and messaging fuel.
Associate 3–7 target contacts per Tier 1 account: one primary for each critical role. If you can’t find them, your list quality is suspect or the account isn’t Tier 1. Track contact coverage and reachability (valid email, LinkedIn presence, phone) as KPIs. Coverage under 50% for a must-win means research before messaging.
Different roles need different assets. Technical evaluators want docs, integration clarity, and risk mitigation. Economic buyers want business cases and adjacent proof. End users want quick wins and a clear “day one” experience. Map assets to these roles before you flood inboxes.
Route and assign with clear SLAs
Routing is where good strategy dies. Define territory or book-of-business rules that are simple enough to audit. Typical hierarchy: existing customer owner, active opportunity owner, then net-new routing by segment (SMB/MM/ENT), region, and capacity. When an account crosses your MQA threshold, auto-assign and timestamp ownership.
Make the SLA explicit: for MQAs, first-touch (email or call) within 2 business hours, 7-day, 5-touch minimum, with two channels minimum. For non-MQAs in Tier 1, weekly micro-touches (likes/comments, light emails) to stay visible without spamming. No-touch purgatory destroys win rates.
Document ownership edge cases: what happens when SDR sources an opportunity in an AE-owned account? Who updates account stages? Who can downgrade an MQA and why? Publish it. Enforcement comes from CRM automation and peer review, not wishful thinking.
Set up the data model right in your CRM
Your CRM must reflect account reality. Use the Company/Account object as the parent, associate all relevant contacts and deals, and standardize properties: ICP Fit Score, Technographic Match, Trigger Count, Account Tier, MQA Score, Buying Committee Coverage, and Active Play.
Create lifecycle fields specifically for accounts: Prospect, Engaged, MQA, Opportunity, Customer, Expansion, Churn Risk. Map transitions to concrete events: MQA when score >= 70; Opportunity at stage Created; Expansion when an additional product/region is in motion. Keep lifecycles separate for contacts; don’t overload one field to do two jobs.
Dashboards should answer: Which accounts crossed MQA this week? Which MQAs were touched within SLA? How many opps per tier and their velocity? What percent of closed-won came from Tier 1 vs Tier 2? If you can’t see this in two clicks, the data model or automation is incomplete. If you need help formalizing this backbone, see our CRM and pipeline implementation.
Orchestrate ABM plays that fit your tiers
Tier 1 deserves human, multi-channel, multi-week programs. Think: research, connection request, personalized opener, relevant asset, ad surround on LinkedIn and search, and a crisp business case offer. Each touch references a live trigger or a known pain - not a random whitepaper gate.
Tier 2 can be a blend: light personalization on the first outreach, then role-based value at scale. Ads educate and retarget; outbound warms; SEO brings the right roles back to the site. Your Tier 2 playbook should be templated enough to run weekly but flexible enough to insert a trigger when it appears.
Tier 3 is research and nurture. Don’t spend SDR time here beyond validation. Watch for fit changes and triggers, and graduate accounts upward when they earn it. This protects your team’s energy and your brand’s reputation.
Outbound done right: volume with standards
Outbound fails when teams confuse volume with effort. The job is to pair a reliable sending infrastructure with messages that respect context. Standard operating ranges: 300–600 emails/day across warmed domains, 3–5 LinkedIn actions/day per SDR, and calls clustered after responses, not randomized spam.
Write sequences for roles, not generic “we do X” pitches. Each sequence has a 30–45 day runway, 6–9 touchpoints, two channels minimum, and a single ask that advances discovery (not “15 minutes this week?” on touch one). Swap in micro-cases and integration snippets as replies increase. If you’re building or rebuilding this channel, our cold email and LinkedIn outreach covers infrastructure, deliverability, and roles-based plays.
Measure outbound by account outcomes, not email vanity. Good: MQA creation, opportunity rate by tier, reply quality, opportunity velocity. Bad: open rates without context, click rates without intent, total sends as a success metric. You get what you report on.
Paid and content aligned to accounts
Account ads exist to warm and confirm interest, not to replace conversation. Surround Tier 1 decision-makers with role-fit creative. Keep the value proposition consistent with outbound and your site. If ads say “seamless ERP integration,” your integration page better answer the real technical questions.
Content should map to the buying committee grid: technical docs for evaluators, ROI calculators and deal desk FAQs for buyers, onboarding quick wins for end users. Post-sale content matters too - it feeds expansion and reduces churn. Thought leadership without “what to do next” rarely moves a deal.
Organic search still fuels account motions. Own the integration pages, problem pages, and adjacent use cases your roles Google daily. If a champion is in research mode, you want your content to reduce their internal friction. When you’re ready to scale this pillar with AI systems, our GTM strategy work connects ICP, message, and channel planning so accounts actually convert.
Measurement: the account funnel and the two reports that matter
There are two views leadership needs weekly. First, the Account Funnel: total named accounts → engaged accounts → MQAs → opportunities → pipeline → revenue. Break it by tier and segment. Second, the SLA and Play Health: new MQAs vs touched within SLA, stalled MQAs with no owner action, and average time from MQA to opp creation.
Benchmarks vary, but a healthy mid-market motion sees 8–15% of Tier 1 accounts cross MQA in a quarter, 30–45% of MQAs convert to opportunities, and 20–35% opportunity-to-win for true ICP. If your MQA→Opp rate is under 15%, either your scoring is noisy, your plays miss the role, or ownership/SLA is broken.
Close the loop with attribution that’s good enough, not perfect. Multi-touch helps, but your steering data is account-level: which mix of outbound, ads, and content reliably creates MQAs by tier? Don’t let attribution debates stall obvious resourcing decisions.
An operator model that ships, not a committee that debates
If your team is small or stuck in meetings, consider the operator route. Anton Chisliuk · AI Marketing Ops runs the ABM spine as one integrated system - ICP, outbound infrastructure, AI SEO, paid, HubSpot, and n8n/Make automation - no account manager layer. Proof, not pitch: for Cleverence (B2B SaaS), organic went from 0→80K visits/month and 0→2K inbound leads/month with a real purchase rate. If you want the backstory and how the operator model works across B2B, e‑commerce, and local healthcare, read more about the operator model.
Example: a 90-day accounts implementation plan
Days 1–30: Align on ICP, build the first accountable Tier 1/2 list (max 1,500 total), set up the CRM data model, and deploy basic scoring. Warm sending domains, finalize outbound sequences by role, and produce the top five assets tied to the buying committee grid.
Days 31–60: Turn on Tier 1 plays. Launch outbound to 100–150 Tier 1 accounts with strict SLAs. Switch on surround ads. Publish integration and pricing-adjacent pages. Iterate scoring based on early response patterns. Create dashboards for MQA creation and SLA compliance.
Days 61–90: Expand to Tier 2. Add role-refined variants to sequences. Tighten routing edge cases. Tune budgets to channels actually creating MQAs. Start a weekly account review: 10 stuck MQAs, 10 fastest-moving opps, 10 newly promoted accounts. Ship small fixes weekly, not quarterly overhauls.
Common pitfalls (and how to avoid them)
Too many accounts, not enough plays. If SDRs can’t finish a Tier 1 loop in two weeks, you have too many Tier 1s. Shrink the list, increase touch quality, and watch opportunity rate climb. Activity logs aren’t the goal; conversations are.
Scoring that hides disqualifiers. If a single blocker tech or regulatory constraint makes a sale impossible, score should reflect that with a heavy penalty. Teams waste months “warming” accounts that will never buy. Bake in the no-gos early.
Disconnected content. Your best shot is when outbound says exactly what the landing page and product pages prove. If outbound promises “fast ERP integration” and your site has a generic integrations blurb, you’ve created friction. Align messaging, assets, and proof by role.
Tooling notes without tool worship
Use your CRM as the hub. Whether you’re on HubSpot or Salesforce, the pattern is the same: clean Company object, clear associations, and automation that routes and times your plays. Supplement with data enrichment and intent as budget allows, but don’t outsource thinking to a score from a third party.
Keep your outbound stack stable: dedicated sending domains, warm-up and monitoring, and a predictable cadence tool. Random tool churn destroys deliverability and measurement baselines. Think infrastructure first, copy second, volume third.
For analytics, start with a living spreadsheet or a simple BI view. Overbuilding early wastes cycles. If leadership can’t see MQA creation and SLA compliance clearly, the fix is process and reporting clarity, not fancy dashboards.
Budget and resourcing: agency, fractional, operator, or DIY?
Agencies often staff with layers and measure success on deliverables shipped, not accounts moved. Fractional CMOs advise well but require an internal team to execute across ops, content, outbound, and ads. DIY can work if you have a strong RevOps lead and at least two execution specialists ready to produce every week.
An operator model compresses strategy and build into one seat. One senior hand sets ICP, configures CRM and automation, stands up outbound, and aligns content and paid around named accounts. It’s not magic; it’s fewer handoffs and faster iteration against one number: pipeline by account tier.
Whichever route you pick, require weekly shipping, transparent dashboards, and clear SLAs. If a partner can’t walk you through which 20 accounts turned into MQAs and why, you’re buying theater, not outcomes.
How to pressure-test your current “accounts” motion
Ask for the list of Tier 1 accounts and the play currently running on each. If the doc doesn’t exist or is stale, there is no ABM program - just aspiration. The fix starts with a live list, assigned owners, and a weekly cadence.
Open your CRM and pull: new MQAs last 7 days, average first-touch time, and MQA→Opp conversion last 30 days by tier. If any of those require exports and VLOOKUPs, you have a data model problem before you have a pipeline problem.
Read five outbound threads. If they’re generic or product-first, expect low conversion. Rework to role-first, trigger-led, and backed by a proof asset. You don’t need prose; you need clarity and relevance.
Conclusion
Accounts are the backbone of B2B growth. Get the ICP tight, lists curated, scoring honest, routing unambiguous, and plays consistent. Report on the account funnel weekly and make small fixes fast. That’s how you move from good ideas to booked revenue.
If you want an outside operator to stress-test your ICP, fix your routing, and stand up an account engine in 90 days, start with a free Growth Audit. Article by Anton Chisliuk - leads, sales, content, and systems, one senior operator.
FAQs
- What’s the difference between an MQA and an MQL?
MQLs score a single contact’s behavior; MQAs roll up fit and engagement at the account level. In B2B with buying committees, MQAs are a better leading indicator for pipeline because they capture the multi-person reality.
- How many Tier 1 accounts should a team own?
As few as your team can run full plays against in two weeks. For a small team (one SDR, one AE), 75–150 Tier 1 accounts is workable. If you can’t touch every Tier 1 with quality this sprint, you have too many.
- Do I need third‑party intent to start ABM?
No. Begin with first‑party intent: pricing page visits, integration docs, product tour activity, and reply quality. Add third‑party intent later to prioritize, not to replace thinking. Many teams overpay for signals they never operationalize.
- How often should we refresh the account list?
Run monthly intake and quarterly deep refresh. Promote/demote accounts based on fit, trigger emergence, and play responsiveness. Don’t churn your entire list; stability supports measurement and relationships.
- What’s a good MQA→Opportunity conversion rate?
Across mid‑market motions, 30–45% is a healthy range when your ICP is sharp and plays are consistent. Under 15% suggests noisy scoring, weak messaging, or SLA gaps. Fix those before adding more volume.
- How do we avoid SDR burnout in ABM?
Protect focus: smaller Tier 1, clear SLAs, templates that are truly role‑based, and daily proof of progress (MQAs and opps by rep, not vanity metrics). Give SDRs the authority to stop working bad‑fit accounts and escalate scoring issues fast.
- Where should account scoring live - CRM or a separate tool?
Put the canonical score in your CRM so routing, reporting, and plays use the same number. You can compute it in an external engine if needed, but write the result back to the Account object with a clear timestamp and component breakdown.
Written by
Anton Chisliuk
Founder & Lead Operator · AI Marketing Operator
Anton Chisliuk is a GTM Engineer and Marketing Systems Architect. He built Cleverence's AI-native revenue OS (88 Make blueprints, MCP hub, 0→200K organic, 2.2K leads/mo) and now delivers outsourced GTM Engineering — CRM, automation, SEO, outbound — for growth-stage businesses via aimrktops.com.
About Anton →Ready to fix this — for real?
Book a free Growth Audit. No sales deck — a 30-minute conversation about your pipeline, stack, and what to ship first.