Reading

ElevenLabs builds the voice layer of AI—models that turn text into speech that sounds human. Most people have already used it when talking with customer service, without realizing it. Klarna runs first-line phone support for 35 million U.S. customers on it. So do Deutsche Telekom, Cisco, Adobe, and a growing list of governments. The company says it is pacing at $600 million in annual recurring revenue and is now reportedly valued at $22 billion by its backers, despite being just four years old.

ElevenLabs co-founder and CEO Mati Staniszewski was asked about gross margins during an interview with TechCrunch Editor in Chief Connie Loizos at the Nrth conference in Toronto in September 2026. His answer was direct: he does not mind margins getting squeezed even further if it means expanding the company's market share. He said that given the research element, the company is able to fine-tune and constrain models in extremely smart ways to optimize costs, but if savings can be passed on to the customer, they do that. In his view, the biggest thing right now is still proving value and being there with the customer, and once value gets created over the next five years, everyone benefits together.

This statement only has concrete meaning within ElevenLabs' competitive landscape. Staniszewski acknowledged in the interview that the company is increasingly bumping into its own customers—Decagon, for example, is a conversational AI platform that trained its voice product on ElevenLabs and now competes with it by running queries through its own models. Staniszewski believes the lines between model companies, platform companies, and application companies are becoming blurrier. He cited Anthropic as an example: what was a model company is definitely a platform and increasingly a wide set of applications.

At the same time, Staniszewski revised his judgment on audio model commoditization. He had said at TechCrunch Disrupt the previous year that audio models would be commoditized within a couple of years. Now he acknowledged that the quality delta achievable at the model level is still significant, but pushed the timeline to three to five years. In other words, he believes the technical moat has a window, but not a permanent one.

Putting these together, Staniszewski's strategic logic is: since the model quality gap will narrow within three to five years, and customers can become competitors at any time, trading margin for customer lock-in and integration depth is rational at this stage. ElevenLabs' other moat lies not in the model itself but in data annotation—Staniszewski said the big part of training has not been so much the volume of data but annotating it. The company has thousands of people internally on a contracting basis helping annotate not only what was said, but when people were speaking, how they said things, and what emotions were used. They even brought in voice coaches to detect accents accurately. This operationally intensive data asset is not something open-source models can directly replicate.

However, the boundaries must be clear: Staniszewski declined to disclose specific gross-margin figures. The $600 million ARR is self-reported by the company. The $22 billion valuation is reportedly from a Bloomberg article in July 2026 about tender-offer talks. His statement about not minding margin compression is an expression of strategic intent, not a realized financial result. Whether the promised mutual benefit materializes over the next five years depends on whether the company can recover costs through pricing power after expanding market share, or whether margins get compressed to the point of being unable to cover research and annotation investment.

GPT-OSS-20B is an open-weight reasoning model with a stubborn habit: regardless of which language the user asks in, its chain-of-thought almost always generates in English. The AWS machine learning team found that on a 50-example multilingual reasoning test, the base model used the correct target language only 22 percent of the time, and that 22 percent came almost entirely from the English samples—French, Spanish, and Italian scored zero, with German at just 10 percent.

The team then ran supervised fine-tuning (SFT) for 1,000 steps using a LoRA adapter (r=8, α=16) across four ml.g6e.12xlarge instances. The result was direct: reasoning-language accuracy jumped from 22 percent to 100 percent. But answer-language reached only 62 percent—the model learned to think in French yet often switched back to English for the final answer.

This is precisely where GRPO (Group Relative Policy Optimization) applies. GRPO works by sampling a group of responses per prompt and pushing the policy toward the above-average ones. If the target behavior has zero probability in the base distribution, there is almost nothing for GRPO to reinforce. After SFT, the model could already reason in the correct language 100 percent of the time and occasionally produce the answer in the right language as well, giving GRPO a signal to reinforce.

