It is almost a law in early-stage investing that you back the team over the idea, because the idea will change and the team is what survives the change. Most founders have heard this. Far fewer know what an investor is actually looking at when they say they are evaluating the team, which is a more specific thing than "are these people impressive."
This article is one in a series. The series discusses the method we use to judge whether a business plan is fundable. We have developed a multipart weighted scorecard, based partly on research into best practices and partly on my experience in the startup and venture space: five startups, two exits, startup investing, and founding a startup accelerator. There will be one article for each scoring category, plus one on red flags.
There's a selfish reason for doing it in the open: we are building the methodology into a managed AI agent that evaluates plans against real investor decisions, and writing each part out is how we find where it's wrong. If you're raising funding for a startup, you get the rubric we would use to grade you. If you think we have weighted something badly, tell us. That's the most useful note we can get.
Team and founder-market fit carries the heaviest weight in our scorecard, tied with traction, and at the earliest stages it is effectively the whole bet. Before there is a product to judge or revenue to count, the team is the asset. The takeaway is simple: this is the dimension where a vague, glowing assessment does the most damage, and where I try hardest to replace impressed with specific facts.
Founder-market fit is not a resume. It's an unfair advantage.
The phrase "founder-market fit" is often used as a synonym for "relevant experience," which sells it short. A strong resume is table stakes. What I'm actually hunting for is an unfair advantage: some reason this particular founder will see things, reach people, or move faster than a generically capable team attacking the same market.
That advantage comes in a few forms. Deep domain experience, where the founder has lived the problem from the inside and knows things outsiders would learn the slow and expensive way. A distribution edge, where they can reach the first hundred customers because of who they already are and who they already know. A technical edge, where they can build something most teams can't. The takeaway: the advantage should be hard for a competing team to replicate by hiring. If any well-funded group could assemble the same fit by posting a job, it isn't fit, it's a checklist.
The clearest version I look for is the founder who has personally suffered the problem they are solving. They tend to know the customer's behavior cold; they make fewer of the obvious early mistakes, and crucially they don't lose interest when the work gets boring, because the problem was personal before it was a company. That last part matters more than founders expect.
Lived it versus shipped it
Here is a distinction I want to sharpen, because the anchor for it is already fairly developed and I think it is the most useful cut on this dimension. There are two kinds of relevant credibility, and they are not the same, though decks present them as interchangeable.
"Lived it" means the founder has firsthand experience of the problem and the customer. They were the buyer, or they did the job, or they ran the team that suffered the pain. This builds belief in the problem, its urgency, and the customer's real behavior. It is the strongest input to founder-market fit.
"Shipped it" means the founder has built and delivered things before, ideally hard things, ideally to a finish. This builds confidence in execution: when they say they will build the product, ship it, and hire the team, they probably will. It is a different signal, and an investor weighs it differently.
The reason the distinction matters is that the two failure modes are opposite. A founder who has lived the problem but never shipped anything is a real execution risk, and the plan needs to address it, usually with a co-founder or early hire who has shipped. A founder who has shipped impressive things but has no lived experience with this particular market is a real risk for founder-market fit and is more likely to have invented the problem from a solution. The takeaway: the strongest teams have both somewhere in the founding group. When I score this dimension, I am partly asking which of the two a team has, and whether they've staffed the one they're missing.
The gap-closing plan is itself the signal
No founding team has every capability on day one. The plan implies a set of things the team must eventually do: build the product, sell to the buyer, navigate the regulations, and, almost always, there is a gap between what the plan requires and what the founders can currently do. This is normal and expected, and it is not what I penalize.
What I penalize is the team that hasn't noticed the gap. The strongest signal on this dimension is not a complete team; it is a team that can name precisely what it is missing and has a credible, specific plan to close it. "We are two technical founders, we know we can't run an enterprise sales motion, and here is the VP profile we're hiring in month six and the two candidates we've already started talking to" is a fundable answer to a real weakness. "We'll figure out sales later" is the same weakness with no answer, and it is far more disqualifying than the gap itself. The takeaway: self-awareness is what I'm scoring, because it predicts how the team will handle the dozen gaps they can't see yet.
Current view, subject to change
This is the dimension I am most confident about, which is partly a warning to myself. Years of pattern-matching on founders builds strong intuitions, and strong intuitions are exactly where bias hides. The same instinct that reliably spots a founder who has lived their problem also quietly over-rewards founders who look and sound like the ones who succeeded before, and that pattern has a demographic shape I don't trust.
So the place I most want this tested is here. We are building team assessment into a managed agent in part because a written rubric, applied the same way every time, can be audited for that bias in a way a gut call in a room cannot. If the agent's team scores correlate with founder outcomes, good. If they mostly correlate with founders resembling a familiar template, the rubric has laundered a prejudice into a number, and that is worse than useless. That finding would change not just a weight but how I think about my own judgment.
What I hold most firmly: the team that names its own gaps and staffs against them beats the team that looks flawless on paper. Awareness of weakness is the most reliable strength on this page, and that is the conclusion I want to leave you with.
Regards,
Charles Stack
Founder, Coworkers.Global