How to Evaluate a Pre-Revenue Startup When There Are No Numbers

The company has no revenue. No customers. Maybe no product. You have 20 minutes on a Zoom call. What do you actually look at?

This is the core problem of pre-seed investing. Every framework built around ARR growth, payback periods, or unit economics becomes useless the moment you strip out the numbers. Which means you need a different set of tools entirely.

Here's how experienced angels actually think about it.

Stop Asking for Financial Projections

The biggest mistake new angels make is applying later-stage thinking to pre-revenue companies. They ask for a model. They scrutinize revenue assumptions. They want to see a five-year forecast.

None of that matters. A founder who's been building for six months has no real data to base a credible model on. What you'll get is arithmetic dressed up as insight, and anyone can make a spreadsheet say whatever they want.

At pre-revenue, you're not evaluating a business. You're evaluating a bet. The bet is on the founder, the problem, and the early signals that something real is forming around them.

The Founder Is the Product

At this stage, the team is almost everything. Not "team" in the abstract sense of "we have a technical cofounder" but in the specific sense of: why is this particular person uniquely positioned to solve this particular problem?

The question I find most clarifying: what has this founder done that nobody asked them to do?

If someone built a prototype before raising, wrote 50 posts about a problem space before starting a company, or spent two years deep in the industry they're now disrupting, that's signal. It tells you they have genuine conviction, not trend-chasing.

Watch for the opposite too. Founders who pivoted to a hot space because the opportunity looked interesting often can't articulate the pain in any specific way. They talk about markets and opportunities. Founders who've lived the problem talk about the moment they got frustrated enough to build.

Ask them to explain the problem as if you've never heard of the space. The clarity of that explanation tells you more than any pitch deck.

Market Signals That Exist Before Revenue

Pre-revenue doesn't mean pre-signal. There are real indicators that a problem is worth solving, and they don't require a single dollar to exist.

Look for communities forming around the problem. Are people gathering on Reddit, Discord, or Slack to share workarounds for the thing this startup wants to fix? DIY solutions are one of the clearest signals of market pull. If people are manually cobbling together a solution from five different tools, there's latent demand waiting for a real product. Reddit communities can be surprisingly predictive of startup opportunities when you know what patterns to look for.

Also look at search behavior. Consistent organic volume around a problem, with commercial intent, tells you people are actively seeking solutions. They're not waiting to be told they have a problem.

Product Signals You Can Actually Measure

Even at pre-revenue, many startups are building in public. And the artifacts of that building are measurable.

GitHub repositories are one of the most underused signals in early-stage investing. Stars, forks, and contributor counts don't always translate directly to business outcomes, but GitHub star velocity is a remarkably consistent leading indicator for developer-focused startups. A repo accumulating stars without any marketing spend means developers are finding it organically and caring enough to bookmark it. That's not nothing.

Waitlist size matters less than waitlist composition. A thousand sign-ups doesn't tell you much. A hundred people, where thirty have the job title of your exact target buyer, tells you a lot.

Product Hunt launches can reveal early customer enthusiasm too. But the metric that matters isn't total upvotes. It's the quality of comments and follow-on behavior. How a product performs on launch day relative to its category tells you whether people are genuinely interested or just clicking.

Hacker News is another useful signal source. When a project surfaces on Hacker News and draws genuine technical engagement rather than dismissal, it often sits ahead of where broader investor attention currently sits.

Early Traction That Doesn't Require Revenue

Revenue is the clearest signal that people value something enough to pay for it. Before revenue, there are real proxies worth tracking.

Retention is the most honest one. If you have 100 beta users and 80 are still active three months later, that's a stronger signal than 500 sign-ups with 20 still engaging. People don't stick around for things they don't find useful. They ghost.

Organic word of mouth is the second. Ask the founder how users are finding them right now. "We haven't done any marketing" paired with consistent inbound says the product is spreading on its own merits. If every user came from a direct founder outreach campaign, that's fine but tells you less about organic pull.

What to Actually Decide After the Meeting

After 20 minutes with a pre-revenue founder, you're not deciding whether this is a good business yet. You can't. The data doesn't exist.

You're deciding three things.

Is this founder credible and specific about the problem? Do they have earned insights, not borrowed ones?

Are there measurable signals outside the pitch, even weak ones, that suggest market pull? GitHub traction, community chatter, waitlist behavior?

Does the market size math work if they're even 10% right about the problem? You don't need a perfect TAM analysis. You need a scenario where a modest outcome still returns your check.

If two of those three answers are yes, the question becomes whether you trust this founder enough to bet early. That's a judgment call, not a spreadsheet.

The angels who consistently get into the best early rounds focus obsessively on finding companies before momentum is obvious to everyone. They make bets with incomplete information, rather than waiting for the revenue that makes the decision obvious.

Build a Consistent Signal-Watching Practice

The hardest part of pre-revenue evaluation isn't identifying the right signals. It's seeing them consistently across enough deals to recognize what good actually looks like.

That means building a workflow for monitoring early-stage startups regularly, not just when someone sends you a deck. The BeforeVC weekly briefing surfaces exactly these kinds of early signals across GitHub, product communities, and developer forums, giving angels a cleaner view of what's forming before the round gets competitive. If pre-seed is part of your strategy, it's worth having a systematic way to see more of it.