Account-based marketing (ABM) playbook for enterprise SaaS 

Quick answer: Use a named account list, role-based problems, and the simplest story that proves value. Run targeted ads for familiarity and 1 to 1 email for conversations, then iterate weekly with sales notes and intent signals. 

Who needs this and why it works

ABM stalls when teams blast the same message at every contact. Precision comes from solving a single role’s problem at a specific stage. 

• Pick 50 to 200 accounts with clear buying signals. 
• Map problems by role – finance, operations, IT. 
• Write one promise and one proof for each role. 

Plays that win for ABM

Combine air cover with human follow-up, so buyers see the same promise in different places. 

• LinkedIn sequences for finance and operations leaders.
• Display to widen reach into the buying committee. 
• 1 to 1 emails that ask one practical question. 

Sales alignment checklist

ABM fails without a tight loop between marketing and sales. 

• Weekly sync on replies and objections. 
• Shared doc of approved claims and examples. 
• Rules for fast follow-up within 24 hours. 

Example scenario

A mid-market team targets a narrow list of accounts. They launch a flagship guide, place a short version with a trusted partner, run role specific LinkedIn, and follow with one question emails. The team measures meetings and multi-threading, then refreshes hooks every month. 

FAQs

1. How many accounts should we start with? 
   Often 50 to 200, depending on ACV and capacity. 
2. How will we know it worked? 
   Use meetings and opportunities as the north star. Track multi-threading and reply quality as leading indicators. 
3. Do we need to gate content? 
   Gate when you need signals and follow-up triggers. Use ungated summaries for reach. 
4. How often should we refresh? 
   Monthly for hooks and examples, quarterly for big updates. 
5. What does good personalization look like? 
   Short and factual. Align to role, problem, and stage. Avoid assumptions. 
6. What are common pitfalls? 
   Click-chasing, inconsistent claims, and skipping QA on partner pages. 

Implementation timeline

• Week 1 – finalize ICP notes and a simple glossary. 
• Week 2 – publish the flagship asset and collect feedback. 
• Week 3 – launch two channels and start outreach. 
• Week 4 – review replies and meetings and refresh hooks. 

Key takeaways

• Audience fit beats raw volume. 
• Short, factual personalization works best. 
• Judge success by meetings and opportunities. 
• Refresh hooks and examples on a predictable cadence. 

Related reading

• DemandWorks + 6sense (integration)
• DemandWorks and 6sense: Strategic integration announcement