November 12, 2026 manufacturing onboarding contract-manufacturing

How to Onboard a Contract Manufacturer Without Losing Your Mind

Three weeks into your first production run, the project manager in Shenzhen sends a message that stops your morning cold: "Four components on your BOM are end-of-life. Two pad footprints don't match the Gerber. And we don't have test specifications — what should we test?" You thought you were three weeks into manufacturing. You're actually three weeks into discovering how much you didn't prepare.

This is the contract manufacturer onboarding story that plays out hundreds of times a year. Not because the CM is incompetent — they're asking exactly the right questions. The problem is that nobody told you these questions were coming.

The Real Timeline

Your Alibaba contact said two weeks. Your investor said "just find a CM and ship." The reality is that onboarding a contract manufacturer properly takes two to six months, depending on your product's complexity and how prepared you are walking in (Season Group).

That timeline isn't the CM being slow. It's the time it takes to align two organizations — yours and theirs — on exactly what gets built, how it gets tested, and what "good" looks like. Rushing this phase is how you end up with a factory floor running on assumptions instead of specifications, and assumptions always fail at scale.

Here's what the timeline actually looks like: NDA and initial engagement takes a week or two. BOM review and quoting takes two to four weeks — longer if there are sourcing issues. DFM review takes another two weeks, and this is where the CM earns their keep, catching manufacturability issues your design team missed. Tooling and fixture fabrication runs two to four weeks. First article inspection adds one to two weeks. And the pilot run — your real dress rehearsal — needs another two to four weeks before you're ready for volume production.

Each of those stages has a failure mode. And every failure sends you backwards, not forwards.

The BOM That Wasn't Ready

Consider what happened to a team building a Bluetooth sensor for industrial monitoring. They sent their CM a BOM exported from KiCad — part numbers, quantities, reference designators. Looked complete. The CM quoted it in four days. Everyone was excited.

Then the engineering review started. The MEMS accelerometer they'd spec'd had a 26-week lead time. The LDO regulator was marked "not recommended for new designs" — Texas Instruments' polite way of saying it's going away. Two 0402 capacitors had footprints that didn't match the land pattern in the Gerber files, because the schematic library had been updated but the layout hadn't been re-exported. And the BOM had no approved alternates listed for any component, meaning every single sourcing issue would come back to the founder for a decision.

None of this was the CM's fault. They were working with what they received. The CM's DFM engineer actually caught all of these issues — that's their job, and they're good at it. But catching them three weeks into the engagement instead of before it meant three weeks of quoting and scheduling had to be redone. The timeline slipped six weeks before a single board was assembled.

What Your CM Actually Needs From You

A contract manufacturer wants to do good work for you. What frustrates them isn't demanding customers — it's ambiguous ones. A CM can build to a tight spec with exacting tolerances. What they can't do is guess what you meant.

Before you contact a CM, you need a complete build package. Not just the BOM and Gerbers, but the full picture: the BOM with manufacturer part numbers, approved alternates for every critical component, and lifecycle status confirmed within the last 90 days. Gerber files exported from the final, released version of your layout — not the version you were still tweaking last Tuesday. An assembly drawing showing component orientation, keep-out zones, and any hand-soldering or rework areas. A test specification defining every measurement, every pass/fail limit, the test sequence, and what equipment is needed. Firmware binaries with version numbers and SHA-256 checksums, plus the programming method and any required provisioning steps. And acceptance criteria — IPC class (most programs default to IPC-A-610 Class 2; safety-critical products need Class 3) (Escatec), cosmetic standards, and any product-specific requirements.

That's a lot of documents. Any reputable PCBA manufacturer should offer a basic DFM review at no cost (Seacomp). Most first-time founders have maybe two of them ready. The rest get improvised during onboarding, which is why onboarding takes months instead of weeks.

The DFM Review That Saves You

The DFM — Design for Manufacturability — review is the single most valuable thing your CM does before production starts. This is where their manufacturing engineer goes through your design and tells you everything that will cause problems on their line.

Pad sizes too small for reliable reflow? They'll flag it. Via-in-pad without capping that will cause solder wicking? They'll flag it. Components too close together for their pick-and-place nozzles? They'll flag it. Panelization that wastes material or complicates depaneling? They'll redesign it. A startup that delays DFM review until post-layout can lose two to six weeks to avoidable redesign cycles (Season Group). A good DFM review catches twenty issues that would have become twenty production defects.

The mistake founders make is treating DFM feedback as criticism. It's not. It's your CM investing their manufacturing expertise in your product's success. A CM that sends back a ten-page DFM report is a CM that cares about your yield. A CM that says "looks fine, we'll start next week" is a CM that's going to discover those same issues during your pilot run, when fixing them costs ten times as much (Promwad).

First Article and Pilot: Your Dress Rehearsal

First Article Inspection is where you verify that the production line — not your design, the actual production process — produces boards that meet your spec. The CM builds three to five units using their production equipment, their operators, their solder paste, their reflow profile. You test every one against your full test specification.

This is where the test spec you wrote before onboarding pays off. Without it, first article inspection becomes "power it on and see if the LED blinks." With a proper test spec, you're measuring voltage rails under load, verifying sensor readings against known inputs, confirming wireless range at the minimum acceptable threshold, and logging every measurement. The data from these first articles becomes your baseline — the reference point for every production unit that follows.

The pilot run scales this to fifty or a hundred units. You're testing the process at close-to-production speed. Are the test fixtures making reliable contact? Is the programming step completing within the expected cycle time? Are the operators following the work instructions correctly? This is your last chance to fix process issues before they multiply across thousands of units.

Setting Up for the Long Run

The real goal of onboarding isn't getting the first batch out the door. It's building a relationship and a set of shared systems that make the second batch, and the tenth, and the hundredth, go smoothly.

That means version-controlled build packages, so the CM always has the current spec and you always know what they're building from. It means shared test data, so you can see yield trends and catch quality issues before they become field failures. It means defined change control, so neither side makes a component substitution or test limit change without the other knowing.

The teams that struggle with CM relationships aren't the ones with demanding specs. They're the ones with no specs at all — where every production decision becomes an email thread and every problem becomes a blame game. When both sides are working from the same defined package, with shared visibility into the same test data, the relationship transforms from vendor management into genuine partnership.

Your CM wants to be proud of what they build for you. Give them the specs, the test criteria, and the shared infrastructure to prove it, and they will.

Need help preparing your build package and onboarding your CM? AN & Factory provides test specifications, shared production dashboards, and CM integration tools. Get in touch.

Sources

Have thoughts on this? Join the discussion on our forum.

← Back to blog