Stage 01
Discover
We build a map of what the organization can already do: its people, technology, data, intellectual property, customers, processes, regulatory position, and how each of those depends on the others. Dependencies and bottlenecks. Information flows and ownership structures. Recurring workarounds and institutional knowledge that no system records.
The objective is not to catalogue assets. It is to reveal latent value and missing connections. Opportunity exists where new connections can be made, and those connections are only visible when the organization is modeled as a whole. Discovery does not begin with a predetermined product or problem. It begins by determining what the organization is actually capable of.
Stage 02
Deconstruct
We separate what a capability fundamentally does from the assumptions, constraints, and historical context attached to its current use. Every asset has two parts. There is the essence, what it fundamentally is. And there is the surround of context: the current product it ships in, the department that owns it, the customers who expect it to behave a certain way, the regulation written around its original use.
GPS is precise location. Navigation is one application. Once the essence is separated from its original constraint, the same capability becomes logistics, insurance, agriculture, and emergency response simultaneously. The capability did not change. The context did.
Stage 03
Abstract
We identify the function underneath the asset: what it does, what problem that function solves, and where else the same problem exists at scale. A telephone network that already verifies its own subscribers is holding an identity business. A factory that already schedules its own machines is holding a scheduling business. A compliance team that has answered the same regulator four hundred times is holding a reference work.
In practice this means writing the capability down as a function with no industry attached, then searching for that function everywhere it is currently performed badly, expensively, or not at all. The output is a list of destination markets with the evidence for each, not a description of what the asset is.
Stage 04
Evaluate
We test each possibility against market demand, economics, law, technology, timing, capital, and execution risk. Most possibilities should not survive. The objective is not to produce more ideas. It is to be able to say why these three and not the other forty.
This stage is often absent from commercialization processes. Without it, abstraction produces a list of ideas rather than a set of viable paths. The rejected paths stay on the record, because knowing why forty were dropped is worth more than the forty.
Stage 05
Engineer
We design the legal, technical, commercial, and operational architecture required to make the opportunity viable, defensible, and scalable. Legal rights, technical feasibility, commercial economics, governance, intellectual property, privacy, and market adoption are not sequential workstreams. They are simultaneous design constraints on one structure.
Most organizations treat these as separate disciplines handled by separate functions. We treat them as one engineering problem. The structure that emerges is designed to align the incentives of every party required to make it work.
Stage 06
Realize
We build the opportunity in whichever form holds its value best: a product inside the business, a new service line, a licensing portfolio, a partnership, a joint venture, a spinout, an independent company, or a capability packaged so that someone will buy the whole of it.
We are not attached to a predetermined implementation model. The opportunity determines the structure. Value capture follows the same logic: fees, licensing, equity, IP ownership, market access, or data rights, depending on what the opportunity and the organization actually require.
