
VM Blog Exclusive Interview with Vivek Vaidya, founding General Partner, super{set}
VM Blog Exclusive Interview with Vivek Vaidya
This VMblog Q&A with super{set} founding GP Vivek Vaidya explains how the studio builds AI-native enterprise companies by pairing capital with hands-on company building (engineering, GTM playbooks) and focusing on proprietary data as the core moat. It spotlights the $200M acquisition of Habu by LiveRamp (2024) as proof of the model, and details what they seek in technical co-founders, how they hard-wire governance/privacy from day one, and which enterprise workflows are ripe for AI over 2025–2030.
Why it’s worth a read: Clear, practical playbooks on how to compress zero-to-one, build data flywheels, run enterprise GTM with design partners, and avoid “model-first” traps. A useful read for founders and operators, not just investors.
To read full Q&A article, go to VM Blog.
Tech, startups & the big picture
Subscribe for sharp takes on innovation, markets, and the forces shaping our future.
NEWS, BLOGS & ARTICLES
Let's keep in touch
We're heads down building & growing. Learn what's new and our latest updates.

AI didn't eliminate the hardest part of building a startup—it moved it. Today, the challenge isn't writing code; it's finding the people who can validate your idea before you race to market. Design partner discovery has become the new go-to-market problem, and the founders who solve it first will build companies that matter.

Every company I talk to is building agents, AI-native tools, and therefore integrating LLMs into their customer-facing production systems. The pace of adoption has been staggering. OpenAI’s rapid growth and Anthropic’s imminent IPO are clear validation points. But there’s a pattern I keep seeing: the demo works, the executive buyers are excited, the board is bought in—and then it hits production, and everybody is surprised with the LLM costs, in the form of credits or tokens consumed. Often this is because of lack of control and foresight with LLM usage as adoption and usage grows. Often there are little to no guardrails or notifications built in to inform users on the degree of usage and consumption over time. Also, there are no guardrails for engineering teams building the AI native solutions for downstream end users.
