WORKING PRINCIPLES
What is different about how we work
We start with the decision, not the deliverable
Most engagements fail because the wrong question gets answered well. Before analysis begins, we map the actual decision — the options, constraints, timeline and criteria for a good outcome. Scope follows from that, not from a standard template.
We go to primary sources
Scientific literature, patent filings, technical documentation, expert interviews with scientists and engineers who work directly in the relevant technology. We do not build analysis on top of analyst reports. This is slower, but it produces a view that is genuinely differentiated.
We show our reasoning
Our outputs include explicit assumptions, scenario structures and sensitivity analysis. Clients see the logic, not just the conclusion — because deep-tech decisions involve genuine uncertainty, and a recommendation that hides its assumptions is not useful when conditions change.
We stay through the decision
We do not hand over a report and leave. We present to boards and leadership teams, answer questions, stress-test the analysis under challenge and help define the first implementation steps. The engagement ends when the decision is made.
ENGAGEMENT PHASES
Four phases, one continuous thread
Each engagement moves through four phases. The phases are sequential but not rigid — we return to earlier stages when new evidence changes the picture.
Frame the decision
Weeks 1–2We map the options under consideration, the constraints that are fixed versus flexible, the decision timeline and the criteria for a good outcome. We identify the key uncertainties — the questions whose answers would most change the recommendation. This phase ends with an agreed scope document.
Client deliverable
Scope document: decision map, key uncertainties, agreed analytical agenda
Build the evidence
Weeks 2–6Primary research to address the key uncertainties: technology readiness assessment from scientific literature and patent analysis; expert interviews; competitive landscape mapping; market and value-chain analysis from first principles. The depth and mix vary by engagement.
Client deliverable
Evidence base: technology assessment, expert interview synthesis, market analysis
Model the options
Weeks 5–8Structured strategic options with explicit assumptions and scenario analysis. Each option is assessed against the decision criteria from phase one. Sensitivity analysis shows which assumptions matter most and what would need to change for a different option to be preferred.
Client deliverable
Strategic options analysis: scenarios, recommendation, sensitivity analysis
Support the decision
Weeks 8–10We present to the relevant decision-makers — board, executive committee or investment committee. We prepare the client team for the questions they will face, stress-test the recommendation under challenge and refine as needed. After the decision, we help define the first implementation steps and the monitoring framework.
Client deliverable
Board-ready presentation, implementation roadmap, monitoring framework
ENGAGEMENT FORMATS
How engagements are structured
Strategy engagement
8–12 weeksA full engagement covering all four phases. Appropriate for significant investment decisions, market entry assessments or portfolio strategy reviews where the decision warrants deep primary research and structured analysis.
Technology assessment
4–6 weeksA focused engagement on technology readiness and commercial maturity. Appropriate when the primary question is whether a technology is ready, on what timeline and for which applications — rather than a full strategic options analysis.
Advisory retainer
OngoingStanding access to Asymm's perspective on a defined technology domain. Appropriate for organisations that need to assess new developments, evaluate opportunities as they arise and prepare for board-level discussions on technology strategy.
A decision that needs this kind of work?
We work with a small number of clients at any time. If you are facing a significant technology or market strategy decision, we would like to hear about it.