1. State the purpose
Bring-up, fit check, demo, or near-production pilot.
Prototype work is not another layer-count product page. XFPCB focuses on complete file packages, early DFM holds prevention, and schedules that match bring-up, enclosure fit, and revision loops.
People searching for prototype PCB manufacturing want realistic turn times, a checklist that prevents CAM stops, and a path from sample to the next revision. They are not looking for a multilayer theory essay. XFPCB structures prototype jobs around purpose: electrical validation, mechanical fit, assembly trial, or customer samples.
Tell us which purpose applies. A board meant only for firmware bring-up can often use stock FR-4 and a standard finish, while a thermal or RF validation sample may need different material discipline even at small quantity.
| Item | Why it matters on prototypes |
|---|---|
| Gerber or ODB++ + NC drill | Mismatched drills are the classic fast-queue stopper. |
| Board outline and units | Prevents profile surprises and wrong scaling. |
| Stackup / thickness / copper | Avoids mid-build material debates. |
| Finish and mask color | Stock finishes stay on the quicker path. |
| Impedance notes (if any) | Missing targets force clarification loops. |
| Quantity and need-by date | Lets planning choose a realistic queue. |
Complexity costs calendar time even on a dedicated quick path. Design the first article to the schedule you need, then harden the design for volume later.
Bring-up, fit check, demo, or near-production pilot.
Use the checklist so CAM can release without guessing.
Samples ship with notes useful for the next revision.
Carry DFM lessons into the following Gerber set or volume release.
Prototypes prioritize learning speed. XFPCB still runs CAM and DFM checks, but documentation and sourcing can stay lighter than a locked volume release. When the design freezes, reuse the same stackup notes so production inherits a known construction.
Send Gerbers or ODB++, drill, outline, stackup or thickness, material, copper, finish, quantity, and needed date. Mark anything still changing so we know what is frozen.
Incomplete or conflicting files that trigger DFM questions. A clean package keeps the job in the fast path more than any expedite note alone.
Yes. See fast prototype PCB assembly. Partial BOMs are acceptable when DNP lines are clearly marked for bring-up.
Use in-stock materials and common finishes, avoid late stackup changes, stay within standard trace and via rules, and consign long-lead parts if assembly is included.
Say what the sample is for (bring-up, fit, demo, or pilot), attach a complete file set, and give the need-by date. XFPCB will flag DFM risks that would kick the job out of a fast queue.