The four core feasibility tests are technical, economic (financial), legal, and operational. Together, they check whether a project can be built, whether it makes financial sense, whether it can be done within the law, and whether the organization can run it. Sources do not agree on one list. Some use these four, some add a scheduling test, and some swap in market and organizational tests. This article explains the common set, the other lists you may see, and where market research fits in.
Why a feasibility study tests more than demand
A feasibility study asks whether a project is worth doing and whether it can be done. A market test answers part of that question: whether customers want the product, and at what price. A project can still fail even when demand is strong, for example because the technology is not ready, the costs are too high, the rules prohibit it, or the team cannot run it. Each test looks at a different kind of risk.
The four core tests
Technical feasibility
Technical feasibility asks whether the project can be built or delivered with the technology, equipment, skills, and infrastructure available. It covers the specific requirements of the product or service, whether existing systems can support them, and whether new systems would be needed. A technical test might ask: do we have the engineers, software, or facilities to deliver this, and if not, can we get them at a reasonable cost?
Economic (financial) feasibility
Economic feasibility asks whether the project makes financial sense. It compares expected costs, such as setup, staffing, materials, and marketing, with expected revenue or savings over a set period. It also considers how the project will be funded and how much financial risk it carries. An economic test might ask: will the project return its costs within a time frame that the organization can accept?
Market research can supply inputs for this test, such as the prices people say they would pay. The Van Westendorp price sensitivity guide explains one way to collect that evidence. Stated prices are only an estimate, so treat them as one input among several.
Legal feasibility
Legal feasibility asks whether the project complies with the laws and rules that apply to it. Depending on the project, this can include licensing, permits, zoning, data protection, product safety, employment rules, and intellectual property. A legal test might ask: do we need a permit to operate here, and can we obtain it?
Legal feasibility often needs specialist advice. Treat any summary, including this one, as a starting point and not as legal guidance.
Operational feasibility
Operational feasibility asks whether the project fits into how the organization works. It covers processes, staffing, management capacity, and whether the project can connect with existing systems without disrupting current work. An operational test might ask: do we have the people and processes to deliver this alongside our current commitments?
Other tests you may see
Several other lists appear in feasibility guides. These are the most common:
- Schedule (or scheduling) feasibility asks whether the project can be finished in a realistic timeframe, given its phases and resources. Many guides add it as a fifth test.
- Market feasibility asks whether there is enough demand, and whether the product can win share. Some guides use this as one of the four in place of legal feasibility.
- Organizational feasibility asks about the legal and corporate structure, and about the skills of the people behind the project. Some consultants list it alongside financial feasibility.
- Environmental feasibility asks about environmental impact and compliance. It is common in construction and resource projects.
When you read a feasibility guide, check which list it uses. The core four, technical, economic, legal, and operational, is the most common starting point.
How the tests fit together
| Test | Question it answers | Typical evidence |
|---|---|---|
| Technical | Can we build or deliver it? | Specifications, technical reviews, supplier quotes |
| Economic | Does it pay back on acceptable terms? | Cost estimates, revenue projections, funding options |
| Legal | Are we allowed to do it? | Permit requirements, regulatory review, contracts |
| Operational | Can we run it with the people and processes we have? | Staffing plans, process maps, capacity estimates |
| Market (if used) | Will customers buy it, and at what price? | Customer research, sales forecasts, competitor review |
A project should pass all of these tests before the organization commits significant money. A failure on one test can stop a project even when the others look good.
Where a market survey fits
A market survey helps with the market and part of the economic test. It can show whether people have the problem, which features matter, and roughly what they might pay. It cannot show whether the product can be built, whether it is legal, or whether the organization can run it. The new product questionnaire guide explains what a feasibility survey can and cannot tell you.
If you are planning a survey to support a feasibility decision, start with the decision: which test or question is the survey supposed to inform? The market research survey questions guide covers how to set that up. For the wider scope of what research should cover, see what should be in market research.
Common mistakes
- Treating demand as feasibility. Strong interest does not mean the project can be built or funded.
- Using a different list than the reader expects. Name the list you are using and why.
- Skipping the legal test. Rules that look minor can stop a project late.
- Relying on a single estimate. Costs, prices, and timelines all change, so test how sensitive the result is to each.
- Presenting a survey result as a sales forecast. Stated intent usually overstates what people do, so use it as directional evidence.
The sample size for a market survey depends on the precision you need. The sample size guide explains how to estimate it.