YC Root AccessRecall.ai: Unlocking the World’s Conversations
David on recall.ai powers conversation recording infrastructure for 1,000+ AI companies.
In this episode of YC Root Access, featuring David, Recall.ai: Unlocking the World’s Conversations explores recall.ai powers conversation recording infrastructure for 1,000+ AI companies Recall.ai provides an API to capture real-time audio/video from meetings, calls, and in-person conversations, serving 1,000+ companies with nearly $20M revenue and <30 employees.
At a glance
WHAT IT’S REALLY ABOUT
Recall.ai powers conversation recording infrastructure for 1,000+ AI companies
- Recall.ai provides an API to capture real-time audio/video from meetings, calls, and in-person conversations, serving 1,000+ companies with nearly $20M revenue and <30 employees.
- The company originated as a call-recording product, where reliability demands forced deep investment in infrastructure that later became Recall’s core defensible asset.
- A pivotal shift occurred as LLM capabilities accelerated, revealing that many AI products needed standardized access to conversation data more than another end-user recorder.
- Fundraising was unusually grindy—$160K after four months for the first product and a seed requiring 120 investor meetings—highlighting perseverance and founder-led networking.
- Growth came from founder-led sales and a talent strategy focused on rare “full-stack” high-agency hires who can own systems, product decisions, and customer outcomes.
IDEAS WORTH REMEMBERING
5 ideasInfrastructure reliability becomes the moat when data is unrecoverable.
Recording failures permanently lose customer conversations, so Recall spent 70–80% of engineering time on stability and scale—work that later compounded into a differentiated platform others didn’t want to rebuild.
Pivot timing followed platform shifts in LLM capability.
As LLMs made unstructured conversation data newly valuable, Recall repositioned from an end-user recorder to an API layer that many AI and SaaS products needed to ship faster.
Deep conviction is strongest when you’ve personally carried the pager.
David’s “nightmares” from being on-call and handling angry customers created visceral certainty the problem was real, helping sustain the team through skepticism and long fundraising cycles.
Your first customers may be former competitors if you remove their pain.
Recall emailed rival call-recording companies offering to take the infrastructure burden; early adopters gained speed advantages, which then pressured others to follow.
Sales is learnable and mostly operational—not ‘black magic.’
David frames sales as (1) clearly explaining value and (2) guiding buyers through internal procurement; Recall’s first $2M revenue was pure outbound led by the founders.
WORDS WORTH SAVING
5 quotesWe are today nearly at $20 million in revenue with a team of less than 30 people.
— David
We're launching 8 million EC2 instances every month.
— David
For the five or six-month period after we launched that call recording product... I actually had nightmares about the infrastructure.
— David
The first $2 million in revenue... was pure outbound and 100% done by Amanda.
— David
There's five times more words spoken at work every year than all the words on the entire internet.
— David
QUESTIONS ANSWERED IN THIS EPISODE
5 questionsOn the technical side, what architecture choices let you process ‘three terabytes per second’ of raw video without ballooning headcount?
Recall.ai provides an API to capture real-time audio/video from meetings, calls, and in-person conversations, serving 1,000+ companies with nearly $20M revenue and <30 employees.
What were the clearest failure signals in the call-recorder business that made the API pivot unavoidable rather than optional?
The company originated as a call-recording product, where reliability demands forced deep investment in infrastructure that later became Recall’s core defensible asset.
When competitors feared you were ‘pulling a trick,’ what proof or contract structure helped convert the first few to paying infrastructure customers?
A pivotal shift occurred as LLM capabilities accelerated, revealing that many AI products needed standardized access to conversation data more than another end-user recorder.
How do you price the API (per minute, per stream, per feature) while handling wildly different customer volumes and reliability expectations?
Fundraising was unusually grindy—$160K after four months for the first product and a seed requiring 120 investor meetings—highlighting perseverance and founder-led networking.
What are the hardest edge cases in botless desktop recording (permissions, OS audio routing, privacy) compared to bot-based meeting capture?
Growth came from founder-led sales and a talent strategy focused on rare “full-stack” high-agency hires who can own systems, product decisions, and customer outcomes.
Chapter Breakdown
Recall.ai today: API for meeting recording powering 1,000+ companies
David explains Recall.ai as an infrastructure API that lets developers capture real-time audio/video and other conversation data across Zoom, Teams, Google Meet, phone calls, and in-person sources. He frames Recall as a foundational layer behind 1,000+ AI and SaaS companies, with strong revenue efficiency and rapid growth.
Engineering at extreme scale: reliability, EC2 sprawl, and video throughput
The conversation zooms into the operational reality of running conversation-capture infrastructure at high volume. David shares concrete scale metrics and highlights why reliability is existential when recordings can’t be recovered if missed.
Hackathon to YC: a 19-year-old’s sprint from Waterloo to Winter ’20
David recounts winning a YC hackathon in 2019, earning a YC interview, and rapidly reshaping the project into something fundable. He describes the intensity of balancing school, travel, and the all-in commitment required to seize the YC opportunity.
Co-founder transitions and committing through uncertainty (finding Amanda)
David explains why early co-founder setups changed—first due to reluctance to leave college, later due to COVID-era risk and desire for stability. He details how alignment on mission and resilience became the deciding factor in bringing Amanda on as the long-term co-founder.
Building the first product: a call recorder before LLMs
Recall’s roots were a standalone call recording product built to manage the team’s own user research and recordings. David describes how the product forced them to become experts in the hardest part—capturing and storing conversations reliably.
Pivot to Recall: selling conversation-capture infrastructure as an API
As LLM capabilities accelerated, David and Amanda recognized conversation data was becoming the substrate for a new wave of AI products. They repackaged their hardened recording stack into an API and repositioned from an app to infrastructure.
Fundraising the hard way: deferred Demo Day, 160K first round, then 120 seed meetings
David details unusually grind-heavy fundraising cycles, first for the recorder and then for Recall. With minimal network and remote constraints, they relied on relentless outreach to founders for introductions, turning persistence into a core operating advantage.
Deep conviction from living the pain: on-call nightmares and infrastructure truth
Asked what proved they were on the right track, David points to firsthand experience operating the system under real customer pressure. The “lived problem” created conviction that outlasted skepticism from outsiders.
Landing first customers by converting competitors into buyers
Recall’s first go-to-market move was counterintuitive: they approached their former competitors. A small number trusted them, adopted the API, and gained speed—creating a visible advantage that helped the category become “standard.”
Learning sales from scratch: $2M outbound and reframing what ‘sales’ is
David explains how the team learned enterprise sales without prior experience, largely through repetition and direct founder-led outbound. He demystifies sales as communicating value and navigating internal buyer processes—not manipulation.
Reaching ~$20M ARR with <30 people: high bar hiring and “full-stack” ownership
The discussion turns to extreme revenue-per-employee and how Recall stays lean intentionally. David attributes it to hiring rare, high-agency operators who span engineering, product, and customer interaction, minimizing information loss from handoffs.
Why conversation data is the future of AI: the ‘missing context’ inside companies
David lays out the macro thesis: spoken language at work dwarfs written artifacts, and most organizational context never enters docs. For AI to be effective, it needs access to conversations—the living substrate of how decisions and knowledge move.
What’s next: botless desktop recording, broader capture surfaces, and data infrastructure
David previews product expansion beyond meeting bots, including a desktop recording SDK and future support for phone, mobile, storage, querying, and preprocessing. The goal is to widen capture coverage and provide end-to-end primitives for working with conversation data.
Hiring and founder advice: high-agency teams and ‘don’t give up’ for at least a year
Closing themes emphasize hiring people motivated by ownership and intensity, given Recall’s role as critical infrastructure for much larger companies. David’s founder advice centers on endurance: competence and product clarity compound over time, and most quit before reaching that point.
EVERY SPOKEN WORD
Install uListen for AI-powered chat & search across the full episode — Get Full Transcript
Get more out of YouTube videos.
High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.
Add to Chrome