There is no shortage of writing on building businesses. The startup canon is substantial and largely useful, even where it has hardened into orthodoxy. Corporate venture building has its own growing body of work, with practitioners and venture studios putting serious thinking on the page about why most corporate venture programmes fail and what would help them succeed. Anyone genuinely working in this space should read it.
What I want to add is narrower than that. Over the years I have helped clients build ventures alongside broader technology and innovation work, with a few of my own along the way. There is a set of patterns I have watched play out repeatedly, which the existing literature touches on but tends to underweight, and which are most easily described by going back to something almost embarrassingly simple. The basics. The same basics a child running a lemonade stand pays attention to without being told, and which most corporate ventures spend the early phase studiously avoiding.
A child running a lemonade stand knows what they are selling, knows who is walking past, knows whether the people they hoped would buy actually did, and knows whether anyone came back. These are the basics of a business, and a child running a lemonade stand spends most of their attention on getting them right. Most corporate ventures, by contrast, spend the early phase on documents, decks, valuations, and conversations with people who are not customers, while the basics of whether the product is any good and whether anyone wants it remain unanswered. What fails in most cases is the attention given to the work that would test the idea, rather than the idea itself, and good venture building is the discipline of putting attention where it belongs.
There are six basics, in my experience, that consistently determine whether a corporate venture succeeds or quietly unwinds. None of them are clever, and they are not new. What is consistently underestimated is how much attention each one needs, and how rarely the early phase of a venture actually delivers on any of them.
The product itself
A child running a lemonade stand tastes the lemonade before deciding to sell it. If it is not any good, they fix it before they put out the sign. This sounds obvious, and yet most corporate ventures launch without anyone genuinely happy with the product, because the conversation has been about positioning, market fit, and differentiation rather than whether the thing being sold is actually any good.
The basic question is whether the product, as it currently exists, is something the people building it would buy and use repeatedly, which is a different question from whether it is better than the alternatives or has a defensible market position. Most products that survive in the long run are products their creators were genuinely proud of in the short run, and most products that fail had a quality problem the founders quietly knew about before launch but did not address because the launch conversation had moved on.
In corporate venture work this gets missed because the people running the venture are rarely the people who would use it, and the people who would use it are not in the room. Fixing this requires getting the venture team into proximity with the actual product experience repeatedly, until they have an opinion about quality that is rooted in use rather than analysis.
The customer
A child running a lemonade stand knows their customers by sight. They know who walks past the house at four in the afternoon and they know which neighbours are likely to stop. They are not thinking about a segment or a persona. They are thinking about Mrs Patel, who walks her dog at the same time every day, and whether she likes lemonade.
Most corporate ventures cannot tell you who their first ten customers will be by name. They can describe a target segment, a buyer persona, a TAM, an addressable market. They cannot tell you who specifically is going to write the first cheque and why that particular person needed what they were selling. The shift from abstract segment to specific named person is not a marketing exercise. It is the move that takes a venture from theoretical to real, and it tends to expose where the actual business is, and where it isn’t.
The discipline here is finding ten people who are actually willing to use what you have built and learning everything about why. These are the people who have tried it, used it, and given you money or time or attention as a result, rather than the people who might in principle be interested. Until those ten people exist, the venture does not exist either, and what you have is a hypothesis rather than a business.
The end-to-end experience
A child running a lemonade stand thinks about the table, the cup, the smile, and the change. They might decorate the sign. They might offer a stronger pour to a customer who has come back. They are paying attention to the entire experience of buying lemonade from them, and not just the lemonade itself.
Most corporate ventures think about features. They build out the product capabilities, the integration points, the API surface, and the dashboard, while the experience of being a customer remains an afterthought addressed late in the build cycle. The result is products that demo well and use poorly, and customer journeys that look reasonable on paper and feel disjointed in practice.
The end-to-end experience is the part of the venture that survives contact with reality. It is what determines whether the first ten customers come back, and whether they tell anyone, which is the only marketing engine a venture has in its early phase. Getting it right requires the venture team to actually live through the experience repeatedly, end to end, including the awkward bits that nobody designed because they happen between the bits that someone did design.
Internal operating discipline
A child running a lemonade stand is one operator with one set of priorities working towards one outcome. The chain of command is short and the alignment problem does not arise.
A corporate venture has none of those things. There are directors, stakeholders, and sponsors. There is a parent organisation with its own priorities and its own constraints. There is a leadership team within the venture that may or may not agree on what they are building, why, or what success looks like. The alignment problem is large, and it does not solve itself.
Internal operating discipline in a venture means that the people running it are genuinely aligned on the same thing, and that the directors backing it are committed in the same way. Most failures of alignment are not visible at launch. They become visible at the first real difficulty, when the alignment that everyone assumed was there turns out to have been different versions of the same words. The director who thought they were backing a quick-win pilot is now in a board meeting with a founder who thought they were backing a multi-year build, and the conversation reveals that the assumptions on both sides were never tested.
Getting this right requires the alignment conversation to happen before the venture launches, in plain language, with the awkward questions actually asked. What are you committing to? How long are you genuinely willing to wait? What does failure look like for you, and at what point would you pull your support? Most corporate ventures do not have these conversations because they feel pessimistic at a moment when everyone wants to feel optimistic, and those are the conversations that determine whether the venture survives its first real test.
Visible spend before visible value
A child running a lemonade stand starts with whatever they have. A folding table, a jug, some plastic cups. The setup is functional and unremarkable, and nobody minds, because there is nothing yet to justify anything more than that.
Most corporate ventures get this exactly the wrong way round. The first visible work is rarely the product. It is the new office, the dedicated innovation centre with the exposed brick and the breakout pods, the premium laptops, the bespoke branding. The venture team gets shiny things long before it has delivered anything that justifies them, and the rest of the parent organisation notices.
I have watched this play out repeatedly inside large professional services firms and across client environments. The venture team gets the separate space, the better equipment, the freedoms the rest of the firm does not have, and the moment the early returns are not yet visible, which they will not be in year one because ventures take longer than that, the resentment that has been quietly building in the rest of the firm becomes the dominant narrative. The venture is no longer a strategic initiative the firm is proud of. It is the expensive thing in the corner that has not yet shown a return, and the political case for shutting it down is already half-written.
The discipline here is to keep the venture’s visible spend in proportion to its visible value. Spend goes on the product, on the customer experience, on the people doing the work. The trappings come later, if they come at all, earned by results the rest of the organisation can recognise. A venture that looks like a venture before it has delivered like one has handed its critics the argument they need before it has had a chance to make its own.
Shareholder commitment and selection
This is where corporate venture building most often comes unstuck, and it is the basic that gets discussed the least.
A venture does not just need shareholders. It needs the right shareholders, selected with the same care you would apply to a founding team. Money is the least important thing a shareholder brings, particularly in a corporate venture context where the cash often comes from a parent budget rather than from someone who has personally weighed the risk. What matters is whether the shareholder understands what they have backed, whether they have the right tolerance for the kind of risk the venture actually carries, and whether their incentives are aligned with the venture’s success on the venture’s timeline.
Corporate ventures get this wrong constantly. The sponsoring executive is enthusiastic at the launch, lukewarm by the second board meeting, and either disengaged or actively interfering by the time the venture hits a real difficulty. The misalignment is rarely about money. It is about whether the shareholder understood and committed to what they actually backed, which is a venture rather than a programme, a project, or a strategic initiative dressed up in venture language.
Selecting shareholders well means choosing people who have backed ventures before, who understand what the difficult phase looks like, and whose own incentives reward long-term venture success rather than short-term political optics. In a corporate setting that is genuinely difficult, because the people writing the cheque are often there for reasons unrelated to whether the venture succeeds. The discipline is to find the ones who are there for the right reasons, and to involve them properly from the start, so that the commitment is real rather than performative.
Why the basics get missed
The startup literature, the corporate innovation frameworks, and the venture studio playbooks all contain genuinely useful work. None of them are wrong about the things they cover. What I have noticed is that the basics tend to be assumed rather than examined, and the conversation moves quickly on to the more sophisticated work of methodology, governance structures, portfolio approaches, and stage-gate criteria.
The basics are unglamorous, and they are also the part of the work most often delegated to people who are not running the venture. The product quality conversation gets handed to a product manager. The customer conversation gets handed to a marketing function. The experience conversation gets handed to a design partner. The alignment conversation gets handed to nobody, and surfaces as a problem only when it is already too late.
Good venture building keeps the basics close to the people running the venture, treats them as the work rather than a precondition to the work, and resists the gravitational pull of the more sophisticated conversations that want to happen instead.
The question worth sitting with
If you are running a corporate venture, or sponsoring one, the question worth sitting with is whether the basics have been taken seriously. Is the product itself genuinely good, in the judgement of someone who has used it? Are the first ten customers real people whose names you know, or a target segment you have not yet tested? Is the end-to-end experience designed, or has it just emerged? Are the people running the venture and the people backing it genuinely aligned on what they are building? Is the visible spend in proportion to the visible value, or is it ahead of it? Are the shareholders the right ones, committed to the right thing, on a timeline that matches the venture’s reality?
If the answer to any of these is uncertain, the work of the venture is to fix that before it does anything else. The lemonade stand has the advantage of forcing those questions into the open. A corporate venture has to choose to ask them, repeatedly, against the pressure of every other conversation that wants to happen instead.
MultipleWorks works with organisations building ventures inside larger businesses, helping them get the basics right before the rest of the work piles in. If this article reflects something you are working through, get in touch at hello@multipleworks.com.hk.