Most startup advice is based on models, frameworks, and best practices. Those are useful — but they often hide how
things actually unfold in real situations. One of the reasons is that key shifts — in ownership, control, or
direction — are often gradual and not immediately visible when they happen.
The founder lessons on this page are based on my own experiences in building technology-driven startups. They
reflect situations I have been directly involved in, where decisions about technology, ownership, team structure,
and strategy played out over time — often in ways that were not fully anticipated at the start.
These are not success stories or failure stories in the usual sense. They are attempts to make sense of what
happened, and to extract lessons that are relevant for technically oriented founders who are navigating these
questions for the first time.
Each case highlights a specific mechanism — such as how ownership translates into control, how technical risk
accumulates, or how intellectual property shapes strategic options — and shows how these mechanisms play out in
practice.
In the early stages of a startup, roles and responsibilities often feel fluid. But as soon as shares are allocated,
those informal arrangements become formal structures of control. In this case, experienced managers were brought in
to strengthen our company — a logical step that gradually evolved into a shift in ownership.
A specific clause, triggered by securing funding, gave the management team additional shares. What initially seemed
like a reasonable incentive resulted in a majority position, and with it, full control over decisions. From that
moment on, technical direction and strategic choices could no longer be influenced by us, the original founders.
What started as an exciting opportunity — combining an existing academic technology with a new application — quickly
turned into a lesson about timing and intellectual property.
The underlying technology had already been published, which seemed to make it freely usable. But once the
application was validated, the university filed a patent on the combination — and secured a position in the startup
as a result.
This case shows how intellectual property does not only depend on whether something exists, but also on who defines
and claims the application. It illustrates how ownership can emerge from collaboration, and how early-stage
decisions around disclosure, validation, and patents can shape the structure of a company before it even fully
exists.
Developing new technology always involves uncertainty. But when multiple uncertainties are combined into a single
development step, the risk increases disproportionately. In this case, several technical challenges were addressed
simultaneously, making it difficult to isolate problems when the system failed to perform as expected.
From an investor's perspective, this kind of risk stacking makes a startup difficult to evaluate and fund. Without
clear validation of individual components, it becomes unclear whether the technology can be made to work at all.
This lesson highlights the importance of reducing uncertainty step by step — both for technical progress and for
attracting investment.
