Up North AIUp North
Back to news

ElevenLabs Says the Turing Test Falls This Year

Vibe Coding Is Dead. Long Live Agent Armies..

Share

ElevenLabs Says the Turing Test Falls This Year

Mati Staniszewski, ElevenLabs' CEO, made a bold public call: conversational AI will pass the Turing test for most users within 6 to 12 months [1]. Coming from someone building voice agents at scale rather than an academic making a philosophical point, that's a claim worth taking seriously — and worth stress-testing.

Sound engineer comparing audio samples at a desk

The technical groundwork backs it up. Recent ElevenAgents updates include lower-latency turn-taking (the awkward pause is disappearing), an Expressive Mode for emotional delivery, and support for 70+ languages [2]. Staniszewski's framing is pragmatic, not hype-driven: the goal is real-world impact in customer service and citizen-facing government interactions, not a lab demo.

If this timeline holds, "can you tell it's a bot" stops being the interesting question. The interesting question becomes: what happens to every phone tree, support queue, and intake form once the honest answer is "no, you can't tell"? Multilingual support at this level also means voice AI stops being an English-first product category — genuinely relevant for Nordic and EU deployments where language fragmentation has always been the practical blocker.

Vibe Coding Is Dead. Long Live Agent Armies.

The consensus at Google I/O 2026 and across builder circles on X: single-agent "vibe coding" — type plain English, get an app — has already given way to orchestrated multi-agent systems, or what people are calling "agent armies" or "swarms" [3]. The visual metaphor going around is an orchestra: planners, coders, and critics working in coordinated roles rather than one model doing everything badly.

Sundar Pichai put a number on it: 75% of new code at Google is now AI-generated, produced by agent teams working through orchestrated workflows, completing projects roughly 6x faster than before [2]. That's not a vendor promising future productivity — that's the world's most scrutinized codebase running on it today. Pichai's framing was explicit: the shift is from prompting a single agent to orchestrating a team of them.

The honest caveat, and it's a real one: orchestration introduces breaking changes and demands verification layers that vibe coding never needed. Enterprise adoption is coalescing around exactly this problem — planners that decompose work, coders that execute, and critics that catch what the coders miss. The moat isn't the code generation anymore. It's the judgment layer that decides what gets built, checked, and shipped.

What This Means For Your Business

Three stories, one throughline: the bottleneck in AI-built software has moved from "can it write code" to "can you orchestrate the system that writes, checks, and ships code." Gemini's video efficiency gains and ElevenLabs' Turing-test timeline are both symptoms of the same maturation — the raw capability is now good enough and cheap enough that the differentiator shifts entirely to how you deploy it, sequence it, and verify its output.

If 75% of Google's code is AI-generated and the company is still standing (and shipping faster), the question for every other business isn't "should we adopt AI coding tools" — that debate is over. It's "do we have the orchestration layer and the verification discipline to run agent teams safely at our scale." Companies still thinking in terms of single-agent copilots are building for last year's architecture. The ones investing now in planner-coder-critic pipelines, human judgment checkpoints, and cost-aware model selection (like Gemini's new video efficiency) are the ones who'll compound the advantage.

Voice is the next frontier to watch closely. If conversational AI genuinely passes the Turing test within a year, the strategic question for any customer-facing business isn't "should we add a chatbot" — it's "what's our judgment layer for the interactions we're about to automate at scale, in 70+ languages, with no tell." That's not a coding problem. It's a governance and design problem, and it's arriving faster than most org charts are prepared for.

Key takeaway: The code is commoditizing in real time — what's left to build, and defend, is the judgment that decides what the agents should do, and when to trust them.

See what we're exploring →

Sources

  1. https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-agentic-video-in-gemini/
  2. https://aistudio.google.com/learn/agentic-video-understanding-with-gemini
  3. https://www.androidauthority.com/gemini-agentic-video-understanding-3705876/
  4. https://x.com/elevenlabsio/status/2021237336793657447
  5. https://www.youtube.com/watch?v=3o62dT-HFOQ
  6. https://blog.google/innovation-and-ai/sundar-pichai-io-2026/
  7. https://indianexpress.com/article/technology/artificial-intelligence/google-75-percent-ai-generated-code-sundar-pichai-10656702/
  8. https://venturebeat.com/ai/vibe-coding-is-dead-agentic-swarm-coding-is-the-new-enterprise-moat

Stay ahead of AI

No spam. Unsubscribe anytime.

Want to go deeper?

Reading the news is one thing. Exploring the frontier is another. See what we're building.