Assessing Founder Potential When There's No Traction (Yet)

A program manager emailed me before her selection committee meeting with a question I've gotten in different forms dozens of times.

"We have two strong applicants for our last spot. One has a great team, clear problem understanding, but no product and no customers—they're pre-MVP. The other has a basic MVP but weak co-founder dynamics and fuzzy thinking about who the customer actually is. Who do we pick?"

My answer: almost certainly the first one.

Not because traction doesn't matter. It does. But because traction is a lagging indicator. It tells you what happened in the past. What you need to evaluate at the selection stage is leading-edge potential—the founder characteristics and behaviors that predict whether someone will be able to create traction, even from zero.

This post is about how to evaluate those things when there's nothing in the market to point to yet.

The Traction Trap

Most selection criteria are built around traction signals: revenue, active users, letters of intent, pilot customers, growth rate.

These are good signals when they exist. But they're available in maybe 20-30% of applications to most early-stage accelerators. For the rest—the pre-revenue, pre-MVP, early-problem-validation founders who make up the majority of most applicant pools—you need a different lens.

The problem is that most programs default to one of two bad responses:

Bad response 1: Require traction anyway. Set a revenue or customer threshold that eliminates the pre-traction pool entirely. This produces a more "fundable" looking cohort on paper, but it excludes many founders who could develop into exceptional program participants—and it systematically disadvantages founders from under-resourced backgrounds who haven't had access to early capital or networks.

Bad response 2: Evaluate idea quality. In the absence of market data, shift evaluation to the idea itself. Is the market big? Is the solution elegant? Is the pitch compelling?

This is worse. You're now evaluating the founder's ability to construct a narrative, not their ability to build a company.

The right response: evaluate the behaviors and thinking patterns that predict founder success, independent of whether they've produced results yet.

What Predicts Founder Success Before There's Traction

Research on what differentiates high-potential early-stage founders from low-potential ones consistently points to a cluster of behaviors and cognitive patterns. They're not about the idea. They're about the person.

Here's what to look for.

1. Quality and depth of problem understanding

   The single strongest predictor of founder potential at the pre-traction stage is how deeply they understand the specific problem they're solving—not from desk research, but from direct engagement with the people experiencing it.
   

   You're looking for:

   • Specific customer conversations, not general market research

   • The ability to articulate the problem from the customer's perspective, not just from the outside

   • Nuanced understanding of when, how, and why the problem occurs

   • Awareness of the workarounds customers are already using
     

   A founder who has talked to 40 potential customers and can articulate the exact moment the pain occurs—and what it costs the customer to live with the problem—has demonstrated something valuable. They know how to learn from the market. That skill will serve them at every subsequent stage.
   

   A founder who can't describe a single specific customer conversation has a gap that should disqualify them, regardless of how elegant the solution sounds.
   

2. Speed and quality of iteration

   At the pre-traction stage, traction hasn't happened yet—but iteration should have. Ask founders: what have you tried, what did you learn, and what did you change?
   

   High-potential founders:

   • Have run experiments, even small ones (a landing page, a survey, a prototype demo)

   • Can articulate what they learned from each experiment

   • Have changed their approach based on what they learned

   • Show a clear bias toward doing over planning
     

   Low-potential founders:

   • Are still refining the plan before testing anything

   • Have done research but no direct market contact

   • Haven't changed anything because they "haven't had time to test yet"

   • Treat the accelerator program as the first step, when it should be a mid-journey accelerant
     

3. Self-awareness and intellectual honesty

   Great early-stage founders know what they don't know—and they talk about it openly. They can identify the biggest risks to their startup, name the assumptions they haven't validated, and articulate what keeps them up at night.
   

   This is counterintuitive. It sounds like weakness. But founders who perform certainty they don't have are hiding their gaps from you and from themselves. Founders who are explicit about uncertainty are managing it actively.
   

   In selection interviews, ask: "What's the biggest assumption in your business model that you haven't validated yet?" The answer tells you a lot. A thoughtful answer with specific concerns and a plan to address them = high potential. "I'm pretty confident in the model" = red flag.
   

4. Genuine domain connection

   Why is this specific person working on this specific problem?
   

   The strongest early-stage founders have an authentic connection to the problem—through lived experience, professional history, deep community involvement, or persistent obsession. This connection creates resilience. When things go wrong (and they will), the founder stays engaged because the problem matters to them.
   

   Founders who are working on a problem primarily because they identified a market opportunity are at much higher churn risk. When the going gets hard and another opportunity appears, they'll leave.
   

   This isn't about excluding first-time entrepreneurs or people pivoting careers. It's about finding the specific reason this person is the right person for this problem—and that reason should be something more than "I thought it was a good business."
   

5. Team dynamics and founder relationships

   For two-person or multi-founder teams, the relationship between co-founders is often more predictive of outcome than any individual characteristic.
   

   Look for:

   • Complementary skills with genuine respect for each other's domain

   • Clear decision-making structure (who leads on what, and why)

   • Track record of working together under pressure, even briefly

   • Evidence of constructive disagreement (they don't always agree—and that's okay)
     

   Red flags:

   • Co-founders who just met (at a hackathon, through a program) with no track record together

   • Founders who describe the relationship in vague terms ("we work great together!") without specific examples

   • Founder teams where one person does all the talking and the other seems deferential or uninvested

   • Skill overlap without complementarity (two engineers, neither doing sales)
     