According to Bloomberg, four co-founders of Chinese artificial intelligence company Z.AI Co.—Li Juanzi, Tang Jie, Xu Bin, and Zhang Peng—participated in a research project between 2018 and 2021. The project was jointly funded by the National Natural Science Foundation of China and the China General Technology Research Institute (CGTRI), with an approved budget of 2.94 million yuan.

Britain’s Security Service (MI5) previously issued an alert stating that CGTRI has “very strong ties” to China’s Ministry of State Security (MSS) and funds academic work intended to strengthen the MSS’s espionage capabilities. MI5 advised UK academic institutions to immediately review any collaborations with CGTRI.

Citing a 78-page project report, Bloomberg said the research envisioned AI systems capable of mining social media posts to identify emerging events and reveal links among people. The report emphasized that this description concerned proposed capabilities, not evidence that such tools were deployed.

China’s Embassy in Britain disputed MI5’s allegations against CGTRI. Z.AI and the four founders did not respond to Bloomberg’s requests for comment. Filings by Z.AI with the Hong Kong Stock Exchange confirm the four individuals as co-founders, with Zhang serving as chief executive.

James Simcox, Chief Product Officer at fintech company Equals, revealed at Okta's annual user conference in Las Vegas that more than 92% of the company's code is now written by AI, up from zero less than 12 months ago. Simcox described the company's journey through three phases: "no AI, AI everywhere, and then back down to AI for tasks that actually make sense."

Internally, Equals experimented with a multi-agent "courtroom" model for handling customer complaints, where one agent argues for the customer, another against, and a third assesses the arguments. Simcox believes this approach can produce fairer outcomes and speed up processing, though human review remains part of the process. This internal testing provided a learning ground before extending agents to customer interactions.

However, not all scenarios benefit from agents. Simcox noted that for straightforward tasks like euro payments, basic automation is more useful and cost-effective than spending tokens on an agent. Agents are better suited for structured challenges between simple automation and complex human investigation. In terms of governance, Equals treats agents like staff but grants them much narrower permissions. For instance, an agent tasked with changing an email address only has permission to read and modify that specific field, allowing actions to be attributed to that specific agent.

Crucially, audit requirements differ. While human actions are logged as "who did what," Equals also logs the reasoning behind agent actions to investigate errors. Simcox expressed concern that a misconfigured agent could make a mistake "100,000 times at the same time," potentially destroying the business. Consequently, he highlighted the importance of Okta's recently announced kill-switch functionality for intervention.

According to the Wall Street Journal, the US Department of Homeland Security has issued an order banning federal civilian agencies from using artificial intelligence technology from the Chinese lab DeepSeek. The directive requires these agencies to remove existing DeepSeek products from their IT systems and prohibits the purchase of any new ones.

The ban extends beyond DeepSeek's own products to include offerings from affiliated companies and third-party services built with DeepSeek implementations. However, the notice did not set a specific compliance deadline or detail the particular security concerns that led to the decision. It remains unclear what "built with" actually means in practice, leaving questions about whether AI gateways like OpenRouter fall under the restriction.

The order is based on a 2018 US law covering supply chain security in federal procurement. This move follows earlier discussions within the US government about taking steps against powerful Chinese open-weight models, such as Kimi K3 from Moonshot AI. While major tech firms like Nvidia, Microsoft, Google, and Meta previously objected to broad restrictions, OpenAI and Anthropic had lobbied for tighter controls, marking a shift towards concrete regulatory action against specific foreign AI providers.

The core asset of a quality-management platform is institutional memory: a similar defect investigated last year, a Corrective and Preventive Action that fixed the root cause, an audit finding that flagged the same gap. That knowledge sits scattered across billions of documents, spanning languages and formats, and no human can search by semantic similarity, so every investigation starts from scratch. The Octave Reliance team saw unlocking this history as its single largest opportunity, and also saw the obstacle: complaint records, audit findings, and corrective actions carry the platform's strictest isolation requirements, and those were exactly the records the AI would need to read. In a platform serving over 14,000 customers across medical devices, pharmaceuticals, and food manufacturing, a single inadvertent cross-tenant disclosure would carry regulatory consequences far outweighing any AI benefit.

