Best Practices for a Feasibility Study and How to Improve Your Analysis

A feasibility study answers a deceptively simple question: Is this project worth pursuing before we commit major money, time, reputation, or organizational capacity? A good study does not try to prove that an idea will succeed. It tests the assumptions that could make the idea fail and gives decision-makers enough evidence to choose whether to proceed, redesign, postpone, or stop. That is why feasibility analysis should come before a full business plan or major capital commitment. A business plan describes how an approved venture will operate and grow. A feasibility study challenges whether the proposed venture is viable at all. Professional support from a feasibility study company can be useful for large or unfamiliar investments, especially when independent market research, financial modelling, technical expertise, regulatory analysis, or lender/investor documentation is required. But whether the work is internal or outsourced, the methodology should be transparent enough that decision-makers can see the assumptions, sources, sensitivity tests, and reasons behind the recommendation. This guide explains the major types of feasibility studies, how to conduct market, technical, operational, financial, legal, organizational, environmental, and schedule analysis, how to build scenarios and sensitivity tests, how to avoid confirmation bias, and how to turn a long report into a clear go/no-go decision.

What a Feasibility Study Is—and What It Is Not

A feasibility study evaluates whether a proposed project or venture can realistically be implemented and sustained. It should answer questions such as: Is there enough demand?; Can we deliver the product or service?; Can we obtain licenses and approvals?; Do we have the required technology?; Can we hire the required people?; Can the economics produce acceptable returns?; Can the project be completed on time?; What could make the project fail?. Feasibility Study vs. Business Plan. A feasibility study asks: Should we do this? A business plan asks: How will we do this? The studies overlap, but the order matters.

Feasibility Study vs. Due Diligence. Due diligence generally investigates a specific asset, company, transaction, or investment before acquisition or commitment. Feasibility is often earlier and more conceptual. Example: Feasibility: Should we build a hotel in this district?; Due diligence: Should we buy this specific hotel site and project company?.

Start With the Decision and the Criteria for Saying Yes

Before gathering data, define the decision the study will support. Examples: Build or do not build.; Enter market A or market B.; Open 5 stores or 20.; Automate internally or outsource.; Launch product this year or delay. Define the Decision Criteria Upfront. A study becomes biased when the team decides the criteria after seeing the result. Possible thresholds include: minimum IRR; maximum payback period; minimum market size; required permits by a certain date; maximum capital requirement; acceptable downside loss. Write an Assumption Register. List every important assumption.

Market Feasibility: Demand, Customers, and Competition

Market feasibility evaluates whether enough customers: have the problem; value the proposed solution; can be reached economically; are willing and able to pay. Market Size. Common layers include: TAM — Total Addressable Market; SAM — Serviceable Available Market; SOM — Serviceable Obtainable Market. Do Not Start With a Giant Global Market Number. A startup selling specialized software to 2,000 regional clinics does not need a presentation saying “the global healthcare market is worth trillions.” The useful question is: How many realistic buyers can we reach, at what price, and at what acquisition cost? Top-Down Market Sizing. Uses: industry reports; government statistics; trade data. It is useful for context but can be overly broad. Bottom-Up Market Sizing. Builds from: number of potential customers; units per customer; price. This is often more useful operationally. Primary Customer Research. Use: interviews; surveys; focus groups; pilot sales; preorders; landing-page tests. Ask About Real Behavior. Weak question: “Would you buy this?” Stronger questions: How do you solve this now?; What did you pay last time?; Who approves the purchase?; What would make you switch?. Competitive Analysis. Map: direct competitors; substitutes; do-it-yourself alternatives; doing nothing. Competitor Research Should Include Economics. Compare: price; capacity; location; quality; delivery; distribution; reviews; occupancy/utilization where relevant.

Financial Feasibility: Revenue, Costs, Capital, and Returns

