Embedded Product Feasibility Analysis - 8-Point Checklist

Why Feasibility Study is Important?

You have a product idea, a rough spec, and a budget. Someone on your team says "let's just build a prototype and see." Three months later you have a working prototype that costs $180 per unit to build and your target retail price is $99. Or your wireless module violates FCC Part 15 rules for your product category and you didn't find out until pre-compliance testing. Or the main IC you designed around went EOL six weeks before your production run.

All of these are feasibility failures. None of them required a prototype to discover. A structured embedded product feasibility analysis done before a single Gerber is drawn - catches the category-level mistakes that prototypes cannot fix. This post gives you the 8-point checklist that hardware teams use to validate whether a product idea is buildable, certifiable, and profitable at scale before spending a dollar on fabrication.

Why Skipping Feasibility Analysis Costs You More Than the Prototype

Prototype costs are visible and bounded. Without an embedded product feasibility analysis, a 5-unit PCB run, components, and assembly typically runs $3,000–$10,000 before you discover a problem that could have been found in a spreadsheet.

It isn't.

The real costs are what happen after the prototype reveals a problem you could have found in a spreadsheet. A BOM cost problem discovered at DVT stage means your hardware architect has to redesign the board, re-source components, re-validate, and re-test. That is typically 8–12 weeks of engineering time plus fabrication. A regulatory compliance gap discovered at pre-compliance testing means engaging a compliance consultant, potentially redesigning the RF section or adding shielding, and re-testing - typically $15,000–$40,000 additional and 4–8 weeks.

Embedded product feasibility analysis is not a gate that slows down your project. It is the exercise that identifies which projects have a viable path and which ones need to pivot before they burn resources on a direction that was never going to work.

The 8 checks below are the core of any embedded product feasibility analysis. They take 1–3 days for a hardware engineer who knows the product domain. Done seriously, each one produces a written output: a BOM cost estimate, a regulatory risk matrix, a component availability report. Those outputs become the foundation of your product brief and eventually your manufacturing plan.

The 8-Point Embedded Product Feasibility Analysis Checklist

Check 1 : Rough BOM Cost vs Target Price

The first check in any embedded product feasibility analysis: build a rough BOM using the product spec. You don't need a schematic - you need a list of major component categories with approximate costs at your target production volume.

Start with the dominant cost drivers: the main processor or MCU, the wireless module or chipset, the display (if any), the battery, the enclosure, and any application-specific sensors or actuators. These typically account for 60–80% of total BOM cost. Filler the rest in at 20–30% of the dominant component total as a rough estimate for passives, connectors, and minor ICs.

Pricing sources at the feasibility stage: Digi-Key and Mouser for current pricing, LCSC for Asian-market alternatives, the distributor pricing at your target volume (100, 1,000, or 10,000 units - the curve is steep between these tiers). Rough assembly cost for a standard IoT PCB runs $5–$20 per board at 100 units, $3–$8 at 1,000 units.

The check: Total BOM + assembly + enclosure + regulatory + logistics must fit within your gross margin target. For a hardware product targeting 50% gross margin, your total COGS must be below 50% of your target selling price. If your rough BOM alone exceeds 60% of target selling price, the product needs a fundamental rethink of the component strategy and not a prototype.

Red flags:

• Wireless module chosen for convenience costs $8–12, but competing products retail at $29

• Display is a 3.5" TFT IPS panel at $15; enclosure is custom injection-mould at $8/unit - total BOM is $42 at 1,000 units for a $49 product

• Single-source specialty sensor with no volume pricing - price at 100 units is the same as at 10,000 units

Check 2 : Regulatory Compliance Scope

The second check in an embedded product feasibility analysis: map your product to its applicable regulatory frameworks. This determines which certifications you need, which design constraints they impose, and how much your compliance budget needs to be.

The check: Does your product timeline and budget include realistic compliance costs and lead times? A founder who has budgeted $5,000 for "FCC certification" and expects to ship in 90 days has not done this check. An FCC modular approval for an unmodified certified module is fast and cheap; a custom RF design with an original Part 15 authorization is not.

Design constraints that certification imposes: FCC Part 15 limits on conducted and radiated emissions constrain your clock frequencies, switching regulator design, and PCB layout. IEC 60601-1 for medical devices imposes creepage and clearance distances that affect PCB layout and enclosure design. ISO 26262 automotive safety imposes functional safety requirements on firmware architecture. These constraints must be known at the design stage - they cannot be added later as a retrofit.

