Smallest.ai's Electron v2 model responds in 53ms – 50x faster than leading TTS competitors. The Indian founding team is targeting a contact center market of 3 million agents.
ENTRY ANGLES
Real-time voice AI for Indian regional languages (Hindi, Tamil, Telugu) targeting bank/brokerage contact centers · Edge inference and model caching layer for low-latency voice AI in emerging markets · Voice AI for regulated industries (medical triage, financial advisory) where latency compliance is a requirement
VERTICALS
CAPABILITIES
Sub-200ms streaming inference architecture, Regional language model training (Indian languages), Edge deployment infrastructure
Voice AI has a trust problem, and it is entirely about timing.
The uncanny valley for AI voice assistants is not accent or intonation – it is the pause. When an AI takes 700 milliseconds to begin responding after a speaker finishes a sentence, the human brain registers it as unnatural regardless of how fluent the eventual response sounds. Users disengage. Enterprise deployments in contact centers and financial services report abandonment rates that make the economics marginal at scale.
Smallest.ai, founded in 2023 by Sudarshan Kamath and Akshat Mandloi – both former Robert Bosch engineers – attacked the pause directly. The company's Electron v2 is a 4-billion-parameter voice model that achieves a time-to-first-token of 53 milliseconds. Its Lightning TTS system generates 10 seconds of audio in 100 milliseconds. The company benchmarks those numbers as 50x faster than leading competitor systems, which include ElevenLabs, Deepgram, and PlayHT.
The architecture is not a faster version of the same approach. Standard TTS processes the full text before generating any audio – sequential generation. Smallest.ai built its models around real-time concurrent processing: input arrives, output begins before input is complete. Smaller, more efficient models optimized for speed rather than general-purpose large models optimized for quality across many tasks.
The $13 million Series A – led by Seligman Ventures with Sierra Ventures, 3one4 Capital, and individual angels – brings total funding to $21 million. Enterprise customers include RingCentral and Truecaller. Target verticals are financial services, healthcare, and contact centers.
ElevenLabs – the most-funded voice AI company in the Western market – built its platform around voice quality and cloning fidelity. That was the correct optimization for entertainment, dubbing, and content creation: use cases where a 700ms latency is invisible because the audio is pre-rendered. Enterprise operational use cases are different. Contact centers, financial advisory, and medical triage all require real-time conversational response, and in those contexts latency is not a quality dimension – it is a binary threshold. Below roughly 200ms, the exchange feels conversational. Above it, users interpret the pause as system uncertainty and either repeat themselves or disengage.
Smallest.ai's specific advantage is architectural. The company built models designed for streaming inference rather than adapting batch inference models to a streaming interface, which is the approach most latency-reduction attempts take. The difference matters because batch-to-stream adaption introduces unpredictable latency spikes under load; a purpose-built streaming architecture maintains consistent latency at scale. For enterprise buyers, the consistency is as important as the average number.
The customer base – RingCentral (100 million users across enterprise communications) and Truecaller (350 million users, primary market India) – signals the geographic and market orientation of the product. Both are high-volume, latency-sensitive, and operating at the scale where a 50x latency improvement is not a demo talking point. It is a unit economic requirement.
The founding team's background matters in a specific way. Both Kamath and Mandloi are from India and built the company initially for the Indian market. India hosts approximately 3 million contact center agents – the largest outsourcing concentration in the world – and serves a customer base that speaks Hindi, Tamil, Telugu, and a dozen other major languages. US-centric voice AI models notoriously perform poorly on these inputs. A voice AI platform purpose-built for Indian language phonetics, at 53ms latency, addresses a market that is both large in absolute terms and nearly unserved by current tooling.
Ultra-low latency voice creates commercially viable use cases that did not exist at 700ms, and the most immediately accessible are in regulated industries where incumbent contact center AI performs worst.
Real-time financial advisory calls in Indian regional languages is the most specific entry point Smallest.ai's architecture enables. The Indian retail investment market has grown from 50 million demat accounts in 2020 to over 150 million in 2026, creating a customer service volume that domestic banks and brokerages currently handle through human agents because AI voice quality in regional languages has been inadequate. A voice AI product that performs at 53ms in Hindi, Tamil, and Telugu – built on Smallest.ai's API or competing on its architecture – would reduce cost-per-interaction by 60–80% in a market where the volume is already proven and the AI alternative has been the obvious next step for years.
The infrastructure layer that Smallest.ai's approach makes necessary is edge deployment. Consistent 53ms latency is only achievable with inference running close to the user – not in a US data center. A startup building the edge inference and model caching layer specifically for voice AI – optimized for low-latency regional routing in India, Southeast Asia, and Latin America – owns a distribution component that Smallest.ai and every competitor will need as they scale beyond English-language Western markets. No one builds this as a standalone product today.
The underlying observation: voice AI's commercial ceiling has been set by latency, not by model quality. Most enterprise deployments that failed in the past two years failed on the latency threshold, not on the quality of the responses. At 53ms, that ceiling moves, and the use cases that become viable for the first time are larger in aggregate than the use cases that were already working.