Faced with that contradiction, the team made an unusual call: rather than shipping one AI feature, it spent its first cycle building a foundation every future feature would sit on. The reasoning was straightforward—Reliance has over 40 applications, each with different document types and workflows, and building AI for one in a silo meant rebuilding the infrastructure for the next. So they inverted the plan: build the horizontal platform first, then cut vertical feature slices into it. Complaint summarization and triage went first, to prove the architecture before the rest followed.

Four tensions shaped the design, and none could be traded away: making data available without risking inadvertent disclosure, executing agents in isolation, reading content that cannot be trusted, and embedding 2 billion documents without a quarter-long wait. When all four had to hold simultaneously, the option space narrowed considerably.

The first key decision was where to enforce tenant separation. Application code would have worked, but it would have meant every future feature team getting it right on every code path, where one missed check risks inadvertent cross-tenant disclosure. The team pushed isolation into the runtime instead: each user session runs in a dedicated microVM with its own CPU, memory, and filesystem, stopped and sanitized when the session ends. That is hardware-level separation designed to hold regardless of how the agent behaves. AgentCore Gateway authorizes at the tool, operation, and parameter level, and automated reasoning provides formal verification against the defined rules.

The second key decision was how to represent the data. The team evaluated embedding models against its own corpus rather than public leaderboards. The deciding questions were specific to this data: what a photo of a cracked housing has to do with the paragraph describing it, and a German complaint with an English CAPA. Cohere Embed v4's multimodal capability places photos and text in one vector space, and native multilingual support means documents in different languages within one tenant's corpus need no translation preprocessing. But the finding that only a proprietary corpus could surface was the dimension choice: Amazon OpenSearch Service costs scale linearly with dimension count, and Embed v4 supports configurable output dimensions of 256 to 1,536. Testing against representative production queries showed 512 dimensions holding target accuracy while cutting storage roughly 66 percent against the 1,536 default. This trade-off would not appear on any public benchmark, because it depends on the actual document mix of defective-product photos, scanned inspection forms, annotated diagrams, and text.

On results, the Complaint Triage Assistant has been running in production for three months. Octave measures 4 to 6 hours per investigation as the work the pipeline absorbed: extraction across formats, the hunt for precedent, and the reading it takes to tell a genuinely similar defect from a coincidence of wording. The foundation cut deployment time per use case by 50 percent—by Octave's own accounting—and semantic search landed in Q2, two quarters ahead of the original Q4 target.

Boundaries worth preserving: all figures come from Octave's internal testing and production self-reporting, published on the AWS official blog. The latency and cost overhead of the microVM approach is not discussed in the source. The team also drew a line it chose not to cross: the assistant surfaces context and precedent, and the quality handler still makes the call—in an industry where that call carries regulatory weight, that boundary shaped what got automated and what did not. This is one company's architecture experience in a specific regulatory context, not a proof of optimality for runtime isolation across all multi-tenant AI scenarios.

Figma announced 20 new MCP partners at its first Config conference held in India, including Amp, ClickUp, Linear, Notion, Mistral, and others. At a media briefing, co-founder Dylan Field told reporters that he does not think MCP is a perfect protocol.

Field's core argument points to a structural asymmetry: MCP was created by Anthropic, yet Anthropic itself does not expose its cloud resources through MCP. Field wrote on X that he found it interesting that the creators of the MCP standard do not expose artifacts or other cloud resources created via MCP. He argued that the debate is framed as open versus closed, everyone always prefers open, and meanwhile issues of asymmetric context sharing are ignored.

The mechanism behind this argument is as follows: MCP standardizes how AI agents connect to external data sources and tools. When application-layer companies open their data according to this standard, the protocol creator—typically a frontier lab with the most powerful models—gains a structured access path without offering reciprocal exposure. Field further stated at the media briefing that MCP is advantaged more to frontier labs.

