Building the founding team before you build the product

In the Create stage a validated opportunity becomes a company: proposition, brand, product architecture, financial model and team. Of those, the team decision is the one that is hardest to reverse and most often taken casually — assembled from who is available rather than from what the venture requires.

Four capabilities, not four founders

Every venture we have built needed the same four capabilities present from the beginning. They do not map to four people. Two people can cover them; occasionally one exceptional operator covers three badly and one well, which is a warning sign rather than a saving.

The most common gap is commercial. Technical founding teams frequently build for eighteen months before discovering that nobody in the team knows how to run a sales process, which turns Launch into a rebuild rather than a release.

What a venture builder changes

In the venture builder model, several of these capabilities are supplied by a permanent team that works across ventures rather than by early hires who must be recruited, paid and retained by a company with no revenue. Product, technology, brand and go-to-market are available from day one and reduce as the venture builds its own capability. That structural difference is explained in what is a venture builder?, and it is why our ventures typically start with a smaller cap table and a larger effective team.

Decide these five things before the work starts

1. 01Roles and decision rights — who decides what, and what requires agreement.
2. 02Equity and vesting — settled in writing, with a schedule, before the first line of code.
3. 03Commitment — who is full-time, from when, and what happens if that changes.
4. 04The first milestone — what the team is collectively accountable for reaching.
5. 05Exit from the arrangement — how someone leaves without damaging the company.

Hiring before there is a product

Early hires are not junior versions of later hires. They are people who can operate without process, choose their own priorities correctly, and do work outside their job title without resentment. Filter for judgement and appetite over credentials. The specific test we use is simple: can this person describe, unprompted, the two or three things that would most move the venture forward this quarter?

That final row is the transition most companies handle worst, and it is a structural problem as much as a people problem — a subject we cover in structuring a venture for scale.

A founding team is not assembled once. It is composed for the stage the company is in, with an honest view of the stage that comes next. The work in Create is to get the first composition right and to make the later changes possible without breaking the company.

Coverage, credibility, capacity

When we assess a proposed founding team we apply three tests in order, and a team can pass the first and fail the other two. Coverage asks whether the four capabilities are genuinely present rather than nominally assigned. Credibility asks whether this specific team is believable to the specific buyer — in regulated and specialist markets, buyers are unusually sensitive to whether the people selling to them have done the job themselves. Capacity asks whether the people named actually have the time the venture needs, which is the test that most part-time founding arrangements fail.

Founder disagreement is a design problem

Founding teams rarely fail because people dislike each other. They fail because two capable people hold genuinely different views about direction and there is no agreed mechanism for resolving it. Deciding in advance who holds the final call on product, on commercial strategy and on hiring removes most of that risk at no cost. Doing it later, during the disagreement, is significantly harder and tends to end relationships rather than arguments.

In our ventures the operating cadence carries a good deal of this weight: a short weekly rhythm where decisions are recorded and revisited on evidence rather than on the strength of the last conversation. It sounds procedural, and it is. It is also the reason a small team can move quickly without gradually losing shared understanding of what it is doing.