A pipeline plan for the SDR seat
Prepared for the team at Deepgram
By Vincent Hembrick
Why I built this
To show my approach, excitement, and dedication to the role I built this for the SDR seat at Deepgram specifically. Below is a break down of the ICP, five accounts that match the ICP, example messaging, and a 30, 60, 90 day plan for how I would ramp. Everything is framed against Deepgram's actual GTM and the trigger patterns in the voice AI market right now. If any of it lands, I would value 15 minutes to compare notes.
Two ICPs, named directly in the JD
The JD names three buyer types: software companies building voice products, co sell partners working with large enterprises, and enterprises solving internal voice AI use cases. Co sell partners cluster with the software builders since both are technical buyers with similar buying behavior, leaving a clean split between voice product builders and enterprise voice operators.
ICP A: Software companies building voice products
Firmographics
- Voice AI ISVs, CCaaS and UCaaS, health tech SaaS, conversational AI, AI scribe startups
- 50 to 5,000 employees, Series A through D
- North America heavy, EMEA secondary
- Multi provider ASR and TTS stack already in production (Whisper, OpenAI Realtime, Google STT, ElevenLabs)
Buyer titles
- CTO and Co Founder & CTO
- VP Engineering, Head of Speech AI
- Head of AI, Head of Conversational AI
- Founder and Founding CEO at pre Series B
- Chief Product Officer at established voice platforms
Pains and triggers
- Hyperscaler ASR billing crossing $1M annually with quarterly cloud cost reviews now visible at the CFO level
- Enterprise sales blocked from healthcare, finance, and government deals because consumer cloud ASR cannot pass HIPAA, FedRAMP, or PCI
- Latency variance from existing providers showing up in production NPS and customer escalations
- Concurrent stream limits during peak events (Black Friday, AEP, election cycles)
- Series B or C close that frees infrastructure budget for vendor consolidation
- Multi provider integration debt eating engineering velocity that the team would rather spend shipping product
ICP B: Enterprises with internal voice AI use cases
Firmographics
- QSR chains (50 plus locations), Tier 1 BPOs, telcos, large insurance carriers, IDN healthcare
- 5,000 plus employees, public markets or PE backed
- North America primary, EMEA enterprises secondary
- Already running voice in production (call center, drive thru, IVR, claims)
Buyer titles
- Chief Digital Officer, Chief Information Officer
- Chief Transformation Officer, Chief Operating Officer
- VP Operations, VP Customer Experience
- VP IT, VP Restaurant Technology
Pains and triggers
- Failed incumbent voice AI deployment (the McDonald's and IBM exit is the canonical 2024 case study) creating board level redeployment pressure
- Hyperscaler ASR contract overruns at scale, opaque billing, vendor lock in pressure
- Labor as percent of revenue at 28 to 32 percent versus 22 percent target, CFO pressure mounting
- Peak event capacity crisis (AEP for health insurance, Black Friday for retail, IRROPS for airlines)
- Client AI mandates pushing BPOs to absorb GenAI cost reduction within 12 to 18 months
- New vertical expansion or M&A integration creating new compliance footprint
Firmographic ranges and buyer titles for ICP A are inferred from Deepgram's public customer footprint, the SDR JD's three buyer types, and the voice AI market analysis I worked through. ICP B verticals are pulled from the Deepgram for Restaurants page, partnership pages, and industry analyst coverage. Worth verifying against the live ICP doc before working.
Five accounts I would stack rank day one
Best fits across both ICPs, no forced 3+2 split. I checked each one against Deepgram's public customer wall, partnership pages, and recent press before listing.
All five are illustrative best fits. I verified each one is not a current customer of the hiring company (homepage, case studies, recent press) before listing. I would still dedupe against the existing CRM and pull in real time triggers (job postings, funding, M&A, breach proximity, partner announcements) before adding any to a sequence.
A four touch sequence in Deepgram's voice
Persona: CTO and co founder at a Series B AI medical scribe, 50 to 200 employees, US and AU footprint. Example target: Heidi Health, illustrative only. Cadence: 4 touches over 12 days, mixing email, LinkedIn, and phone. Voice calibrated to Deepgram's plain spoken, benchmark backed tone.
How I would ramp at Deepgram in my first 90 days
The plan below mirrors how I ramped at Certara, where I went from 0 sales experience to top of the BDR table by pairing tight learning loops in month one with disciplined high volume execution through months two and three.
Learn the voice AI stack and Deepgram's edge
- Articulate what Deepgram solves at the CTO, VP Product, and CEO level for all three buyer types named in the JD: software builders, co sell partners, and enterprises
- Shadow top SDRs and AEs across each motion to see how each buyer type gets worked
- Listen to recorded discovery calls and demos to internalize how Nova-3, the Voice Agent API, and self hosted deployment land in technical conversations
- Get fluent in Salesforce, Outreach, Sales Navigator, Apollo, and ZoomInfo
- Study three competitors (Google STT, AssemblyAI, and Microsoft DAX for healthcare) and map where Deepgram wins on accuracy, latency, deployment, and pricing
- By day 30, have my own call script and personal email playbook tied to the three highest leverage trigger types: hyperscaler bill review, compliance blocked deals, and post McDonald's IBM redeployment
Run the cadence, hit ramp quota
- Lock the daily schedule: research and list building 9 to 10, cold calls 10 to noon, email and LinkedIn outreach 1 to 3, follow ups and CRM hygiene 3 to 5
- Build a 100 account named list weighted across both ICPs and run the 4 touch sequence at full volume
- Hit the Month 2 ramp quota
- Roleplay technical objections daily with peer SDRs and a Sales Engineer: latency benchmarks against hyperscalers, BAA execution speed for healthcare buyers, FedRAMP positioning for federal opportunities, and the McDonald's IBM redeployment story for QSR
- Weekly feedback loop with my manager on what is converting, then iterate the framework week by week
- Fail fast, log everything, adjust
Analyze the funnel, build the personal playbook
- Pull conversion data across the full funnel: dials to connects, connects to meetings, meetings to SQLs, broken out by ICP and by trigger type
- Identify which trigger and persona combinations produce the strongest pipeline contribution and double down
- Consistently hit quota and lead the SDR team in call activity
- Continue ongoing development through voice AI podcasts, the Deepgram blog, and weekly product updates so I stay sharp on a category that moves every month
- By day 90, have a personal playbook documenting which triggers, personas, and openers work best for me at Deepgram, ready to share back to the team
- That playbook is the artifact that signals AE track readiness, the 18 month goal I would be working toward
If any of this is in the ballpark of how the Deepgram team is thinking, I would value a 15 minute conversation to compare notes on what is working, what is not, and where I would plug in fastest. If the plan above misses the mark, that is also useful feedback for me. Either way, thank you for reading.
Vincent Hembrick