How to Probe for These in an Application

Most application questions are poorly designed for evaluating pre-traction potential. They ask "what's your business model?" when they should ask "what did you learn from the last thing you built or tested?"

Better application questions for pre-traction founders:

• "Describe a conversation you've had with someone who experiences the problem you're solving. What surprised you?" (Tests primary research depth and genuine curiosity)

• "What have you built or tested so far? What worked, what didn't, and what did you change as a result?" (Tests iteration behavior)

• "What's the single biggest thing you don't know yet that would change your direction significantly?" (Tests self-awareness and intellectual honesty)

• "Why are you specifically the right person to be working on this problem?" (Tests founder-problem fit)

• "What would have to happen for you to give up on this startup and work on something else?" (Tests resilience and authenticity of commitment)

How to Probe for These in an Interview

Interviews with pre-traction founders should be structured around evidence of the behaviors above—not around evaluating the idea.

Useful interview probes:

For problem understanding:

• "Tell me about the most recent customer conversation you had. What did you ask, and what did you learn?"

• "What do your target customers do today instead of using your solution? Why do they do it that way?"

For iteration behavior:

• "Walk me through the experiments or tests you've run in the last 60 days."

• "What's something you believed three months ago that you no longer believe?"

For self-awareness:

• "If I were a skeptic about your startup, what would be my strongest argument against it?"

• "What's the assumption you're most nervous about testing? Why haven't you tested it yet?"

For founder-problem fit:

• "Tell me about a time you personally experienced the problem you're solving."

• "If the accelerator program didn't exist, what would you be doing with this idea in the next three months?"

For team dynamics (multi-founder teams):

• "Tell me about a significant disagreement you've had as a team. How did you resolve it?"

• "What does your co-founder do that you couldn't do yourself?"

Calibrating Expectations by Stage

Not all pre-traction founders are at the same stage. Your evaluation standards should adjust accordingly.

Pre-idea founders (accepted only by specific programs designed for them):

• Evidence of strong domain expertise or lived experience

• History of learning fast and shipping things

• Strong self-awareness and intellectual curiosity

• No expectation of market contact yet

Problem-validated founders (have identified the problem, minimal solution work):

• Substantial primary research (20+ customer conversations minimum)

• Clear articulation of problem, customer, and early hypothesis about solution

• Some evidence of iteration on their understanding

• Beginning to think about solution approaches

MVP-building founders (have a testable prototype or early product):

• Direct market contact with actual users or potential customers

• Evidence of what they've learned and changed

• Beginning traction signals (waitlist, beta users, early feedback)

• Clear next hypothesis to test

If your program is designed for MVP-stage founders, it's okay to set a higher bar for market contact. If your program specifically supports early-stage founders, your criteria should be calibrated to what's realistic for that stage—not what would impress an investor.

Common Mistakes When Evaluating Pre-Traction Founders

Mistake 1: Mistaking confidence for competence

Confident founders perform better in selection interviews. They tell a cleaner story, handle challenges smoothly, project certainty. But confidence is a presentation skill, not a founder skill. Some of the best early-stage founders I've worked with presented uncertainty and real doubts in their selection interviews—because they were being honest.

Calibrate for intellectual honesty, not polish.

Mistake 2: Overweighting idea quality

"This is a really interesting space" is not a good reason to accept a founder. The idea will almost certainly change during your program. You're not selecting the idea—you're selecting the person who will navigate the inevitable changes.

Mistake 3: Underweighting execution evidence

Even pre-traction founders should have done something. If the application has lots of planning and no doing, that's a signal. The question isn't what they've achieved—it's whether they have a bias toward action.

Mistake 4: Applying traction-stage criteria to pre-traction founders

If your rubric rewards customer count, revenue, or growth rate, you're systematically disadvantaging founders who applied at an earlier stage—including founders from underrepresented backgrounds who often have less access to early capital and networks.

Separate your criteria by stage, or explicitly note that traction evidence is weighted differently depending on where the founder is in their journey.

The Bottom Line

Traction is a lagging indicator. It tells you what happened—not who a founder is or what they're capable of becoming.

The best pre-traction founders show it in how they think, how they learn, how they engage with uncertainty, and how they move. They've talked to real customers, run real experiments, and changed real things based on what they learned. They know what they don't know—and they're actively working to find out.

Evaluate that. Not the pitch deck. Not the confidence level. Not the size of the market.

The founder who shows up to your program having done the work—even if they have zero revenue—will learn faster, pivot smarter, and extract more value from every mentor session than the founder who impressed your committee with a polished story and nothing behind it.

Find the ones who've done the work.

.

.

.

Want a framework for evaluating pre-traction founders? I've built a Pre-Traction Assessment Guide with stage-calibrated evaluation criteria, interview question banks, and a scoring rubric for founders at each stage from pre-idea through early MVP. Download it here.

You might also find the Founder Stage Calibration Tool useful—it's a quick assessment to determine what stage a founder is actually at and what evaluation standards apply. Grab it here.

This post is part of a series on founder experience for accelerators, incubators, and startup studios. If you found this useful, you might also like: "The Selection Matrix: A Rubric for Evaluating Founders Without Bias" and "Founder-Program Fit: The Most Underrated Selection Criteria."