How to Evaluate Startup Founders: Signals That Predict Execution

At seed stage, the founder is the investment. The product will pivot, the market will shift, but the team's ability to execute is the constant. Which makes founder evaluation most of the job.

Why Founders Matter Most at Seed#

A seed check is a bet on a team before the product and market have proven themselves. Everything else on the scorecard, market, product, traction, is a bet on the founder's ability to find them. Get the team wrong and nothing else matters.

Execution Signals#

The best predictor of whether a founder can deliver is whether they are delivering right now. That is readable in their public shipping record: the commits they push, the repositories they build, and the pace at which they do it. It is the least gameable founder check available ^[2].

Technical Depth#

For technical founders, public code is a direct record of capability. It shows what they actually build, at what pace, and with how many collaborators. It is also the cheapest check: reading a founder's public GitHub costs nothing and cannot be rehearsed.

Team-Building Signals#

A founder who can recruit is a founder who can scale. Watch contributor growth on their projects. A founder whose team is expanding is building something other people want to work on, which is itself a signal about the company.

The Red Flags#

A few signals override everything else. A pitch that contradicts the public record. A shipping pace that does not match the claimed traction. A founder who cannot name the specific problem their product solves. Any one of these is worth walking away over.

Reading Founders in Public#

A weekly-updated panel of 350+ startup orgs gives you a surface for spotting founders who ship, independently of their network ^[1]. It does not replace the conversation, but it decides who earns one ^[3].

Founder evaluation is judgment, but the inputs to that judgment are increasingly public. Read the shipping record first, then take the meeting.