THE CHALLENGE
Hitting the limits of legacy data stores
Before shifting from AI research to enterprise products, ElevenLabs’ legacy database lacked native free-text search, draining engineering time.
The rapid advancement of artificial intelligence has transformed how global enterprises interact with audiences, shifting the focus from simple text interfaces to audio experiences. During the initial wave of the generative AI boom in 2022, London startup ElevenLabs set out to change the way humans interact with businesses through technology by building APIs for audio models.
“Our voice Text to Speech model was revolutionary,” said Alex Holt, Field CTO at ElevenLabs.
“It was the first AI model that sounded human.” However, ElevenLabs soon realized that deploying exceptional voice models was only part of the operational matrix.

“Building an API that enables you to turn text into speech is fantastic,” said Holt. “But our customers all struggled with the same challenge: building something that not only sounds human but also interacts in a human way.” To unlock true business value, the technology had to be interactive, context-aware, and integrated into complex enterprise environments.
This realization drove ElevenLabs’ evolution from a voice research lab into a product-focused platform provider as well. Beyond offering developer APIs, it began delivering end-to-end solutions that allowed enterprises to instantly deploy human-sounding agents connected directly to their core sales, support, and operational workflows.
Yet the company faced an architectural roadblock during the development of its high-accuracy Speech to Text transcription and editing product. The application required advanced interfaces to let users edit, format, and correct transcribed text in real time. However, ElevenLabs’ legacy database provider lacked native support for free-text search. To bypass this limitation, the company’s engineering team had to build a makeshift architecture, layering secondary index stores on top of the primary database and writing custom code to keep specific data fields synchronized.
“It became a full-time job for someone to maintain the secondary database and the code to synchronize between the two,” explained Holt.
