Findings must connect to source logic
Decision teams should be able to see how a conclusion follows from data, institutional context, and assumptions.
Methodology
We begin with the decision a client has to make, then build the evidence map required to understand exposure, constraints, alternatives, and residual uncertainty.
Operating method
Human experts frame the question and interpretation criteria. Computational systems help structure data, surface patterns, and make large evidence sets easier to reason through. The final output is written for decisions, not for model demonstration.
| Stage | Output |
|---|---|
| Intake | Decision question, geography, sector, timeline, and constraints. |
| Evidence map | Products, suppliers, regions, policy exposure, and financing signals. |
| Decision memo | Findings, options, thresholds, uncertainty, and next actions. |
Process
Define the decision, stakeholder audience, time horizon, known constraints, and what a useful answer must resolve.
Assemble the relevant firms, suppliers, regions, products, contracts, policy rules, and financing relationships.
Identify concentration, substitution constraints, working-capital pressure, policy sensitivity, and missing information.
Translate findings into options, assumptions, thresholds, and next actions for leadership or operating teams.
Support follow-up review, supplier qualification questions, monitoring design, or briefing materials when the decision moves forward.
Quality standard
A useful advisory product does not simply describe complexity. It clarifies what is known, what remains uncertain, which exposures matter, and what choices are available.
Decision teams should be able to see how a conclusion follows from data, institutional context, and assumptions.
Concentration, tariffs, financing friction, or supplier dependency matter only when they change cost, continuity, or strategic options.
The final memo should support action: options, thresholds, residual uncertainty, and clear next steps.