惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

F
Fortinet All Blogs
Microsoft Security Blog
Microsoft Security Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
Vercel News
Vercel News
Application and Cybersecurity Blog
Application and Cybersecurity Blog
C
Check Point Blog
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
W
WeLiveSecurity
The Hacker News
The Hacker News
L
LINUX DO - 热门话题
T
Tenable Blog
Hugging Face - Blog
Hugging Face - Blog
Google Online Security Blog
Google Online Security Blog
博客园 - Franky
P
Proofpoint News Feed
H
Hacker News: Front Page
P
Privacy & Cybersecurity Law Blog
月光博客
月光博客
P
Proofpoint News Feed
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
The GitHub Blog
The GitHub Blog
云风的 BLOG
云风的 BLOG
博客园_首页
www.infosecurity-magazine.com
www.infosecurity-magazine.com
C
CERT Recently Published Vulnerability Notes
Forbes - Security
Forbes - Security
I
InfoQ
Stack Overflow Blog
Stack Overflow Blog
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Attack and Defense Labs
Attack and Defense Labs
N
News and Events Feed by Topic
博客园 - 叶小钗
T
Threat Research - Cisco Blogs
aimingoo的专栏
aimingoo的专栏
D
Darknet – Hacking Tools, Hacker News & Cyber Security
小众软件
小众软件
大猫的无限游戏
大猫的无限游戏
MongoDB | Blog
MongoDB | Blog
CTFtime.org: upcoming CTF events
CTFtime.org: upcoming CTF events
Hacker News - Newest:
Hacker News - Newest: "LLM"
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 司徒正美
O
OpenAI News
G
Google Developers Blog
Martin Fowler
Martin Fowler
罗磊的独立博客
S
SegmentFault 最新的问题
T
Tor Project blog
量子位

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant Common SOC 2 Failures (Real World) Stop Vibe-Checking Your AI App: A Practical Guide to Evals How to Use SonarQube and SonarScanner Locally to Level Up Your Code Quality Your Next To-Do App Is Dead — I Replaced Mine with an OpenClaw AI Sign a Nostr event in 60 lines of Python using coincurve — no nostr-sdk, no nbxplorer, no rust toolchain ITGC Audit Explained Like You’re in Big 4 Patch Tuesday abril 2026: Microsoft parcha 163 vulnerabilidades y un zero-day en SharePoint Stop scraping everything: a better way to track competitor price changes Listing on MCPize + the Official MCP Registry while routing payments OUTSIDE the marketplace — how I kept 100% of my x402 revenue Building an AI-Powered Risk Intelligence System Using Serverless Architecture Why We Ripped Function Overloading Out of Our AI Toolchain Testing AI-Generated Code: How to Actually Know If It Works SaaS Churn Is Killing Your Business. Here Is What to Do About It (Without a Support Team) The Speed of AI Is No Longer Linear - And Self-Improving Models Are Why How to Implement RBAC for MCP Tools: A Practical Guide for Engineering Teams From Standard Quote to Persuasive Proposal: AI Automation for Arborists I built a CLI that scaffolds complete multi-tenant SaaS apps Axios CVE-2025–62718: The Silent SSRF Bug That Could Be Hiding in Your Node.js App Right Now The dashboard that ended our friendship Data Pipelines Explained Simply (and How to Build Them with Python) The Hidden Cost of AI Systems Nobody Talks About. undefined vs undeclared, and how typeof behaves Switching from file-based jobs to NATS/Kafka in Rust without changing code io_uring Adventures: Rust Servers That Love Syscalls Why Agentic AI is Killing the Traditional Database The POUR principles of web accessibility for developers and designers Quantum Neural Network 3D — A Deep Dive into Interactive WebGL Visualization How To Install Caveman In Codex On macOS And Windows Automation Pipeline Reliability: Why Your Workflow Breaks When Nobody Is Watching I Built an 'Open World' AI Coding Agent — It Works From ANY Folder From Freelancing to Product: A Tech Service Company's SaaS Transformation China's AI Giants: Adding Tencent Hunyuan & ByteDance Doubao to AI University (74 Providers) On the Vibe Coders and Their Lies clerk: Auto-Summarize Your Claude Code Sessions AI Weekly — 2026/04/10–04/17 | The Model Lockdown Is Here, but the Toolchain Is the Real Battleground AI 週報 — 2026/04/10–2026/04/17 模型封鎖潮來了,但工具鏈才是真戰場 Maybe this is how Open-Source apps are born... 🚀 Fine-Tune LLMs with LoRA and QLoRA: 2026 Guide tRPC v11 + Next.js App Router: End-to-End Type Safety Without the Boilerplate ShadCN UI in 2026: Why I Stopped Installing Component Libraries and Started Owning My Components SaaS Billing in React Server Components: Stripe + Supabase Without a Single `useEffect` Join our DEV Weekend Challenge — $1,000 in Prizes Across TEN winners! Submissions Due April 20 at 6:59 AM UTC. Implementing FSRS Spaced Repetition in Flutter + Supabase — Adding Memory Science to an AI Learning App "I Texted My Localhost From the Train — Claude Code Fixed the Bug Before I Got Home" I Built a Sales Prep AI and It Went Deeper Than Expected Design to Code #2: One JSON, Eleven Outputs Solving the 100M-Row Problem: A Summary Table Pattern for High-Volume Push Notification Logs Flutter Web With Wasm: What Actually Changes For Developers I Built 50 Royalty-Free Soundtracks for My Side Project in a Weekend Using AI Music Generation The Vibe Coding Security Checklist: 7 Things to Check Before You Ship Stop Letting Googlebot Guess Fix Your React App's SEO Right Desconstruindo o Streaming do LinkedIn: Como Criar um Engine de Extração de Vídeo de Alta Performance com HLS e FFmpeg (EDA Part-1) EDA (Exploratory Data Analysis) Explained With Real Life — Why Looking at Your Data Is the Most Important Step in Machine Learning Brand Relationship Management at Scale: Our 4-Touch Outreach System for 200+ Brands Why String.fromEnvironment() Might Return an Empty String in Dart JGuardrails 1.0.0 — Hardening Java LLM Apps Against Jailbreaks, Toxicity, and Prompt Injection Plan and Schedule a Full Week of Threads Content From One Claude Conversation Coding Cat Oran Ep3, Five Tables Changed Everything Updated: BFF Pattern I'm done watching freelancers get buried by 200 proposals. So I'm building the alternative. This is my first post BFS Algorithm in Java Step by Step Tutorial with Examples Tracking LLM Pricing Monthly: An Open Dataset for 22 AI Models How We Measure Content ROI on a Comparison Site: Revenue Attribution Without Perfect Data Introducing Nova AI Ops: The AI-Native Operating System for SRE Teams I built a free desktop video downloader for Windows — Grabbit How Talkie OCR Helps Vision-Impaired & Dyslexic Users Read the World Around Them VRCFaceTracking安装和iPhone面捕配置教程,有bug Even CrowdStrike Can't See Your Agents The Automation Gold Rush: What n8n Workflows and Claude Are Opening Up for Developers Right Now
Hardware Startup Manufacturing in China: A Founder's Guide
China Sourcing Agents · 2026-05-31 · via DEV Community

