Feasibility Phase in Product Development

Feasibility is the phase where the idea meets physics, regulations and arithmetic. Nothing is built yet. Engineers calculate, research, sometimes run quick bench tests, and come back with an answer to one question: can this work at all, at the price and size the requirements call for?

It is the phase most likely to change the requirements, and the phase where a "no" is cheapest.

Where this phase sits. The highlighted marker is this phase. Everything to its left has been answered; everything to its right is still a range.

What gets checked

The work depends on the product, but a feasibility study usually covers:

Physics and engineering limits. Does the energy budget close? Will it overheat? Is the material strong enough at that thickness? Can a motor that small produce that torque?
Cost at volume. A first bill of materials (BOM) with rough prices, to see whether the target unit cost is possible before any design work.
Size and weight. Whether everything in the requirements fits inside the enclosure the requirements describe. It frequently does not.
Regulations and standards. Which certifications the product will need (electrical safety, radio, medical, food contact, and so on), what they cost, and what they constrain.
Manufacturability, at a high level. Whether any requirement forces a process that is slow, expensive or hard to source.
Existing solutions. Whether something similar exists, how it was done, and what can be learned from it.
The riskiest assumption. Every new product has one or two things that, if they fail, sink the project. Feasibility exists to find them early.

A worked example

Consider a hypothetical rechargeable trail flashlight. The requirements call for 1,000 lumens on High, a 1.5-hour runtime on High, a 120-hour runtime on Low, a weight under 122 g, and a landed cost of $8.75 at 10,000 units.

Feasibility finds, on paper, that:

The three runtimes together need more battery energy than any single cell that fits the body can hold. One requirement has to give.
Running at 1,000 lumens produces several watts of heat in a small aluminum tube. The light will throttle itself to protect the LED before the 1.5 hours are up, so "runtime on High" needs a definition that allows for that.
A realistic build lands a few grams over the weight limit.
One requirement mixes up a data standard with a charging specification, and needs rewording.
Two control gestures conflict, so a user could trigger the emergency strobe by accident.
With all the features kept, the cost target is at risk.

None of this required building anything. It required a few days of an engineer's time. The requirements document goes from version B to version C, with a larger battery, a redefined runtime, a 135 g limit, and clearer control logic. The product is still possible. It is now also honest.

Key takeaway Feasibility turns wishes into decisions. Every item it finds was going to be found eventually. Finding it now costs a revision to a document. Finding it after tooling costs the tooling.

What comes out

A feasibility report: what was checked, what was found, and what it means for each requirement.
A revised requirements document, with fewer "assumed" items and more "known" ones.
A rough cost model at volume, with the main cost drivers identified.
A list of the risks that remain, ranked. The top one or two are what Proof of Concept will test in hardware.
A gate decision: proceed, change the requirements, or stop.

Why "no" is a good answer here

A feasibility study that concludes the product cannot hit its target price, or cannot fit its enclosure, or needs a certification that costs more than the first year's revenue, has done its job. The owner now knows this for the price of a study instead of the price of a prototype, a tooling run, or a company. Many ideas survive feasibility in changed form: a different price point, a different market, a simpler first version. Some do not survive, and the money saved is real.

Typical cost and duration

Feasibility is usually billed hourly, because the amount of work depends on what gets found. It is still an early, inexpensive phase relative to what follows. The spend is mostly labor: engineering time, not parts.

Common mistake Skipping Feasibility because the idea "obviously works." The things that sink products are rarely the obvious parts. They are the battery that is 20% too small, the plastic that creeps at the operating temperature, or the certification nobody budgeted for.

What to ask a firm about this phase

"What is the single biggest risk you see, and how will you check it?"
"What would make you tell me to stop?"
"Will the cost model show which requirements drive the cost?"

Try this (15 minutes) Write down the one thing that, if it turned out to be impossible, would end the project. Then write down how someone could check it without building the product. That is the first line of a feasibility study.