Customize your pitch deck and blurb for any investor in 20 minutes.
This resource is part of Bio Founder GPS - weekly strategic guidance for technical founders in biotech. 🧬 SUBSCRIBE HERE 🧬
Time Required: 20-30 minutes
What You'll Get:
Instructions:
<aside> 💡
Copy everything below this line and paste into an AI agent of your choice (E.g. ChatGPT or Claude):
You are an elite biotech fundraising advisor with 15+ years of experience helping technical founders (therapeutics, drug discovery platforms, diagnostics) raise capital from diverse investor types. Your expertise includes understanding how different investor archetypes evaluate opportunities and what specific information they need to make investment decisions.
I'm a biotech founder preparing to fundraise, and I need help customizing my pitch materials for different investor archetypes. I'll provide you with my current materials, and you'll help me optimize them for 5 distinct investor types.
PART 1: CONTEXT ON INVESTOR ARCHETYPESBefore we begin, here's what each investor archetype cares about most:
Archetype 1: Friends & Family / Non-Industry Angels & Family OfficesKnowledge Level:
General business fundamentals but limited biotech expertiseMay have read headlines about biotech/AI but don't understand drug developmentDon't know realistic timelines, biotech business models, or exit dynamicsWhat They Care About:
Can I understand this in 2 minutes?Why is this problem important (human impact)?Why is now the right time?Can this founder execute?How do I get my money back (exit story with precedents)?Who else is investing (social proof)?Common Mistakes Founders Make:
Leading with technology/mechanism before establishing the problemUsing jargon without definitionAssuming they understand drug development timelinesNot providing concrete exit examplesArchetype 2: Industry Angels & Sophisticated Family OfficesKnowledge Level:
Former pharma executives, exited biotech founders, or dedicated life sciences investorsDeep understanding of drug development, business models, and competitive landscapeKnow what "good" data looks like vs. hypeWhat They Care About:
Is the technology truly defensible (IP, competitive moats)?Can this team execute operationally (not just scientifically)?What's the realistic value creation path (partnerships, exit timing)?Who's validating this (pharma interest, KOL advisors)?Is the founder coachable and strategic?Common Mistakes Founders Make:
Spending too much time educating them on basics they already knowNot articulating clear competitive differentiationLacking specifics on traction or pharma engagementUnderestimating their network and ability to verify claimsArchetype 3: Generalist Early-Stage VCsKnowledge Level:
Understand venture mechanics and fund economicsFamiliar with tech/SaaS metrics but less deep in biotechKnow biotech trends (AI/ML, CRISPR buzzwords) but lack technical depthWill rely on advisors for scientific due diligenceWhat They Care About:
Does this fit our fund thesis (tech-enabled, capital-efficient)?Can this scale like a tech company (leverage, margins)?Is the market opportunity venture-scale ($1B+ outcome)?Who else is investing (syndicate quality)?Can we explain this to our LPs?What's the path to the next round?Common Mistakes Founders Make:
Using overly abstract or unrealistic TAM numbersNot bridging biotech and tech languageFailing to show platform scalability or leverageLong timelines without near-term milestonesArchetype 4: Biotech-Focused VCsKnowledge Level:
Deep domain expertise (PhDs/MDs on staff)Know your space better than you doHave seen hundreds of platforms and programsUnderstand competitive landscape, regulatory paths, exit dynamicsWhat They Care About:
Is the science truly differentiated (not just incrementally better)?Can this team execute at the highest level?What's the data quality (rigorous validation)?Is this fundable through next 2-3 rounds?Does this fit our portfolio (complement vs. compete with existing investments)?Can we build a $500M+ outcome?Common Mistakes Founders Make:
Overstating differentiation without rigorous proofInsufficient data quality or controls
</aside>