Who owns my prototype design, and do I need an NDA?

Jerome Privott · · 7 min read

Dark byitl graphic: the words 'You do' under the label 'Who owns the design', with 'board, firmware and case files' and the caption 'Every file is yours, once it's paid for.'

The short answer

You should own every file the builder makes for your device once you have paid for it: the circuit board files, the firmware source code and the case CAD. Get that in writing before any work starts. Sign an NDA before you share details, but know what it does: it is a promise to keep your information private, not ownership of your idea. At byitl, ownership moves to you milestone by milestone as you pay, and if you stop early you keep everything you paid for.

What files should I own when the prototype is done?

All of them, in a form you can change. A working device is three pieces of engineering, and each one leaves files behind. Here is the list our terms promise for a hardware build, in plain words:

Part Files you should get What they are
Circuit board Schematic and layout (we use KiCad), Gerbers, BOM, pick-and-place The drawing of the circuit, the board's shape, the files a factory prints the board from, the parts list, and where each part sits
Firmware Source code The code that runs on the device, in a form a developer can read and change
Enclosure STL and editable STEP, plus cut files if a part is laser cut The case, as a file you can 3D print and as real CAD you can edit
Everything else Renders, an assembly guide, review reports Pictures, how to put it together, and the checks it passed

The word to watch is "editable." A compiled firmware file lets you load the code onto the device, but a developer can't sensibly edit it. An STL prints fine, but editing it later is painful; I wrote about why in STEP vs STL. Ask for the source behind every output.

Does paying for the work make me the owner?

Only if the contract says so. Don't assume it. Look for a sentence that says ownership transfers to you, and when.

Ours is in section 4 of our terms: ownership of what we deliver "transfers to you when you have paid for it." For hardware that means the board, firmware and enclosure files.

We bill a prototype in three parts: 40% at kickoff, 30% when you approve the design, 30% at handoff. You can stop after any milestone and owe nothing more. If you stop, you own the deliverables of every milestone you paid for. Paid milestones are not refunded, because the design time and parts behind them are already spent.

If a builder's contract says nothing about who owns the work, ask a lawyer what that means for you before you pay. I'm not a lawyer, and nothing here is legal advice.

What about the builder's own tools?

A builder will keep its own tools, and that is fair, as long as you get a license to whatever of theirs ends up inside your product. Anyone who builds more than one device reuses templates and code. You don't need to own those. You need to be able to use them forever, with anyone.

Our terms handle it this way. We keep the tools, templates and reusable code we had before your project or build for general use. Where any of it is in your deliverables, you get a "permanent, royalty-free license to use, modify and manufacture it, with any manufacturer."

A real example. On our builds, the firmware's list of which chip pin does what is generated from the board design by our own tooling instead of being typed by hand. The generator stays with us. The file it writes for your board ships in your firmware source, and you can change it.

Can I take the files to a different manufacturer?

Yes, and that is the real test of whether you own your design. If you can send the files to any factory without asking the builder first, you own it. If you can't, you don't, whatever the contract calls it.

We had to do exactly this on our own device, the HC-01 humidor controller. The rev D boards came back from JLCPCB in July 2026. Three of the five would not power on, and two more had a display header that was only partly connected. Part of that was our mistake in the board files, and we wrote it up.

We fixed the files and sent rev E to a different company, PCBWay. All five rev E boards worked. Two things changed between the batches, the fix and the factory, and I can't say which one mattered more.

The point here is simpler. We could switch factories without asking anyone, because we held every file: Gerbers, parts list, placement file. Your prototype should leave you in the same position.

Do I need an NDA before I talk to a builder?

Ask for one before you share details beyond a one-line description. An NDA (non-disclosure agreement) is a contract to keep what you share private. We sign yours, or send our short mutual NDA, before you share anything.

Know what an NDA does and doesn't do:

  • It does commit the people who sign it to keep your information private and use it only for your project.
  • It doesn't give you ownership of the idea. That is what the contract and, if you need one, a patent are for.
  • It doesn't cover anyone who didn't sign it, so anyone else you show the details to should sign one too.

Two more things to check. First, your files will reach the board factory and parts suppliers, because that is how a board gets made. Our terms limit sharing to the manufacturing partners and service providers the work needs, our professional advisers, and cases where the law requires it. Second, ask whether the builder posts client work in a portfolio. We don't show your renders, photos or code publicly without your written permission.

What about a patent?

That is a question for a patent attorney, not a prototype builder. If you plan to file one, talk to an attorney before you show the prototype in public or start selling it, and ask them about timing. A prototype can help the conversation, because it shows exactly what you built.

Five questions to ask any builder before you sign

  1. Which files do I get, by name, including editable source for the board, firmware and case?
  2. When does ownership move to me: on final payment, or as I pay each milestone?
  3. If I stop partway, what do I own?
  4. Can I have it made by any manufacturer, and what license covers your tools inside my files?
  5. Will you sign my NDA before I share details, and will you post my project anywhere?

A builder who can answer all five in one sentence each has thought about it. Our answers are on the prototype page and in section 4 of our terms.

Questions people ask

Will a prototype builder steal my idea? I can only speak for us. What protects you either way is in writing: an NDA signed before you share details, and a contract that says you own the files once you pay.

Do I own the design if I stop halfway? With us, you own the deliverables of every milestone you paid for. With anyone else, read the contract for what happens when you stop.

Is an NDA the same as a patent? No. An NDA is a private promise between the people who sign it. A patent is a different legal right with its own rules, so ask a patent attorney about that one.

Do I get the firmware source code? You should. With us you get the full firmware source for the ESP32 chip family, not just the compiled file.

Can you show my prototype on your website? Not without your written permission. That covers renders, photos and code.

Have a device idea? Send a brief or score your device, or book a 15-minute call. We sign your NDA first if you want one.

Related