From Idea to Company: How We Build New Ventures

Almost every new venture begins the same way: someone notices a gap. A product that does not exist yet, or exists but is done badly, or exists but is not sold to the people who would actually want it. The idea itself is rarely the hard part. Most experienced operators can generate a plausible business idea in an afternoon. What separates an idea from a company is everything that happens between noticing the gap and actually building something that fills it — and that is where most ventures fail, long before the market ever gets to judge them.

The idea is rarely the problem

When we look at a new venture opportunity, we try to resist the temptation to fall in love with the idea itself. An idea is cheap to have and expensive to be wrong about. The real question is never "is this a good idea" in the abstract — it is whether the idea survives contact with the specific, unglamorous details that determine whether it can actually be built, sold, and operated at a profit. Most good ideas do not fail because they were bad ideas. They fail because nobody stress-tested them before capital was committed, and the stress test happened after the money was already spent.

This is why we treat validation as a distinct phase, not a formality on the way to the part we are actually excited about. Before we commit meaningful capital to a new venture, we want to know — as concretely as possible — what it will cost to produce, who will actually buy it, at what price, and through what channel. If we cannot answer those questions with reasonable confidence, we have not yet earned the right to write a large check, no matter how good the idea sounds in a room.

Real partners, not assumed ones

A recurring mistake in early-stage venture building is planning around a supply chain or a technology partner that does not yet exist in any concrete form — a plan that says, in effect, "we will find a manufacturer" or "we will find the right technology" as if that step were a formality to be handled later. We try to invert that order. Before we commit to a venture, we want to have identified real manufacturing or technology partners, understood their actual capabilities and constraints, and confirmed that what we intend to build can genuinely be built at the quality and cost the plan assumes. A venture plan built on a partner who might exist is not a plan; it is a hope with a spreadsheet attached.

This is slower than simply deciding to build something and figuring out production later. We think that is the correct trade. Sourcing a real partner early exposes the assumptions in a plan far more honestly than any amount of internal analysis can — a manufacturer will tell you, quickly and concretely, whether your cost assumptions were realistic in a way that a business plan never will.

Unit economics before scale

Once we are confident a venture can be built, the next discipline is proving that it works economically at small scale before spending to grow it. It is entirely possible to build a product that works, find people willing to buy it, and still lose money on every unit sold once real costs are accounted for. Scaling a venture with broken unit economics does not fix the problem — it multiplies it. So before we increase spend on production, marketing, or headcount, we want to see, with real numbers rather than projected ones, that the venture makes sense at the margin. Growth should amplify something that already works, not paper over something that does not yet.

A controlled launch, not a bet

The last discipline is in how a venture actually reaches the market. We are wary of the big-bang launch — the moment where a large amount of capital is committed to marketing and distribution all at once, on the assumption that the earlier work was sound. We prefer a launch that is controlled and evidence-based: reaching a limited market first, watching how real customers actually behave, and only then increasing exposure once the evidence supports it. This is less dramatic than a full launch, and it is also considerably less risky, because it lets reality correct the plan before the plan has consumed all the capital allocated to it.

Future Tech Manager, a venture currently in development within our portfolio, is a live example of this thinking in practice. It is a new line of automotive care products, designed and manufactured in Europe, and it has gone through exactly this sequence — identifying real manufacturing partners, working through product and cost validation, and building toward a controlled commercial launch rather than a large one. It is not yet commercially available, and we would rather take the time to get the sequence right than rush a launch that has not yet earned it.

None of this guarantees a venture will succeed. What it does is make sure that when a venture fails, it fails for a real reason — a market that did not want the product, a cost structure that could not be fixed — rather than for the avoidable reason of capital committed before the idea was actually tested.