How to Build a Founding Team From Scratch

Most early-stage advice about founding teams focuses on the obvious: find someone technical if you're a business person, find someone who can sell if you're an engineer. That's not wrong, but it's not where founding teams actually fail. They fail because of trust, working styles, and misaligned expectations — none of which show up on a resume or a skills matrix.

The Skill Gaps That Actually Matter

The real question isn't "do we have a technical person." It's: which functions are so core to your specific business that they need to be in the founding team?

For most product startups, you need someone who can build the thing and someone who can sell it. But "build" and "sell" are broad. A founding engineer at a deep-tech company needs different skills than one at a consumer app. A "sales" co-founder at an enterprise startup is doing enterprise relationship-building, not growth hacking.

Map the first 18 months. What are the 4-5 things the company absolutely must do to survive? Who is doing each of those? The gaps that aren't covered by you or anyone committed to the company are the gaps you need to fill.

There's also a second category: judgment gaps. You want at least one person who has done some version of this before, or who has worked closely with someone who has. Pattern recognition is underrated in early-stage companies.

Evaluating a Potential Co-Founder

Do a project together before you commit. Not a long one — two or three weeks of meaningful work. It's the fastest way to see how someone actually operates: do they ship, do they communicate proactively, do they make good decisions under uncertainty, can they handle being wrong?

Questions worth answering before the decision:

• How do they handle disagreement? Have a real argument with them about something that matters and watch the process, not just the outcome.
• What do they want from this? Not "what's their ambition" but what do they actually want — money, status, learning, proving something? These shape behavior in ways that get hard later.
• What's their risk tolerance? This one is underestimated. If one founder can't afford to not have salary within six months and the other has two years of runway personally, they will make very different decisions.
• Do they have the time? Part-time co-founders can work in very early stages, but you need to be explicit about what that means for equity and decision-making.

Reference checks matter here more than anywhere else. Talk to people who have worked with them under pressure, not just people they listed.

The Dynamics That Predict Failure

Most founding team failures trace back to a small number of patterns:

Unequal commitment without equal conversation. One person starts working full-time while the other stays in their job "for a few more months." This creates resentment, then fights, then usually a split.

Overlapping roles without clear ownership. Both founders are doing "everything," which means both founders are second-guessing everything. Every important decision becomes a referendum.

Different timelines to money. One founder needs the company to pay them in six months. The other doesn't. They're operating on fundamentally different risk profiles and rarely say so out loud.

Politeness instead of candor. Early founding teams are often friends, and friends are often polite. This is lethal in a startup. If you can't tell your co-founder that a decision they made was wrong, you're already in trouble.

When you're navigating the question of whether a specific person is right for a founding role, an outside perspective can help — whether from a mentor or a structured advisory resource like Founderboard, where you can pressure-test your thinking with advisors who've been through it.

The Hard Conversations to Have Early

You need to have these before they become urgent. They're awkward now; they're catastrophic later.

Equity. What's the split and why? Equal splits are common but not always right. If you have meaningfully different contributions, experience, or opportunity costs, equal equity can breed resentment. Whatever you decide, both people should be able to articulate the reasoning.

Vesting. Four-year vest with a one-year cliff is standard. Skipping vesting on the grounds that you trust each other is a mistake you'll regret the first time the other person leaves. Vesting protects both of you.

Salary. What are people taking home, and when? Zero is fine if everyone can sustain it. But "zero for now" needs an actual number attached — at what milestone does that change?

Roles. Who makes what kinds of decisions? Who has final say on product? On hiring? On fundraising strategy? You don't need an org chart, but you need to know who owns what.

Exit preferences. Do you both want to build a billion-dollar company, or would one of you take a $15M acquisition in year three? This sounds abstract until you're in a room with an acquirer.

Co-Founder vs. Early Employee

This is one of the more important decisions early on. The distinction matters legally, economically, and in terms of what you're asking someone to sign up for.

A co-founder is someone taking on founder-level risk — probably with limited or no salary, significant equity, and real decision-making power. An early employee is someone who's getting market-adjacent compensation, a smaller equity package, and a job rather than co-ownership.

If someone is joining after the company has traction, is getting salary from day one, and isn't taking on personal financial risk, they should probably be an early employee with a strong equity package — not a co-founder. The title confusion creates problems later: they expect co-founder treatment and you expect employee accountability.

The test: is this person a founder, or is this person the first person I'm hiring to help execute a vision that already exists?

A Note on Founder Count

Two to three founders tends to work well. Solo is viable (more on that in a separate piece). Four or more and you're already managing a small team before you've built anything, and decision-making gets slow.

The size that matters most isn't the headcount — it's whether the skills, temperament, and commitment are genuinely complementary. One great co-founder with whom you have complete trust is worth far more than three people who all bring capability but have friction.