The use case is technology-led.
The team can explain what the startup does, but not yet which strategic system problem becomes materially better because the technology is present.
← How CompoundWorks works · Technology-to-System Fit Review
CORPORATE INNOVATION · VENTURE CLIENTING
The technology is interesting.
The question is where it creates strategic value inside your system.
Promising external technology does not create strategic value by being impressive in isolation. Its value depends on the role it can play inside an existing product, platform or operation — what it augments or replaces, which assets it can reuse, which dependencies it introduces and whether the combined system becomes materially more capable.
Bounded review · no prior Diagnostic Sprint required when the technology and strategic question are already identified.
The Review starts with the corporate system, not the startup pitch. The question is not whether the technology is interesting in general, but where it creates non-additive value inside the system you already own.
WHEN TECHNOLOGY SCOUTING BECOMES SYSTEM DESIGN
Finding promising technology is easier than deciding what it should become inside your system.
Innovation teams are good at finding technically interesting ventures. The harder decision begins after discovery: whether the technology strengthens an existing capability, replaces one, creates a new system role or simply adds another layer of complexity. A pilot launched before that decision is explicit can prove that the technology works without proving that it belongs.
The role inside the system is ambiguous.
It is unclear whether the technology should augment an existing capability, replace it, become a shared platform service or remain a specialist component.
Integration could consume the value.
The apparent benefit depends on data, interfaces, infrastructure, governance or operational changes whose cost and dependency implications have not yet been made explicit.
The pilot is being asked to discover the strategy.
A proof of concept is being prepared before the organisation has defined what the combined system is supposed to prove, reuse or change.
THE SYSTEM-FIT DECISION
Decide the role of the technology before deciding how to pilot it.
Technology-to-System Fit is a composition decision. The aim is not to maximise the amount of external technology adopted. It is to identify where combining startup capability with existing corporate assets creates value that neither side creates alone — and to make the system implications of that combination explicit.
01
Strategic value
Where does the combination create more than an incremental feature?
Identify the product, operational or platform outcome that becomes possible or materially better when the external capability is composed with assets the organisation already owns.
02
System role
Should the technology augment, replace, enable or remain outside the current system?
Define the target role clearly enough that product, platform and business owners understand what responsibility the external technology is expected to carry.
03
Integration boundary
What has to connect — and what new dependencies does that create?
Make interfaces, data, infrastructure, control, deployment and ownership boundaries explicit before integration work obscures the strategic decision.
04
Validation path
What would a pilot have to prove to justify the next commitment?
Translate the fit thesis into evidence: what must be demonstrated about value, integration, reuse, operating conditions and deployment before the organisation should proceed.
This is where Compound Innovation becomes an applied decision framework: not "is the startup interesting?", but "where can its technology create non-additive value inside the existing system?"
WHAT THE REVIEW ANSWERS
Turn external technology from an interesting object into a system decision.
- Should the technology augment an existing capability, replace one, enable a new system role or remain outside the current system?
- Where does combining corporate and startup capability create compound rather than merely additive value?
- What role should the technology own inside the target product, platform or operation?
- Where should the integration boundaries sit across data, interfaces, infrastructure, control and deployment?
- Which corporate and startup assets can be reused rather than duplicated?
- Which architectural or dependency implications could change the strategic case?
- What must a subsequent pilot prove before the organisation should make the next commitment?
THE OUTPUT
A system-fit decision package — not a technology scouting report.
- Augment versus replace decisionA clear decision on whether the external capability should strengthen an existing component, replace one, enable a new role or remain outside the target system.
- Where compound value existsThe specific combination of startup capability and existing corporate assets that creates a materially stronger product, platform or operational outcome.
- Target system roleThe responsibility the technology should carry inside the future system and the product, platform or operational context in which that role makes sense.
- Integration boundariesThe interfaces, data, infrastructure, control, deployment and organisational boundaries that define how the external capability connects to the existing system.
- Reusable corporate and startup assetsThe data, services, interfaces, workflows, IP, infrastructure or delivery assets that should be reused instead of recreated on either side.
- Architecture and dependency implicationsThe coupling, platform, deployment, governance and dependency consequences that could strengthen or weaken the strategic case.
- What a subsequent pilot must actually proveExplicit value, integration, reuse, trust and operating evidence required before a pilot can justify the next commitment rather than merely demonstrate technical feasibility.
The Review defines the system-fit decision and the evidence required to test it. It does not replace detailed solution engineering, procurement diligence, vendor selection or full pilot delivery.
BUILT FROM COMPOUND SYSTEMS
System fit is where technology strategy meets integration reality.
CompoundWorks is built from direct experience composing technologies inside mission-critical systems, shaping products and platforms across converging technology domains, and later seeing from the enterprise-adoption side what survives contact with real industrial environments.
NADS · SYSTEM INTEGRATION
Work where no technology creates value alone.
Built and scaled a 70+ FTE defence engineering business delivering €50M+ in mission-critical systems and R&D projects with the Spanish MoD, NATO and major industrial primes.
Evidence behind the Review: system boundaries · integration responsibility · multi-stakeholder environments · operational constraints
TMRW · COMPOUND INNOVATION
Shape product and platform roles across converging technologies.
Co-founded TMRW and helped scale it to 150+ employees after €10M+ funding while shaping products and platform concepts across XR, simulation, AI, digital twins and industrial systems.
Evidence behind the Review: convergence thesis · product role · platform logic · where combined capabilities create new value
THREEDY · ENTERPRISE FIT
See whether the technology fits the customer's operating system.
As VP Customer Success during Threedy's post-Series-A growth phase, worked on repeatable enterprise delivery and adoption across complex industrial deployments for OEM and Tier-1 customers.
Evidence behind the Review: enterprise integration · operating context · customer adoption · constraints that appear beyond the technology itself
The common pattern: external technology becomes strategic only when its role, boundaries and dependencies reinforce the system around it.
HOW THE WORK MOVES
Start with the system you own. End with a decision worth testing.
01
SYSTEM CONTEXT
Define the strategic problem before evaluating the technology
Map the relevant product, platform or operational context, existing capabilities, constraints and the outcome the organisation is trying to improve.
02
COMPOUND VALUE
Identify what becomes possible when the capabilities combine
Test where the startup capability creates new or materially stronger value when composed with corporate assets — and where it merely duplicates what already exists.
03
ROLE & BOUNDARIES
Place the technology inside the target system
Define augment-versus-replace logic, target system role, reusable assets, interfaces, dependencies and the architecture changes the combination requires.
04
VALIDATION PATH
Make the next commitment conditional on evidence
Translate the fit thesis into explicit pilot hypotheses, evidence and decision criteria so the organisation knows what must be true before proceeding.
WHEN THIS IS NOT THE RIGHT START
Use Technology-to-System Fit only when the decision is about where external technology belongs.
You are still scouting the market
If the organisation has not yet identified a specific technology or strategic question, this Review is premature. It is not a generic startup-discovery or technology-scouting service.
The pilot already proved value; rollout is now the problem
If the technology's role is clear and the challenge is why a successful pilot is not becoming repeatable operational deployment, use Pilot-to-Program instead.
See Pilot-to-Program →The intervention is already bounded
If the strategic role is clear and the remaining need is specifically architecture/composability, trust and deployment readiness, decision structure or partner design, start directly with the relevant Focused Domain Sprint.
See Focused Domain Sprints →The transaction question is whether the venture itself can scale
If the buyer needs independent evidence on whether a target company can support the growth or acquisition thesis, use Scale-Readiness Diligence rather than a system-fit review.
See Investors & M&A →WHAT HAPPENS NEXT
A good Review can justify a pilot — or prevent the wrong one.
Stop or defer
The combination does not create enough strategic value, the dependencies outweigh the benefit or the organisation is not ready to support the required system change. Not piloting is a valid outcome.
Pilot with explicit proof conditions
The fit thesis is credible. The organisation can proceed with a pilot designed to prove the specific value, integration, reuse and operating assumptions that justify the next commitment.
Pilot-to-Program →Resolve a bounded system change first
The strategic value is clear, but architecture, composability, deployment readiness or the partner model must change before testing the combination responsibly.
Focused Domain Sprints →A follow-on is not automatic. The Review is complete when the organisation can decide whether to stop, test or change the system first — and can explain the evidence behind that decision.
BEFORE THE PILOT BECOMES THE STRATEGY
Decide what the technology is actually for.
If promising external technology has already been identified but its strategic role, integration boundaries and system implications are still unclear, the Technology-to-System Fit Review is designed to turn interest into a decision worth testing.