Red flags:

• Product uses an unmodified certified wireless module but adds an external antenna - antenna change typically voids modular certification and requires new FCC testing

• Medical application but product is being designed to consumer electronics standards

• Product ships globally but team has only budgeted for FCC , CE, IC, and UKCA add cost and schedule

Check 3 : Component Availability and Supply Chain Risk

Component availability and supply chain risk is check 3 in the embedded product feasibility analysis. Search the critical components in your product spec on Digi-Key, Mouser, and LCSC. Check stock levels, lead times, and lifecycle status.

Components to check specifically:

• Main MCU or SoC: Check lifecycle status (active, not recommended for new design, end of life). Check stock across distributors and independent brokers. Check whether the part went on allocation during the 2020–2022 semiconductor shortage and what the recovery pattern looked like.

• Wireless module or chipset: Check FCC/CE certification status. Modules are sometimes discontinued 12–18 months after certification. A module that is certified today may be EOL before your production volume ramps.

• Application-specific sensors: Check whether the sensor you need has a second source. A single-source MEMS sensor with a 26-week lead time is a production risk if supply tightens.

• Power management ICs: Check for any active product change notices (PCN) from the manufacturer. PCNs can alter package or electrical characteristics and require requalification.

The check: Every critical component should have either a confirmed second source or a stock position you can secure in advance. If a component has a lead time above 16 weeks at standard distributors, you need a plan for that component before design starts - not after you've committed to it in your BOM.

Red flags:

• Main IC is NRND (Not Recommended for New Designs) status

• Lead time at standard distributors is 26–52 weeks with no stock available

• Component is only available through one distributor in your region

• Wireless module uses a custom RF front-end chip that is sole-sourced by the module manufacturer

Check 4 : Firmware and Software Complexity Estimate

Firmware and software complexity is check 4 of the embedded product feasibility analysis. Map the firmware requirements against your team's capacity and the platform's SDK maturity.

The check: Does your firmware complexity estimate match your team capacity and your product timeline? A startup with two firmware engineers cannot build a custom Linux BSP with a secure boot chain and ship in 6 months. A product with a custom RTOS and a cloud integration layer cannot be "wrapped up" in the final month of development.

Critical questions:

• Does your MCU choice have a mature, well-documented SDK? ESP-IDF for ESP32, Zephyr for Nordic nRF, STM32Cube for STM32, and Arduino framework for rapid prototyping all have different maturity levels and community support depth.

• Does your wireless interface require a certified stack? Bluetooth SIG qualification, Wi-Fi Alliance certification, and Zigbee certification each add timeline and cost.

• Is your team new to the target platform? Ramping on a new embedded platform adds 4-8 weeks minimum.

Red flags:

• Team has never worked with the chosen MCU family before

• Product requires BLE 5.x extended advertising and the chosen SoC SDK's BLE stack is poorly documented

• Firmware schedule assumes concurrent hardware bring-up and firmware development on the same board revision

• Medical or safety-critical application but no IEC 62304 or ISO 26262 process is planned

Check 5 : Power Budget and Battery Life Reality Check

Power budget is check 5 of the embedded product feasibility analysis. Run a rough power budget calculation from the product spec before any PCB work.

For battery-powered products, the calculation is:

Battery life (hours) = Battery capacity (mAh) / Average current draw (mA)

The mistake most teams make: they calculate average current draw from the datasheet numbers for each chip in its active state, then multiply by "duty cycle" based on their planned firmware behavior. That ignores standby current, leakage, the actual active-to-sleep transition behavior, and the hardware draw from the charging circuit, regulators, and passive components.

A practical power budget should include:

The check: Does your calculated average current draw at your target usage profile meet your battery life target with a 20% margin? If you need 30-day battery life and your rough power budget gives 8 days, the product architecture - MCU choice, wireless protocol, sensor polling rate needs to change before you design the schematic.

Red flags:

• Target is 6-month battery life on a CR2032 coin cell but product includes a Bluetooth connection that is always on

• Power budget has not accounted for peak transmit current during BLE advertising (typically 5–15mA for 0.5–10ms) even though the product uses a 100mAh LiPo

