I’ve spent the last five years building technology for VC funds, first at EQT as part of the Motherbrain platform, now the past two years at Inflection where I’ve built our core infrastructure with the help and guidance of Alexander Lange and Jonatan Luther-Bergquist.
Along the way, I’ve noticed a recurring pattern: most engineers joining VC come from the outside, and there’s no real onboarding guide for the role.
They’re talented people who haven’t worked in venture capital before, don’t yet know how funds operate, and often spend their early months figuring out the basics: what data matters, what tools exist, where to focus first. I was one of them back in the day.
So I wrote the guide I wish I’d had: Building for Venture Capital.
What It Covers
The guide is organized into three parts:
How venture capital funds actually work, from the perspective of someone building technology for them. Fund structures, LP relationships, investment processes, and the common mistakes technical hires make when they don’t understand the domain.
A tour of the tools and systems VC funds use: research platforms, sourcing tools, CRM and deal flow, fund operations, portfolio support, fundraising, and external presence. For each category, I cover what the tool does, when to build vs. buy, and real examples from working funds.
The deeper technical work: choosing your technology stack, working with data providers, data modeling for VC, entity resolution, data quality, warehousing, integrations, security and compliance, and emerging trends like MCP and AI agent orchestration.
There’s also a resources section with curated newsletters, books, research papers, and a prompt bank for common VC workflows.
Why Open Source?
At Inflection, we believe the VC industry benefits when funds share knowledge about how technology is shaping the way we operate. Too often, this expertise stays siloed within individual firms. By publishing this guide, we want to create more conversation about how new technologies are changing what's possible for VC funds of all sizes.
The whole thing is on GitHub. If something’s wrong or missing, you can open an issue or submit a PR. If you’ve got prompts, resources, or perspectives that would help others, contributions are more than welcome.
Acknowledgments
This wouldn’t exist without the people I’ve worked with at Inflection and EQT who shaped how I think about this work. Special thanks to the external contributors who shared their perspectives.
Check it out at buildingfor.vc. Feedback welcome.
// AP