Hardware Feasibility: The Four Questions to Answer Before You Build
Hardware ideas usually stall in one of two ways: you build too early, or you research forever. A feasibility assessment exists to stop both. It doesn't have to be long. It has to answer four questions. If you're at the very start, run them after the first steps in a from-scratch hardware path.
1. Which path, and why?
List the candidate approaches (display, power, sensing, enclosure, whatever applies), then pick one, with sources behind the choice. A conclusion without sources is just an opinion.
2. What is still unverified?
Every plan has assumptions. Write them down as unverified risks, and keep them separate from what you have confirmed. This is the part people tend to skip, and it is where projects get hurt.
3. What is the smallest real test?
For the riskiest assumption, design the minimum hands-on test that would confirm or kill it. Keep it cheap, quick and specific, and decide in advance what result counts as a pass. Examples are in a worked guide to the smallest real test.
4. What is the scope of the next stage?
Define what the next stage covers and what it doesn't, so the project can move forward without scope creep. For hardware, that usually means choosing your next prototype stage.
A worked example (synthetic demo)
The example below is a synthetic demonstration written to show the process. It is not a real user project, and nothing was manufactured or tested.
Desk temperature indicator. Goal: read the temperature clearly at a reading desk. Unknown: viewing distance, budget and accuracy. The first move isn't to pick parts. It is to pin down the viewing distance, because that decides which display and power options are worth comparing.
See the demo on the cases page.
Keeping the answers in one place
ThingWeave keeps requirements, research with its sources, the chosen path and its reasons, and open risks in one private project that you and your agent share over MCP. Engineering sign-off, procurement and manufacturing are not offered. Why this matters: recording the chosen path and its reasons.
We are in pilot, and you can sign up and try it. Start your first project →
FAQ
What is a hardware feasibility assessment?
A short, sourced check of whether and how an idea can be built: the recommended path, unverified risks, a minimum test plan and the next-stage scope.
When should I do one?
Before you commit money to parts, tooling or a full prototype, and again when you resume a paused project.
Can an AI agent do the research?
An agent can gather and summarise sources. A person still needs to judge the risks and run the physical tests.
Does ThingWeave certify my design?
No. Its outputs are research drafts with sources and open risks, not engineering certification.
Can ThingWeave manufacture my product?
No. Manufacturing and fulfilment are not offered in the pilot.