Stage 01
Discover
We model the organization's capability graph: people, technology, data, intellectual property, customers, processes, regulation, and the relationships between them. 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 transferable function beneath the asset: what it does, what problem that function solves, and where else the same problem exists. This is where telecommunications can become identity, manufacturing can become optimization, and legal compliance can become structured knowledge.
Abstraction is a disciplined analytical exercise, not a creative one. It requires holding a capability entirely outside its original organizational, technical, and commercial context and asking only: what is the underlying problem this solves, and where else does that problem exist at scale?
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 maximum ideation. It is defensible selection.
This stage is often absent from commercialization processes. Without it, abstraction produces a list of ideas rather than a set of viable paths. Evaluation is the discipline that converts possibility into probability. The rejected paths stay visible, because disciplined rejection is evidence, not waste.
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 materialize the opportunity through the structure best suited to preserve, scale, and capture value: an internal product or operating system, a new service or revenue line, a licensing portfolio, a strategic partnership, a joint venture, a corporate spinout, an independent venture, or an acquisition-grade capability.
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.
