Feasibility & architecture
Most expensive hardware mistakes are made before the first schematic: a sensor that cannot reach the required accuracy, a battery that lasts two days instead of two months, a BOM that kills the margin. We check the physics and the numbers first.
Turn an idea into a system architecture, a component shortlist and a realistic cost and risk picture before anyone draws a schematic.
When you need it
- You have a product idea and requirements, but no electronics yet.
- Your software team is ready and needs to know what the hardware will realistically look like.
- You need a credible BOM cost and timeline for investors or a grant application.
- You are choosing between two or three technical approaches and want an engineer to decide with data.
What you hand us
- What the product must do, in plain language. A one-page brief is enough.
- Target unit cost, volumes and launch date, even if rough.
- Constraints you already know: size, power source, environment, certifications.
What you get back
- Requirements specification with measurable targets (voltage, current, accuracy, battery life, temperature range).
- System block diagram and interface definition between hardware, firmware and your software.
- Component shortlist with availability and lifecycle checked against distributors.
- Power budget and, for battery products, a battery-life estimate.
- Preliminary BOM cost at prototype and at production volume.
- Risk register and a staged plan with cost per stage.
How we do it
We start from a short written questionnaire and whatever documents you have, then write the requirements back to you in numbers. Anything that cannot be measured gets challenged. From there we sketch two or three candidate architectures, estimate power, cost and complexity for each, and recommend one.
Where a requirement is borderline (range, accuracy, battery life, thermal limits), we calculate it or simulate it instead of guessing. If a risk can only be retired on the bench, it goes into the proof-of-concept plan.
Questions about feasibility & architecture
Do I need a feasibility study for a simple product?
For a small board with well-known parts, feasibility can be a half-day review folded into schematic design. For anything with batteries, wireless, power conversion or tight cost targets, a short study usually saves more than it costs.
Will you sign an NDA before I explain the idea?
Yes. We sign a mutual NDA before any technical discussion if you ask for one, and we can use yours.
Send us what you have. We tell you what it takes to finish it.
Answer five questions and see an indicative budget in two minutes. When you are ready, sign our NDA, upload your documentation and get a fixed quote. Everything by e-mail, with a call whenever you prefer.