Feasibility Studies: Testing an Idea Before Committing a Budget
Most products rest on a few assumptions that, if wrong, sink the project: that a sensor can detect the signal, that a model reaches useful accuracy, that the battery lasts long enough or that the unit cost fits the price. A feasibility study tests those assumptions with experiments and estimates, within a fixed time and budget, and ends in a decision. This article explains what a good study covers and what it should deliver.
At a glance
- Unknowns
- Questions nobody on the team can yet answer with evidence.
- Bench test
- A focused experiment that answers one question, not a miniature product.
- BOM est.
- An early bill-of-materials estimate that tests whether the unit cost works.
- Go / no-go
- Criteria agreed in advance, so the result leads to a decision.
The problem
Without a study, the riskiest assumption is often tested last, after enclosures, firmware and app are well advanced. When it fails, most of that work is lost, along with the time and the confidence of whoever funded it.
Studies go wrong in the opposite way too. Without defined questions and an end date they drift into open-ended research, or into building a prototype product that answers nothing clearly.
A feasibility study is finished when it can support a decision, not when the prototype looks good.
What a study covers
Technical feasibility asks whether the core function can be achieved with available parts and methods, tested on the bench under realistic conditions. Commercial feasibility asks whether the unit cost, compliance requirements and component supply fit the business case.
The deliverable is a short report: each question with its evidence and answer, the risks that remain, a recommended architecture and a rough estimate of development effort. A no-go, or a redirect, is a valid and valuable result.
What good looks like
List the assumptions the product depends on and rank them by how likely they are to be wrong and how costly that would be.
Design the smallest experiment or estimate that answers each high-risk question, and agree pass criteria before starting.
Run the work within a fixed time box, then review the evidence and decide to proceed, change direction or stop.
| Area | Typical question | Evidence |
|---|---|---|
| Sensing | Can the signal be detected in real conditions? | Bench measurements |
| AI or algorithms | Is accuracy adequate on representative data? | A small model tested on sample data |
| Power | Will the battery last the required time? | Measured current profile and budget |
| Unit cost | Can the cost meet the target price? | Early BOM estimate with quotes |
| Compliance | Which approvals apply in each market? | Standards list and design implications |
| Supply | Are key parts available for the product life? | Lifecycle status and lead times |
A time-boxed study
- List assumptions: What must be true
- Rank by risk: Likelihood and cost of being wrong
- Experiment: Smallest test for each question
- Estimate: Cost, effort and remaining risk
- Decide: Proceed, redirect or stop
What it changes
Informed Decision
Funding follows evidence rather than optimism.
Retired Risk
The biggest unknowns are answered first, when changes are cheap.
Realistic Estimate
Development effort and unit cost are grounded in measurement.
Better Architecture
Experiments shape the design before it is fixed.
Where to go next
If the study proceeds to development, carry its experiments forward as early test cases. They often become the first verification tests.
Keep the study code and hardware clearly separate from the product design. Feasibility work is built for speed, not for production.
Problems this prevents
- The riskiest assumption tested last
- A study with no end date
- Results with no agreed pass criteria
- Prototype code shipped as product code
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.