If you’ve read our R&D Venture Studio Playbook, you already know that we’re obsessed with turning breakthrough research into impactful ventures. In our last series of posts, we explored why and how to build an R&D venture studio — the opportunities, the mechanics, and the process we’ve honed through years inside MIT’s research ecosystem.
This new series is about something different: the hard parts.
Over the next six posts, we’ll dive into the real challenges every R&D venture studio will face — from hiring elite venture builders to bridging the technology readiness gap — and share the best practices we’ve learned (sometimes the hard way) for overcoming them.
Note: Today’s post is free to all readers. Some of the future posts in this mini-series will be available exclusively for paid subscribers.
Every R&D venture studio lives and dies by who it hires to build its ventures. At MIT Proto Ventures, that role is the Venture Builder — a unique hybrid of technical expert, startup founder, and investor. The VB isn’t just another member of the team. They are the engine of venture creation.
They’re embedded in the labs, spotting latent opportunities. They’re in investor meetings, translating scientific breakthroughs into investable narratives. They’re the ones connecting dots between researchers who might never have met — and between ideas that might never have collided — without them.
When you get the VB hire right, the whole studio accelerates. Get it wrong, and the most promising technology in the world will sit on the shelf.
Early on, we made the same mistake we’ve seen in other venture studios: trying to hire VBs at postdoc-level salaries.
On paper, this seemed reasonable — after all, our candidates had PhDs, deep technical expertise, and experience in research environments. But the reality? Anyone with the skills to be an effective VB could make significantly more elsewhere, often with less risk and more stability. Our salary range sent an unspoken signal: this is an operational role, not a founder’s role.
As a result, we received very few qualified applications. The ones we did get often lacked the entrepreneurial drive we needed.
The fix was simple but essential: we adjusted the compensation to be competitive with a venture capital associate role, not an academic postdoc. Immediately, the pipeline changed. We started attracting candidates who had not only the technical chops but also the founder mindset — people motivated by the chance to build something world-changing.
Salary alone isn’t enough. If you want someone to pour their heart and soul into building a venture, they need a reason beyond a paycheck.
That’s why at MIT Proto Ventures, we structured the role so that we take no equity in the resulting ventures. The VB becomes a true founder, with the same upside as if they had discovered the opportunity on their own.
This was instrumental in recruiting our strongest VBs — and it’s a stark contrast to many private venture studios, which take substantial equity and can leave capitalization tables “broken” from the start. In those cases, outside investors often shy away, and talented founders think twice before joining.
A Venture Builder should be building — scouting tech, validating markets, assembling founding teams, and shaping ventures. To make that possible, we’ve learned to surround them with support:
Advisory boards with both internal and external experts.
Operational help for event planning, legal, and IP reviews.
A finite time horizon (two years), which keeps the sense of urgency high.
By keeping the VB focused on high-value activities — and by making the role a stepping stone to founding their own company — you create the conditions for exceptional talent to thrive.
If you’re building your own R&D venture studio:
Pay for what you want to attract. If you want founder-caliber talent, compensate accordingly.
Align incentives with venture success. Give VBs real ownership opportunities.
Support, don’t distract. Free them from operational drag so they can focus on high-leverage work.
Set a clock. A finite term sharpens focus and signals that this is a launchpad, not a career desk.
Get this right, and you’ll have a team capable of finding and building the ventures that no one else could.
In the next post (for paid subscribers), we’ll tackle the CTO Conundrum:
What do you do when the perfect founding technical lead is still in the lab — and doesn’t want to leave?
We’ll share the strategies we’ve used to bridge that gap and successfully recruit founding technical talent for deep tech ventures.
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.