• Wireless module chosen for ease of integration has a sleep current of 800µA more than the total power budget allows

Check 6 : Mechanical and Thermal Constraints

What to do: Check whether your product's physical requirements create design constraints that your current spec doesn't account for.

Mechanical:

• What IP rating does the product need? IP67 requires a gasket-sealed enclosure and PCB conformal coating. That adds $2–5/unit in assembly cost and requires a custom enclosure design.

• What are the drop and vibration requirements? Consumer wearables typically target 1.5m drop onto concrete. Industrial sensors in vibrating machinery need strain-relieved connectors and ruggedized mounting. These requirements constrain PCB size, component placement, and connector selection.

• What is the target PCB form factor? Wearables are often constrained to <30mm diameter and <5mm height this affects component selection and routing density more than almost anything else.

Thermal:

• Does your product have a power-dissipating component - wireless module, voltage regulator, motor driver, charging IC in a sealed enclosure? What is the maximum junction temperature of that component and what is the steady-state temperature rise in your enclosure?

• A switching converter dissipating 0.5W in a sealed plastic enclosure will reach thermal equilibrium at 30–50°C above ambient. [verify before publishing] If ambient is 40°C (sun-exposed outdoor product), your component is operating at 70–90°C - check every component's temperature rating against that.

The check: List all mechanical and thermal constraints from the product spec. For each one, identify the design implication and whether your current component choices and enclosure concept are compatible.

Red flags:

• Target is IP68 but team is planning to use standard through-hole connectors. It cannot be sealed to IP68 without a connector boot that may not exist for that connector series

• Product has a processor running at 1GHz in a 50×50mm sealed ABS enclosure. Thermal management needs active planning at this stage

Check 7 : Manufacturing and Assembly Readiness

What to do: Check whether your product design is manufacturable by your target contract manufacturer (CM) at your target volume.

Key questions:

• Component package compatibility: Does your design use 0201 or 01005 passives? Not all CMs run 01005 placement reliably at low volume. Does it use QFN or BGA packages? Confirm your CM's X-ray and reflow profile capability for your package types.

• PCB complexity: Does your design require HDI (high-density interconnect) with microvias, buried vias, or via-in-pad? Standard CMs cannot fabricate HDI boards - you need a specialized fab at a premium cost.

• SMT and through-hole mix: Mixed-technology boards require two separate assembly passes. This adds $0.50–$2.00/board in assembly cost and increases the risk of thermal damage to components from double reflow.

• Test coverage: How will you test each unit at the end of the assembly line? A product with no test plan ships unknown quality. Functional test fixtures for embedded products typically cost $5,000–$20,000 to develop. Factor this into your NRE budget.

Red flags:

• Design uses 01005 components for a product at 500 units/month - most low-volume CMs don't justify the process investment at that volume

• No test plan exists and "we'll figure it out" is the response to the question

• Target CM is in a different country than your regulatory market and has no experience with FCC/CE documentation

Check 8 : Team and Execution Capacity

What to do: Map the skills required against the skills available.

An embedded product development project typically needs:

The check: For every required skill, you either have it in-house, have a confirmed outsource partner who has done similar work, or have a realistic plan to acquire it. "We'll hire someone" is not a plan at the feasibility stage — it is a gap.

Red flags:

• Team has firmware and mobile app covered but no hardware engineer - the schematic and PCB work remain unassigned

• CTO is planning to do both hardware design and firmware for a product with any complexity above a simple sensor node, this is a 12–18 month serialized schedule risk

• No regulatory path is planned for a medical application

Feasibility Is Not a Barrier. It's the Fastest Path to a Prototype That Works

The 8-point embedded product feasibility analysis is not a gate. It is a map. Run it and you know which problems you are signing up to solve before you spend money on fabrication. Skip it and you find those problems at the worst possible time - after the BOM is locked, after the schematic is done, after the PCB is built.

The checks above take a few days. A board respin takes months. The math is straightforward.

If you are working through a product feasibility for an embedded IoT, wearable, or medical device and want a embedded team that has done this across dozens of product categories - CoreFragment's team can run a structured feasibility review with you. We'll give you a BOM estimate, a regulatory scope map, and a direct recommendation on where your concept needs to change before prototyping makes sense.