The Anatomy of a Pre-Seed Strategy

Problem Hypothesis & Validation

Testing Your Beliefs Before Betting Your Career on Them

Every startup begins with a hypothesis: "I believe [specific group of people] have [specific problem] that is painful enough to pay for a solution." The pre-seed stage is about testing this hypothesis rigorously before committing significant time and resources. Most first-time founders skip this step because it feels unproductive — talking to strangers about their problems does not feel like "building a startup." But customer discovery is the most valuable activity a pre-seed founder can engage in. Retool's David Hsu did not start with the idea for a low-code internal tool platform. He started with the observation that every company he worked at wasted engineering time building CRUD apps for internal operations. He interviewed over 40 engineering managers to validate that this was a universal, painful, and budget-worthy problem before writing a line of code. That disciplined validation gave him conviction that the market was real.

• →Formulate your problem hypothesis in a specific, testable format: who has the problem, how frequently, how painful it is, and what they currently do about it
• →Conduct at least 30-50 customer discovery interviews before building anything — use the Mom Test methodology to get honest feedback
• →Look for signals of desperation, not just interest: are potential customers actively searching for solutions, cobbling together workarounds, or spending money on inadequate alternatives
• →Document every interview systematically and look for patterns — if 70%+ of interviewees describe the same core pain point, you have strong problem validation

Co-Founder Selection & Alignment

Choosing the Partner Who Determines 50% of Your Outcome

Data from Y Combinator shows that co-founder conflict is the second leading cause of startup failure, behind only lack of market need. The pre-seed stage is when co-founder alignment must be established — not through vague conversations about shared vision, but through explicit agreements on equity splits, role definitions, decision-making authority, vesting schedules, and exit scenarios. The best founding teams share complementary skills (typically technical + commercial), aligned values, and a shared understanding of what success looks like. Equally important is what they disagree on: healthy co-founder relationships require the ability to have productive conflict about strategy without it becoming personal. Brian Chesky and Joe Gebbia of Airbnb worked together for years before starting the company and had deeply complementary skills — Chesky in business and Gebbia in design. Their pre-existing trust and clearly defined roles allowed them to move faster than a newly formed team ever could.

• →Choose co-founders based on complementary skills and shared values — not friendship alone; the best co-founder is someone you trust AND who fills gaps in your capabilities
• →Have explicit conversations about equity split, vesting, roles, decision rights, and what happens if one founder wants to leave — before writing any code
• →Implement 4-year vesting with a 1-year cliff for all founders, including yourself — this protects everyone if the team does not work out
• →Spend at least 2-4 weeks working together intensively before making a permanent commitment — co-founder trial periods reveal incompatibilities that conversations cannot

Rapid Prototype Development

Building the Minimum Thing That Proves Your Core Thesis

The pre-seed prototype serves one purpose: to test whether your proposed solution resonates with the people who have the problem you identified. This is fundamentally different from building a product. A prototype can be a landing page, a Figma mockup, a no-code tool, a spreadsheet-powered service, or a minimal coded application. The key is that it tests your core value proposition — the single most important thing your product must do — with real potential customers. Notion's first prototype was so ambitious (a general-purpose productivity tool with blocks-based architecture) that it failed completely. Ivan Zhao had to lay off his team, move to Kyoto, and rebuild with a radically simplified approach. The lesson was not that ambition is wrong — it is that the pre-seed prototype must validate the core interaction model before expanding to a full vision.

• →Identify the single riskiest assumption in your business and design the prototype to test that specific assumption
• →Set a strict time limit for prototype development: 2-6 weeks maximum; anything longer means you are building a product, not testing a hypothesis
• →Use the fastest possible tool: no-code platforms, landing pages, manual concierge delivery, or Wizard of Oz approaches before writing production code
• →Define success criteria before building: what specific metric or qualitative signal will tell you the prototype validates your thesis

Initial Customer Acquisition

Getting Your First 10 Customers Without a Product or a Budget

Pre-seed customer acquisition is fundamentally different from growth-stage marketing. You are not looking for scale; you are looking for signal. Your goal is to find 5-10 people who are so desperate for a solution to their problem that they will tolerate a broken, incomplete product to get it. These early adopters are not typical customers — they are the people Paul Graham calls "the desperate few." They are disproportionately forgiving, disproportionately vocal in feedback, and disproportionately valuable as social proof for future fundraising. Loom (originally called Opentest) pivoted multiple times before finding product-market fit with video messaging. Each pivot started with the same approach: the founders personally messaged potential users, offered free access to a barely functional product, and used the feedback to iterate rapidly. The first 10 users of any startup are almost always acquired through personal outreach — not marketing.

