Rime picks up $24M Series A to help enterprises field customer calls 39%

By Ivan Mehta39%

7/15/2026, 6:00:00 AM

BS Summary: This article contains 22 faulty reasoning types, including Halo Effect, Attempt to Sell a Product or Service, and Post Hoc (False Cause), with Appeal to Authority as the most egregious example at 19.8% saturation with 109 hits. Analysis detected 1,165 faulty-reasoning hits from 551 analyzed words, generating a BS Score of 44.6% and a BS Rank of 39% (13,367 of 21,887 articles). This article is better (less manipulative) than 61.10% of the article peer group.

Voice AI startups’ biggest unlock has been handling calls for enterprises in areas like sales, marketing and customer support. 
Large organizations are offloading calls to voice model developers like ElevenLabs and Deepgram; infrastructure companies like Vapi, Retell, and LiveKit; and dedicated customer support shops like Decagon and Sierra. 
San Francisco-based Rime is trying to gain an edge in this crowded market with its voice AI models that are trained on conversational data that it records, aiming to reduce its clients’ customization load. 
Founded in 2022 by former Stanford PhD student Lily Clifford, ex-Amazon Alexa engineer Brooke Larson, and Stanford engineer Ares Geovanos, Rime has built a recording studio in San Francisco to collect its own conversational data rather than relying on scraping the web for audio. 
The startup said it focuses on tuning its voice models to nail the pronunciation of different brand entities and industry-specific terms. 
It employs a phoneme-based architecture to adapt to different pronunciations so that customers don’t have to retrain models for their specific industry. 
Rime on Wednesday said it has raised $24 million in a Series A funding round that was led by M13 Ventures. 
Twilio Ventures, Corazon Capital, Unusual Ventures and other existing investors also participated. 
Clifford said that despite progress in voice AI development, enterprises still prefer legacy IVR implementations, as AI voice technology still can’t match up to IVR’s effectiveness. 
“The voice technology is still not there to automate the vast majority of enterprise phone calls. 
LLMs have made it a lot easier to build voice applications that work, but they haven’t changed how it feels to interact. 
Talking with a voice AI agent is not the most compelling experience for the end user. 
It’s kinda like a new IVR, but with a better voice,” she said. 
The startup started off with a pipeline of separate models for speech-to-text, text-to-speech, and a large language model. 
But it is now shifting focus to develop better speech-to-speech models to reduce latency, improve turn-taking, and tackle issues like background noise. 
The new approach will also serve to decrease reliance on orchestration, so the company doesn’t have to manage a bunch of models. 
Rime says it has customers in food service, healthcare, airlines, and fintech. 
The company claims that because of its training data and model positioning, customers stay longer on the call, which has helped it win enterprise contracts from clients like Mayo Clinic, Dialpad, Upstart, and Asurion. 
With the new funding, Rime is planning to expand its team of 35 people, aiming to hire for model development, engineering, and partnerships. 
It recently brought on Rafael Valle, who worked on audio understanding at Meta Superintelligence Labs and NVIDIA’s applied deep learning audio research team, as its Chief Scientist. 
“Companies like ElevenLabs have moved into being an orchestration and the application layer, going head to head with the Sierras and Decagons of the world. 
I think there’s just so much more to be done technically, and Rime’s approach of pushing forward on the best model with low latency and high reliability in a regulated environment stands out,” M13’s Morgan Blumberg told TechCrunch. 
It had previously raised $5.5 million in a seed round last May. 
Blumberg is joining the startup’s board as part of the fundraise. 
Article reasoning-pattern comparisonThis article: 14.9%Ivan Mehta: 2.0%TechCrunch: 3.0%Confirmation Bias14.9%This article: 0.0%Ivan Mehta: 1.3%TechCrunch: 1.4%Anchoring Bias0.0%This article: 10.9%Ivan Mehta: 3.3%TechCrunch: 3.5%Availability Heuristic10.9%This article: 8.7%Ivan Mehta: 0.5%TechCrunch: 1.1%Representativeness Heuristic8.7%This article: 0.0%Ivan Mehta: 0.4%TechCrunch: 0.6%Hindsight Bias0.0%This article: 6.9%Ivan Mehta: 2.8%TechCrunch: 2.5%Overconfidence Bias6.9%This article: 2.2%Ivan Mehta: 4.1%TechCrunch: 4.8%Framing Effect2.2%This article: 0.0%Ivan Mehta: 0.3%TechCrunch: 0.6%Loss Aversion0.0%This article: 2.4%Ivan Mehta: 0.5%TechCrunch: 0.6%Status Quo Bias2.4%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.2%Sunk Cost Effect0.0%This article: 14.3%Ivan Mehta: 5.9%TechCrunch: 4.9%Optimism Bias14.3%This article: 7.6%Ivan Mehta: 1.2%TechCrunch: 1.3%Pessimism Bias7.6%This article: 7.6%Ivan Mehta: 3.1%TechCrunch: 5.0%Negativity Bias7.6%This article: 6.2%Ivan Mehta: 3.5%TechCrunch: 2.1%Self-Serving Bias6.2%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.5%Fundamental Attribution Error0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Actor-Observer Bias0.0%This article: 0.0%Ivan Mehta: 0.3%TechCrunch: 0.6%In-Group Bias0.0%This article: 0.0%Ivan Mehta: 0.2%TechCrunch: 0.3%Out-Group Homogeneity Bias0.0%This article: 19.1%Ivan Mehta: 4.4%TechCrunch: 3.5%Halo Effect19.1%This article: 0.0%Ivan Mehta: 0.1%TechCrunch: 0.1%Horn Effect0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%Ivan Mehta: 0.9%TechCrunch: 2.3%Recency Bias0.0%This article: 0.0%Ivan Mehta: 0.2%TechCrunch: 0.3%Primacy Effect0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Blind-Spot Bias0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.3%Ad Hominem0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.6%Straw Man0.0%This article: 19.8%Ivan Mehta: 4.5%TechCrunch: 4.4%Appeal to Authority19.8%This article: 0.0%Ivan Mehta: 0.8%TechCrunch: 1.7%False Dilemma0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.7%Slippery Slope0.0%This article: 0.0%Ivan Mehta: 0.1%TechCrunch: 0.2%Circular Reasoning0.0%This article: 16.5%Ivan Mehta: 6.4%TechCrunch: 6.0%Hasty Generalization16.5%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.2%Red Herring0.0%This article: 4.5%Ivan Mehta: 2.4%TechCrunch: 1.1%Bandwagon4.5%This article: 4.0%Ivan Mehta: 0.7%TechCrunch: 2.2%Appeal to Emotion4.0%This article: 6.7%Ivan Mehta: 0.7%TechCrunch: 0.6%Begging the Question6.7%This article: 18.1%Ivan Mehta: 2.5%TechCrunch: 2.9%Post Hoc (False Cause)18.1%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Tu Quoque0.0%This article: 9.1%Ivan Mehta: 0.7%TechCrunch: 0.5%Burden of Proof9.1%This article: 0.0%Ivan Mehta: 0.2%TechCrunch: 0.2%Appeal to Nature0.0%This article: 0.0%Ivan Mehta: 0.2%TechCrunch: 0.3%Composition/Division0.0%This article: 2.9%Ivan Mehta: 0.9%TechCrunch: 2.4%Anecdotal2.9%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%No True Scotsman0.0%This article: 6.9%Ivan Mehta: 1.9%TechCrunch: 2.0%Ambiguity (Equivocation)6.9%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.0%Gambler’s Fallacy0.0%This article: 0.0%Ivan Mehta: 0.2%TechCrunch: 0.2%Middle Ground0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.0%Personal Incredulity0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Special Pleading0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Genetic Fallacy0.0%This article: 0.0%Ivan Mehta: 1.7%TechCrunch: 2.0%Unattributed Quote0.0%This article: 0.0%Ivan Mehta: 0.4%TechCrunch: 0.7%Quote-first Misdirection0.0%This article: 3.8%Ivan Mehta: 1.4%TechCrunch: 4.6%Biased Writer Voice3.8%This article: 0.0%Ivan Mehta: 0.3%TechCrunch: 0.8%Indoctrination0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Politically Left Leaning Bias0.0%This article: 0.0%Ivan Mehta: 0.0%TechCrunch: 0.1%Politically Right Leaning Bias0.0%This article: 18.3%Ivan Mehta: 7.6%TechCrunch: 4.9%Attempt to Sell a Product or S…18.3%

