Designing a founding team before there's a company to hire into

Most founding teams are not designed. They are assembled from whoever was in the room when the idea got serious: a friend with the right skills, a co-founder found through an intro that happened to land at the right time. None of this is a criticism. It is just how most companies start. It is also, quietly, the first design decision a venture makes, and it usually gets made by circumstance rather than by what the idea actually requires.

What does an idea actually require, before there's a team?

Every real idea implies a set of capabilities long before it implies a team. A marketplace idea implies someone who can solve the cold-start problem on both sides at once. A regulated product implies someone who can navigate compliance without slowing the build to a crawl. A hardware idea implies someone who has actually shipped a physical product before, not just designed one. None of this shows up on a whiteboard when two people decide to start a company together. It only becomes visible later, usually as a gap nobody planned for.

What goes wrong when the team gets assembled by availability instead of requirement?

Two patterns, and they are opposite failures.

Overlap: two co-founders with genuinely similar strengths, both good at the same thing, and the capability the idea actually needed, sales, or regulatory navigation, or deep technical execution, has nobody clearly responsible for it. It gets absorbed as a side task by whoever has the least on their plate that month, which is a different person every month.

Gaps disguised as personality: the classic "we'll figure out sales later" or "one of us will pick up finance." This is not a plan, it is a hope, and it is usually only noticed once the idea has already scaled past the point where figuring it out on the fly is fast enough.

How would you design a founding team on purpose?

Start from the idea, not from who's available. List what the idea genuinely requires to go from validated to built to sold, capability by capability, the same way you would map capabilities against a scaling company's goal. Then look at who's actually in the room and where the honest gaps are. A gap is not a reason to abandon the idea. It is a reason to know, precisely, what to look for in the next person, instead of hoping the right person appears.

This is the same discipline as writing a role canvas before a job posting, just run before the roles, or the company, exist yet. Purpose, outcomes, decisions, interfaces, defined against the idea's actual requirements, not against two people's existing skills and a vague sense that it will work out.

Isn't this something a venture studio or investor should already be doing?

Some do, informally: a partner's gut sense that something's missing in a founding pair, rarely written down, rarely applied the same way twice. That inconsistency is the actual gap. A studio assembling multiple ventures, or an investor evaluating several founding teams a year, benefits from doing this the same rigorous way every time, for the same reason a repeatable diagnostic beats a one-off gut check anywhere else in this practice.