What should a pre-seed founder focus on first?

At the pre-seed stage, your single most important job is to get close enough to a real problem — and real users — that you can form honest, testable hypotheses about your market. Fundraising, competition, and scaling are secondary concerns that become relevant only after you've done the hard work of direct customer engagement. Founders who skip this step and optimize for appearances over reality are the ones who fail quietly and fast.

Treat Your Startup as Fragile — Because It Is

Most pre-seed founders dramatically underestimate how early-stage they really are, and that misdiagnosis leads them to prioritize the wrong things. Paul Graham's observation in 'Do Things That Don't Scale' is that almost every startup is fragile at the start — not because the idea is bad, but because nothing has been stress-tested yet. Airbnb, one of the most successful startups ever funded, was roughly 30 days of direct user engagement away from dying. That's not an anomaly; that's the default condition.

The practical implication: stop managing your startup from a distance. Don't survey users — sit with them. Don't analyze churn in a spreadsheet — call the people who left. Your instinct at this stage will be to build systems and processes that feel professional, but what you actually need is information so granular that no system can capture it yet. The founders who survive pre-seed are the ones who treat every user interaction as a diagnostic session, not a transaction.

One common trap is dismissing your own startup before it has a chance to grow. Graham's point here is sharp: even Bill Gates underestimated Microsoft's potential while he was building it. If you're already mentally categorizing your company as a 'small startup,' you may be cutting off paths before they open. Pre-seed is the stage where your job is to stay alive long enough to see what you're actually building.

Do Unscalable Things on Purpose

The counterintuitive truth about pre-seed is that the activities that feel embarrassingly small — personally onboarding every user, hand-writing follow-up notes, physically going to where customers are — are exactly the activities that matter most. Graham's framework in 'Do Things That Don't Scale' reframes this not as a temporary compromise but as a deliberate strategy. When your user base is tiny, you have asymmetric access to information that a larger company can never replicate. Use it.

What does this look like in practice? It means your customer support should come directly from a founder, not a contractor. It means you should know your first 50 users by name, industry, and use case. It means you should be personally present at the moments when users fail to understand your product — not reading about those moments in analytics dashboards. The goal isn't to do these things forever. The goal is to extract enough signal that when you eventually do build scalable systems, they reflect what customers actually need rather than what you assumed they needed.

Founders worry that being this attentive to individual users won't scale — but Graham's point is that this concern is backwards. If you make your early users genuinely delighted, you'll eventually have 'too many users to give this much attention to' — and that is a good problem. The founders who never get there are the ones who skipped the obsessive early phase in favor of premature systematization.

Know Your Market Hypothesis Clearly and Honestly

Investors at the seed stage — and especially at pre-seed — aren't expecting you to have certainty. They're evaluating whether you have a credible hypothesis and whether you're honest enough to identify the gaps in it yourself. Paul Graham makes clear in his YC application guidance that what kills startups isn't competition; it's poor execution. But founders who don't understand their competitive landscape, or who wave it away, signal something worse than having competitors: they signal they're either not paying attention or they're not being straight.

For a pre-seed founder, this means developing a point of view about your market that you can articulate without spin. You should know who else is working on this problem, what their approach is, and where you believe they're wrong or incomplete. You don't need to pretend competitors don't exist or that they can't hurt you. You need to show that you've thought about it seriously and that your specific approach has a defensible angle — whether that's a technical insight, a distribution advantage, or a customer segment that others have ignored.

The practical test: can you explain your market hypothesis to a skeptic and preemptively name the two or three most serious objections? If you can't, you're not ready for investor conversations — and more importantly, you don't yet have the clarity you need to execute well. Fundraising is downstream of this clarity, not upstream of it.

Defer Fundraising Until You Have Something Real to Show

There's a gravitational pull toward fundraising at the pre-seed stage that can consume months of founder time before it produces anything useful. Paul Graham's advice in 'How to Raise Money' is built around a key structural insight: fundraising should be done in compressed, focused bursts — not as an ongoing background activity that bleeds into product and customer work. For a pre-seed founder without much traction, the risk is spending all your time pitching before you've built the thing that makes pitches worth taking.

The more important point is that fundraising is a lagging indicator, not a leading one. The founders who raise quickly at pre-seed are almost always the ones who spent the preceding months doing things that generated genuine proof points — user engagement, early revenue, a technical breakthrough, or a domain insight so specific it's clearly proprietary. Investors at this stage are evaluating the founders as much as the idea, and the most convincing signal you can offer is evidence that you learn fast and execute honestly under uncertainty.

If you haven't yet built anything or talked to more than a handful of potential customers, the right move is usually to keep fundraising off the table for another 60 to 90 days and use that time to generate something worth talking about. A pre-seed raise on the back of real signals — even small ones — will close faster and on better terms than a raise based on a deck alone.

Build the Founding Team Dynamic That Investors Actually Evaluate

When investors assess a pre-seed team, they're looking at three overlapping things: general founder quality, domain-specific expertise, and the relationship between cofounders. Graham's framing in his YC application guidance is that these three factors determine whether a team will be able to find a path to a big market — not just whether they've correctly identified the market already. This means the cofounder relationship and individual credibility are as much a part of your 'product' at pre-seed as the actual software or service.

What this means practically: founders should be honest, including internally, about where their team has gaps. A technical cofounder who has never sold and a sales-focused founder who has never built a product together is a common combination — and it works, but only if both people understand and respect what the other brings. The dysfunction that kills early startups is usually not a skills gap but a trust and communication gap between founders. Before you worry about your pitch, examine whether your founding team can have hard conversations clearly and quickly.

You should also audit domain expertise candidly. Having worked in an industry for three years gives you a different kind of insight than having studied it from the outside. Neither disqualifies you, but investors will probe this. If your edge is your insight as an outsider who sees something the industry missed, be specific about what that insight is. If your edge is deep insider knowledge, be specific about how it changes your execution. Vague claims about 'understanding the space' are the weakest possible position at pre-seed.

“Almost all startups are fragile initially… The big danger is that you'll dismiss your startup yourself.”

— Paul Graham, source

The one thing to do

Before anything else, spend 60 days doing nothing but talking to and manually serving real potential users until you have specific, honest observations about their behavior — everything else follows from that.

Frequently asked questions

Should a pre-seed founder be fundraising or building?

Building and talking to users first. Fundraising without traction or a sharp hypothesis wastes months and produces weak results. Compress your fundraise into a focused sprint after you have something real to show.

How many users do I need before pre-seed fundraising makes sense?

There's no universal threshold, but you need enough users to have genuine observations about behavior, retention, and problems — not just signups. Even 10 deeply engaged users who love your product is a stronger position than 500 who never came back.

Do I need to worry about competitors at pre-seed?

You need to know them and be honest about them, but you don't need to fear them. Poor execution kills startups far more often than competition. Investors will be more concerned if you seem unaware of competitors than if you name them clearly.

What's the single biggest mistake pre-seed founders make?

Optimizing for appearances — a polished deck, a smooth pitch, a professional process — before they've done the unglamorous work of understanding real users deeply. The unscalable, hands-on work is the job, not the obstacle to the job.

Sources

More playbook answers · Growth Prophet home