Arrive with
A non-confidential use case, one owner for technical decisions and a shortlist of open issues.
PROPOSED ITINERARY
A proposed small-group itinerary for hardware founders, from components and prototype planning to assembly and pilot-run decisions.
A non-confidential use case, one owner for technical decisions and a shortlist of open issues.
Benchmarking, prototype trade-offs, proposed production visits and a pilot plan.
A shortlist of tests and unanswered supplier questions, with evidence and owners recorded.
Read the four-day agenda · See a worked example · Check trip arrangements
Find relevant components and benchmark samples in Huaqiangbei.
Review design-for-manufacturing questions and prepare a prototype quote request.
Request visits matched to your project and discuss test and assembly constraints.
Summarize lead times, open questions and next steps for a small run.
Sample purchases, transport, accommodation and any third-party fees are quoted separately. Dates and access are subject to confirmation.
This proposed itinerary is aimed at founders, product managers and engineering leads deciding how to move from an idea or working sample toward a manufacturable product. It is most useful when you can arrive with an actual decision, a non-sensitive description and the person who owns the technical trade-offs.
You may need to choose between a standard enclosure and a custom tool, work out which manufacturing step sets your lead time, or compare a prototype process with a possible pilot process. If the only question is where to buy parts, start with the one-day market itinerary. If you already have a drawing and one supplier decision to make, the two-day sourcing itinerary can be a closer fit.
Start with a short comparison list. At the market, look for off-the-shelf parts that could reduce custom work and finished products that help you compare size, mounting or user experience. Record sample IDs, exact models and the reasons you accepted or ruled out each one. End the day with a list of one or two decisions that need engineering input.
Review the interfaces between electronics, enclosure and assembly. Identify hard requirements, design details a supplier can change, and items that require a new test. Convert the strongest option into a request for a first article. Ask which tolerances are expensive, what could change without affecting function and how the team will approve revisions.
Request access to a production setting relevant to the design, subject to host confirmation. Ask the supplier to explain the path from incoming materials to inspection using a comparable job. Where no site visit is available, request a scoped technical meeting or reschedule. Record the operation observed, capabilities reported by the host and questions requiring a quote or written evidence.
Translate the visit into a sample test, a pilot quantity and approval gates. Estimate the components of the cost without treating indicative prices as quotes. Decide which items need supplier follow-up and which must be tested by your team. Finish with an owner, due date and planned evidence for each open issue.
| Day | Bring to the session | Leave with |
|---|---|---|
| Market research | A short BOM, current samples or comparable products. | A labeled sample list with price, condition and the next test. |
| Prototype planning | One build decision and non-confidential drawings or dimensions. | A first-article RFQ and acceptance criteria. |
| Factory meetings | Questions tied to a process the host has confirmed. | A record of observations, supplier answers and missing evidence. |
| Pilot plan | Candidate suppliers, a pilot target and open cost items. | A follow-up plan with one owner and deadline for each decision. |
The proposed $2,499 per-person itinerary is subject to dates, group composition and confirmed access. Decide before booking which stage needs group sessions and which sensitive discussions should be arranged separately.
Suppose a working bench prototype uses an off-the-shelf board, separate display and a hand-cut enclosure. The team wants a pilot lot small enough to revise after user tests. The market day compares displays and connectors with enough documentation to narrow the options. The prototype discussion identifies the mounting points and ventilation clearances that need to stay fixed. During a supplier meeting, the team asks how the connector and display are fitted and how the fully assembled product would be checked.
By the final day, the team has several choices. A standard enclosure could be modified for the next pilot, with a custom tool evaluated after demand is clearer. A CNC sample could answer the fit question while a separate assembly quote addresses functional testing. The team writes both paths down and identifies what to test before placing an order.
Build a four-day trip brief using your current design stage and top decisions.
Choose whether the next build needs to prove fit, finish, electronics integration or test coverage. The Shenzhen rapid prototyping guide connects each decision with the process to request and the evidence to take home. If your group is still deciding what part of the ecosystem to explore, start with the self-guided Shenzhen tech route.