Figma's actual strategy is to both embrace and critique the standard. The company is expanding MCP support, but Field said the reason Figma does not want to be fully open is that the more data the company exposes through MCP, the higher the chance of abuse. He acknowledged that most users do not intend to use MCP or Figma data maliciously, but the company still has to think about those potential risks. Field later added that Figma plans to support Pi, the open-source tool that one of MCP's co-creators had complained about.

The value of this argument lies not in whether it ultimately proves correct, but in that it raises a concrete design question: when a protocol is created by the most powerful participant in an ecosystem, how do smaller companies adopting that protocol avoid becoming one-sided data suppliers? For developers evaluating AI agent integration options, the asymmetric context sharing Field identifies is a practical constraint to consider, not merely an ideological open-versus-closed debate.

Hamlet is an AI-powered civic data platform that indexes and transcribes city council, planning commission, and zoning board meetings across the United States, allowing real estate developers, journalists, researchers, and citizens to search meeting content and track local policy developments. CEO Sunil Rajaraman says customers want to know whether a council member will approve their housing project, why or why not, and what history the city has that might make it hesitate. This business requires processing extremely messy data from more than 7,200 governing bodies, and the engineering team is small—velocity matters more than almost anything.

Lead Developer Erich Douglass recalled the previous state: they ran one production instance and one staging instance on AWS RDS, with much of their work involving tuning data pipelines against very specific data. Every pull request required 15 to 30 minutes to get staging into the right state before they could run validations. Senior AI Engineer Jeff Hui added that 15 to 30 minutes was the best case—when you happened to copy exactly the right data. Each engineer could spend several hours a week keeping test data current, including cloning pieces of production locally to chase down issues.

After switching to Databricks Lakebase Postgres, every pull request automatically gets its own branch of production data, connected to its preview environment. Douglass says when the preview deploys, the data is ready—they can test against production data and even write to it without touching production. Hui says now when they hit a bug, they have the exact data that caused it, and they can check the fix against that same data.

But what truly changed the workflow was not the saved minutes. Hui says branching makes their workflow a much better fit for AI coding agents. Each pull request is isolated from production; they give an agent like Claude or Codex access to its branch and let it run its own checks. The agent runs the data pipelines to completion and looks at whether the change does what it should. Every pull request gets that first pass from an agent. By the time a person looks at it, they are already fairly confident it works. A human still approves the merge, but more and more of the rest is automated.

The prerequisites of this workflow deserve attention: the agent needs an isolated, complete environment containing real data to run end-to-end pipelines and judge results on its own. If the data is synthetic or stale, the agent's verification does not equal verification against real scenarios. Hui stated a similar principle when discussing video speaker identification—

You can't hand a model a video and hope for the best. You have to collect everything around it that helps it make the right call.

For coding agents, the surrounding information is that real data.

It should be noted that this is a customer interview published on the official Databricks blog. Douglass and Hui describe their own team's actual practices; the time savings are self-reported figures without a stated measurement method. Hamlet is a small team, and whether their workflow applies to larger teams or different technology stacks is not discussed in the original.

French artificial intelligence startup Mistral AI launched Voxtral 3 on October 20, 2026, a full-stack solution designed specifically for real-time voice agents. The series includes a speech-to-text model (Voxtral Small Transcribe 3), a text-to-speech model (Voxtral Mini TTS 3), and a voice agent SDK based on LiveKit. Mistral states that these components combine into a single streaming pipeline, enabling agents to simultaneously 'listen,' 'think,' and 'speak,' while also calling external tools during conversations, such as booking appointments or checking invoices.

In terms of capability coverage, Voxtral 3's transcription supports over 50 languages, while its text-to-speech output supports more than 35 languages and 50 dialects, featuring emotional adaptation. This aims to address common issues in current voice AI applications, such as robotic tones and insufficient multilingual support.

Beyond technical performance, Mistral emphasizes deployment flexibility. The system can run on user-owned infrastructure or via EU-hosted APIs to ensure data remains within Europe. This option directly addresses corporate concerns about data sovereignty and GDPR compliance. Pricing starts at $0.0035 per minute for transcription. Currently, independent test data regarding actual performance in complex noisy environments and end-to-end latency is not available; vendor-reported metrics still require third-party verification.