Most hardware crowdfunding campaigns don't fail at the fundraising stage. They fail in the four to eight months that follow — specifically in the transition from "working prototype" to "factory-ready design." A sourcing agent with an engineering background changes this equation because they catch design-for-manufacture (DFM) issues before tooling is cut, before the money is committed.

This guide covers what actually happens between a Kickstarter closing and a shipping container leaving Shenzhen — the stages, the costs, what can go wrong at each, and where an experienced hand makes a measurable difference.

The three stages most hardware startups don't plan for

The hardware startup mental model is usually: build prototype, run campaign, ship product. The factory side is treated as an implementation detail.

In practice there are three distinct engineering stages between a working prototype and a shipping product, and each one involves a different factory relationship and different costs.

Stage 1: Prototype → Engineering Validation (EV)

This is the stage founders are familiar with. The goal is to prove the product works. EVs are usually hand-built or contract-assembled in small quantities (1–10 units). The factory relationship, if there is one, is loose — often a prototype house rather than a production factory. Cost at this stage is dominated by NRE (non-recurring engineering) and component procurement at retail or near-retail prices.

Stage 2: Engineering Validation → Design Validation (DV)

This is where most hardware startups get surprised. DV means proving the design can be manufactured reliably and repeatedly. The factory takes the EV design and builds 20–100 units using production-like processes. Defects in this stage are design defects — PCB layouts that cause soldering issues, housing tolerances that make assembly too slow, components that fail at production-line temperatures.

