The founding team is the single most predictive factor in whether a startup succeeds or fails. Investors say “bet on the jockey, not the horse” so often it’s become cliché—but the data backs it up. A great team can salvage a mediocre idea; a mediocre team will destroy a great one. After evaluating hundreds of startup pitches across SaaS, fintech, and healthcare verticals, here’s how I actually evaluate founding teams—not the polished pitch deck version, but whether these people will survive the next eighteen months.
The first question I ask is whether this team understands the problem they’re solving at a fundamental level. Surface-level domain knowledge—reading reports, following industry news, having worked in the sector—isn’t enough. I look for founders who have lived the problem, who have scars from trying to solve it themselves, who spent years complaining about existing solutions before deciding to build one themselves.
Take Stripe versus the dozens of payment gateways that came before it. Patrick and John Collison didn’t just recognize that online payments were fragmented—they had experienced the pain of building their own payment infrastructure at Auctomatic and understood exactly why existing solutions failed developers. That experiential knowledge separates domain experts from people who simply read that a market is large.
When evaluating domain expertise, dig into specifics. Ask founders to explain the last significant trend in their industry that surprised analysts. Ask them to identify the three most well-funded competitors and articulate exactly why each one will or won’t win long-term. Ask them to describe a regulatory change coming in the next two years and how it affects their business model. If they can’t answer with depth and nuance, they don’t have domain expertise—they have familiarity that will evaporate when real challenges arrive.
The practical takeaway: require founders to demonstrate expertise through specific, verifiable experience. Someone who “has worked in healthcare for ten years” is less compelling than someone who built and sold a healthcare analytics company to a major payer, who can tell you exactly why EHR integration remains unsolved, and who can name the three startups that failed trying to solve that problem and why each failed.
There’s a persistent myth that first-time founders are more “hungry” and therefore more likely to succeed. The data tells a different story. Repeat founders have materially higher success rates—not because they get lucky, but because they’ve internalized the lessons that kill first-time founders: how to manage cash runway, how to fire underperforming employees, how to pivot when the market says no.
I don’t disqualify first-time founders automatically. But I adjust my expectations and due diligence accordingly. A first-time founder with no operational startup experience needs to demonstrate exceptional self-awareness and surround themselves with advisors who can mentor where they lack experience. A repeat founder should point to specific failures and articulate exactly what they learned—and more importantly, what they would do differently.
One of my most successful investments was in a founder who previously built a company that completely failed. She raised a small seed round, built a product no one wanted, pivoted twice, ran out of money, and had to lay off her team. Three years later, she came back with a new idea addressing a problem she’d discovered during her first venture. Her previous failure wasn’t a black mark—it was the most valuable part of her pitch. She understood capital efficiency, customer development, and that her first idea was wrong. That’s worth more than a founder who’s never been tested.
The practical takeaway: ask founders about their biggest operational failure and listen for specificity and self-awareness. Those who say “we didn’t have enough capital” or “the market wasn’t ready” are usually avoiding the real answer. The ones who can say “I hired the wrong person for head of sales because I was afraid to conflict with them, and we lost six months of runway” are the ones who’ve actually learned something.
This is where many investors—especially those without technical backgrounds—get comfortable too quickly. They see a technical founder and assume execution capability is covered. It isn’t. Technical expertise and the ability to ship a product users actually want are related but distinct skills.
I’ve seen brilliant engineers build products that were technically elegant and completely useless in the market. I’ve seen non-technical founders with strong technical co-founders who couldn’t effectively communicate product requirements and ended up with a product that solved problems nobody had. Technical execution capability isn’t about whether the founder can write code—it’s about whether they can translate customer needs into a product that solves those needs efficiently.
The best proxy I’ve found is asking to see the product. Not the demo built for the pitch, but the actual product being used by real customers. How fast did they ship the initial version? How many iterations has it gone through? What features are customers actually using versus what the founders thought they’d use? A technical founder who can point to a product with clear usage patterns, who can explain why certain features were prioritized over others, and who can show velocity of iteration—this is someone who can execute.
For non-technical investors evaluating technical capability, bring in a technical advisor or co-investor. There’s no shame in admitting you can’t assess code quality or architecture decisions. What would be a shame is investing based on a superficial assessment that turns into a technical debt problem you can’t escape.
The practical takeaway: require a live product demonstration with real customer data. Ask founders to show you their analytics, feature usage data, and defect rate. Ask them to explain the last significant technical decision they made and why. If they can’t explain it in terms a reasonably intelligent person could understand, they may not have the technical judgment needed for the long haul.
The most common startup failure mode I see—and the most preventable—is a founding team with a massive skill gap nobody acknowledges. Usually, this looks like two technical founders with no business or go-to-market experience, or two business founders trying to manage a technical product they don’t understand.
The ideal founding team covers core functional areas: product and technology, go-to-market and sales, and operations and finance. You don’t need all three at day one, but you need a credible plan for how these functions will be handled. A two-person team with one technical and one business founder is stronger than a three-person team where everyone has the same background.
What I look for beyond the resume is whether founders can articulate what they don’t know and why their co-founder complements them. If a technical founder tells me their co-founder handles “all the business stuff,” that’s a red flag—they haven’t thought specifically about what business stuff needs to be done or whether their co-founder is actually good at it. If a founder tells me “I’m the technical one and [name] handles sales, specifically enterprise SaaS sales, and they’ve personally closed deals at companies like [specific examples],” that’s someone who has thought about complementarity concretely.
The practical takeaway: map each founder’s primary functional responsibility and then test their knowledge of adjacent areas. A product founder should understand enough about marketing to explain their acquisition channels, even if they don’t build the campaigns. A sales founder should understand enough about product development to explain their feature roadmap, even if they don’t write code. Deep expertise in one area with reasonable fluency in others is the profile that survives the inevitable moments when someone is unavailable.
This is the factor I see investors skip most often, and it’s one of the strongest predictors of team failure. People who have never worked together don’t know how they conflict, don’t know how to resolve disagreements, and don’t have the trust foundation to survive startup stress.
I strongly prefer founding teams with prior working relationships—whether from the same company, the same university research group, or a previous venture. I want to know how they resolved disagreements in the past, not hypothetically, but with specific examples. What was the last significant conflict they had, and how did they work through it? What is each founder’s communication style under stress?
A word of caution: prior collaboration history only matters if it was a positive experience. I’ve seen teams who co-founded after working together at a company where one person was the manager and the other was the report—the power dynamic was never addressed, and it surfaced as a major problem once they were equals in their own company. I’ve also seen co-founders who were best friends in college and had never worked together professionally. Friendship isn’t a proxy for working compatibility.
The practical takeaway: require at least one specific story about a past collaboration that went poorly and how they resolved it. The ability to navigate conflict is more important than the absence of conflict. Teams that have never disagreed probably haven’t been in situations stressful enough to surface disagreement.
Startups are fundamentally learning exercises. Founders who succeed absorb new information, update their beliefs quickly, and act on what they’ve learned. This sounds obvious, but it’s actually quite rare. Many founders are convincing in the moment and then revert to their original positions when pressure mounts.
Assessing coachability is tricky because you want founders confident enough to make hard decisions with incomplete information but open enough to recognize when they’re wrong. The worst profiles are founders who are unshakeably certain of everything (they’ll double down on failing strategies) or always looking for external validation (they’ll chase whatever new idea someone suggests).
I assess learning velocity by asking about specific belief changes. When did a founder last change their mind about something significant based on new information? What was the evidence that caused the change, and how quickly did they adjust? This is more revealing than asking whether they’re “open to feedback”—everyone says yes to that question.
I also look at how founders handle questions they don’t know the answer to. Do they improvise confidently, making things up? Do they get defensive? Or do they say “I don’t know, let me think about that and get back to you”—and then actually get back to you with a thoughtful answer? The third response is what you’re looking for.
The practical takeaway: ask founders about a specific time they changed their mind and why. Then verify the change actually happened by asking about the timeline and evidence. Watch for founders who claim to be constantly learning but can’t articulate a single concrete belief update from the past year.
Startup founders face a specific psychological profile that correlates with success: high tolerance for ambiguity, ability to function while receiving contradictory feedback, persistence through extended periods of uncertainty, and most importantly, the capacity to experience failure without having it define their self-worth.
This is the hardest factor to evaluate in a short meeting, but there are reliable proxies. How did the founders handle the pandemic? How did they respond to the market correction in 2022? Ask about their lowest point in the past year—not to make them uncomfortable, but to see whether they’ve processed difficulty in a healthy way. Founders who are still bitter about past failures, or who describe themselves primarily through their failures, may lack the psychological resilience needed. Founders who can describe difficulty with perspective, who can acknowledge their own role in what went wrong without spiraling into self-blame, and who can identify what they gained from the experience—these are the ones with the right psychological profile.
I also pay attention to how founders talk about competitors. Those who describe competitors as “dumb” or “lucky” are usually projecting. Those who can articulate what competitors do well, what they might do next, and what the founder would do differently if they were running that company—that’s someone with a realistic assessment of their environment.
The practical takeaway: look for evidence of psychological resilience in how founders talk about past difficulties, not in the difficulty itself. The goal isn’t founders who have never failed—the goal is founders who have failed and emerged with their confidence intact and their judgment improved.
Beyond positive evaluation criteria, there are specific patterns that should give any investor pause. The first is a solo founder with no plan to fill critical skill gaps. I understand the appeal of a single founder with total control—the data, however, is clear: funded companies with solo founders underperform at every stage. If you’re considering a solo founder, require a specific, credible plan for adding co-founders or senior talent within the first six months.
The second red flag is misaligned equity. If co-founders have equal equity but vastly different time commitments, commitment levels, or risk profiles, that’s a structure that will create resentment. I want to see equity splits that reflect actual contribution and ongoing risk—and I want to see that those conversations happened explicitly, not that they were avoided because they were uncomfortable.
The third red flag is founders primarily motivated by the startup lifestyle rather than the specific problem. Someone who wants to “build a company” and is searching for a problem to solve is fundamentally different from someone who can’t stop thinking about a specific pain point and has decided building a company is the only way to address it. The first profile will move on to the next idea when this one gets hard. The second profile will find a way to make it work.
The fourth red flag is an inability to articulate why this company, why now. If founders can’t explain specifically why this particular market opportunity exists at this particular moment—and why they specifically are positioned to capture it—they probably haven’t thought about it enough. The best founders can tell you exactly what shifted in the market (technology, regulation, consumer behavior) that made this idea viable now when it wasn’t viable five years ago.
The practical takeaway: treat red flags as eliminators rather than discount factors. A great team with one concerning pattern might be worth investing in with additional oversight. A great team with three red flags is likely to fail, and no amount of upside makes that risk worthwhile.
All of these factors should emerge through conversation, not through a checklist of questions asked and answered. The best investor-founder meetings feel like intellectual conversations between people who understand the same domain—not like job interviews. Let the conversation wander. Ask about what the founder read recently. Ask about what they disagree with you on. Ask about what keeps them up at night. These tangential discussions reveal far more than structured questioning.
As you develop your own evaluation framework, recognize that every investor’s priorities differ based on their thesis, their network, and their own strengths and weaknesses. An investor with deep healthcare expertise will naturally weight domain experience differently than a generalist investor. The important thing is to have a framework, to be consistent in applying it, and to recognize when you’re deviating from your criteria because a founder is particularly charismatic or the deal flow is thin.
The investors who do best over time are those who have developed strong conviction in what they look for and who stick to that standard even when it means passing on popular deals. The moment you start compromising on team quality because the deal looks exciting or because you haven’t found anything else in weeks, you’ve already begun the calculation that leads to write-offs.
The startup landscape continues to shift in ways that affect how we evaluate teams. Remote and distributed teams are now standard rather than exception, which changes how we assess collaboration history—founders who’ve never met in person now routinely build successful companies, and our evaluation frameworks need to account for that reality.
Similarly, the rise of solo founders building with AI-assisted development tools is creating new patterns we don’t have good data on yet. The traditional argument against solo founders—that they can’t cover all the necessary skills—weakens when one person with AI tools can effectively do the work of a small team in the early stages. This is an area where my own framework is evolving, and I expect the next few years of data will reshape conventional wisdom significantly.
What remains constant is that teams matter more than ideas, that execution beats strategy, and that the qualities that make founders successful are identifiable if you’re willing to look past the pitch deck. Develop your framework, apply it consistently, and trust your judgment. The best investors aren’t those who never make mistakes—they’re the ones who make consistent mistakes that they can learn from.
If you're raising seed funding for the first time, you'll encounter two instruments that sound…
The way you structure your first external fundraising round will shape your company's trajectory for…
Every founder eventually faces the moment when someone asks the question that cuts through all…
If you're raising capital for the first time, the moment you sign a term sheet…
The startup world throws around "product-market fit" like it means something fuzzy and inspirational. It…
If you're raising capital or issuing equity to early employees, the cap table determines who…