Who should design your board, and why not just pick the cheapest?
A PCB is a small part of a product budget but a large part of its schedule risk. A board that does not work, cannot be assembled reliably or needs a respin costs more in lost time than a careful design would have cost up front. The cheapest provider often leaves out review steps, documentation or fabricator communication, and you find out only when the prototype arrives.
The first thing to establish is who will actually do the work. Some companies resell design work to a subcontractor, which adds a layer of communication and margin, and your questions reach the designer only second hand. Ask directly whether the people you speak with are the people drawing your board, and whether any part of the job is subcontracted.
Each model has a place. An in-house designer knows your product best but is limited to a single viewpoint and availability. Freelancers can be excellent but vary widely and may be a single point of failure, while a design agency offers more depth and continuity at the cost of a more structured process.
| Factor | Freelancer marketplace | Design agency | In-house designer |
|---|---|---|---|
| Experience range | Varies widely by individual; needs careful vetting | Usually several designers with different specialties | Deep product knowledge, narrower technology exposure |
| Continuity | Depends on one person being available | Team coverage if someone is unavailable | Strong while the person stays; a risk if they leave |
| Process and review | Individual habits; peer review often absent | Defined workflow and internal review is possible | Depends on company practice and a second reviewer |
| Scalability | Hard to scale across several boards at once | Can add capacity for concurrent projects | Fixed capacity unless you hire more |
| Best fit | Small, well-defined boards with a low risk of change | Complex or multi-discipline projects and ongoing products | Steady, long-term design load tied closely to one product |
Do their tools and file formats match yours?
Ask which design tool the provider uses and whether you will receive native project files or only exports. Native files in the same ecosystem you use let your team open, review and modify the design later without rebuilding it from Gerbers, which is far harder than it sounds. Hire PCB Designer works primarily in Altium Designer, so Altium native projects are a natural fit.
If you use a different tool, ask how they handle it: whether they can work natively in it, or how they would translate libraries and schematics. Also ask about library practice, since a clean and verified component library is what makes a design maintainable.
What DFM, DFA and board technology experience should they show?
Design for manufacturing and design for assembly are what separate a board that looks right on screen from one that builds and assembles reliably. Ask how the provider checks a design against fabricator capabilities, how they handle stackup agreement and what review happens before release. Hire PCB Designer follows a DFM and DFA workflow, and works with a team that spans a US headquarters in Wyoming and a fabrication center in Bangladesh.
Then match their experience to your board. Multilayer, HDI, rigid-flex and high-speed designs each have their own pitfalls, so ask for a description of comparable boards they have designed, the main challenges, and what they would do differently. Specific, technical answers are a better sign than a general claim of experience in everything.
Can they integrate schematic, firmware and enclosure work?
Many board problems come from the boundaries between disciplines: a pin assignment that firmware cannot use, a connector that collides with the enclosure, or a thermal assumption nobody checked. A provider who handles schematic capture, layout, firmware and mechanical design together can catch these issues earlier, because one team sees the whole product.
That does not mean you must buy everything from one provider. It means you should ask how they coordinate with your firmware and mechanical teams, what information they exchange, and who is responsible for resolving conflicts.
Which deliverables should you receive at the end?
Agree the deliverables in writing before work starts, so that the handover is complete and you are not dependent on the provider later. A good package lets another engineer or a fabricator pick up the project without guesswork.
- Native project files: schematic, PCB layout, libraries and project settings.
- Fabrication outputs: Gerber or ODB++, drill files and the netlist for verification.
- Bill of materials with manufacturer part numbers and approved alternates where relevant.
- Assembly drawings, pick-and-place data and any special assembly notes.
- Stackup documentation, including layer order, materials and impedance targets.
- Fabrication notes and drawings stating tolerances, finishes and special requirements.
Who owns the IP and how is confidentiality handled?
Your design is intellectual property, so clarify ownership before sharing detailed files. Ask for the terms in writing: who owns the design files on completion, whether the provider may reuse any part of the work, and how they store and protect your data. A signed NDA and a clear services agreement should be normal, and any hesitation to put terms on paper is a warning.
Also ask who has access to your files inside the provider organization, and what happens to them when the project ends. Questions about data handling are reasonable, and a mature provider will answer them plainly.
How do communication, revisions, references and certifications fit in?
Ask how projects are managed: who your point of contact is, how often you get updates, how design reviews are scheduled, and how many revision rounds are included. Clear rules about change requests protect both sides, and a provider with a defined process is easier to work with than one improvising. Time zone overlap also matters, and a team spread across several regions should be able to explain how handovers work.
For credibility, ask for relevant references or examples that can be shared under confidentiality, and ask which quality standards they follow. IPC standards for PCB design and fabrication and ISO 9001 quality management are worth asking about, along with what they actually mean in daily practice. Treat them as questions to put to every provider, and ask for evidence rather than accepting a logo.
What are the 10 questions to ask before you hire?
Send these to each shortlisted provider and compare the answers side by side. Vague or evasive replies tell you as much as detailed ones.
- Who will actually design my board, and is any work subcontracted?
- Which design tool do you use, and will I receive native project files?
- How do you perform DFM and DFA checks, and when do you talk to the fabricator?
- Which boards similar to mine (layer count, HDI, rigid-flex, high-speed) have you designed?
- Can you coordinate schematic, firmware and enclosure work, and how?
- What exactly will I receive at handover, including documentation and stackup?
- Who owns the IP, and will you sign an NDA with terms in writing?
- How many revision rounds are included, and how are changes priced?
- How will we communicate, and how often will I see progress?
- Which references, examples and quality standards can you share?
This guide is general educational information. Requirements vary by project, fabricator and applicable standards, so confirm specifics with your manufacturer and test lab.