Fixing these problems requires design revisions, which may require new tooling. DV is iterative and expensive, and founders who didn't budget for it either delay or compromise on quality.

Stage 3: Design Validation → Production Validation (PV)

PV is the bridge from "we can make it" to "we can make it at volume." A pilot run of 200–500 units is assembled, inspected, and used to set yields, cycle times, and QC pass rates. The data from PV is what the factory uses to price the mass production run and commit to a timeline.

Founders who budget for Stage 1 and get surprised by Stages 2 and 3 are the ones who miss their shipping estimates by four months and go back to backers asking for patience.

What a sourcing agent does at each milestone

Before your campaign launches

The work that happens before a campaign is often the most valuable and the least visible. A sourcing agent with manufacturing experience can:

  • Survey the supplier landscape for your product category — who makes it, what the typical MOQ looks like, what certifications are achievable and at what cost
  • Produce a preliminary Bill of Quantities (BOQ) cost estimate based on your design, before you've committed to any factory
  • Flag DFM issues in your prototype design that would require expensive tooling revisions later
  • Identify which certifications (FCC, CE, RoHS) you need and give you a realistic timeline — this is important because certification timelines frequently conflict with shipping promises made during crowdfunding campaigns

The cost of this work: typically $500–1,500 for a preliminary manufacturing review and supplier landscape report. The value: knowing before you campaign whether your $45 landed price target is achievable, and whether your "ships in June" promise is realistic.

Campaign funded: RFQ and factory selection

Once you have funds committed, the first formal step is getting quotes from qualified factories. A well-run RFQ process involves:

  • Sending a complete RFQ to 5–8 pre-qualified factories (not 50 — factories that see a mass RFQ give it minimum effort)
  • Completing a factory audit for the top 2–3 respondents — you want to visit before you place any money
  • Signing NDAs with the shortlisted factories before sharing your full design files

The NDA step is one that founders consistently skip because they're eager to move fast. Don't. Your design files contain your manufacturing IP. A factory that receives your Gerber files, BOM, and housing drawings without an NDA has no legal obligation not to copy them or share them with a competitor. The NDA doesn't guarantee IP safety — nothing does in China manufacturing — but it creates a legal paper trail and signals that you're a serious buyer who knows how the process works.

Factory audits for electronics startups focus on specific capabilities: SMT line specifications (which nozzle sizes, what pick-and-place machines), in-house testing capability (aging chambers, functional test fixtures, RF test), and quality certifications relevant to your product. Use the factory audit checklist to know what to look for.

Engineering samples (ES): 5–20 units

After signing a manufacturing agreement with your chosen factory, the first formal deliverable is engineering samples — typically 5–20 units built by the factory using production-like processes. The timeline is usually 4–8 weeks from order to delivery.

Engineering samples are not the same as your prototype. The factory makes them using their tooling (if tooling exists at this stage), their component suppliers, and their assembly process. This is when you first see what your product actually looks like when made by someone else, at scale.

