HeyGen SaaS vs API Conflict

HeyGen is moving from being a video app into being a platform, and that changes who it can sell to without creating channel conflict. A SaaS customer uses HeyGen directly to make training, sales, or translated videos inside HeyGen. An API customer uses the same avatar engine under its own brand inside another product. Once both exist, every new workflow HeyGen adds can help direct revenue, but it can also make an API buyer wonder whether HeyGen is building toward the same end customer.

• D-ID avoided this problem by staying API first. It powered products like MyHeritage and other white label integrations instead of building a broad end user suite, which made it easier for software companies to trust it as infrastructure rather than a future rival.
  1 sacra
• Tavus made a similar choice. Its pitch is that digital twin video should live inside HubSpot, Intercom, or Shopify like infrastructure, with customers owning the front end and workflow. That gives partners room to build differentiated products on top without worrying about a competing SaaS package.
  3 sacra 4 sacra
• HeyGen is now on both sides of the market. It sells direct subscriptions, it offers API plans starting at $99 per month, and some vertical apps reportedly use HeyGen under the hood for UGC ads and chatbots. That expands distribution fast, but it also means some partners are effectively resellers built on a supplier that still sells its own finished product.
  1 sacra 2 sacra

The likely direction is a clearer split between HeyGen as the best packaged app for marketers and SMBs, and HeyGen as the engine for narrowly tailored partners in categories like sales agents, support, and UGC ads. The winners in avatar infrastructure will be the companies that decide which layers they own, and which layers they leave to customers.