ClarifyThe autonomous CRM that helps you sell more
Promoted
canitbebuilt
Your hardware idea, inspected. Verdict, BOM, 3D model.
222 followers
Your hardware idea, inspected. Verdict, BOM, 3D model.
222 followers
Have a hardware idea? Describe it in a sentence. You get back a verdict (Buildable / Buildable with changes / Heavy lift / Not viable), a bill of materials costed at 100, 1,000 and 10,000 units, subsystem risk ratings, certification gates for your market, and a 3D concept model. Two minutes, no signup. Criteria come from 23 years of hardware building. Running on GPT-5.6 Terra.
canitbebuilt
canitbebuilt
@jogindertanikella Congratulations on the launch!!
canitbebuilt
@austinbuhl Thank you! :)
canitbebuilt
@thys_beesman Thank you for your comment. I wanted the reports to feel less like they came from a spreadsheet and more like they came from an experienced hardware engineer. So I used my 23 years of experience to shape the prompting and the evaluation rubric. The judgment isn't arbitrary, it's grounded in practical engineering gates. As more engineers challenge the reports, I'll keep refining that rubric.
canitbebuilt
@thys_beesman On the verdicts: you're right, there's judgment involved. My 23 years isn't deciding the answer, it's defining the engineering rubric. The tool checks concrete gates like custom silicon vs integration, manufacturing complexity, and certification requirements. Most engineers agree on those. Where opinions differ is usually because someone has already built that category before. The verdict is calibrated for a first-time team, and I should make that clearer. If an engineer disagrees, I'd genuinely like the report serial number because that's valuable calibration data.
On BOM costing: it's a directional estimate, not live pricing. The goal isn't to predict the exact BOM, but to show the right cost range and what's driving it. Prices for modules and batteries change, so these numbers are for go/no-go decisions, not procurement. Think of it as an experienced hardware engineer's first-pass estimate, with the reasoning shown.
Dial
the framing of 23 years of judgment encoded into a verdict is the interesting part to me. when it says Buildable, is there any confidence signal for ideas that fall outside your own experience base, or is every verdict presented with the same certainty regardless of how novel the idea is
canitbebuilt
@galdayan Thank you for your comment. If you say a Nuclear Power Reactor, it's going to show as Not Viable. :) So all are not having the same certainty.
Dial
a BOM generated from a text description is only as useful as how close it is to sourceable reality - part costs and availability swing wildly by region and by whether you're ordering 10 units vs 10,000. is the BOM pulling from live supplier/distributor pricing or is it more of a ballpark estimate based on typical component costs?
canitbebuilt
@omri_ben_shoham1 Thank you for your comment. Linking live supplier/distributor pricing would be a natural progression once there's some traction. Right now, it's a rough estimate and will vary based on quantity.
Dial
makes sense, rough-but-directional is still way more useful than nothing at the idea stage. quantity-based variance is probably the harder problem to solve for anyway since a single-unit BOM and a 500-unit BOM can point to completely different suppliers
canitbebuilt
@omri_ben_shoham1 Thank you. It's just to give a rough idea right now for people to get started. Plan to integrate supplier quotes in the next phase.