Qatar's manufacturing strategy: translate ambition into a bankable plan

The first component of a bankable plan is demand that has been established rather than assumed. That means identifying which customers, in which segments, currently purchase the product or a substitute, from where, at what delivered cost and to what specification.

Where a proposition may depend on a small number of large buyers, its risk profile differs from one serving a broad base, and the plan should state which it is: customer concentration, order size, contract length and the realistic prospect of winning share from an incumbent. Whether that concentration exists for your product is a project-specific question to be tested with named buyers, not assumed from the country.

The same discipline applies to export propositions. Regional demand should be evidenced for the specific destination and product rather than extrapolated from a national target, and the plan should record what evidence would change the conclusion.

A useful test is to ask what the project would look like if its largest prospective buyer did not order. If the answer is that the case collapses, then buyer concentration is the project's central risk and should be treated as such — with a named, confirmed counterparty rather than an assumed one.

Capability covers the technical ability to produce to specification and the organisational ability to operate reliably. For a manufacturer new to a product, this usually means a technology partner, a licensed process or a recruitment and training plan — each with a cost and a lead time that belongs in the plan.

Input resilience deserves particular attention where a project depends on imported material. The relevant questions are project-specific: the number of viable supply routes for each critical input, the lead time and variability of each, the working capital implied by holding sufficient inventory, and whether any critical input has a single realistic source. These must be established for the inputs the project actually uses rather than inferred from the country's overall trade position.

Operating economics is where the plan either closes or does not. It needs a defensible cost structure including energy, labour, consumables and logistics; a costing of the utilisation ramp; and a cash flow that reflects the working capital build during that ramp. The test is not whether the project is attractive at full production, but whether it survives the period before it gets there.

Milestone plans in early-stage projects often track activity: a feasibility study completed, a site identified, a partner approached. These are easy to record and tell you little. A more useful milestone tests an assumption that could stop the project.

The strongest milestones are those that would change the decision if they failed. A confirmed purchase intention from a named buyer at a stated specification and volume. A tested, documented input supply route. A validated process yield at pilot scale. A cost estimate supported by quotations rather than indicative figures.

Arranging milestones this way means the project's own governance becomes the mechanism for discovering problems early, when they are cheap to address — rather than at the point of capital commitment.

Support comes in forms with very different evidential weight, and the plan should treat them differently rather than grouping everything under one heading. The distinction that matters is whether the benefit is legally secured and contractually committed, or discretionary and unconfirmed.

A benefit that is legally secured — a signed agreement, a contracted grant with defined milestones, or a tax treatment already established in law and applicable to the project — can legitimately enter the base case, provided its terms are set out and the counterparty risk assessed. Counterparty risk includes the payer's ability and willingness to perform, the conditions attached, the timing of receipt relative to the project's cash needs, and what happens if a condition is not met. A secured benefit modelled without those terms is still an assumption, not a certainty.

Discretionary support that is not yet confirmed belongs in the sensitivities, not the base case. Where eligibility is untested, terms are unpublished, or the benefit depends on a future administrative decision, it should be modelled as an upside case that improves the outcome if it lands. The base case is then whatever remains after the unconfirmed items are stripped out — which is the number that determines whether the project can proceed at all.

The reason for this discipline is not that support is unreliable. It is that a plan which cannot distinguish a contracted benefit from a hoped-for one cannot tell its own stakeholders which risks it is carrying. A project that requires discretionary support on day one to service its debt has a materially different risk profile from one that is viable without it and treats any support as improvement.

The general caution is that a plan whose unconfirmed assumptions are load-bearing is under-tested at the point of capital commitment. That is a statement about evidence, not about whether any particular project can be financed — a project with secured, well-termed support and demonstrated commercial fundamentals is in a different position entirely from one whose case rests on support that has not yet been granted.