This section tests whether the project produces acceptable financial outcomes. Estimate: capital expenditure; startup cost; working capital; revenue; operating expenses; tax; financing; terminal value where appropriate. Revenue Build. Do not begin with: “Revenue grows 20% per year.” Build from drivers. Hotel: Rooms × occupancy × average daily rate Factory: Capacity × utilization × selling price SaaS: Customers × average recurring revenue Cost Build. Separate: fixed costs; variable costs; semi-variable costs. Capital Expenditure. Include: land; construction; machinery; technology; professional fees; contingency; pre-opening costs. Working Capital. Projects often fail not because they are unprofitable on paper but because cash is tied up in: inventory; receivables; deposits. Break-Even Analysis. Break-even asks when contribution covers fixed cost. Simplified: Break-even units = Fixed costs ÷ Contribution per unit Net Present Value. NPV discounts future project cash flows back to present value. A positive NPV at the appropriate discount rate can support viability, but the discount rate and cash-flow assumptions must be reasonable. Internal Rate of Return. IRR is the discount rate that makes NPV equal zero. It is widely used for investment projects but can be misleading when: cash flows change sign multiple times; projects differ greatly in size; reinvestment assumptions are unrealistic. Payback Period. Payback measures how long it takes to recover the initial investment from cash flows. It is easy to understand but ignores: cash after payback; time value of money unless discounted payback is used. Sensitivity and scenario analysis. Do not evaluate only the base case. Test what happens when: price falls 10%; volume is 20% lower; construction cost rises 15%; launch is delayed 6 months; interest rates rise. Find the Variables That Matter Most. A sensitivity table may reveal that project value is extremely sensitive to: occupancy; raw material cost; customer churn. Those variables deserve more research. Scenario Analysis. Use at least: downside; base; upside. Each scenario should be internally consistent. Do Not Make the Upside Case a Fantasy. An upside case should reflect plausible strong performance, not impossible market share.

Technical, Operational, and Supplier Feasibility

Technical feasibility asks whether the project can physically and technologically work. Consider: equipment; software; capacity; utilities; integration; technical skills; reliability; maintenance. Technology Readiness. Separate: proven technology; commercially emerging technology; unproven R&D. A project depending on an unproven technical breakthrough has a different risk profile. Proof of Concept. Before full implementation, test: critical integration; production yield; throughput; software performance. Capacity. Verify: design capacity; practical capacity; maintenance downtime; changeover; quality losses. Rated capacity is not always achievable annual output. Utilities and Infrastructure. Projects may require: electricity; water; gas; internet; waste treatment; roads; port access. 5. Operational Feasibility. Operational feasibility asks whether the organization can actually run the project. Consider: people; process; suppliers; maintenance; quality; customer service; inventory; logistics. Staffing. Identify: roles; headcount; skills; salary; hiring lead time; training. Do Not Assume Talent Is Available. A project can be technically feasible but operationally impossible if the region lacks: engineers; licensed clinicians; specialist operators. Supplier Feasibility. Check: number of suppliers; capacity; lead time; minimum order quantity; currency; country risk. Single-Source Risk. If one supplier controls a critical component, identify: backup; safety stock; qualification timeline.

Legal, Regulatory, Schedule, and Organizational Feasibility

Identify: business license; sector license; planning/zoning; building approval; environmental approval; labor regulation; product certification; privacy; tax. Do This Early. Do not complete a full financial model and then discover: the land use is prohibited; the product needs three years of regulatory approval; foreign ownership is restricted. Legal Feasibility Is Jurisdiction-Specific. For a project in Dubai, London, Mumbai, or Texas, local rules differ. Use licensed local legal and regulatory professionals for material decisions. 7. Schedule Feasibility. A project can be profitable but still fail if it cannot be ready when needed. Build a realistic timeline for: design; permits; procurement; construction; installation; commissioning; hiring; launch. Critical Path. The critical path identifies activities that determine project completion date. A one-month delay in a noncritical task may have no effect. A one-month delay in a critical permit may delay the entire project. Use Dependencies. Do not simply put tasks on a calendar. Show: what must happen first; what can happen in parallel. Schedule Contingency. Allow for: permit delay; shipping; weather; rework; vendor delays. 8. Organizational Feasibility. Ask whether the project fits the organization’s: strategy; leadership capacity; culture; systems; governance. Strategic Fit. A profitable project may still be inappropriate if it: distracts management; conflicts with brand; uses capital needed elsewhere. Governance. Define: project sponsor; decision rights; reporting; stage gates.

Environmental, Social, Site, and Community Feasibility

