A common early mistake is sending the same short message to many factories: “I have an AI product idea. Can you make it, and what is the price?” The responses are difficult to compare because each supplier imagines a different product, customization scope, sample route, and production volume.
The better starting point is not a longer supplier list. It is a clearer brief.
1. Bring one concrete product reference
A reference gives the supplier a physical frame for the conversation. It can be an existing product page, marketplace listing, photo, sketch, short video, enclosure concept, development board, or competitor product.
The reference does not mean “copy this product.” Add a short note explaining what you want to keep and what must change.
- Keep: product form, approximate size, wearing method, interaction pattern, or charging method.
- Change: AI function, camera or microphone setup, enclosure details, firmware, branding, language, connectivity, or packaging.
- Unknown: areas where you want the supplier or solution provider to propose options.
2. Write the intended outcome in one sentence
Describe what the user should be able to do with the product, not only the technology inside it.
The outcome helps determine whether the project needs an existing product, a solution platform, a custom board, a new enclosure, or several partners.
3. State the current stage honestly
A supplier needs to know whether you have an idea, software demo, reference product, functional prototype, existing sample, prior quotation, or production-ready package. These stages lead to different conversations.
| Current stage | Useful first conversation | Likely next evidence |
|---|---|---|
| Idea or use case | Product form and supplier-type clarification | Reference product and first-sample goal |
| Software or AI demo | Device form, compute, sensors, connectivity, and API boundary | Hardware architecture options |
| Reference product selected | Standard product versus customization route | Customization list and sample availability |
| Hardware prototype | Design-for-manufacture gaps and supplier capability | Controlled technical package and test plan |
| Existing quote or sample | Scope comparison, risk review, and next revision | Aligned quote assumptions and acceptance criteria |
4. Define what the first sample must prove
“A finished product” is not a useful first-sample goal. Choose one or two priority questions.
- Can the AI interaction run with acceptable latency on the intended hardware route?
- Can the selected microphones, cameras, sensors, battery, and connectivity work together?
- Can an existing product support the required firmware, app, API, language, or branding changes?
- Does the enclosure direction fit the intended user, environment, and assembly constraints?
- Is the project ready for a quotation, or does it need another technical clarification first?
A clear sample goal also prevents early spending on cosmetic details that do not answer the main product risk.
5. Separate must-have requirements from flexible choices
If every detail is described as mandatory, the supplier cannot propose a practical standard platform. If everything is flexible, the quote will not represent a comparable product.
| Requirement group | Examples to state | Mark as |
|---|---|---|
| Core function | Voice interaction, image capture, local inference, cloud connection, sensing, alerts | Must-have |
| Physical constraints | Wearable form, maximum size, weight direction, mounting, water or dust exposure | Must-have or target |
| Technical preferences | Processor family, operating system, radio, battery capacity, connector | Preferred or open |
| Commercial presentation | Logo, color, packaging, accessories, manual language | Now or later |
6. Explain the AI, software, and firmware boundary
“AI hardware” may mean very different responsibilities. Tell the supplier where the model runs and who is expected to own each layer.
- Does inference run on-device, on a phone, on a gateway, or in the cloud?
- Who provides the AI model, mobile app, backend, device firmware, and update mechanism?
- Which APIs or protocols must the device expose?
- Does the first sample need production firmware, or only a controlled demonstration path?
- Which credentials, datasets, model weights, or customer information must never be shared with the supplier?
This boundary is often more important than the phrase “AI-enabled.” It determines compute requirements, module choices, test responsibilities, and which type of partner is suitable.
7. Give commercial assumptions — even if they are provisional
A quote without quantity, customization scope, destination, or packaging assumptions is not a stable comparison. If you do not know the final numbers, label them as planning assumptions.
- Number of evaluation samples needed.
- Possible first-batch range — or “unknown until sample validation.”
- Target market and delivery country.
- Target timing and which date is actually fixed.
- Branding, packaging, accessories, and documentation expectations.
- Any target cost range, clearly separated from an approved budget.
8. Identify target-market and compliance questions early
The supplier does not own your entire market-access decision. Product category, radio functions, battery configuration, intended use, and destination market can change design, testing, documentation, labels, and logistics.
- For the EU, identify which product rules may apply before treating a CE mark as a supplier-provided shortcut. The European Commission states that manufacturers are responsible for conformity assessment, technical documentation, the EU declaration of conformity, and affixing the CE marking where applicable.
- For products with radio-frequency functions entering the United States, review the relevant FCC equipment-authorization route and current guidance for the actual device configuration.
- For lithium cells or batteries, confirm the battery model, configuration, supplier documentation, and transport-test evidence relevant to UN Manual of Tests and Criteria subsection 38.3.
This is not a compliance determination. It is a reason to identify the target market before the hardware and supplier route become expensive to change.
9. Decide what you will not send in the first message
Share enough to test supplier fit, not every confidential asset at once. WIPO notes that trade-secret protection generally depends in part on taking reasonable steps to keep information secret, including confidentiality agreements with business partners.
Before sending detailed files, separate the information into three levels:
| Sharing level | Examples | Purpose |
|---|---|---|
| Initial fit check | Reference product, intended outcome, stage, sample goal, high-level requirements | Confirm supplier category and capability |
| Controlled technical review | Redacted diagrams, interface requirements, selected CAD views, partial BOM, test needs | Clarify feasibility and quote inputs |
| Restricted execution files | Full CAD, complete BOM, firmware source, model weights, keys, proprietary datasets | Share only when necessary, with access and ownership boundaries defined |
A one-page first supplier brief
The first brief can stay short. It should answer these questions:
- Product: What is it, and what should the user be able to do?
- Reference: Which product, sketch, demo, or prototype shows the intended direction?
- Stage: What evidence already exists?
- Sample goal: What must the first sample prove?
- Scope: What is fixed, preferred, flexible, or still unknown?
- Software boundary: Who owns model, app, cloud, firmware, and integration work?
- Commercial context: Sample quantity, possible batch range, target market, and timing.
- Next question: Which supplier type and sample path appear realistic?
A useful supplier conversation starts with a defined sample question — not a request for the cheapest finished product.
Questions to ask the supplier
- Are you the manufacturer, solution provider, trading company, module supplier, or project integrator for this scope?
- Which parts are standard, and which parts would require new engineering or tooling?
- What information is still required before a meaningful sample or production quote?
- What will the first sample demonstrate, and what will remain unfinished?
- Who owns and maintains firmware, tooling, test fixtures, and production files?
- Which compliance documents or test reports relate to the exact proposed configuration?
- What assumptions could change the quoted price, MOQ, sample timing, or production route?
Common mistakes before supplier outreach
- Asking for a firm price from an undefined product. The result is usually a rough number built on hidden assumptions.
- Contacting only “factories.” Early AI hardware may need a solution provider, module partner, design resource, existing-product vendor, or multi-party route.
- Requesting full customization before validating the core interaction. This adds enclosure, tooling, firmware, and MOQ complexity too early.
- Comparing quotes without normalizing scope. Two prices are not comparable if they include different modules, tooling, testing, packaging, or software work.
- Sending sensitive files before confirming fit. Use staged disclosure and define confidentiality, access, and ownership boundaries.
Frequently asked questions
Can I contact a Shenzhen supplier with only an AI product idea?
Yes, but treat it as a path-clarification conversation rather than a firm quotation request. Bring a reference, intended use, current stage, and first-sample goal.
Do I need a complete BOM before the first conversation?
No. A complete BOM is not required for an initial review. You should still provide the function, must-have requirements, sample goal, target market, and any known module or enclosure constraints.
Should I send source code or model files immediately?
Usually no. First confirm supplier fit using high-level interfaces and responsibilities. Share restricted execution files only when necessary and after confidentiality, access, and ownership boundaries are clear.
What should the first sample prove?
Choose one or two priority risks: the AI interaction, module combination, power and connectivity route, enclosure direction, or feasibility of modifying an existing product.
Official references for planning
- European Commission: manufacturer responsibilities for CE marking
- FCC Office of Engineering and Technology: equipment authorization guidance database
- UNECE: UN Manual of Tests and Criteria, Revision 8 and Amendment 1
- WIPO: trade secrets and reasonable confidentiality measures
Send one product reference for a sourcing path review.
Aixumo will help clarify the likely supplier type, possible sample route, information needed before quote, key sourcing risks, and the most useful next step.