Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.
Mistake #1: Jumping In Too Early
At Inflection, we started by building a sourcing platform including agents, multiple data sources, and a graph database for modeling relationships. It showed some promising results, but didn’t deliver the value we were hoping for. The interesting companies surfaced by the tool? We were already talking to them. Growing the haystack didn’t help us find better needles.The valuation memos were a much smaller project. Our ops team compiled them by hand for the audit. Helping automate that work saved them time and gave us a chance to try out a few AI frameworks.
Finding the first useful project
When you’re hired to build technology, it’s easy to feel like the first few weeks only count if you ship something. Give yourself time to sit in on a deal. At Inflection, shadowing the partners showed us how much research was getting lost between conversations. That was the starting point for Kepler.Document what you see. Map out the current workflows, not the ones they told you about in the interview, but the ones you actually observed. Identify pain points. Document the current tools and data sources they’re using. Interview each team member individually. You’ll be surprised how different the story is when you talk to people one-on-one versus in a group setting.There’s one exception: if the fund is two people and has literally no technology at all, you may need to move faster. But even then, start small and specific. Build one thing that solves one problem. Then build the next thing.
Mistake #2: Not Aligning on Buy vs. Build Strategy
Here’s a nightmare scenario: You spend three months building a custom deal flow CRM. You’re proud of it. It’s tailored perfectly to the fund’s workflow. Then in a partner meeting, the managing partner casually mentions they’re also evaluating Affinity and Attio. Wait, what? Nobody told you they were considering buying software.Or the reverse happens. You do your homework, research the available tools, and propose using Affinity for deal flow management. The GPs look confused. They hired a “CTO.” They expected you to build something custom. They’re visibly disappointed that you want to buy instead of build.So when should you buy versus build? Commodity functionality should almost always be bought. CRM basics, email tracking, document signing. These are solved problems. Complex compliance requirements like fund administration and LP reporting should definitely be bought unless you have deep expertise and significant resources. Standard integrations with banks, DocuSign, and other services work better when you’re using established tools. If you’re a small team without significant engineering resources, buy more and build less. And if speed to value matters more than perfect fit, buying gets you there faster.Build when you have true differentiation. If your fund has a novel sourcing strategy or unique thesis that requires custom tooling, that’s worth building. Build when you have highly specific workflows that genuinely don’t map to existing tools (but be honest about whether they’re truly unique). Build when you have the engineering resources to maintain what you create. Build when you’ve actually tried existing tools and they’ve failed for specific, articulable reasons.There’s also a middle ground: build on top of bought software. Use vendor APIs to extend functionality. Build internal tools that integrate with external platforms. Create custom reporting and analytics on top of existing data. This often gives you the best of both worlds.Have the hard conversation early: “Here’s what exists that we could buy. Here’s what we’d need to build. Here’s the tradeoffs in terms of time, cost, and fit. What’s more important to you: speed or perfect fit?” Get this alignment before you write a single line of code or sign a single software contract.
Author Note: What not to build anymoreI’ve seen funds try to build custom CRMs, which used to be meaningful differentiation. But now you can get most features off the shelf with tools like Affinity or Attio. As a solo engineer or small team, I wouldn’t spend time building a new one from scratch.The same goes for data scraping. I’ve seen engineers spend weeks building LinkedIn scrapers. While that data is important, your time as an engineer is the most expensive resource. Don’t waste it when you can buy data from providers like People Data Labs, Crunchbase, or others. Build on top of purchased data, don’t recreate it.
Mistake #3: Not Having Enough Resources
Author Note: The evolving backlog at InflectionWhen we started building at Inflection, we had this huge backlog of products we thought we needed (you can find a lot of them in this list from before I was hired). If I was to execute on all these projects, I would always be context switching and stretched too thin. The key was constantly setting realistic priorities with the partnership, spelling out what it would actually take to build things, and forcing them to give feedback on what mattered most.Over time, many of those “critical” needs changed. The fund evolved. More importantly, more products became available to buy off the shelf. Half the backlog became irrelevant or solvable with purchased tools. Keep re-prioritizing based on what’s actually needed today, not what seemed important six months ago.
What one engineer can take on
You’re the only technical person at a five-person fund managing $50M. In your first week, you collect all the requests. They want a custom deal flow CRM. Portfolio tracking dashboards. Automated LP reporting. A public-facing fund website. Internal knowledge management. Data pipelines from five different sources. You write it all down. You start estimating.This is two to three years of work. Minimum. For one person.This happens because funds fundamentally underestimate software complexity. They don’t understand what goes into building and maintaining custom software. And honestly, you probably overestimate what you can ship alone too. You’re optimistic. You’re capable. You think you can move fast. Nobody scoped the work before hiring you. The interview focused on vision and potential, not realistic timelines. The “how hard can it be?” mentality prevails.Here’s what one technical person can realistically do: integrate and manage existing tools, build one or two custom internal tools (simple ones), automate some workflows, create custom reports and dashboards, and manage data infrastructure. That’s a full plate. That’s valuable work.Here’s what one technical person cannot do: build and maintain a full custom stack from scratch, replace Carta, Affinity, and DocuSign with custom-built alternatives, provide 24/7 support for critical systems, or keep up with every new request that comes in.You need to set expectations early. During the interview process, ask to see the list of desired projects. Ask about team size and budget for contractors or vendors. Be honest about what’s realistic. Discuss priorities: what actually comes first? In your first month, audit all the requested projects. Estimate time for each one generously (double your initial estimate, then add 50%). Show the math: “This is three years of work. I’m one person. Let’s talk about priorities.”Put the cost of maintaining what you’ve already shipped alongside the new requests. If a partner wants another custom tool, show them which piece of work would move back.
AI Makes Code Cheaper. You Still Own the System.
A partner sees you build a working prototype in an afternoon. The obvious question: “If AI can build this so quickly, why are we paying for all this software?”Separate a demo from a tool the fund can depend on. A demo might process one clean pitch deck. A dependable workflow needs to handle scanned PDFs, missing fields, failed requests, and corrections without quietly putting wrong numbers in the CRM. Faster coding doesn’t remove that work.It’s a fair question. AI coding tools make custom software worth considering for more problems. But generating the code is only part of the work. Someone still needs to understand the workflow, connect the data, handle permissions, check the output, deploy it, and fix it when an upstream API changes. You need to agree who owns each part. It doesn’t all have to be you.Make the distinction explicit: “I can show you a prototype this week. Before we rely on it, we need to test it against real documents, agree who checks the results, and budget time to support it.” When you compare that with a vendor’s price, count the time spent reviewing and maintaining the tool, model usage, data subscriptions, and what it costs the fund when the tool gets something wrong.
You Don’t Have to Build Every Application Yourself
Tools like Lovable and Claude Code open up another option: you maintain the shared infrastructure, while people across the fund build the applications they need. An investor builds a research dashboard. Someone in legal builds a document review workflow. Fund ops builds a reporting interface. They understand the work and can iterate on it directly.Your role changes. You provide reliable data, authentication, permissions, integrations, and a straightforward way to deploy. They own the workflow and decide whether the application is useful. You help them connect to the right systems and review what needs review before other people depend on it.Security makes this division of work possible. When an associate opens a partner’s app, the backend must enforce the associate’s access to each record and document. Build that into the shared infrastructure before connecting real fund data.Give people somewhere to experiment with sample data. When someone wants to share a useful prototype, you should already have a way to deploy it with authentication, logging, and a switch to revoke access. That’s the work the next person building a tool can reuse.Agree on ownership as the application grows. A personal research tool and a reporting workflow used by the whole fund need different levels of support. Before a prototype becomes part of the weekly process, decide who checks its output, handles failures, and maintains it if its creator moves on. Bring engineering into consequential changes, such as writing back to shared records or sending information externally.
Mistake #4: Over-Engineering for Scale You Don’t Have
Our initial sourcing tool at Inflection was set up on Kubernetes for workflow management, using Terraform. All the sins I told myself I wouldn’t commit. Over a week, we transitioned to Modal. We ended up saving ourselves a bunch of money on resources we didn’t need and had a much more reliable tool. Sometimes you need to catch yourself mid-over-engineering and course correct.For a deal tool serving twenty people, start with one application, Postgres, and a scheduled job. If a query gets slow, look at its execution plan before adding another service.Add complexity only when you have a specific problem. The database is slow? Add indexes and optimize queries. Deployments are risky? Add tests and CI/CD. The server goes down? Add monitoring and auto-restart. But don’t build complex caching because something “might be slow someday.” Build it when it’s actually slow today.
Mistake #5: Not Understanding Data Sensitivity and Compliance
When a partner asks to send meeting notes to a new service, follow one real note. Who supplied it? Who can read it today? Where will the transcript and summary end up? Ask ops or compliance which obligations apply. The security chapter covers how to enforce those decisions.Suppose an auditor asks for historical valuations with complete audit trails. You can’t produce it. Your system overwrites old values. Now you need both the original figure and a record of who changed it.In your first month, have explicit conversations: “What data can never leave our systems?” “What are our confidentiality obligations?” “What’s our risk tolerance around third-party tools?” “What audit requirements do we have?” Review the actual LP agreements. Understand the constraints, but also understand where there’s flexibility.At a larger firm, make time for the CISO and the internal IT team. Find out how they reviewed the last tool that handled similar data. That conversation is much easier before you build the integration.
Mistake #6: Building in a Vacuum
A great model I saw was having someone from the investment team act as a part-time “product manager” during major rollouts. They understood the workflows, could prioritize features, and gave real-time feedback. It’s a big ask, but even a few hours a week from the right person makes a huge difference.Show the person doing the work an early version with one of their own deals in it. Watch where they get stuck. It’s much cheaper to change the next iteration than to find out at rollout that the dashboard answers the wrong question.But internal tools need constant feedback. Partners are experts at investing, not at articulating product requirements. They think in terms of outcomes and workflows, not features and data models. Requirements evolve as they start using early versions and realize what actually matters in practice. Workflows evolve as the fund grows. Your initial understanding is always incomplete, no matter how many questions you asked.Create feedback loops. Weekly demos to the team. A Slack channel for feature requests. Regular one-on-ones with heavy users. Usage analytics showing what features actually get used. Embrace being wrong: “I built this based on what I thought you needed. What’s wrong with it?” “Here are three options. Which direction feels right?” “This is a prototype to test the concept.”
Mistake #7: Treating Investors Like Engineers
You’re in a partner meeting presenting your solution. “We’ll use a denormalized data model with materialized views for performance,” you explain. The partners nod politely. The conversation moves on quickly. You realize they’re not engaging with the technical details because those aren’t the details that matter to them.Or you sit down with a partner expecting them to write detailed requirements with acceptance criteria, like product managers do. They describe the outcome they want: “I want better deal tracking.” You ask for more specifics about fields and workflows. The conversation stalls. You’re speaking different languages.Investors think in outcomes, not implementations. “I want to see which deals are getting stale.” “I need to prepare for quarterly LP calls.” “I can’t remember who introduced this company.” The value is in solving the problem, not in how you solve it technically. They trust you to make the technical decisions.Translate technical decisions into business value. Don’t say “I’ll implement real-time sync with a WebSocket connection.” Say “The data will update immediately when anyone makes changes.” Show, don’t tell. Don’t explain the architecture. Show a working prototype. Let them experience the solution.Ask outcome-focused questions. Not “What fields should be in the Deal model?” Ask “What do you need to know about a deal to make a decision?” Their requirements come as business needs, not technical specifications. Extract requirements through conversation and observation. Build something, show it, refine it based on how they actually use it.This has been a big learning for me being the only engineer at Inflection: you need to wear the product hat, probably more than the engineering hat. Be really great at showing new features, but also explaining when and how to use them. Write documentation. Set metrics and follow up on those metrics. Kill what isn’t working.
{"docsConfig":{"theme":"mint","$schema":"https://mintlify.com/docs.json","name":"Building for VC","colors":{"primary":"#374151","light":"#4B5563","dark":"#1F2937"},"logo":{"light":"https://mintcdn.com/booleanindustries/LCnsVdhZ3wBnM9_T/logo/light.svg?fit=max\u0026auto=format\u0026n=LCnsVdhZ3wBnM9_T\u0026q=85\u0026s=a1deace3f3cb2b6fc6e4ae36635c8e6f","dark":"https://mintcdn.com/booleanindustries/LCnsVdhZ3wBnM9_T/logo/dark.svg?fit=max\u0026auto=format\u0026n=LCnsVdhZ3wBnM9_T\u0026q=85\u0026s=5d8ce5d533f8a5cd3095ce8f4f722cce"},"favicon":"https://mintcdn.com/booleanindustries/q7AnHl4KIucVa1OB/favicon.svg?fit=max\u0026auto=format\u0026n=q7AnHl4KIucVa1OB\u0026q=85\u0026s=e7f5334c214876513e6a8ee49bf13d48","navbar":{"links":[{"href":"https://github.com/alexpatow/building-for-vc","label":"GitHub"}]},"footer":{"socials":{"github":"https://github.com/alexpatow/building-for-vc"}},"seo":{"metatags":{"canonical":"https://buildingfor.vc","og:title":"Building for VC","og:description":"A technical guide to building technology for VC funds: from understanding the domain to shipping production systems.","twitter:card":"summary_large_image","twitter:title":"Building for VC","twitter:description":"A technical guide to building technology for VC funds: from understanding the domain to shipping production systems."},"indexing":"all"},"fonts":{"family":"Inter"},"contextual":{"options":["copy","view","chatgpt","claude","perplexity","mcp","cursor","vscode"],"display":"header"},"styling":{"latex":true},"navigation":{"pages":[]}},"deployment":{"deploymentMetadataValue":{"subdomain":"booleanindustries","hasAudioNarration":false,"actualSubdomain":"booleanindustries","customDomains":["buildingfor.vc"],"gitSource":{"type":"github","owner":"alexpatow","repo":"building-for-vc","deployBranch":"main","isPrivate":false,"contentDirectory":"","mountPath":"","label":""},"feedback":{"edits":true,"issues":true,"thumbs":true},"entitlements":{},"buildId":"6afb57b2b033735f822e3c16","clientVersion":"0.0.4271","searchFilterCounts":[{"language":"default","tag":"Guide","count":33},{"language":"default","tag":"Part 3: Technical Foundations","count":17},{"language":"default","tag":"Part 2: The VC Tech Stack","count":9},{"language":"default","tag":"Data Providers","count":8},{"language":"default","tag":"Part 1: Understanding VC","count":4},{"language":"default","tag":"Introduction","count":3}]},"assistantConfig":{"enableAskAiButton":false,"enableStarterQuestions":false,"enableAskAiSearchBar":true},"basePath":"","hasChatPermissions":false,"hasWebMcpPermissions":false,"toggles":[{"name":"kill-isr","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-rbac-roles","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-mintlify-slack","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"agent-integrations-settings","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"rbac-expansion","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-pr-grouping","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"custom-prefix","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"analytics-v7","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"user-flows-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"no-publish-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-onboarding","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving-live","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"stripTemperatureMiddleware","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"support-platform-pylon-zendesk","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"snapshot-serving","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"instant-rollback","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications-server","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"granular-notifications","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automations-fable","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fixed-ai-action-pricing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"site-roles","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"automation-resolve-merge-conflict","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"scoped-publishing","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"mintql","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"page-level-analytics","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-version-history-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"billing-page-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"full-page-search","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workspace-projects","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"assistant-v5","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"fork-pr-previews","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"revalidation-jwt","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-sso-scim","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"hobby-abuse-scan","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"dashboard-inbox","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-signup","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-dual-write","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"workos-enabled","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"approve-review-flow","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"editor-metadata","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"sso-setup-deadline-banner","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"turbopuffer-serve","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"live-agents","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"starter-pricing","enabled":true,"variant":{"name":"treatment","enabled":true,"payload":{"type":"string","value":"treatment"},"feature_enabled":true},"impressionData":false},{"name":"llms-txt-v2","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false},{"name":"wildcard-email-auth","enabled":true,"variant":{"name":"disabled","enabled":false,"feature_enabled":true},"impressionData":false}],"googleFontsInlined":false},"customCss":[]}
{"page":{"pagePath":"guide/part-1-understanding-vc/common-mistakes","slug":"/guide/part-1-understanding-vc/common-mistakes","pageMetadata":{"title":"Common Mistakes When Starting at a Fund","description":"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.","href":"/guide/part-1-understanding-vc/common-mistakes"},"description":{"compiledSource":"\"use strict\";\nconst {jsx: _jsx} = arguments[0];\nconst {useMDXComponents: _provideComponents} = arguments[0];\nfunction _createMdxContent(props) {\n const _components = {\n p: \"p\",\n ..._provideComponents(),\n ...props.components\n };\n return _jsx(_components.p, {\n children: \"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.\"\n });\n}\nfunction MDXContent(props = {}) {\n const {wrapper: MDXLayout} = {\n ..._provideComponents(),\n ...props.components\n };\n return MDXLayout ? _jsx(MDXLayout, {\n ...props,\n children: _jsx(_createMdxContent, {\n ...props\n })\n }) : _createMdxContent(props);\n}\nreturn {\n default: MDXContent\n};\n","frontmatter":{},"scope":{}},"pageType":"default","mdx":{"mdxSource":{"compiledSource":"\"use strict\";const{Fragment:_Fragment,jsx:_jsx,jsxs:_jsxs}=arguments[0];const{useMDXComponents:_provideComponents}=arguments[0];function _createMdxContent(props){const _components={a:`a`,p:`p`,strong:`strong`,..._provideComponents(),...props.components},{Heading,Tip}=_components;if(!Heading)_missingMdxReference(`Heading`,true);if(!Tip)_missingMdxReference(`Tip`,true);return _jsxs(_Fragment,{children:[_jsx(Heading,{level:`2`,id:`mistake-#1-jumping-in-too-early`,children:`Mistake #1: Jumping In Too Early`}),`\n`,_jsx(_components.p,{children:`At Inflection, we started by building a sourcing platform including agents, multiple data sources, and a graph database for modeling relationships. It showed some promising results, but didn’t deliver the value we were hoping for. The interesting companies surfaced by the tool? We were already talking to them. Growing the haystack didn’t help us find better needles.`}),`\n`,_jsx(_components.p,{children:`The valuation memos were a much smaller project. Our ops team compiled them by hand for the audit. Helping automate that work saved them time and gave us a chance to try out a few AI frameworks.`}),`\n`,_jsx(Heading,{level:`3`,id:`finding-the-first-useful-project`,children:`Finding the first useful project`}),`\n`,_jsxs(_components.p,{children:[`When you’re hired to build technology, it’s easy to feel like the first few weeks only count if you ship something. Give yourself time to sit in on a deal. At Inflection, shadowing the partners showed us how much research was getting lost between conversations. That was the starting point for `,_jsx(_components.a,{href:`/guide/part-2-tech-stack/research-platforms`,children:`Kepler`}),`.`]}),`\n`,_jsx(_components.p,{children:`Document what you see. Map out the current workflows, not the ones they told you about in the interview, but the ones you actually observed. Identify pain points. Document the current tools and data sources they’re using. Interview each team member individually. You’ll be surprised how different the story is when you talk to people one-on-one versus in a group setting.`}),`\n`,_jsx(_components.p,{children:`There’s one exception: if the fund is two people and has literally no technology at all, you may need to move faster. But even then, start small and specific. Build one thing that solves one problem. Then build the next thing.`}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#2-not-aligning-on-buy-vs-build-strategy`,children:`Mistake #2: Not Aligning on Buy vs. Build Strategy`}),`\n`,_jsx(_components.p,{children:`Here’s a nightmare scenario: You spend three months building a custom deal flow CRM. You’re proud of it. It’s tailored perfectly to the fund’s workflow. Then in a partner meeting, the managing partner casually mentions they’re also evaluating Affinity and Attio. Wait, what? Nobody told you they were considering buying software.`}),`\n`,_jsx(_components.p,{children:`Or the reverse happens. You do your homework, research the available tools, and propose using Affinity for deal flow management. The GPs look confused. They hired a “CTO.” They expected you to build something custom. They’re visibly disappointed that you want to buy instead of build.`}),`\n`,_jsx(_components.p,{children:`So when should you buy versus build? Commodity functionality should almost always be bought. CRM basics, email tracking, document signing. These are solved problems. Complex compliance requirements like fund administration and LP reporting should definitely be bought unless you have deep expertise and significant resources. Standard integrations with banks, DocuSign, and other services work better when you’re using established tools. If you’re a small team without significant engineering resources, buy more and build less. And if speed to value matters more than perfect fit, buying gets you there faster.`}),`\n`,_jsx(_components.p,{children:`Build when you have true differentiation. If your fund has a novel sourcing strategy or unique thesis that requires custom tooling, that’s worth building. Build when you have highly specific workflows that genuinely don’t map to existing tools (but be honest about whether they’re truly unique). Build when you have the engineering resources to maintain what you create. Build when you’ve actually tried existing tools and they’ve failed for specific, articulable reasons.`}),`\n`,_jsx(_components.p,{children:`There’s also a middle ground: build on top of bought software. Use vendor APIs to extend functionality. Build internal tools that integrate with external platforms. Create custom reporting and analytics on top of existing data. This often gives you the best of both worlds.`}),`\n`,_jsx(_components.p,{children:`Have the hard conversation early: “Here’s what exists that we could buy. Here’s what we’d need to build. Here’s the tradeoffs in terms of time, cost, and fit. What’s more important to you: speed or perfect fit?” Get this alignment before you write a single line of code or sign a single software contract.`}),`\n`,_jsxs(Tip,{children:[_jsx(_components.p,{children:_jsx(_components.strong,{children:`Author Note: What not to build anymore`})}),_jsx(_components.p,{children:`I’ve seen funds try to build custom CRMs, which used to be meaningful differentiation. But now you can get most features off the shelf with tools like Affinity or Attio. As a solo engineer or small team, I wouldn’t spend time building a new one from scratch.`}),_jsxs(_components.p,{children:[`The same goes for data scraping. I’ve seen engineers spend weeks building LinkedIn scrapers. While that data is important, your time as an engineer is the most expensive resource. Don’t waste it when you can buy data from providers like `,_jsx(_components.a,{href:`https://peopledatalabs.com/`,children:`People Data Labs`}),`, `,_jsx(_components.a,{href:`https://www.crunchbase.com/`,children:`Crunchbase`}),`, or others. Build on top of purchased data, don’t recreate it.`]})]}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#3-not-having-enough-resources`,children:`Mistake #3: Not Having Enough Resources`}),`\n`,_jsxs(Tip,{children:[_jsx(_components.p,{children:_jsx(_components.strong,{children:`Author Note: The evolving backlog at Inflection`})}),_jsxs(_components.p,{children:[`When we started building at Inflection, we had this huge backlog of products we thought we needed (you can `,_jsx(_components.a,{href:`https://svrgn.substack.com/p/an-engineering-approach-to-venture`,children:`find a lot of them in this list`}),` from before I was hired). If I was to execute on all these projects, I would always be context switching and stretched too thin. The key was constantly setting realistic priorities with the partnership, spelling out what it would actually take to build things, and forcing them to give feedback on what mattered most.`]}),_jsx(_components.p,{children:`Over time, many of those “critical” needs changed. The fund evolved. More importantly, more products became available to buy off the shelf. Half the backlog became irrelevant or solvable with purchased tools. Keep re-prioritizing based on what’s actually needed today, not what seemed important six months ago.`})]}),`\n`,_jsx(Heading,{level:`3`,id:`what-one-engineer-can-take-on`,children:`What one engineer can take on`}),`\n`,_jsx(_components.p,{children:`You’re the only technical person at a five-person fund managing $50M. In your first week, you collect all the requests. They want a custom deal flow CRM. Portfolio tracking dashboards. Automated LP reporting. A public-facing fund website. Internal knowledge management. Data pipelines from five different sources. You write it all down. You start estimating.`}),`\n`,_jsx(_components.p,{children:`This is two to three years of work. Minimum. For one person.`}),`\n`,_jsx(_components.p,{children:`This happens because funds fundamentally underestimate software complexity. They don’t understand what goes into building and maintaining custom software. And honestly, you probably overestimate what you can ship alone too. You’re optimistic. You’re capable. You think you can move fast. Nobody scoped the work before hiring you. The interview focused on vision and potential, not realistic timelines. The “how hard can it be?” mentality prevails.`}),`\n`,_jsx(_components.p,{children:`Here’s what one technical person can realistically do: integrate and manage existing tools, build one or two custom internal tools (simple ones), automate some workflows, create custom reports and dashboards, and manage data infrastructure. That’s a full plate. That’s valuable work.`}),`\n`,_jsx(_components.p,{children:`Here’s what one technical person cannot do: build and maintain a full custom stack from scratch, replace Carta, Affinity, and DocuSign with custom-built alternatives, provide 24/7 support for critical systems, or keep up with every new request that comes in.`}),`\n`,_jsx(_components.p,{children:`You need to set expectations early. During the interview process, ask to see the list of desired projects. Ask about team size and budget for contractors or vendors. Be honest about what’s realistic. Discuss priorities: what actually comes first? In your first month, audit all the requested projects. Estimate time for each one generously (double your initial estimate, then add 50%). Show the math: “This is three years of work. I’m one person. Let’s talk about priorities.”`}),`\n`,_jsx(_components.p,{children:`Put the cost of maintaining what you’ve already shipped alongside the new requests. If a partner wants another custom tool, show them which piece of work would move back.`}),`\n`,_jsx(Heading,{level:`3`,id:`ai-makes-code-cheaper-you-still-own-the-system`,children:`AI Makes Code Cheaper. You Still Own the System.`}),`\n`,_jsx(_components.p,{children:`A partner sees you build a working prototype in an afternoon. The obvious question: “If AI can build this so quickly, why are we paying for all this software?”`}),`\n`,_jsx(_components.p,{children:`Separate a demo from a tool the fund can depend on. A demo might process one clean pitch deck. A dependable workflow needs to handle scanned PDFs, missing fields, failed requests, and corrections without quietly putting wrong numbers in the CRM. Faster coding doesn’t remove that work.`}),`\n`,_jsx(_components.p,{children:`It’s a fair question. AI coding tools make custom software worth considering for more problems. But generating the code is only part of the work. Someone still needs to understand the workflow, connect the data, handle permissions, check the output, deploy it, and fix it when an upstream API changes. You need to agree who owns each part. It doesn’t all have to be you.`}),`\n`,_jsx(_components.p,{children:`Make the distinction explicit: “I can show you a prototype this week. Before we rely on it, we need to test it against real documents, agree who checks the results, and budget time to support it.” When you compare that with a vendor’s price, count the time spent reviewing and maintaining the tool, model usage, data subscriptions, and what it costs the fund when the tool gets something wrong.`}),`\n`,_jsx(Heading,{level:`3`,id:`you-don’t-have-to-build-every-application-yourself`,children:`You Don’t Have to Build Every Application Yourself`}),`\n`,_jsxs(_components.p,{children:[`Tools like `,_jsx(_components.a,{href:`https://lovable.dev/`,children:`Lovable`}),` and `,_jsx(_components.a,{href:`https://code.claude.com/docs/en/overview`,children:`Claude Code`}),` open up another option: you maintain the shared infrastructure, while people across the fund build the applications they need. An investor builds a research dashboard. Someone in legal builds a document review workflow. Fund ops builds a reporting interface. They understand the work and can iterate on it directly.`]}),`\n`,_jsx(_components.p,{children:`Your role changes. You provide reliable data, authentication, permissions, integrations, and a straightforward way to deploy. They own the workflow and decide whether the application is useful. You help them connect to the right systems and review what needs review before other people depend on it.`}),`\n`,_jsxs(_components.p,{children:[`Security makes this division of work possible. When an associate opens a partner’s app, the backend must enforce the associate’s access to each record and document. Build that into the `,_jsx(_components.a,{href:`/guide/part-3-technical-foundations/security-and-compliance`,children:`shared infrastructure`}),` before connecting real fund data.`]}),`\n`,_jsx(_components.p,{children:`Give people somewhere to experiment with sample data. When someone wants to share a useful prototype, you should already have a way to deploy it with authentication, logging, and a switch to revoke access. That’s the work the next person building a tool can reuse.`}),`\n`,_jsx(_components.p,{children:`Agree on ownership as the application grows. A personal research tool and a reporting workflow used by the whole fund need different levels of support. Before a prototype becomes part of the weekly process, decide who checks its output, handles failures, and maintains it if its creator moves on. Bring engineering into consequential changes, such as writing back to shared records or sending information externally.`}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#4-over-engineering-for-scale-you-don’t-have`,children:`Mistake #4: Over-Engineering for Scale You Don’t Have`}),`\n`,_jsxs(_components.p,{children:[`Our initial sourcing tool at Inflection was set up on Kubernetes for workflow management, using Terraform. All the sins I told myself I wouldn’t commit. Over a week, we transitioned to `,_jsx(_components.a,{href:`https://modal.com/`,children:`Modal`}),`. We ended up saving ourselves a bunch of money on resources we didn’t need and had a much more reliable tool. Sometimes you need to catch yourself mid-over-engineering and course correct.`]}),`\n`,_jsx(_components.p,{children:`For a deal tool serving twenty people, start with one application, Postgres, and a scheduled job. If a query gets slow, look at its execution plan before adding another service.`}),`\n`,_jsx(_components.p,{children:`Add complexity only when you have a specific problem. The database is slow? Add indexes and optimize queries. Deployments are risky? Add tests and CI/CD. The server goes down? Add monitoring and auto-restart. But don’t build complex caching because something “might be slow someday.” Build it when it’s actually slow today.`}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#5-not-understanding-data-sensitivity-and-compliance`,children:`Mistake #5: Not Understanding Data Sensitivity and Compliance`}),`\n`,_jsxs(_components.p,{children:[`When a partner asks to send meeting notes to a new service, follow one real note. Who supplied it? Who can read it today? Where will the transcript and summary end up? Ask ops or compliance which obligations apply. The `,_jsx(_components.a,{href:`/guide/part-3-technical-foundations/security-and-compliance`,children:`security chapter`}),` covers how to enforce those decisions.`]}),`\n`,_jsx(_components.p,{children:`Suppose an auditor asks for historical valuations with complete audit trails. You can’t produce it. Your system overwrites old values. Now you need both the original figure and a record of who changed it.`}),`\n`,_jsx(_components.p,{children:`In your first month, have explicit conversations: “What data can never leave our systems?” “What are our confidentiality obligations?” “What’s our risk tolerance around third-party tools?” “What audit requirements do we have?” Review the actual LP agreements. Understand the constraints, but also understand where there’s flexibility.`}),`\n`,_jsx(_components.p,{children:`At a larger firm, make time for the CISO and the internal IT team. Find out how they reviewed the last tool that handled similar data. That conversation is much easier before you build the integration.`}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#6-building-in-a-vacuum`,children:`Mistake #6: Building in a Vacuum`}),`\n`,_jsx(_components.p,{children:`A great model I saw was having someone from the investment team act as a part-time “product manager” during major rollouts. They understood the workflows, could prioritize features, and gave real-time feedback. It’s a big ask, but even a few hours a week from the right person makes a huge difference.`}),`\n`,_jsx(_components.p,{children:`Show the person doing the work an early version with one of their own deals in it. Watch where they get stuck. It’s much cheaper to change the next iteration than to find out at rollout that the dashboard answers the wrong question.`}),`\n`,_jsx(_components.p,{children:`But internal tools need constant feedback. Partners are experts at investing, not at articulating product requirements. They think in terms of outcomes and workflows, not features and data models. Requirements evolve as they start using early versions and realize what actually matters in practice. Workflows evolve as the fund grows. Your initial understanding is always incomplete, no matter how many questions you asked.`}),`\n`,_jsx(_components.p,{children:`Create feedback loops. Weekly demos to the team. A Slack channel for feature requests. Regular one-on-ones with heavy users. Usage analytics showing what features actually get used. Embrace being wrong: “I built this based on what I thought you needed. What’s wrong with it?” “Here are three options. Which direction feels right?” “This is a prototype to test the concept.”`}),`\n`,_jsx(Heading,{level:`2`,id:`mistake-#7-treating-investors-like-engineers`,children:`Mistake #7: Treating Investors Like Engineers`}),`\n`,_jsx(_components.p,{children:`You’re in a partner meeting presenting your solution. “We’ll use a denormalized data model with materialized views for performance,” you explain. The partners nod politely. The conversation moves on quickly. You realize they’re not engaging with the technical details because those aren’t the details that matter to them.`}),`\n`,_jsx(_components.p,{children:`Or you sit down with a partner expecting them to write detailed requirements with acceptance criteria, like product managers do. They describe the outcome they want: “I want better deal tracking.” You ask for more specifics about fields and workflows. The conversation stalls. You’re speaking different languages.`}),`\n`,_jsx(_components.p,{children:`Investors think in outcomes, not implementations. “I want to see which deals are getting stale.” “I need to prepare for quarterly LP calls.” “I can’t remember who introduced this company.” The value is in solving the problem, not in how you solve it technically. They trust you to make the technical decisions.`}),`\n`,_jsx(_components.p,{children:`Translate technical decisions into business value. Don’t say “I’ll implement real-time sync with a WebSocket connection.” Say “The data will update immediately when anyone makes changes.” Show, don’t tell. Don’t explain the architecture. Show a working prototype. Let them experience the solution.`}),`\n`,_jsx(_components.p,{children:`Ask outcome-focused questions. Not “What fields should be in the Deal model?” Ask “What do you need to know about a deal to make a decision?” Their requirements come as business needs, not technical specifications. Extract requirements through conversation and observation. Build something, show it, refine it based on how they actually use it.`}),`\n`,_jsx(_components.p,{children:`This has been a big learning for me being the only engineer at Inflection: you need to wear the product hat, probably more than the engineering hat. Be really great at showing new features, but also explaining when and how to use them. Write documentation. Set metrics and follow up on those metrics. Kill what isn’t working.`})]})}function MDXContent(props={}){const{wrapper:MDXLayout}={..._provideComponents(),...props.components};return MDXLayout?_jsx(MDXLayout,{...props,children:_jsx(_createMdxContent,{...props})}):_createMdxContent(props)}return{default:MDXContent};function _missingMdxReference(id,component){throw new Error(`Expected `+(component?`component`:`object`)+\" `\"+id+\"` to be defined: you likely forgot to import, pass, or provide it.\")}","frontmatter":{},"scope":{"config":{},"pageMetadata":{"title":"Common Mistakes When Starting at a Fund","description":"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.","href":"/guide/part-1-understanding-vc/common-mistakes"}}},"mdxSourceWithNoJs":null},"mdxExtracts":{"tableOfContents":[{"title":"Mistake #1: Jumping In Too Early","slug":"mistake-#1-jumping-in-too-early","depth":2,"children":[{"title":"Finding the first useful project","slug":"finding-the-first-useful-project","depth":3,"children":[]}]},{"title":"Mistake #2: Not Aligning on Buy vs. Build Strategy","slug":"mistake-#2-not-aligning-on-buy-vs-build-strategy","depth":2,"children":[]},{"title":"Mistake #3: Not Having Enough Resources","slug":"mistake-#3-not-having-enough-resources","depth":2,"children":[{"title":"What one engineer can take on","slug":"what-one-engineer-can-take-on","depth":3,"children":[]},{"title":"AI Makes Code Cheaper. You Still Own the System.","slug":"ai-makes-code-cheaper-you-still-own-the-system","depth":3,"children":[]},{"title":"You Don’t Have to Build Every Application Yourself","slug":"you-don’t-have-to-build-every-application-yourself","depth":3,"children":[]}]},{"title":"Mistake #4: Over-Engineering for Scale You Don’t Have","slug":"mistake-#4-over-engineering-for-scale-you-don’t-have","depth":2,"children":[]},{"title":"Mistake #5: Not Understanding Data Sensitivity and Compliance","slug":"mistake-#5-not-understanding-data-sensitivity-and-compliance","depth":2,"children":[]},{"title":"Mistake #6: Building in a Vacuum","slug":"mistake-#6-building-in-a-vacuum","depth":2,"children":[]},{"title":"Mistake #7: Treating Investors Like Engineers","slug":"mistake-#7-treating-investors-like-engineers","depth":2,"children":[]}],"codeExamples":{}},"jsLinks":[],"subdomain":"booleanindustries","siteName":"Building for VC","title":"Building for VC","navMaps":{"firstHrefInVersion":{},"firstHrefInLanguage":{}},"lastModified":"2026-11-16T19:21:26.268Z","originalFileLocation":"guide/part-1-understanding-vc/common-mistakes.mdx"},"headHtml":"\u003cscript data-mint-head>(function(){var d=document.documentElement,p=null;if(!p){try{p=localStorage.getItem(\"isDarkMode\")}catch(e){}if(p==='true')p='dark';else if(p==='false')p='light';if(p!=='light'\u0026\u0026p!=='dark'\u0026\u0026p!=='system')p=\"system\"}var r=p==='system'?(matchMedia(\"(prefers-color-scheme: dark)\").matches?'dark':'light'):p;d.classList.remove(r==='dark'?'light':'dark');d.classList.add(r);d.setAttribute(\"data-theme-preference\",p)})();\u003c/script>\u003cmeta data-mint-head name=\"description\" content=\"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.\">\u003cmeta data-mint-head name=\"application-name\" content=\"Building for VC\">\u003cmeta data-mint-head name=\"generator\" content=\"Mintlify\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/android-chrome-192x192.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"apple-touch-icon\" type=\"image/png\" sizes=\"180x180\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/apple-touch-icon.png\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/favicon-16x16.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/favicon-32x32.png\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/favicon.ico\" media=\"(prefers-color-scheme: light)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"192x192\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon-dark/android-chrome-192x192.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"16x16\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon-dark/favicon-16x16.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"icon\" type=\"image/png\" sizes=\"32x32\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon-dark/favicon-32x32.png\" media=\"(prefers-color-scheme: dark)\">\u003clink data-mint-head rel=\"shortcut icon\" type=\"image/x-icon\" href=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon-dark/favicon.ico\" media=\"(prefers-color-scheme: dark)\">\u003cmeta data-mint-head property=\"og:title\" content=\"Building for VC\">\u003cmeta data-mint-head property=\"og:description\" content=\"A technical guide to building technology for VC funds: from understanding the domain to shipping production systems.\">\u003cmeta data-mint-head property=\"og:site_name\" content=\"Building for VC\">\u003cmeta data-mint-head property=\"og:url\" content=\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes\">\u003cmeta data-mint-head property=\"og:type\" content=\"website\">\u003cmeta data-mint-head property=\"og:image\" content=\"https://booleanindustries.mintlify.site/_mintlify/api/og/v2?division=Part+1%3A+Understanding+VC\u0026amp;title=Common+Mistakes+When+Starting+at+a+Fund\u0026amp;description=Learn+the+seven+common+mistakes+developers+make+when+joining+VC+funds+and+how+to+avoid+them+before+they+cost+you+months+of+work.\u0026amp;theme=6cc8b5eb4b2c211fc542f4e8\u0026amp;signature=9b99997d378b908d8c95dd4231e2589198698e20eef7cf1cd1dffbd30ac7f8bf\">\u003cmeta data-mint-head property=\"og:image:width\" content=\"1200\">\u003cmeta data-mint-head property=\"og:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"twitter:card\" content=\"summary_large_image\">\u003cmeta data-mint-head name=\"twitter:title\" content=\"Building for VC\">\u003cmeta data-mint-head name=\"twitter:description\" content=\"A technical guide to building technology for VC funds: from understanding the domain to shipping production systems.\">\u003cmeta data-mint-head name=\"twitter:image\" content=\"https://booleanindustries.mintlify.site/_mintlify/api/og/v2?division=Part+1%3A+Understanding+VC\u0026amp;title=Common+Mistakes+When+Starting+at+a+Fund\u0026amp;description=Learn+the+seven+common+mistakes+developers+make+when+joining+VC+funds+and+how+to+avoid+them+before+they+cost+you+months+of+work.\u0026amp;theme=6cc8b5eb4b2c211fc542f4e8\u0026amp;signature=9b99997d378b908d8c95dd4231e2589198698e20eef7cf1cd1dffbd30ac7f8bf\">\u003cmeta data-mint-head name=\"twitter:image:width\" content=\"1200\">\u003cmeta data-mint-head name=\"twitter:image:height\" content=\"630\">\u003cmeta data-mint-head name=\"msapplication-config\" content=\"/mintlify-assets/_mintlify/favicons/booleanindustries/Xan3p51zjaxYbcQS/_generated/favicon/browserconfig.xml\">\u003cmeta data-mint-head name=\"apple-mobile-web-app-title\" content=\"Building for VC\">\u003cmeta data-mint-head name=\"msapplication-TileColor\" content=\"#374151\">\u003clink data-mint-head rel=\"canonical\" href=\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes\">\u003clink data-mint-head rel=\"alternate\" type=\"application/xml\" href=\"/sitemap.xml\">\u003clink data-mint-head rel=\"alternate\" type=\"text/markdown\" href=\"/guide/part-1-understanding-vc/common-mistakes.md\">\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https://buildingfor.vc/#organization\",\"name\":\"Building for VC\",\"url\":\"https://buildingfor.vc\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https://mintcdn.com/booleanindustries/LCnsVdhZ3wBnM9_T/logo/light.svg?fit=max\u0026auto=format\u0026n=LCnsVdhZ3wBnM9_T\u0026q=85\u0026s=a1deace3f3cb2b6fc6e4ae36635c8e6f\"}},{\"@type\":\"WebSite\",\"@id\":\"https://buildingfor.vc#website\",\"name\":\"Building for VC\",\"url\":\"https://buildingfor.vc\",\"publisher\":{\"@id\":\"https://buildingfor.vc/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes#webpage\",\"url\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes\",\"name\":\"Common Mistakes When Starting at a Fund\",\"description\":\"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.\",\"dateModified\":\"2026-11-16T19:21:26.268Z\",\"isPartOf\":{\"@id\":\"https://buildingfor.vc#website\"},\"breadcrumb\":{\"@id\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes#breadcrumb\"}},{\"@type\":\"BreadcrumbList\",\"@id\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Part 1: Understanding VC\",\"item\":\"https://buildingfor.vc/guide/part-1-understanding-vc/what-is-a-vc-fund\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Common Mistakes When Starting at a Fund\",\"item\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes\"}]},{\"@type\":[\"Article\",\"TechArticle\"],\"@id\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes#article\",\"headline\":\"Common Mistakes When Starting at a Fund\",\"name\":\"Common Mistakes When Starting at a Fund\",\"description\":\"Learn the seven common mistakes developers make when joining VC funds and how to avoid them before they cost you months of work.\",\"url\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes\",\"mainEntityOfPage\":{\"@id\":\"https://buildingfor.vc/guide/part-1-understanding-vc/common-mistakes#webpage\"},\"dateModified\":\"2026-11-16T19:21:26.268Z\",\"publisher\":{\"@id\":\"https://buildingfor.vc/#organization\"},\"isPartOf\":{\"@id\":\"https://buildingfor.vc#website\"}}]}\u003c/script>\u003cscript data-mint-head type=\"application/ld+json\">{\"@context\":\"https://schema.org\",\"@type\":\"WebSite\",\"name\":\"Building for VC\",\"publisher\":{\"@type\":\"Organization\",\"name\":\"Building for VC\"},\"provider\":{\"@type\":\"Organization\",\"name\":\"Mintlify\",\"url\":\"https://mintlify.com\"}}\u003c/script>","agentPointerHref":"/guide/part-1-understanding-vc/common-mistakes.md","siteName":"Building for VC","nav":{"global":null,"tabs":[{"tab":"Guide","icon":"book-open","groups":[{"group":"Introduction","pages":[{"title":"Building for Venture Capital","href":"/guide"},{"title":"Quick Reference","href":"/guide/quickstart"},{"title":"Contributors","href":"/guide/contributors"}]},{"group":"Part 1: Understanding VC","pages":[{"title":"What is a VC Fund?","href":"/guide/part-1-understanding-vc/what-is-a-vc-fund"},{"title":"Understanding Your VC Fund","description":"Learn how to analyze your specific fund's stage, strategy, and workflows to build the right technical solutions.","href":"/guide/part-1-understanding-vc/understanding-your-vc-fund"},{"title":"Common Mistakes When Starting at a Fund","href":"/guide/part-1-understanding-vc/common-mistakes"},{"title":"Hiring Your Data Team","description":"When to hire your first data person, what to look for, and how the team evolves.","href":"/guide/part-1-understanding-vc/hiring-your-data-team"}]},{"group":"Part 2: The VC Tech Stack","pages":[{"title":"Introduction to the VC Tech Stack","href":"/guide/part-2-tech-stack/introduction"},{"title":"Research Platforms","href":"/guide/part-2-tech-stack/research-platforms"},{"title":"Sourcing Tools","href":"/guide/part-2-tech-stack/sourcing-tools"},{"title":"CRM and Deal Flow Management","href":"/guide/part-2-tech-stack/crm-and-deal-flow"},{"title":"Fund Operations","href":"/guide/part-2-tech-stack/fund-operations"},{"title":"Portfolio Support","href":"/guide/part-2-tech-stack/portfolio-support"},{"title":"Fundraising","href":"/guide/part-2-tech-stack/fundraising"},{"title":"Website and External Presence","href":"/guide/part-2-tech-stack/website-and-external-presence"},{"title":"Putting It Together","href":"/guide/part-2-tech-stack/putting-it-together"}]},{"group":"Part 3: Technical Foundations","pages":[{"title":"Choosing Your Technology Stack","href":"/guide/part-3-technical-foundations/choosing-your-stack"},{"group":"Data Providers","pages":[{"title":"Data Providers","href":"/guide/part-3-technical-foundations/data-providers/index"},{"title":"Data Starter Kits","href":"/guide/part-3-technical-foundations/data-providers/starter-kits"},{"title":"Accessing Data","href":"/guide/part-3-technical-foundations/data-providers/accessing-data"},{"title":"Company Data Providers","href":"/guide/part-3-technical-foundations/data-providers/company-data"},{"title":"Signal Data Providers","href":"/guide/part-3-technical-foundations/data-providers/signal-data"},{"title":"People Data Providers","href":"/guide/part-3-technical-foundations/data-providers/people-data"},{"title":"Other Data Providers","href":"/guide/part-3-technical-foundations/data-providers/other-data"},{"title":"Data Provider Considerations","href":"/guide/part-3-technical-foundations/data-providers/considerations"}]},{"title":"Data Modeling for Venture Capital","href":"/guide/part-3-technical-foundations/data-modeling"},{"title":"Entity Resolution","href":"/guide/part-3-technical-foundations/entity-resolution"},{"title":"Data Quality and Validation","href":"/guide/part-3-technical-foundations/data-quality"},{"title":"Data Warehousing and Analytics","href":"/guide/part-3-technical-foundations/data-warehousing"},{"title":"Knowledge Graphs","href":"/guide/part-3-technical-foundations/knowledge-graphs"},{"title":"Integrations","href":"/guide/part-3-technical-foundations/integrations-and-apis"},{"title":"Security and Compliance","href":"/guide/part-3-technical-foundations/security-and-compliance"},{"title":"Emerging Trends","href":"/guide/part-3-technical-foundations/emerging-trends"}]}]}]},"basePath":"","title":"Building for VC","deploymentId":"dpl_Em2U4NQQ2N2DE3HPbPUJVZLnAtvc","buildId":"dpl_Em2U4NQQ2N2DE3HPbPUJVZLnAtvc","dynamics":[],"chunks":[]}