Evaluate ES units against a written evaluation checklist, not against your gut feeling. Areas to check:

  • Mechanical fit and finish: housing tolerances, button feel, seam alignment
  • Electrical function: all features working per spec
  • RF performance: Bluetooth, WiFi, or cellular operating at spec across temperature range
  • Battery runtime: within 10% of target
  • Charging: full cycle with the correct charger

Document every deviation from spec in writing. This document becomes the basis for the DV revision discussion with the factory.

Pilot run (PR): 50–200 units

After ES revisions are incorporated and the factory signs off on a validated design, the pilot run produces 50–200 units using the production process — the same assembly line, the same component reels, the same test fixtures that will be used in mass production.

The pilot run is where manufacturing yields first become visible. If the factory's SMT line has a solder paste stencil that's slightly off spec, you'll see a consistent reflow defect pattern. If the injection molding tool has a sink mark issue, you'll see it in every unit. A 5% yield loss on a pilot run of 200 units is annoying. The same 5% yield loss in a mass production run of 10,000 units is a $50,000 problem, assuming a $100 unit cost.

For your first production relationship with a new factory, run a pilot run. The cost is higher per unit than mass production (because they're not at full line efficiency), but the data it generates is worth more than the savings from skipping it.

Mass production (MP): 500+ units

By the time you reach mass production, the factory should have:

  • A validated design with approved component substitutions documented
  • A test fixture calibrated to your spec
  • An AQL sampling plan agreed in writing
  • A delivery timeline with milestone dates

Quality inspection in mass production follows three stages:

Pre-production (PP) inspection: Before manufacturing starts, verify the factory has received the correct components. Check BT module part numbers, battery cell model, PCB revision, housing tooling revision. Specification drift starts here — factories sometimes substitute cheaper components without notifying the buyer. Catching it before a run starts is free; catching it after 5,000 units are assembled is not.

During-production (DUPRO) inspection: When 10–20% of the batch is complete, inspect the first finished units. Problems found at this stage affect only the units already assembled; the remaining 80–90% of the run can be corrected. This is the highest-value QC intervention in mass production.

Pre-shipment inspection (PSI): When 100% of production is complete and at least 80% is packed, perform an AQL sample check. For consumer electronics, AQL 2.5 is standard — on a 5,000-unit batch, this means checking 200 units with a pass/fail threshold of 10 defects.

DFM: the most expensive review to skip

Design for Manufacturability review is a systematic check of your design against the capabilities and constraints of the production process. For an electronics product, a DFM review typically covers:

  • PCB trace spacing and via sizing: pick-and-place machines have minimum component size requirements; some component footprints look fine in CAD but cause soldering defects on a production reflow oven
  • Component footprint accuracy: a 0402 resistor with a poorly-matched footprint will have inconsistent solder joints; multiply that by 50 components per board and 5,000 boards
  • Housing draft angles: injection-molded housing parts need draft angles (typically 0.5°–3° depending on finish) to release from the mold; zero-draft surfaces cause mold sticking and part deformation
  • Battery connector accessibility: if the battery connector is in a location that requires removing three other sub-assemblies to access, labor cost per unit goes up and assembly consistency goes down
  • Test point accessibility: ICT (in-circuit test) fixtures need physical access to test points; a board where critical test points are under components or on the wrong layer will require either a custom fixture or manual testing

The cost of catching a DFM issue before tooling is cut: a DFM review typically runs $500–1,500 and takes 3–5 days.

The cost of catching it after: a mold revision in Dongguan typically costs $3,000–15,000 depending on the revision complexity, and adds 4–6 weeks to the timeline. A PCB layout revision after the first production run requires a new Gerber order, new stencil, and scrapping the boards already assembled. On a 200-unit pilot run, that's $4,000–12,000 in wasted material depending on component cost.

Request a DFM review before any tooling is cut. For an OEM/ODM project, the factory should provide DFM feedback as part of the engagement — but don't assume they will without asking, and don't assume their feedback is complete. For the PCB side specifically, our PCB assembly sourcing page covers the factory evaluation criteria — SMT line specifications, IPC class requirements, and inspection coverage — that determine whether a factory can actually produce your board to spec.

The tooling decision

Injection molding tooling is the largest single capital cost in most consumer hardware products, and it's the one founders are least prepared for.

Prototype tooling (soft tooling): Aluminum molds, faster to machine, lower cost ($2,000–8,000 for a simple 2-cavity mold), shorter lifespan (typically 5,000–20,000 shots). Used for early DV and pilot runs. The advantage is that modifications are cheaper — you can still add material to an aluminum mold via welding, whereas a steel mold modification is significantly harder and more expensive.

Production tooling (hard tooling): Hardened steel (typically P20 or H13), slower to machine, higher cost ($5,000–50,000 depending on part complexity and number of cavities), rated for 500,000–1,000,000+ shots. Required for mass production runs above 10,000–20,000 units.

Who owns the tooling: You do, or should. Tooling paid for by the buyer belongs to the buyer — this should be stated explicitly in the manufacturing agreement. A factory that holds your tooling without a clear ownership agreement has significant leverage over your supply chain. If you switch factories, tooling they "own" doesn't move with you.

Where tooling is stored: Typically at the factory that uses it. Get explicit written agreement on storage, maintenance responsibility, and the right to retrieve it on 30 days' notice.

For PCB tooling: the Gerber files and pick-and-place program are your production IP. Keep copies. Panelization — arranging multiple PCBs on a single production panel — is something the factory handles but you should understand: it affects SMT line efficiency and cost per board.

Certifications: timing matters more than you think

For most consumer electronics products sold in the US and EU, you need:

  • FCC (Part 15): Required for US market, covers intentional and unintentional RF emitters. Certification process: 6–12 weeks, cost $5,000–15,000 for a typical Bluetooth device. Voluntary testing labs (A2LA accredited) in China or US.
  • CE marking: Required for EU market, covers multiple directives (RED for radio, LVD for low-voltage, ROHS). Timeline: 4–12 weeks depending on directives involved. Can often run in parallel with FCC.
  • RoHS: EU restriction of hazardous substances — requires declaration from component suppliers, verified against your BOM. Usually bundled with CE process.
  • UN 38.3: Required for lithium battery transport, regardless of market. Without it, your finished goods can't be air-shipped.

The crowdfunding timing trap: Kickstarter and Indiegogo campaigns routinely promise delivery timelines that don't include certification time. A campaign that closes in January and promises August delivery is implicitly assuming that FCC and CE certification are already underway or complete — which they almost never are for a first-time product.

The realistic buffer: start FCC/CE certification in parallel with your pilot run, at minimum. That means certification is running while you're still validating the manufacturing process. If the certification test fails (common — first submissions fail roughly 40–50% of the time for products with RF components), you have time to address the findings before mass production is complete.

The module approach: Using a pre-certified BLE or WiFi module (Nordic Semiconductor, Espressif, u-blox, Murata) significantly reduces your certification scope. Instead of certifying the entire radio system, you certify only the product-level integration — typically shorter timeline and lower cost. For a first product, using a certified module is almost always the right call.

Common milestone mistakes

Locking in a factory before IP agreements are signed. Some factories will not work without an NDA; some will. Regardless of what they say, sign one before sharing Gerbers, BOM, or housing drawings. The factory that copies your design two years later is often not the one that seemed obviously untrustworthy — it's the one you thought was your partner.

Starting tooling before DFM review. This happens when founders are impatient and the factory is eager to take the tooling payment. Tooling is the point of no return. Whatever DFM issues exist in the design at that point become very expensive to fix. Do the DFM review, get written sign-off, then cut tooling.

Paying 100% deposit before production is validated. Standard payment structure is 30% deposit on order confirmation, 70% before shipment — after passing PSI. Factories that insist on 50% or more upfront before you've seen any product are a risk signal. A founder who pays 100% upfront has no leverage if quality problems emerge during production.

Skipping the pilot run to save time. The argument is usually "we need to ship in four months and the pilot run takes six weeks." The reality: a pilot run that reveals a 12% yield loss will cost you far more than six weeks if you discover the same problem during mass production. The factories that are most confident you don't need a pilot run are the ones you should be most concerned about.

Not identifying a backup supplier before mass production starts. Single-source dependency on a factory is manageable when everything is going well. It becomes a serious business problem when the factory has a fire, a labor dispute, or simply decides your order isn't a priority. Maintain a relationship with at least one qualified backup factory after your first production run.

Realistic timeline and cost

The following assumes a consumer electronics product with custom injection-molded housing, PCB with BLE module, and battery — targeting US and EU markets at 5,000-unit initial production run.

Phase Duration Key Deliverable Typical Cost
Factory shortlist + audit 2–4 weeks Verified factory, signed NDA $500–1,500
Engineering samples 4–8 weeks 5–20 units vs. spec $2,000–8,000
DFM review + tooling 6–10 weeks Production-ready tooling $8,000–40,000
Pilot run 4–6 weeks 50–200 units, validated process $3,000–15,000
Certifications (parallel) 8–16 weeks FCC + CE certificates $5,000–20,000
Mass production 4–8 weeks Production units MOQ × unit cost
Pre-shipment inspection 1 week AQL pass certificate $300–500
Ocean freight (Shenzhen → LA) 3–5 weeks Goods at destination port $2,000–6,000

The total elapsed time from "campaign funded" to "goods at US warehouse" is realistically 9–14 months for a first-time product. Campaigns that promise 6-month delivery from close are banking on everything going right on the first try — which almost never happens.

The total capital required before the first dollar of revenue (excluding campaign funds for the production order itself): $20,000–80,000, depending on product complexity, tooling requirements, and certification scope. This is often a shock to founders who assumed the campaign proceeds would cover everything.

The sourcing agent's role: what it changes

The process above is manageable. It's also the process where most things go wrong, and where having experienced representation on the ground in China changes the outcome.

Specific ways a manufacturing-experienced sourcing agent changes the equation:

  • Pre-campaign manufacturing review: identifies whether your target cost and timeline are achievable before you promise them publicly
  • DFM review: catches issues before tooling is cut, not after
  • Factory audit: verifies capability and quality history directly, not from a sales presentation
  • Production management: someone watching the line who can read a production spec, not just translate "it looks fine"
  • Inspection management: coordinates PP, DUPRO, and PSI with a qualified inspector, reviews reports before you see them

For the EU startup Bluetooth speaker case, this end-to-end support covered five months from factory selection to delivery of 5,000 units with a 0.4% defect rate. For the US smartwatch startup, it meant navigating concurrent FCC and CE certification while the factory ran the pilot run — shaving six weeks off the timeline by running processes in parallel rather than sequentially.

Both of those outcomes are available in the consumer electronics category at volumes in the 2,000–10,000 unit range. They're not exceptional — they're what competent manufacturing management produces.

What to do next

If you're at the crowdfunding stage and want to understand what production will actually cost and take, get in touch. We scope this out before you commit to a factory — a preliminary manufacturing review and supplier landscape report typically takes 5–7 business days and gives you numbers you can put into a real production budget.

If you're past the campaign stage and already working with a factory, the questions to ask before you cut tooling: Has the design been through a DFM review? Is there a signed NDA? Have you audited the factory, or taken their word on capability? The answers to those three questions predict most of what happens next.

For more on the factory evaluation side of this process, the factory audit checklist covers the 47 specific points worth verifying before you commit to a supplier.