Account-Based Selling Playbook for Enterprise Deals

Account-based selling is account-based marketing's twin. While marketing builds awareness and credibility, sales orchestrates relationships across multiple stakeholders in a single account.

This playbook is your selling framework.

What Account-Based Selling Is

Account-based selling (ABS) means: selling to an account, not a contact.

Instead of "I have a contact at TechCorp who's interested," you have "I'm selling into TechCorp's entire buying committee."

This is different because:

1. You coordinate across multiple stakeholders
2. You have different conversations with each (not one pitch, four versions)
3. You manage political dynamics (one person says yes, another says no)
4. You track progress at the account level, not contact level

Step 1: Identify the Buying Committee

For each account you're pursuing, map the buying committee.

Economic Buyer

Controls budget. Usually: - CFO - VP Finance - VP in the relevant function (VP Sales, VP Marketing, VP Ops)

What they care about: - ROI - Cost - Risk (What if it doesn't work?) - Timeline

Your message to them: "This solution improves efficiency by X%, saves Y dollars, or generates Z revenue. Here's the payback period."

Technical Buyer

Evaluates solution fit. Usually: - CTO or Head of Engineering - Tools/Ops person in the relevant function - Security or IT person

What they care about: - Integration (does it connect to our existing tools?) - Security and compliance - Scalability - Implementation effort

Your message to them: "This integrates with [their tools], meets [their security needs], and scales to [their size]. Implementation is [timeframe]."

End-User Champion

Uses the tool daily. Usually: - Individual contributor - Team lead - Head of the relevant function (Head of Sales, Head of Marketing)

What they care about: - Ease of use - Time saved - Impact on their work - Whether their team will adopt it

Your message to them: "This saves you X hours per week, improves Y metric, and your team will actually use it."

Coach or Ally

Internal advocate. This person isn't in the buying committee but advocates for you.

What they care about: - Making their boss look good - Getting their problems solved - Career advancement

Your message to them: "This solves your problems, makes you a hero internally, and here's how to position it to your boss."

Potential Blockers

People who can say no: - Head of Security - Head of Compliance - IT director - Incumbent vendor relationship owner

What they care about: - Risk mitigation - Process adherence - Relationship preservation

Your message to them: "We've addressed all risk and compliance concerns. Here's our security docs. We work well with your existing tools."

Step 2: Research Each Stakeholder

Before you reach out, research them.

For the economic buyer: - Recent earnings calls or financial reports - Leadership team changes - Strategic initiatives mentioned in press

For the technical buyer: - Their technology stack - Technical talks or presentations they've given - Blog posts or LinkedIn activity

For the end-user champion: - LinkedIn profile and activity - What they've posted about their role or challenges - Any podcasts or interviews

For potential blockers: - Their stated concerns or policies - Past vendor relationships - Public statements on security or compliance

Create a Hypothesis for Each

Write one sentence for each stakeholder:

"John (CFO) is focused on cost control post-acquisition. He'll care about ROI and payback period."

"Maria (VP Sales) is being measured on pipeline growth. She'll care about whether this helps her team close faster."

"Ahmed (Head of Security) has been cautious about new vendors post-breach. He'll need strong compliance documentation."

These hypotheses guide your conversations.

Step 3: Create Multi-Threaded Outreach

You don't outreach to all stakeholders equally. You have a sequence.

Week 1: Initial Contact (Usually to a Referred or Inbound Lead)

Reach out to the first contact. Usually the champion who was already engaged or referred you.

Goal: Learn about the account and identify other stakeholders.

Example email:

"Hey [Champion],

Thanks for suggesting we connect. I'd love to learn more about what you're working on and how [product] might help.

Before we jump on a call, a quick question: Who else on your team is thinking about [problem we solve]? Ideally, I'd love to understand how you all approach this.

Free this week for 15 min?"

Week 2: Secondary Stakeholder Introduction

Once you've talked to the champion, ask them to introduce you to 1-2 other stakeholders.

Example message to champion post-call:

"Thanks for the call. I really got a sense of what you're trying to accomplish. I have a few thoughts on how [product] could help.

Before I share more, would it make sense to loop in [Technical Buyer] so they can weigh in on the technical fit? And potentially [Economic Buyer] so we can talk through the financial side?"

Most champions will make the introduction. (If they don't, you can't move forward. This is a signal that they don't have sufficient buy-in.)

Week 3: Parallel Conversations

Now you have direct contact with 2-3 stakeholders. Have tailored conversations with each.

With the technical buyer: - Deep dive on integration and implementation - Walk through security/compliance docs - Discuss timeline and resource needs

With the economic buyer: - Discuss ROI, cost, and payback - Walk through reference customers and outcomes - Discuss pricing and contracting timeline

With the champion: - Continue exploring their use case - Keep them informed about progress - Make them feel like a partner in the deal

Do not have the same conversation with all three. Each gets a customized conversation.

Week 4+: Consensus Building

As you move through conversations, you're building consensus. This doesn't mean agreement. It means each stakeholder understands the solution and can make an informed decision.

Goal: Get to a trial or demo that includes all stakeholders.

Step 4: Manage Stakeholder Dynamics

Politics are real. One person wants to move forward. Another has concerns. Your job is to surface concerns early and address them.

Identify Alignment and Misalignment

After a few conversations, do an internal audit:

• Economic buyer: Interested or concerned about cost?
• Technical buyer: Positive on integration, or worried about implementation effort?
• Champion: Still enthusiastic or starting to have doubts?
• Blockers: Any red flags?

If you have one enthusiastic champion and everyone else is MIA, you have a problem. That champion won't be enough.

Manage Concerns Directly

If the technical buyer seems worried about integration, address it head-on:

"I picked up that integration might be a concern. Can I share our integration docs and connect you with our CTO to walk through the details?"

If the economic buyer is worried about cost, address it:

"I know cost is a concern. Let me walk through the ROI and payback. If the numbers don't work, let's say that now rather than later."

Transparency builds trust.

The Veto Rule

Remember: one person can kill the deal.

If the head of security says no, you're done. If the CFO says the budget isn't there, you're done.

Your job is to identify concerns early so you can address them. Not overpower them, address them.

Step 5: Move to Demo/Trial

A demo or trial is the commitment point. This is where consensus matters.

Demo Strategy

Your demo should include: - The champion (they understand the use case) - The technical buyer (so they see fit) - At least one other stakeholder (ideally economic buyer or end-user)

Before the demo:

1. Prep individually: 15-min call with each attendee to understand their focus and questions
2. Customize the demo: Show the use case that matters to them
3. Align on next steps: Decide what success looks like after the demo

After the demo:

1. Follow-up individually: Call each attendee to get their feedback
2. Address concerns: If someone raised a red flag, address it before it festers
3. Move to trial: Get agreement on a 2-week trial with success criteria

Trial Success Criteria

"Here's what we'll measure during the trial:

• Integration with [your tool] takes [X hours]
• [Champion's team] can onboard in [Y days]
• [Metric] improves by [Z%]

If we hit these, we move to close. If we miss, we figure out why and adjust."

Write these down. Agree with stakeholders. This removes surprises.

Step 6: Navigate the Close

This is where politics and personalities really matter.

Common Close Dynamics

Scenario 1: Champion wants to move forward, economic buyer is hesitant on cost.

Action: Economic buyer-focused conversation. Walk through ROI, comparison to current solution, and ask directly: "What would make this work financially?"

Scenario 2: Technical buyer has concerns, champion still enthusiastic.

Action: Address technical concerns directly with technical buyer. Don't let the champion override. If technical buyer says no, the deal likely dies.

Scenario 3: Everyone's positive, but there's a mysterious delay.

Action: This usually means something changed (budget got cut, priority shifted, political issue). Ask directly: "What's changed? What am I missing?"

The Sponsor Rule

As you move through the deal, confirm you have an executive sponsor: someone with budget authority who will advocate internally.

Usually this is the economic buyer or the champion's manager.

"Who in your organization will advocate for this internally? Who has to sign off?"

If you can't identify a sponsor, the deal will likely stall.

FAQ

Q: What if we can't identify all stakeholders? A: Ask your champion. "Who else needs to sign off on this?" If the champion can't tell you, they don't fully understand the politics, which is a red flag.

Q: How do we handle competitor relationships? A: Ask about it early. "I know you're working with [competitor]. How's that going? What would need to change for us to be a contender?" Listen. Don't trash the competitor.

Q: What if one stakeholder says no? A: Ask why. Address the concern if you can. If you can't, accept it. Don't try to overpower their veto.

Q: How long should this process take? A: For enterprise deals, expect 8-12 weeks from first conversation to trial. 12-16 weeks from trial to close.

Q: Should we involve executives in these conversations? A: Maybe. For deals >$500K, consider having your CEO or VP do one conversation with their economic peer. This can unlock stuck deals.

Next Steps

Pick one of your Tier 1 accounts. Map the buying committee. Create hypotheses for each stakeholder. Then execute the multi-threaded outreach.

You'll see faster deal velocity and higher win rates.

Ready to orchestrate across your buying committees? Abmatic AI gives you visibility into who's engaging at each account.