• →Target early adopters who are actively suffering from the problem — these people will tolerate an imperfect product because the pain of the status quo exceeds the friction of your prototype
• →Use direct, personal outreach: cold emails, LinkedIn messages, community posts, and warm introductions from your network
• →Offer your prototype for free or at a deep discount in exchange for weekly feedback sessions — the feedback is more valuable than the revenue at this stage
• →Track engagement obsessively: are early users coming back on their own, telling others, and using the product in ways you did not anticipate

Pre-Seed Fundraising Mechanics

Raising $250K–$2M When You Have Nothing but Conviction and a Prototype

Pre-seed fundraising is unique because you are raising capital based primarily on the team, the problem, and early signals — not on revenue or proven metrics. Investors at this stage are betting on founders, not financials. This means the fundraising process is fundamentally about storytelling and credibility: can you articulate a compelling problem, demonstrate that you have unique insight into the solution, and show early evidence (prototype, customer interviews, waitlist, LOIs) that your thesis has merit? The mechanics of pre-seed fundraising have shifted significantly in recent years: SAFEs (Simple Agreements for Future Equity) have replaced convertible notes as the standard instrument, valuations have settled into predictable ranges by geography and market, and the angel/pre-seed fund ecosystem has expanded dramatically. Understanding these mechanics — and avoiding common term sheet mistakes — can save founders significant ownership and optionality.

• →Use SAFEs (post-money valuation cap, no discount) as the standard instrument — they are founder-friendly, quick to execute, and understood by all investors at this stage
• →Target a raise of 12-18 months of runway: enough to build an MVP, acquire initial customers, and reach milestones that justify a seed round
• →Build your investor pipeline before you need capital: start conversations 3-6 months before your target raise date and convert relationships into commitments
• →Lead with the problem and your unique insight, not the solution — pre-seed investors invest in founders who deeply understand a market, not in product demos

Accelerator & Program Strategy

Maximizing the 3-Month Window That Can Define Your Trajectory

Accelerators like Y Combinator, Techstars, and their peers compress 6-12 months of startup learning into a 3-month sprint. The best accelerator participants extract maximum value by arriving with a clear hypothesis, using the program's network to rapidly validate or invalidate their assumptions, iterating the product weekly based on mentor and customer feedback, and building relationships with investors months before Demo Day. The worst participants treat the accelerator as a classroom experience — attending every session, meeting every mentor, but never making the hard strategic decisions that the program is designed to force. YC's mandate to "launch early and often" exists because the accelerator timeline forces urgency that human nature resists. Companies that launch within the first 2 weeks of YC consistently outperform those that wait until week 8.

• →Arrive at the accelerator with a validated problem hypothesis and a working prototype — do not use the program to figure out your idea
• →Set weekly shipping goals and hold yourself accountable: launch something to real users within the first 2 weeks of any program
• →Prioritize 3-5 mentors with deep domain expertise over 20 mentors with surface-level advice — depth of relationship beats breadth of network
• →Begin investor outreach 4-6 weeks before Demo Day: the fundraise starts during the program, not on Demo Day itself

“

The biggest mistake I see in YC is founders who spend the whole batch building in stealth and launch at Demo Day. The point of YC is not Demo Day — it is the 12 weeks of intense customer feedback that precede it. The companies that do best launch in week 1 and iterate 12 times before Demo Day.

— Dalton Caldwell, Managing Director at Y Combinator

Pre-Seed to Seed Transition Planning

Setting the Foundation for Everything That Comes Next

The transition from pre-seed to seed is the first major inflection point in a startup's life. Seed investors will evaluate you on a different set of criteria than pre-seed investors: they want to see quantitative traction (users, revenue, engagement metrics), product velocity (how fast you ship and iterate), and evidence of a scalable market opportunity. The decisions you make during the pre-seed stage — your corporate structure, cap table cleanliness, metric tracking infrastructure, and hiring choices — will either accelerate or delay this transition. Notion's pre-seed period lasted several years and included a near-fatal product failure, but Ivan Zhao used that extended pre-seed period to build deep technical infrastructure and a distinctive product vision that eventually drove explosive growth. The pre-seed to seed transition is not about speed — it is about building the foundations that make speed possible later.

• →Incorporate properly from the beginning: Delaware C-Corp for US startups seeking venture capital, with clean 83(b) elections filed for all founders
• →Build metric tracking infrastructure early: set up analytics, define key metrics, and track cohort data from your first customer — seed investors will ask for 6-12 months of data
• →Plan your seed round milestones backwards: if you want to raise seed in 12 months, define the metrics you need to hit and build a roadmap to achieve them
• →Keep your cap table clean: limit pre-seed investors to a manageable number, use standardized SAFEs, and avoid complex terms that create issues in future rounds