Account Based Marketing (ABM) – Outbound Specialist

Overview

You're doing outbound prospecting for a 15-person AI/data engineering consulting firm. You identify target accounts, research decision-makers, and run multi-channel campaigns (email, LinkedIn) to book qualified discovery calls. You're selling complex, expensive consulting engagements—not a simple SaaS product—so your messaging needs to be highly personalized and technically credible.

Role Snapshot

Company Context

Stage: Early-stage, bootstrapped or self-funded (no funding info found)

Size: 15 employees

Growth: Actively hiring for outbound, suggesting they're trying to scale pipeline generation

Market Position: Small player in a crowded AI consulting space—competing against established firms like Accenture, Deloitte Digital, and boutique AI shops

GTM Reality

Pipeline Sources:

• 0% Inbound - They're a 15-person consulting firm with minimal brand recognition. No one's searching for "TechAIVV" on Google.
• 100% Outbound - You're building everything from scratch: lists, messaging, sequences, cadences.
• Referrals/Partners - Possibly some, but they're hiring you to create net-new pipeline.

SDR/AE Structure: You book meetings, AEs or founders take them and run the sale. You're not closing deals yourself.

SE Support: N/A—the consultants themselves are the technical experts who demo capabilities.

Competitive Landscape

Main Competitors: Large consulting firms (Accenture, Deloitte, PWC), boutique AI agencies, offshore dev shops, and in-house teams at larger companies.

How They Differentiate: Likely positioning as more nimble/affordable than big firms, more strategic than dev shops, with specific AI/MLOps expertise.

Common Objections:

• "We're already working with [Accenture/McKinsey/etc.]"
• "We have an internal data team"
• "What makes you different from the 50 other AI consultants who emailed me?"
• "Can you show me similar work you've done in our industry?"

Win Themes: Deep technical expertise, faster time-to-value than big firms, proven experience in specific tech stacks.

What You'll Actually Do

Time Breakdown

Research & List Building (30%) | Outreach & Sequencing (40%) | CRM/Reporting (20%) | Internal Sync (10%)

Key Activities

• Build Target Account Lists: Use Apollo, ZoomInfo, LinkedIn Sales Navigator to identify companies likely to need AI/data engineering (e.g., Series B+ tech companies, enterprise retailers doing digital transformation). You're looking for VP Eng, Head of Data, Chief Data Officers, CTOs.

• Research & Personalization: Spend 10-15 minutes per account researching their tech stack, recent funding, job postings for data roles, conference talks their team has given—anything that signals they might need outside AI/data help. You need ammunition for personalized messages.

• Write & Launch Sequences: Create 5-7 touch campaigns (emails + LinkedIn messages) with specific value props tied to what you found in research. Most messages get ignored. You're tweaking subject lines, CTAs, and timing constantly.

• Follow-Up & Nurture: Most people don't respond to touch 1-3. You're managing dozens of active sequences, responding to the occasional reply (many are "not interested" or "reach back out in 6 months"), and trying to keep conversations alive.

• CRM Hygiene: Log everything in their CRM. Track open rates, reply rates, meeting conversion rates. Report weekly on activity metrics and pipeline generated.

• Collaborate with Sales: When you book a meeting, brief the AE/founder on what you learned about the account. Sometimes they'll ask you to loop back in after the call to re-engage other stakeholders.

The Honest Reality

What's Hard

• Low response rates: You're cold emailing VPs at enterprise companies about expensive consulting projects. 1-2% reply rates are normal. Most ignore you entirely.

• Long, unclear buying cycles: Even when someone takes a meeting, deals take months to close (if they close). You rarely see immediate results from your work. Pipeline you generate in Q1 might close in Q3.

• Personalization is time-intensive: You can't just blast 500 generic emails. Each account needs research and custom messaging. This limits your volume.

• Competing with huge brands: Prospects get pitched by Accenture, McKinsey, and 20 other AI shops. You're the unknown 15-person firm. Building credibility is hard.

• Unclear ICP: At a small consulting firm, the ICP is often "anyone who might need AI help." You'll spend time figuring out which verticals/company sizes actually convert.

What Success Looks Like

• You consistently book 10-15 qualified discovery meetings per month for the sales team
• 30%+ of your meetings result in follow-up conversations (not one-and-done)
• You maintain 50-60 personalized outreach touches per day across email and LinkedIn
• Your messaging resonates—reply rates improve from 1% to 2-3% as you dial in your ICP and value props

Who You're Selling To

Primary Buyers:

• VP Engineering / CTO at Series B-D tech companies (50-500 employees)
• Head of Data / Chief Data Officer at mid-market or enterprise companies
• VP Product or Chief Digital Officer at traditional companies doing digital transformation

What They Care About:

• Do you understand our specific technical problem (data infrastructure, MLOps, AI product development)?
• Can you show relevant case studies in our industry?
• How fast can you deliver results vs. us hiring in-house?
• What's the risk if this doesn't work? (They're allergic to expensive failed consulting projects)
• Are you going to hand us off to offshore juniors or work with senior people?

Requirements

• 4-5 years of B2B outbound experience, ideally in SaaS or professional services
• Hands-on experience with Apollo, ZoomInfo, LinkedIn Sales Navigator, and CRM (Salesforce/HubSpot)
• Strong ability to research accounts and personalize messaging—you can't succeed with templated spray-and-pray here
• Comfortable selling complex, high-ACV solutions (not transactional e-commerce or SMB)
• Self-sufficient—they're a 15-person company, so you won't have tons of enablement or support
• Ability to work ambiguity—you'll be defining ICP, testing messaging, and iterating as you go