551 words analyzed.

Speakers

2speakers28%attributed speech395writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 12 words • 100.0% coverageWriter's voice • 19 words • 0.0% coverageWriter's voice • 29 words • 0.0% coverageWriter's voice • 34 words • 100.0% coverageWriter's voice • 44 words • 0.0% coverageWriter's voice • 21 words • 100.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 21 words • 0.0% coverageWriter's voice • 12 words • 0.0% coverageLily Clifford • 26 words • 0.0% coverageLily Clifford • 16 words • 0.0% coverageLily Clifford • 22 words • 0.0% coverageLily Clifford • 16 words • 0.0% coverageLily Clifford • 13 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 12 words • 0.0% coverageWriter's voice • 34 words • 100.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 27 words • 0.0% coverageMorgan Blumberg • 25 words • 0.0% coverageMorgan Blumberg • 38 words • 0.0% coverageWriter's voice • 12 words • 0.0% coverageWriter's voice • 11 words • 0.0% coverage
Selected voice

Lily Clifford

100%flagged-word coverage
93 attributed words60% of attributed speech81% writer coverage
0%15.0%30.0%Attempt to Sell a Product -25.6 ptsWriter: 25.6%Lily Clifford: 0.0%0.0%Biased Writer Voice-5.3 ptsWriter: 5.3%Lily Clifford: 0.0%0.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.