Tavus positions digital twins as infrastructure

Diving deeper into

Hassaan Raza, CEO of Tavus, on building the AI avatar developer platform

Interview
digital twins are a uniquely complex problem that has a very, very large research effort behind it.
Analyzed 4 sources

This is why Tavus is positioning digital twins as infrastructure, not as a feature. A believable replica is not one model that turns text into a face. It is a stack of tightly coordinated systems for lip sync, eye gaze, gesture, expression, translation, and real time rendering, where small errors make the whole video feel fake. That complexity favors specialist model providers over every SaaS team building its own version.

  • The hard part is not just making a face speak. The hard part is matching the tiny cues people notice instantly, eye contact, head movement, mouth shape, timing, and emotional expression. Tavus describes its pipeline as multiple components, not a single model, and says most systems still control only limited parts of the face well.
  • That technical difficulty maps directly to product structure. Synthesia and HeyGen sell finished apps for training, onboarding, and sales videos, while Tavus is built as an API layer for other software products to embed avatar generation inside their own workflows. In practice, that means HubSpot like tools can add AI video without hiring a replica research team.
  • The market signal is that realism has crossed a threshold where buyers will pay for it. HeyGen reached an estimated $22M ARR in May 2024 as talking heads moved closer to escaping the uncanny valley. But infrastructure economics still matter, because application companies can swap providers as quality converges and prices fall.

From here, the winners are likely to be the companies that keep pushing avatar quality while making it cheap enough to disappear into other products. As face control expands into full expression, head pose, and live interaction, digital twins move from prerecorded sales videos into core software workflows, where the model provider becomes part of the app's basic operating layer.