What decision is the sponsor trying to make, and by when?
Turn the opportunity into something that can be tested.
We organize the sponsor goal, market demand, site and infrastructure, technical options, policy limits, commercial logic and key assumptions before expensive development work begins.
Each section explains the problem, the choices that matter and what it takes to move from planning to implementation.
Structure the work around evidence, ownership and the next decision.
We organize the sponsor goal, market demand, site and infrastructure, technical options, policy limits, commercial logic and key assumptions before expensive development work begins.
INDUX treats project development as a sequence of decisions rather than a collection of reports. Each workstream should reduce uncertainty, identify the owner of the next action and make it clearer whether the project should advance, change or stop.
Development principle: do not spend the next dollar of development capital until the project team knows which uncertainty that dollar is intended to reduce.
Good diligence is specific enough to expose what is still unknown.
These questions are not a generic checklist. They represent the types of uncertainties that can change project scope, economics, timing, ownership or the willingness of a public or private partner to proceed.
Who has the problem, who pays, and what evidence proves demand exists?
Which land, power, water, logistics, digital or utility dependencies could block the project?
What technical alternatives should be compared before selecting a solution?
Which licenses, policy decisions, rights, standards or public approvals determine feasibility?
Which assumptions are facts, which are estimates, and who owns the next validation step?
Feasibility is a connected argument, not six independent studies.
A project can be technically possible and still fail commercially, financially, legally or operationally. The development team needs one view showing how those dimensions interact.
Separate facts from estimates before they become model inputs.
An assumption register should record the statement, evidence source, confidence level, owner, validation method, deadline and what decision changes if the assumption proves false.
Illustrative format only. The examples above do not describe a current INDUX project.
Advance, revise, hold or stop.
A disciplined gate review protects development capital. Every gate should state the evidence reviewed, unresolved conditions, required approvals, next budget and named owners.
Advance
Evidence supports the next level of development spend.
Revise
The opportunity remains viable but scope or structure must change.
Hold
A dependency must be resolved before additional development.
Stop
Evidence no longer supports the original project thesis.
Track the few indicators that show whether the work is becoming more investable.
These are illustrative metric categories. Actual measures depend on sector, project stage, financing and approved project data.
Every deliverable should answer a decision.
INDUX can tailor the depth of work to project stage. The objective is not document volume; it is a controlled package of evidence and analysis that helps stakeholders make the next decision with less ambiguity.
Project thesis & opportunity brief
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Demand and offtake evidence pack
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Site / infrastructure dependency map
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Technical options and screening matrix
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Policy / legal / approval register
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Assumption register and next-gate recommendation
Purpose, assumptions, source evidence, decision owner and next action can be attached to the work product.
Turn the next project decision into a structured workstream.
Bring the country, sector, project stage, sponsor, known constraints and the decision that is blocking progress. INDUX can help organize the evidence, economics, partners and implementation path.