Overview
You sell Recall.ai's Meeting Bot API to engineering teams and product managers who are building conversation intelligence tools, productivity apps, or internal meeting features. You're closing developers and technical PMs who evaluate based on API documentation, integration complexity, and pricing. This is a technical sale where you need to understand REST APIs, webhooks, and video conferencing platform integrations.
Role Snapshot
| Aspect | Details |
|---|---|
| Role Type | Full-cycle AE (some SDR support likely) |
| Sales Motion | Balanced - inbound from developers + targeted outbound |
| Deal Complexity | Consultative with technical evaluation |
| Sales Cycle | 3-8 weeks (developer evaluation + stakeholder approval) |
| Deal Size | $15-40K ACV |
| Quota (est.) | $1.1M/year ($275K/quarter, ~$92K/month) |
Company Context
Stage: Early-stage (34 employees, likely Seed/Series A)
Size: 34 employees
Growth: Actively hiring multiple AE roles mid-Q1, suggesting demand momentum
Market Position: Infrastructure provider in the meeting intelligence space - not competing with end-user tools like Gong, but selling to companies building those tools
GTM Reality
Pipeline Sources:
- ~40% Inbound - developers finding them through search, API documentation sites, technical communities. Quality varies - some are ready to buy, others are just researching options
- ~40% Outbound - you identify companies building meeting features (productivity tools, coaching platforms, internal tools) and reach out to their engineering/product leads
- ~20% Referrals/PLG - developers who've tried the product or seen the docs and want to talk pricing/volume
SDR/AE Structure: Likely shared SDR pool or hybrid model (you do some of your own prospecting)
SE Support: No dedicated SEs at this size - you handle technical questions, potentially with engineering team backup for complex scenarios
Competitive Landscape
Main Competitors: Other meeting bot API providers, companies building in-house (biggest competitor), potentially Fireflies/Otter APIs if they have developer offerings
How They Differentiate: Multi-platform support (Google Meet, Teams, Zoom, Slack), SDK options beyond just API, infrastructure focus vs end-user tool
Common Objections: "We can build this ourselves" (from engineering teams), pricing concerns at scale, reliability/uptime questions, integration complexity
Win Themes: Time-to-market (months saved vs building), multi-platform support, maintained integrations as platforms change APIs
What You'll Actually Do
Time Breakdown
Prospecting (25%) | Active Deals (50%) | Internal (25%)
Key Activities
- Technical discovery calls: You're talking to developers and PMs about their architecture, what they're building, volume needs. You need to understand their tech stack well enough to speak credibly about integration paths.
- Demo/POC management: Walking through API documentation, helping them get started with test integrations, troubleshooting initial implementation issues. You're not coding but you're in their Slack helping them get live.
- Multi-stakeholder closing: Even though the developer wants you, you often need to get a VP Engineering or Head of Product to sign off on the contract and commit to the annual spend.
- Outbound prospecting: Researching companies that have meeting recording features or are building AI meeting tools, finding the right PM or engineering contact, cold outreach via email/LinkedIn to book discovery calls.
The Honest Reality
What's Hard
- "We'll build it ourselves" wall: Engineering teams often think they can build meeting recording infrastructure. You spend time convincing them it's harder than it looks (platform API changes, edge cases, maintenance).
- Long technical evaluations: Developers want to test everything. POCs can drag on while they tinker, and you're stuck waiting for them to find time between sprints.
- Deal size variability: Some deals close at $15K, others at $50K depending on volume. You need 20-30 deals per year to hit quota, which means constant pipeline generation.
- Technical depth required: You can't BS developers. If you don't understand REST APIs, webhooks, or how OAuth works, you'll lose credibility fast.
What Success Looks Like
- Closing 6-8 deals per quarter at an average of $30-35K ACV
- Keeping 10-15 active opportunities in technical evaluation/POC stage
- Converting 25-30% of qualified POCs to closed-won
- Managing 30-40 cold outbound touches per week to keep pipeline full
Who You're Selling To
Primary Buyers:
- Engineering Managers / VPs of Engineering (budget authority)
- Product Managers / Heads of Product (feature owners)
- Technical founders at earlier-stage companies
What They Care About:
- Integration speed: How fast can their devs get this live vs building from scratch
- Reliability at scale: Uptime guarantees, how many concurrent bots they can run, latency
- Pricing predictability: Per-meeting costs, volume discounts, what happens if they scale 10x
- Platform coverage: Do you support all the platforms their customers use (Teams, Meet, Zoom, Webex)
- Maintenance burden: Who handles platform API changes, new features, edge case bugs
Requirements
- 3+ years closing experience in technical/API/infrastructure sales
- Startup experience (you're building process, not following established playbooks)
- Experience selling to technical buyers (developers, engineering leaders)
- Comfortable with technical concepts (APIs, SDKs, authentication, webhooks)
- Self-sourcing capability - you can prospect and qualify your own pipeline
- Track record hitting quota in a product-led or developer-focused environment