Liquid AI released LFM2.5-VL-DSpark on September 24, a speculative-decoding draft model for its 3B vision-language model LFM2.5-VL-3B. The company reports decode speedups up to 3.13x on device and 2.66x on an H100, with end-to-end latency improving up to 2.62x and 2.27x respectively.

The draft model has roughly 280M parameters, adding 8.9% to the deployed model's size, and ships with day-one support for llama.cpp, MLX-VLM, and SGLang. Speculative decoding is exact: the target model verifies every proposed token, so output is unchanged.

The company itself names the limit: speculation accelerates only decoding, not vision encoding or prefill, and on edge devices those stages take up more of the wall time, so end-to-end gains fall well below decode gains. All speed figures are the vendor's own measurements across six vision tasks.

OpenAI announced on October 20, 2026, that its latest AI models have shown significant progress in handling "low-resource" programming languages. These include COBOL, Fortran, and Visual Basic. While these languages have far less available training code than modern languages like Python, IBM estimates that COBOL alone powers more than 40 percent of online banking systems and 95 percent of all ATM transactions worldwide.

According to two evaluations built by OpenAI, the GPT-6 Astra model achieved an average test pass rate of 87.4 percent across 20 languages on MultiLangBench, a substantial increase from approximately 38 percent for the previous generation, GPT-5.6 Terra. The MultiLangBench task requires models to build a SQLite-compatible database engine from scratch.

On a specific COBOL migration benchmark, which involves translating COBOL into C++, Java, Kotlin, Python, or Rust, GPT-6.1 Sol reached 86.6 percent accuracy at low reasoning effort, compared to just 5.4 percent for GPT-5.6 Sol. Increasing the reasoning effort pushed the accuracy up to 97.9 percent.

It is important to note that these figures are based on OpenAI's internal evaluations and have not been independently reproduced. Furthermore, the high accuracy rates were achieved under specific configurations, such as maximum reasoning effort, which may not reflect typical production use cases due to cost and latency constraints.

Stijn Van Nieuwerburgh, a professor of finance and real estate at Columbia Business School, argues in a paper prepared for a Brookings Institution conference that the economic output consumed by US artificial intelligence infrastructure construction may exceed that of historical mega-projects like electricity and railroads. According to Reuters, the study projects that by 2032, approximately 3.6% of US GDP will be invested annually in this sector, with a cumulative scale exceeding $10 trillion.

This ratio is significantly higher than the peak of US railroad construction in the late 19th century, which accounted for about 2.2% of GDP annually. In comparison, the Interstate Highway System started in the 1950s and the telecommunications expansion in the mid-1990s both saw annual investments slightly above 1% of GDP. Van Nieuwerburgh points out that previous expansions in rail and telecom triggered asset bubbles and subsequent crashes. The current AI infrastructure boom not only has unprecedented scale but also increasingly complex financing structures involving banks, private credit institutions, and special purpose vehicles (SPVs). This opacity evokes comparisons to the pre-subprime crisis era.

To test the viability of these investments, Van Nieuwerburgh calculated the required revenue gap. He estimates that by 2032, the AI industry needs to generate approximately $3.7 trillion in total annual revenue to achieve currently expected investment returns. However, the combined annual revenue of leading companies like OpenAI and Anthropic is currently estimated at only about $100 billion. This implies that related revenues must grow at a rate of roughly 80% per year to bridge this massive gap. If market demand remains uncertain, technology changes too rapidly, or execution bottlenecks occur, high leverage rates could lead to "substantial downside risk" upon a shift in market expectations.

However, the professor emphasizes in the paper that this does not mean a financial crisis is imminent. He suggests that strong growth in AI applications, high infrastructure utilization rates, and continuous improvements in model capabilities could support the anticipated infrastructure investments and generate stable cash flows. The paper was scheduled for formal submission on Friday, with its core message serving as a reminder to investors and policymakers to monitor the tension between current capital expenditures and future revenue potential.