Depending on project, evaluate: emissions; water; waste; traffic; noise; biodiversity; community impact. Community Acceptance. A technically permitted project may still face: public opposition; political delay; reputation risk. 10. Site Feasibility. For physical projects, site analysis may include: land title; access; utilities; geotechnical conditions; flood risk; neighbors; future expansion. Geotechnical Risk. Unexpected soil conditions can add substantial construction cost. Use site investigation appropriate to the project.

Risk Analysis, Red-Teaming, and Source Quality

Create a risk register.

Do Not Score Risks Just to Fill a Matrix. Use the register to make decisions. Risk Owners. Assign one person responsible for each major risk. 12. Red-Team the Project. Ask a team that did not create the proposal to challenge it. Questions: What would make this fail?; Which assumptions are optimistic?; What data is weakest?; What is management ignoring?. Confirmation Bias. People who created the idea naturally want it to succeed. Independent review reduces the risk that the study becomes a sales document. 13. Use Source Hierarchy. Prefer: government data; audited filings; primary customer research; vendor quotations; recognized industry sources. Treat marketing reports and unsourced statistics cautiously. 14. Date the Data. Market conditions change. For every major input, record: source; date; geography; definition. 15. Separate Facts From Assumptions. Example: Fact: Competitor charges $100/month. Assumption: We can charge $120/month.

This distinction makes the model auditable. 16. Use Independent Quotes. For large capex, obtain more than one quote where practical. One supplier may: underestimate scope; price aggressively; omit installation. 17. Include Contingency. Projects rarely cost exactly the initial estimate. Contingency should reflect uncertainty rather than an arbitrary percentage copied from another industry.

Financing, Tax, Governance, and Stage Gates

A financially viable project may still be unfundable. Evaluate: equity required; debt availability; interest; security; covenants; DSCR. 19. Tax Feasibility. Model: corporate tax; VAT/GST/sales tax; customs; withholding; property tax. Use qualified tax advice. 20. Define the Final Recommendation. The study should end with one of several decisions: Proceed.; Proceed with conditions.; Redesign.; Delay.; Do not proceed. “Proceed With Conditions”. Conditions might include: secure anchor customer; obtain permit; reduce construction cost; raise required equity. 21. Use Stage Gates. Do not release the entire budget at once. Example: Gate 1 — market validated; Gate 2 — permits feasible; Gate 3 — financing committed; Gate 4 — final investment decision.

What the Final Feasibility Study Should Deliver

A professional report may include: Executive summary.; Project description.; Market analysis.; Technical analysis.; Operational plan.; Legal/regulatory analysis.; Financial model.; Risk analysis.; Scenarios.; Recommendation. 23. Executive Summary. A decision-maker should be able to understand: investment; expected economics; major risks; recommendation. without reading 200 pages. 24. Keep the Financial Model Auditable. Separate: inputs; calculations; outputs. Avoid hardcoding hidden assumptions throughout formulas. 25. Update the Study. A feasibility study can become obsolete if: cost changes; competitor enters; regulation changes; financing changes. Trying to prove the sponsor is right.; Using only top-down market size.; Ignoring working capital.; No downside case.; Outdated data.; Ignoring permit timing.; Using vendor claims as independent evidence.; No decision criteria. When to Hire an External Consultant. External support may help when: investment is large; market is unfamiliar; lenders need independent analysis; technical expertise is specialized; management needs an unbiased view. How to Choose a Feasibility Consultant. Ask: What primary research will you conduct?; Who builds the financial model?; Can we inspect assumptions?; What similar projects have you studied?; How do you handle negative findings?. Red Flag: Guaranteed Positive Feasibility. A consultant who promises a positive conclusion before research is not performing independent feasibility analysis.

Demand is evidenced.; Technical solution is proven enough.; Resources are available.; Regulatory path is credible.; Downside is survivable.; Financing is realistic.; Schedule is achievable.; Major risks have owners.; Return meets decision criteria.

Conclusion

A feasibility study is most valuable when it is willing to conclude that a project should not proceed. The purpose is to protect capital and improve decisions, not validate enthusiasm. Build the analysis around explicit assumptions, primary evidence, operational reality, and a financial model that can be stress tested. Identify the variables that drive success, test a credible downside case, and define decision thresholds before seeing the answer. When the study is complete, management should know more than whether the base-case spreadsheet is profitable. It should know what must be true for the project to succeed, what would cause failure, and which risks need to be resolved before capital is committed.