Many feasibility studies are written to justify a decision that has already been made. Appjad (أبجد) works with owners at the moment of commitment, and the pattern repeats: the document is thick, the evidence is thin. Use this checklist today to pressure-test a feasibility study — yours or one prepared for you — before you sign or fund anything.
Key takeaways
- A study written to approve a decision is marketing, not analysis.
- Demand evidence must come from real buyer behaviour, not from opinions.
- Every number should survive a run on your worst realistic month.
- Write the stop conditions before you commit, not after.
Check which question the study actually answers
Read the executive summary first, then trace how the conclusions were reached. A decision-grade study is open to being wrong; a justification document is not.
- Does the study ask "should we do this?" or only "how do we do this?"
- Does it name what would make the venture fail, in plain words?
- Does it list the assumptions it depends on, and who verified each one?
- Could a reader reach the opposite conclusion from the same evidence?
Test the demand against real behaviour
Interviews and surveys measure goodwill. What buyers actually do — pay, sign, pre-order — is the only demand evidence that carries weight in a decision.
- Ask for letters of intent or advance commitments, not expressions of interest.
- Talk to buyers who currently pay a competitor for the same need.
- Run a small willingness-to-pay test: a deposit, a pilot, a priced offer.
- Check seasonality and payment habits in your target market before assuming a steady run-rate.
Run the numbers on your worst realistic month
Base cases flatter every venture. The number that matters is what the project needs from you when revenue arrives late and costs arrive early.
- Rebuild the financial model with the worst credible case, not a catastrophe — a slow first year, higher acquisition cost, delayed permits.
- Find the break-even point and the date it realistically arrives.
- Calculate the cash required to survive until then, including your own time.
- Decide now who funds the gap if it appears, and on what terms.
Check the operating plan, not only the market
A venture can fail with a real market behind it if the day-to-day operation was never designed. This is the part owners most often discover after launch.
- Who runs the operation daily, and does that person exist today or must they be hired?
- Which single supplier, platform or licence can stop the whole venture?
- Which approvals, regulations or partnerships sit on the critical path?
- What happens in the first ninety days after launch, hour by hour, for the core team?
Set the stop conditions in writing
Feasibility is not a one-time verdict. Decide now, in writing, what evidence will continue the venture and what evidence will stop it. This protects you from your own momentum later.
- Define the metrics that mean "continue" and the metrics that mean "stop".
- Set a review date, before launch, when those metrics are checked.
- Name the person who holds the authority to stop it — and confirm they will use it.
- Record the decision and the conditions where future partners and investors can see them.
The purpose of a feasibility study is not to approve the project. It is to find out, cheaply and on paper, whether the project deserves to exist.
Next step: turn the study into a decision memo
Appjad helps owners turn feasibility work into real decisions: a short diagnostic, a written scope with risks named, and a venture built from idea to launch in defined stages. If you are holding a study you are not sure you can trust, start with a working session with Appjad — bring the document, and leave with a clear list of what to verify before any money moves.
