Electronic Prototyping
Working hardware fast, built where it was designed, so every iteration answers a question instead of raising new ones.
What is electronic prototyping?
Electronic prototyping is building early versions of a product to answer engineering questions before committing to production tooling. A prototype might prove a concept works, test what a user experiences, or qualify the final design. We design and assemble prototypes ourselves, so each iteration turns around in days rather than vendor cycles.
A prototype is a question, not a small production run
The most expensive prototyping mistake is building a beautiful five-figure unit to answer a question a quick lash-up could have settled. The second most expensive is the reverse: trying to learn production lessons from a breadboard. Every build we quote starts with the same conversation — what, exactly, is this prototype supposed to prove?
Get that answer right and prototyping is cheap insurance. It is the difference between finding a dead-end architecture on the bench and finding it after tooling.
What we prototype
If it has a circuit board in it, it is probably in range. Typical builds:
Why in-house assembly changes prototyping
A prototype iteration at most design firms means releasing files, quoting an assembler, waiting out the queue, and receiving boards weeks later — sometimes with a mystery defect and no one accountable for it. Ours are built in-house, by people who can ask the designer what they meant.
The practical difference: our schedule is set by part lead times rather than by an assembler's queue. And when a board misbehaves, engineering and assembly diagnose it together the same afternoon instead of over a two-vendor email chain.
Proof-of-concept vs works-like/looks-like vs production-intent: which prototype do you need?
Prototype is one word for three different tools. A proof-of-concept tests an idea, works-like and looks-like builds test the product experience, and a production-intent prototype tests the design you will manufacture. Building the wrong one wastes the money the right one would have saved.
| Proof-of-concept | Works-like / looks-like | Production-intent | |
|---|---|---|---|
| Question it answers | Can this idea work at all? | Is this the right product? | Is this design ready to manufacture? |
| Built from | Dev kits, eval boards, breadboards | Custom PCB in a representative enclosure | Final parts, final processes, final form |
| Fidelity | Function only, no form | Close to the real experience, shortcuts inside | Indistinguishable from early production units |
| Speed & spend | Days to weeks, minimal cost | In between on both | Slowest and most expensive, by design |
| What follows | A real development program, or a cheap no | Design refinement with user feedback | EVT/DVT validation and the production ramp |
Prototyping with assembly down the hall
From design files to working boards
- 01
Define the Question
Every prototype exists to answer something specific. We write that question down first, because it decides how rough or how real the build needs to be.
- 02
Design for Speed
Schematic and layout choices favor iteration: parts that are in stock, test points everywhere, and modules standing in where custom design can wait.
- 03
Build & Bring Up
Boards are assembled on site and brought to life on the bench, instrumented so every observation becomes usable data.
- 04
Iterate or Graduate
Findings feed the next revision, or the design graduates to production-intent engineering. Either way you get the results and a clear recommendation.
What comes back from the build
Build capability at a glance
Electronic Prototyping FAQs
Typically in days once parts are in hand, because our boards are built where they are designed. In practice, part availability sets most prototype schedules — long-lead components, not assembly time.
Budget for two to three board revisions on a typical product. One is rare and usually means the product was simple. Five usually means the requirements were still moving. The goal of each build is to make the next one boring.
Yes. A proof-of-concept prototype is often the cheapest way to find out whether an idea deserves a full development program.
They are already in the design. Prototyping, engineering, and production are one team here, so every assembly issue and test finding from prototype builds feeds directly into the production-intent design instead of getting lost in a handoff.
Explore related services
Electronic Product Design
End-to-end electronic product design — requirements, system architecture, hardware, PCB, firmware, and validation — carried all the way to production.
Mechanical & Enclosure Design
Enclosure and mechanical design for electronic products — 3D CAD, thermal paths, ingress sealing, and DFM for molding, machining, and printing.
IoT Product Development
IoT product development at the device level: radio selection, RF and antenna design, low-power firmware, provisioning, and certification.