How to know whether a feasibility study is actually decision-ready

Most feasibility studies get written. Few actually get used. The gap between the two is not a gap in research volume — it's a gap in decision clarity. A study that spends forty pages describing market size but never answers "should we proceed, and on what terms?" has failed at its most basic job.

After working on feasibility assignments across sectors including regulated financial services, extractive industries, food service, and market entry, the pattern is consistent: studies that inform real decisions share five structural features. Studies that don't tend to miss the same things.

1. The decision is named at the start

A decision-ready study opens with one question: what is the decision-maker trying to decide? Not "is there a market for X" but "should Organisation Y invest N amount to enter Market Z under the following conditions?" That specificity determines everything else — which evidence to gather, which assumptions to test, and what the final recommendation needs to say.

Studies that open with broad market descriptions or industry overviews are usually studies that were commissioned without a clear decision in view. The research then tries to be comprehensive rather than purposeful, and comprehensiveness is rarely what the decision-maker needed.

2. Assumptions are explicit, not embedded

Every feasibility study rests on assumptions. Revenue projections assume customer volumes. Cost estimates assume input prices. Regulatory timelines assume institutional responsiveness. The question is not whether assumptions exist — they always do. The question is whether they appear in the document clearly enough to be challenged.

A decision-ready study puts its key assumptions somewhere visible — often a summary table near the financial model — and explains the basis for each. This lets the decision-maker say "we believe volume will be lower than your projection" and see what that means for the conclusion without having to excavate the document.

Studies that embed assumptions in narrative paragraphs force the reader to hunt for them, and most decision-makers won't. The hidden assumption becomes the study's most dangerous element.

3. Evidence is domain-specific, not generic

A useful feasibility study on a Bureau de Change operation should contain specific data on CBN licensing requirements, recent changes to foreign exchange compliance requirements, actual street market demand patterns, and a realistic assessment of what it costs to run a compliant operation. A study that substitutes generic finance-industry paragraphs for this specific evidence has not done the work.

Domain specificity is hard because it requires actual research — not rephrased secondary sources. It requires understanding the difference between what a regulation says on paper and how it is actually enforced. It requires talking to people who operate in the space, not just reading reports about it.

When a client receives a feasibility study, a useful test is to ask: could this document have been written for any similar project in any similar sector? If the answer is yes, the specificity is insufficient.

4. Risk is treated as a real constraint, not a disclaimer

Risk sections in most feasibility studies are cover. They list everything that could go wrong, hedge every statement, and then the financial model proceeds as if none of those things will happen.

A decision-ready study treats risk differently. It identifies the two or three risks that, if they materialise, would change the recommendation — and then models what happens in those scenarios. Not thirty-seven risks with "medium" probability. Three or four risks that genuinely matter, with a clear view of how the decision changes if they occur.

This requires the analyst to take a position, which is uncomfortable. But it's what the decision-maker actually needs. A feasibility study that concludes "proceed, provided Volume Risk is managed through [specific mechanism]" is more useful than one that concludes "there are both opportunities and risks."

5. The recommendation is specific and conditions are stated

The final test of a decision-ready study is the recommendation. Not a summary of findings. Not a reiteration of the market context. A clear statement of what the decision-maker should do, under what conditions, and what would change that advice.

"We recommend proceeding to a conditional licence application, subject to confirmation of the lease terms and the appointment of a qualified compliance officer within 60 days" is a decision-ready recommendation.

"The market presents significant opportunities for well-positioned operators with the right capital and regulatory clarity" is not a recommendation. It is a sentence that means nothing.

What this means for commissioning

If you're commissioning a feasibility study, define the decision at the outset and put it in the brief. Ask the consultant to show you where the assumptions will appear in the document. Ask what the recommendation structure will look like. If the answers are vague, the output will probably be vague too.

If you're reviewing a completed study, the five tests above give you a rapid diagnostic. A study that passes all five is worth the time it takes to read. One that fails consistently should probably be redone — or at minimum, supplemented — before any serious capital or organisational commitment follows from it.