Feasibility Studies
Financial Feasibility Study
A financial feasibility study tests whether the commercial and operating assumptions of a project translate into a viable cash-flow case. It shows how much capital the project requires, when that cash is needed, how quickly revenue builds, when the project reaches break-even, which assumptions drive value and whether the economics remain acceptable when conditions are weaker than the base case.
The model should not create the business case; it should measure it. Revenue assumptions must come from market evidence, cost and capacity assumptions must reflect the operating/technical plan, and financing assumptions must be separated clearly from the underlying project economics.
Start with an auditable assumptions architecture
A credible financial model begins with assumptions that can be traced to their sources and owners.
The assumptions register should distinguish:
- independently researched market inputs;
- management assumptions;
- supplier or specialist quotations;
- technical/capacity assumptions;
- current contractual or operating inputs;
- financing assumptions; and
- variables that remain uncertain and require scenario testing.
Material assumptions should include a date and basis. This matters because price, capex, labour, rent, demand and financing conditions can change. A model that cannot be updated without rebuilding its logic is less useful as a decision tool.
Revenue model: translate the market case into cash-generating activity
Revenue should be built from the underlying commercial drivers rather than a top-down growth percentage wherever practical.
Depending on the business model, drivers may include:
- number of customers or contracts;
- units sold;
- price per unit;
- capacity and utilisation;
- occupancy;
- average order or transaction value;
- recurring versus one-off revenue;
- churn or retention;
- sales-cycle conversion; and
- ramp-up from launch to steady state.
These assumptions should reconcile with the market feasibility work. If the financial model requires more customers, higher pricing or faster utilisation than the market evidence supports, the conflict should be visible rather than hidden inside a growth rate.
Capital expenditure: what must be funded before and during launch?
CAPEX should capture the investment required to create the operating asset or capability assumed by the project.
Depending on the project, this can include:
- land, lease premiums or deposits;
- construction and fit-out;
- equipment and machinery;
- technology and systems;
- furniture and fixtures;
- professional/project-development cost;
- installation and commissioning;
- pre-opening expenditure that is capitalised where appropriate; and
- contingency consistent with the maturity of the estimates.
The timing of capex is critical. A total project cost can appear manageable while the monthly or quarterly funding profile creates a liquidity constraint before operations begin.
Where estimates require engineering design, quantity surveying, supplier quotations or specialist validation, their level of confidence should be stated. A feasibility model should not present a preliminary estimate as a contracted cost.
Operating expenditure: model the cost structure at the proposed scale
OPEX should distinguish fixed, semi-variable and variable costs where that distinction affects the decision.
Potential cost categories include:
- payroll and employee-related cost;
- rent and occupancy;
- utilities;
- raw materials or cost of goods sold;
- logistics and distribution;
- maintenance;
- technology subscriptions and support;
- marketing and sales;
- insurance;
- professional services;
- licences and recurring fees; and
- administrative overhead.
The cost structure should reflect the operating model and capacity assumptions. If additional volume requires additional shifts, equipment, delivery capacity or sales resources, the model should step those costs appropriately rather than assuming unlimited scale at a fixed cost base.
Working capital: bridge accounting profit and cash
A project can show accounting profit and still run out of cash. Working capital is therefore a core feasibility variable, particularly during ramp-up.
The model may need to account for:
- customer payment terms and receivables;
- supplier payment terms and payables;
- inventory levels and replenishment cycles;
- deposits and advance payments;
- seasonality;
- VAT/tax timing where relevant to the project and specialist advice; and
- minimum operating cash buffers.
The working-capital profile should reflect how the business actually trades. A B2B project with long receivable cycles has different funding needs from a cash/retail model even if both produce the same accounting margin.
Build an integrated cash-flow view
The financial model should show when cash enters and leaves the project from development through stable operations.
A decision-ready view typically makes visible:
- development/pre-opening cash outflows;
- monthly or quarterly operating ramp-up;
- operating profit and cash conversion;
- working-capital movements;
- capital expenditure by stage;
- taxes/other project-specific obligations where appropriately scoped;
- financing inflows/outflows if included;
- peak funding requirement; and
- cumulative cash position.
This timeline exposes the difference between a project that is profitable in year three and a project that can survive the cash requirements of years zero to two.
Break-even analysis
Break-even should be expressed in terms that management can use operationally.
Depending on the project, the model can show:
- revenue break-even;
- units/customers needed to cover relevant costs;
- utilisation or occupancy break-even;
- operating break-even by month; and
- cash break-even after development and working-capital requirements.
The study should also show how break-even changes when price, variable cost or fixed cost moves. This helps management understand the operating margin of safety rather than treating break-even as a single static number.
NPV, IRR and payback
Return metrics can support the decision when they are calculated from transparent cash flows and interpreted correctly.
Net present value (NPV)
discounts project cash flows at an appropriate required rate to estimate value created above that hurdle.
Internal rate of return (IRR)
identifies the discount rate at which NPV equals zero and can be compared with the relevant return threshold.
Payback period
estimates how long cumulative project cash flows take to recover the initial investment.
Each metric has limits. IRR can be misleading for unusual cash-flow patterns or comparisons between very different project sizes. Payback ignores value after the payback point and does not by itself measure value creation. NPV depends materially on the cash-flow forecast and discount-rate assumption.
The study should therefore present metrics together with the assumptions and downside cases that drive them, not as isolated proof that the project is attractive.
Funding requirement and financing assumptions
The model should identify the project’s funding requirement before deciding how it will be financed.
Useful outputs include:
- total funding required;
- peak funding requirement;
- funding by development stage;
- equity contribution assumptions;
- debt or other funding assumptions where relevant;
- financing cost and repayment schedules where included; and
- liquidity headroom under downside cases.
The project’s unlevered economics should be distinguishable from the effect of a chosen financing structure where relevant. A financing structure can change equity cash flows, but it does not make weak underlying project economics disappear.
Any lender, investor or financing decision remains subject to that institution’s own criteria; a feasibility model does not guarantee funding.
Scenario analysis: build coherent alternative futures
A scenario should represent a plausible operating state rather than an arbitrary percentage change across every line.
A base case should reflect the most supportable assumptions. A downside case might combine slower demand, lower utilisation, delayed opening and higher costs if those risks are related. An upside case should be supported by a credible commercial or operating mechanism.
Typical scenario variables include:
- revenue ramp-up;
- price;
- volume/utilisation;
- capex;
- opex;
- working-capital days;
- opening date;
- capacity; and
- financing conditions where relevant.
The output should show the effect on cash requirement, break-even, NPV, IRR, payback and any other decision metric being used.
Speak with an adviser
Defined mandates on fixed fees, ongoing counsel on retainer, and customised scopes for complex requirements.
Sensitivity analysis: identify the variables that can change the decision
Sensitivity analysis isolates one or two important variables to show how strongly they affect the result.
This is particularly useful for assumptions with uncertainty or limited evidence. If a modest change in demand or capex turns NPV negative, that assumption is not a footnote—it is a decision condition that requires stronger validation or mitigation.
The study should prioritise sensitivities that management can influence or investigate, rather than producing large tables with little decision value.
Link the financial model back to market and technical evidence
Financial feasibility should not become a spreadsheet silo.
Market feasibility determines customer volume, pricing, market share and ramp-up. Technical feasibility determines capacity, equipment, utilities, implementation timing and significant capex/opex assumptions. The financial model integrates those inputs and reveals whether they can coexist economically.
Established project-appraisal methodology follows this integrated structure. UNIDO’s feasibility guidance links market, technical, financial and investment analysis, while its COMFAR framework reflects the role of structured financial/economic analysis in project appraisal.
The implication for the client is practical: every material financial assumption should have a commercial, operational or evidence basis that can be challenged.
Model governance and handover
The model should remain useful after the final presentation.
Good handover practice includes:
- clear input, calculation and output logic;
- visible scenario controls;
- an assumptions register;
- consistent units and time periods;
- checks for key balance/cash-flow relationships;
- documentation of material formulas or model logic where needed; and
- identification of assumptions that require periodic update.
The objective is not unnecessary complexity. It is sufficient transparency for management to understand why the model reaches its conclusion and what changes it.
What the client receives
Depending on scope, a financial-feasibility package can include:
- executive financial decision memo;
- assumptions register;
- revenue model;
- CAPEX schedule;
- OPEX model;
- working-capital schedule;
- integrated cash-flow model;
- break-even analysis;
- NPV, IRR and payback analysis where appropriate;
- funding-requirement analysis;
- base, upside and downside cases;
- sensitivity analysis;
- financial risk register; and
- recommendation with the financial conditions required for go, revise or no-go.
Go, revise or no-go from the financial perspective
A go conclusion means the project produces acceptable cash-flow and return outcomes under the agreed base assumptions and remains sufficiently resilient under realistic downside testing.
A revise conclusion means the project may become viable if scale, price, capex, cost structure, phasing, capacity or another driver changes.
A no-go conclusion means the project cannot support the capital required or the downside risk is disproportionate to the expected financial outcome under supportable assumptions.
The financial conclusion should then be read alongside market, technical and strategic considerations rather than treated as the only project decision criterion.
Why EXMC
Evidence EXMC already publishes about its own work, used here only within its documented scope.
Representative examples published by EXMC. Client identities are generalised to maintain confidentiality. Published work does not by itself establish permission to perform activities that require specific regulatory authorisation.
Frequently asked questions
What financial metrics should a feasibility study include?
The right metrics depend on the decision, but common outputs include cash requirement, operating and cash break-even, NPV, IRR and payback. The model should also show revenue, capex, opex, working capital and cash flow because return metrics cannot be interpreted safely without the assumptions that create them.
How are downside cases and sensitivities built?
Downside cases combine plausible adverse assumptions—such as slower demand, lower utilisation, higher capex/opex or delayed opening—into coherent operating scenarios. Sensitivity analysis then isolates the variables that most influence cash requirement, break-even and returns.
How should market and operating assumptions link to the model?
Customer volume, price, share and ramp-up should come from market analysis. Capacity, equipment, staffing, utilities, timing and technical costs should come from the operating/technical case. The financial model integrates these assumptions and flags conflicts where the project economics require conditions not supported elsewhere.
Does a financial feasibility study guarantee funding or returns?
No. It analyses project economics under stated assumptions. Actual performance can differ, and financing decisions are made by lenders or investors under their own criteria. The study should make uncertainty visible through scenarios and sensitivity testing rather than imply a guaranteed outcome.
Discuss your financial case
If you need to understand the project’s true cash requirement, break-even, downside resilience and return profile before approval, EXMC can build the financial feasibility analysis around the market and operating evidence behind the investment case.