Who can help with both the circuit board and the product enclosure?
Make It Physical can review the electronics and mechanical requirements together, then scope component sourcing, board assembly, enclosure fabrication, integration and agreed tests. Bring an electronics concept, existing modules or engineering files. We confirm design readiness and the responsibilities for any additional development before quoting the build.
The interfaces deserve attention early
A board that works on a bench may still need changes to fit inside a product. Mounting holes, connector locations, cable bends, display openings and access to switches all affect the enclosure. Heat, power, ventilation and antenna placement can also influence the mechanical design.
Share both sets of requirements at the start. We review the interfaces so the proposal covers how the parts are expected to fit and be assembled. Critical dimensions and acceptance checks are agreed against a specific design revision.
Start with modules or custom PCB files
An early concept may use existing modules to explore a function. A later version may need a custom board. We assess the starting point with you; a parts list generated by AI should be checked for exact manufacturer part numbers, compatibility and availability.
For an existing PCB design, useful inputs include Gerbers and drill files, a bill of materials, placement data, schematics and notes about the intended behavior. Explain which files are final and which are drafts. Missing design work is scoped before it becomes an assumption in a fabrication quote.
Define assembly and test responsibilities
The proposal identifies which parts are sourced, which are fabricated and what is assembled. Component substitutions are subject to approval. Wiring, fasteners, connectors and installation instructions may be as important as the board itself.
Specify how the device should be powered and what a passing test looks like. Firmware loading, firmware development, calibration, test fixtures and regulatory work require explicit agreement. A prototype functional check is not a certification or a guarantee of production compliance.
Make the handover specific
Agree whether the result should be a loose board, a fitted assembly or an enclosed working prototype. List the documentation and test records required as deliverables. If you need a second build later, keep the approved design revision and component decisions identifiable.
Quantity, source availability, enclosure process and the extent of integration affect costs and timing. Shipping arrangements are reviewed for your destination. Submit the complete product requirements even if you are unsure which parts need engineering first.
Questions about this starting point
Can I send existing modules instead of a custom PCB design?
Describe the modules and how they should work together. Suitability, sourcing and integration work are reviewed before committing to a build.
Can the enclosure be developed around my board?
Share the board dimensions, mounting holes, connectors and component heights. We review the mechanical design work needed and agree its scope.
Is firmware development included automatically?
No. Firmware development, loading and testing responsibilities must be specified in the proposal.
Prepared by Make It Physical · Updated October 20, 2026. Project scope and deliverables are confirmed after review.