Start here, a quick product snapshot

• Tell us the core product concept you want on shelves and the primary retail channel or placement you are targeting
• Describe the user experience or brand cues that must feel unique compared to typical reference designs
• How many SKUs, colors, or hardware variants do you expect at launch Options: Single SKU, 2-3 variants, More than 3, Undecided
• When is your internal target for first on-shelf availability, for example within 9 months, 12 months, or later Options: Within 6 months, Within 9 months, Within 12 months, 12+ months, Undecided
• Tell which stakeholder will own post-launch success metrics, for example VP Product, Head of Hardware, or Head of Operations Options: VP Product, Head of Hardware, Head of Operations, Head of Supply Chain, Other
• Name the top three nonfunctional must-haves, for example battery life, thermal performance, or MTBF

Where the product must stand out on shelves

• Walk me through the one design or feature outcome that, if we failed to achieve it, would make the product feel indistinguishable from other ODM offerings
• Describe any reference designs you view as acceptable inspiration and what parts of those you would explicitly not accept copying
• Who in your buying group weighs industrial design most heavily during retailer or distributor evaluations Options: VP Product, Head of Design, Merchandising Lead, Retail Buyer, Other
• List the metrics you will use to quantify differentiation during the pilot, for example retailer feedback, user testing score, or price premium Options: Retailer feedback, User testing score, Price premium vs reference, Brand perception study, Other
• Identify the business cost if the product is perceived as generic, for example lost shelf space, larger promotions, or delayed reorder cycles
• If we proposed starting from an existing reference platform with only industrial changes, would that be acceptable, acceptable only with exclusivity, or a deal breaker Options: Acceptable, Acceptable with exclusivity, Deal breaker, Undecided

The timeline your leadership expects and the milestone that makes or breaks it

• Identify the nonnegotiable milestone that must be met to hit your nine-month shelf target Options: Tooling complete, Certification approved, Pilot production completed, Sample approval, Other
• When does leadership expect the first production samples to be available for retailer reviews Options: Within 8 weeks, 8-12 weeks, 12-16 weeks, Not set
• Estimate the revenue or funding consequences if the launch slips by three months, for example lost shelf windows or additional marketing spend
• Which timeline risk matters most to you, tooling, certification delays, component lead time, or firmware integration Options: Tooling, Certification, Component lead time, Firmware integration, Other
• If a single critical lead part has a 20-week lead time, could you accept a phased launch, pause the program, or switch parts with a redesign Options: Accept phased launch, Pause until parts available, Switch parts with redesign, Undecided

Firmware and integration, the things that usually stall projects

• Why would receiving only a reference BSP be unacceptable for getting your application stable at launch
• Map your current application architecture and which layers will require direct BSP or driver control for a stable launch
• Who within your team will be the program owner for firmware integration and how many full time engineers are allocated to this launch Options: None, 1-2 engineers, 3-5 engineers, 5+ engineers, Undecided
• Do you require the seller to assign a dedicated firmware integration team that owns the BSP and drivers through production acceptance Options: Yes, No, Maybe with conditions
• Measure the tolerance for firmware instability at pilot, for example acceptable crash rate, boot failures, or thermal events Options: Zero tolerance, <1% field failures, 1-5% acceptable, Higher acceptable for early runs
• Can you provide access to your application test harness or APIs under NDA within two weeks to unblock integration Options: Yes, No, Requires internal approval

Money, IP, and exclusivity — what must be settled before engineering starts

• Could unclear IP ownership or delayed exclusivity terms stop you from releasing NRE funds Options: Yes, No, Depends on terms
• Outline the IP ownership split you expect across mechanical, firmware, and board-level designs
• Tell us who negotiates IP and exclusivity clauses on your side, legal, product, procurement, or founders Options: Legal, Product, Procurement, CEO/Founders, Other
• Are you prepared to commit to a nonrecurring engineering payment upfront in exchange for a defined exclusivity term Options: Yes, Yes with limits, No, Need internal approval
• Name the maximum per-unit cost delta you can accept for an exclusive design versus a nonexclusive reference derivative Options: <$1, $1-3, $3-5, >$5, Not sure

Top obstacles that historically kill timelines and budgets

• List the three risks you fear most on a hardware launch that would force you to pause the program
• Share the last time a hardware project missed its launch and the primary reason it happened
• In your experience, which vendor dependency causes the most delays, single-source components, test fixture availability, or compliance lab queues Options: Single-source components, Test fixtures, Compliance lab queues, Other
• Where in the supplier chain do you want visibility, for example component vendors, contract manufacturer, or subcontract assembly Options: Component vendors, Contract manufacturer, Subcontract assembly, All of the above
• Can you absorb the cost and schedule impact if a regulatory certification requires hardware rework late in development Options: Yes, contingency exists, No contingency, Unsure

The other options you are actively weighing

• Are you actively considering building this capability in-house rather than using an external manufacturer, and why Options: Yes, building in-house, Considering hybrid, No, prefer external
• Which external paths have you evaluated, reference-platform OEMs, full ODM partners, or local contract manufacturing Options: Reference-platform OEM, Full-ODM partner, Local contract manufacturer, Multiple of those
• Under what conditions would you stay with your incumbent supplier instead of switching, such as price, exclusivity, or speed
• Do any internal stakeholders propose solving this without a partner by hiring a hardware team, and if so who Options: Yes, leadership, Yes, product, No, Undecided
• Would you prefer time to shelf over total program cost if the in-house route met your timeline but cost more Options: Time to shelf, Total cost, Both equally, Undecided

Operational readiness and gating constraints we must verify

• Detail any regulatory approvals, export restrictions, or facility audits that would block production start within your target window
• How many integration points does your product require, for example cloud APIs, carrier provisioning, or third-party modules Options: None, 1-2, 3-5, More than 5
• Have you already prepared design files, component specs, or test plans that must be transferred to the seller under agreement Options: Yes, all, Yes, partial, No, Will create together
• Please name who will own component sourcing approvals and single-source exceptions during the program Options: Buyer procurement, Seller procurement, Joint committee, Undecided
• Within what timeframe would you be able to provide access to your labs or schedule a facility tour for supplier evaluation Options: Within 2 weeks, 2-4 weeks, 1-2 months, Later
• Will your team accommodate on-site integration for firmware review if IP constraints require in-person access Options: Yes, Requires agreement, No

Decision owners, budget, and the acceptance criteria that unlock funding

• Please name who has final sign-off authority for releasing NRE, approving IP splits, and greenlighting production acceptance Options: CEO/Founder, VP Product, Head of Engineering, Procurement
• Rate the urgency of this project on your roadmap compared with other initiatives, 1 low to 5 critical Options: 1, 2, 3, 4, 5
• Estimate the NRE budget range you are prepared to commit to upfront Options: <$50k, $50k-150k, $150k-500k, >$500k, Undecided
• Typically, do procurement or legal gating processes add more than four weeks to contract finalization Options: Yes, typically, Sometimes, No
• Would procurement approve production pricing and tooling payment within two weeks if the pilot meets agreed acceptance criteria Options: Yes, No, Depends on terms
• Outline the single acceptance metric that, if achieved in pilot, would trigger immediate approval to move to mass production

Concrete next steps that accelerate a decision

• Walk me through the smallest, fastest next step that would move you from evaluation to a signed NRE in 30 days
• Could you commit to a two-day integration workshop and facility visit within the next 4 weeks Options: Yes, Maybe, No
• Share the documents we should review first, for example your requirements document, existing BOM, or compliance history Options: Requirements document, Existing BOM, Compliance history, Test plans, Other
• Will you assign a named program owner who can make tradeoff decisions during engineering Options: Yes, No, TBD
• Is there a preferred cadence and channel for weekly program updates, for example email, video call, or platform updates Options: Weekly video call, Weekly written update, On-platform updates, Biweekly
• Finally, if the pilot proves the key metric, what single action would make you sign the engineering agreement within that week

• Design & Integration Workshop

• Orientation: concept-to-production overview
• You confirm the restated current state and accept the stated cost of staying on a reference platform as accurate.
• Provide a choice-weighted NRE proposal for the two selected design options, including costs, timeline, and proposed IP/exclusivity terms.
• You select one preferred industrial design direction and accept its impact on tooling time and differentiation tradeoffs.
• Confirm the current state and its cost to your team
• Deliver a firmware integration plan that lists milestone ownership, BSP delivery criteria, and expected validation gates.
• Industrial design options mapped to your brand goals
• Share your prioritized list of product differentiation features, target unit price, and any absolute constraints on materials or components.
• You confirm the firmware integration approach and accept that owning the BSP reduces the typical debugging delays identified in Discovery.
• Identify the internal decision-makers and confirm their availability for the final review session to approve NRE and exclusivity terms.
• Reference-platform tradeoffs and variant mapping
• You agree the recommended next-step deliverable to advance toward a commercial proposal with timelines and IP terms.
• Firmware integration approach and BSP ownership proof
• Integration sequencing to meet the nine-month shelf date
• Confirm this matches your stated needs
• Decision and next steps

• Design & Integration Workshop (Solution Experience)
• Design & Integration Workshop Deck
• Design & Integration Solution Brief

• meeting
• slides
• document

• Industrial design and enclosure concept delivery
• Electrical schematic and component selection
• PCB layout and signal integrity implementation
• Firmware BSP and driver integration
• Prototype assembly (alpha and beta units)
• Tooling design and injection mold production
• Regulatory certification testing and submission
• Bill of Materials sourcing and cost optimization
• Design for Manufacturability (DFM) updates
• Pilot production run and process validation
• Volume manufacturing and assembly line setup
• Test jig and automatic optical inspection programming
• Source code and design IP handover package
• Packaging design and supply chain fulfillment
• Warranty and post-production support setup

Industrial design and enclosure concept delivery

• Which product form factors do you want explored (handheld, wall-mount, desktop, DIN-rail)? Options: Handheld, Wall-mount, Desktop, DIN-rail, Other
• Which enclosure materials and finish options should be prioritized (ABS injection, PC blend, aluminum CNC, powder coat)? Options: ABS injection, PC blend, Aluminum CNC, Powder coat, Other
• Who to consult internally for brand/ergonomic constraints for the housing (e.g., head of product, industrial designer)?
• When do you need the first industrial design sketches and rapid 3D print-fit models delivered? Options: 2 weeks, 4 weeks, 6 weeks, Flexible
• Describe the environmental and human-interface requirements for the enclosure (IP rating target, button travel, display cutout tolerances).

Electrical schematic and component selection

• Which functional blocks must be present on the schematic (power management, radio module, sensor I/O, external comms)? Options: Power management, Radio module (cell/Wi-Fi/Bluetooth), Sensor I/O, External comms (Ethernet/USB), Other
• What target power budget and battery runtime (hours) must the power stage satisfy for your use case? Options: <8 hours, 8-24 hours, >24 hours, Mains powered only
• Which component availability constraint is critical (long-life parts, single-source restriction, lead-time under X weeks)? Options: Long-life (5+ years), Single-source restriction, Lead-time under 12 weeks, No special constraint
• List any required regulatory-related BOM constraints (RoHS/REACH compliance, radio module pre-certified, restricted substances).
• How will you prioritize cost versus performance when we evaluate alternate passives, power ICs, and radio modules? Options: Cost priority, Performance priority, Balanced (target % cost reduction), Undecided

PCB layout and signal integrity implementation

• Which high-speed interfaces on the board require controlled-impedance routing (PCIe, USB3, HDMI, DDR, RF traces)? Options: PCIe, USB3, HDMI, DDR, RF traces, None
• What target board stack-up and layer count do you expect for this product (e.g., 4-layer with split plane, 6-layer with dedicated ground)? Options: 4-layer (split plane), 6-layer (dedicated ground), Custom stack-up (specify)
• Who will provide the high-level timing or SI constraints for SERDES, memory, or RF interfaces if applicable?
• Which manufacturing test methods must the PCB support (in-circuit test ICT, boundary-scan, flying probe)? Options: In-circuit test (ICT), Boundary-scan, Flying probe, Functional test only
• Describe thermal dissipation requirements and any heat-sinking or airflow passages that the PCB layout must accommodate.

Firmware BSP and driver integration

• Which board support package (BSP) surfaces are required to be delivered fully integrated (bootloader, kernel, device trees, board init scripts)? Options: Bootloader, Kernel, Device tree, Board init scripts, All listed
• What OS and major kernel version do you target for your application integration (e.g., Linux kernel series or RTOS name)?
• Which peripheral drivers must be production-ready at handover (Wi-Fi, cellular modem, audio codec, PMIC, sensors)? Options: Wi-Fi, Cellular modem, Audio codec, PMIC, Sensors, Other
• How should we manage secure boot, code signing, and private key custody for delivered firmware artifacts? Options: We manage keys, You provide HSM/keys, Joint plan, Undecided
• Describe performance thresholds the BSP must meet for your app (boot time to user app, network stack throughput, cold start latency in seconds).

Prototype assembly (alpha and beta units)

• How many alpha and beta units do you require for lab validation and field trials? Options: Alpha: 1-5, Beta: 6-20, Alpha: 1-10, Beta: 20-50, Custom quantities (specify)
• Which prototype build fidelity is acceptable for alpha versus beta (hand-assembled boards, assembled PCBA with 3D printed enclosure, pilot injection shell)? Options: Hand-assembled PCBA, PCBA + 3D printed enclosure, Pilot injection shell, Other
• Who will own coordination of field trial logistics for beta units (shipment, test scripts, feedback capture)?
• What functional test scripts or checklist must each prototype pass before it leaves the lab (power-on, RF link, sensor calibration, thermal soak)?
• What acceptance criteria will confirm that alpha and beta units meet mechanical fit, firmware stability, and functional requirements for a production release?

Tooling design and injection mold production

• Which tooling strategy do you prefer for enclosure production (single-cavity, multi-cavity, family mold)? Options: Single-cavity, Multi-cavity, Family mold, Undecided
• What target cavity count and cycle-time expectation should the injection mold meet to hit your per-unit cost at volume? Options: 1-2 cavities, 4 cavities, 8+ cavities, Undecided
• Which mould validation artifacts do you require before approving production tooling (first article inspection FAI samples, shrinkage report, tool maintenance plan)? Options: FAI samples, Shrinkage report, Tool maintenance plan, All listed
• How should we manage tool ownership and exclusivity (we retain tooling, transfer to you, or joint ownership)? Options: We retain tooling, Transfer to you after cost recovery, Joint ownership, Need to negotiate
• Describe surface texture, EMI shielding inserts, and overmold requirements that must be incorporated into the tooling design.

Regulatory certification testing and submission

• Which regulatory regimes must this product be certified for (FCC/IC, CE Radio Equipment Directive, UL safety, RCM)? Options: FCC/IC, CE RED, UL safety, RCM, Other
• Which radio module strategy will you use: pre-certified module or end-device certification path? Options: Pre-certified module, End-device certification, Hybrid / Undecided
• What emissions and immunity thresholds are required for your target markets (specific standard numbers or class)?
• Who will be the named applicant on certification submissions and do you have local regulatory representation where required? Options: You are applicant, We act as applicant, Joint applicant, Undecided
• Which test-lab deliverables do you expect us to provide at submission (test reports, lab photos, firmware build IDs, traceability matrices)? Options: Test reports, Lab photos, Firmware build IDs, Traceability matrix, All listed

Bill of Materials sourcing and cost optimization

• What annual or launch volume estimates should we use to model component pricing and MOQ (minimum order quantity)? Options: <5k units/year, 5k-50k, 50k-250k, 250k+
• Which parts are candidate 'sole-source' or proprietary and cannot be swapped for equivalents?
• How aggressive should cost-down exercises be (target percent reduction from initial BOM cost)? Options: No cost-down, 5-10%, 10-20%, >20%
• Which traceability and lot-control requirements must the supply chain support (date codes, RoHS certificates, country-of-origin)? Options: Date codes required, RoHS/REACH certificates, Country-of-origin info, All listed
• Describe any import/export constraints or ITAR-like controls that affect component sourcing for this product.

Design for Manufacturability (DFM) updates

• Which DFM focus areas should we prioritize during layout and enclosure finalization (panelization, fiducials, assembly torque points)? Options: Panelization, Fiducials, Assembly torque points, All listed
• What AQL (Acceptable Quality Level) standard do you require for assembled boards and final units? Options: AQL 1.0, AQL 1.5, AQL 2.5, Custom
• Who on your team will approve DFM change exceptions that impact fit or user experience?
• Which mechanical tolerances are binding for assembly (e.g., display gasket clearance, connector seating depth in mm)?
• List any factory process constraints we must design for (lead-free solder profile limits, max board dimensions for pick-and-place).

Pilot production run and process validation

• How many units should the pilot run produce to validate processes and supply chain (pilot lot size)? Options: 100-500, 500-2,000, 2,000-5,000, Custom
• Which quality gates must pilot units pass (FAI first article inspection, run rate Cpk, process capability studies)? Options: FAI, Run rate Cpk, Process capability study, All listed
• What in-line inspection and sampling plan is required during pilot (percent of units for AOI, ICT, functional test)? Options: 100% AOI, 10% functional, 50% AOI, 100% functional, Custom sampling plan
• Who will be the escalation contact for pilot nonconformances and what SLA for root-cause response do you expect? Options: 24 hours, 48 hours, 72 hours, Custom
• What acceptance evidence will validate pilot production is ready to proceed to volume (FAI report, AQL pass, Cpk threshold)?

Volume manufacturing and assembly line setup

• Which manufacturing capacity targets must the line meet (units/day, shifts per day) for your launch plan?
• What line balancing and takt time constraints should we design for to meet your ramp schedule?
• Which traceability systems must be implemented on the line (serial number serialization, MES integration, lot linking)? Options: Serial number serialization, MES integration, Lot linking, All listed
• How should we structure first-article inspection, gateway inspections, and final inspection ownership and sign-off for each production batch?
• Describe required factory accreditations or audits you will run (facility tour checklist, ISO 9001 evidence, social compliance).

Test jig and automatic optical inspection programming

• Which ICT/functional test coverage must be implemented on the test jig (power rails, boundary-test, RF loopback, sensor calibration)? Options: Power rails, Boundary-test, RF loopback, Sensor calibration, All listed
• What AOI fault categories are critical to detect in-line (solder bridging, tombstoning, missing components)? Options: Solder bridging, Tombstoning, Missing components, All listed
• Who will maintain ATS/JIG software updates and test vector ownership after handover? Options: We maintain, You maintain, Joint maintenance, Undecided
• Which test throughput target (devices per hour) must the jig/AOI achieve to meet line takt time? Options: <30 devices/hr, 30-100 devices/hr, >100 devices/hr, Custom
• List any special fixtures or handlers required (thermal chamber interface, pogo-pin patterns, vacuum fixtures).

• Master Services Agreement (MSA)
• Statement of Work (SOW) — Engineering & NRE Scope
• Manufacturing & Supply Agreement (MSA/Supply)
• Tooling, Capital Equipment & Amortization Schedule
• IP Assignment and Licensing Agreement
• Design Exclusivity Addendum
• Payment & Milestone Schedule
• Acceptance Test Protocol & Quality Gates
• Continuity of Supply & Transition Commitment
• Source Code & Documentation Escrow Agreement
• Change Order Agreement

• Go-live Health Check (weeks 1-4)
• First Production Measurement (weeks 4-10)
• 90-day Operational Review and Remediation Status (around day 90)
• Quarterly Production and Warranty Review (ongoing)

• Ensure the open defect and firmware backlog is prioritized and has committed timelines for remediation.
• Open root-cause analysis tickets for the top three failure modes with required verification tests and due dates.
• Publish a weekly KPI update (first-pass yield, early field failure rate, on-time delivery rate) to the shared channel until metrics stabilize.
• Prepare evidence package for any remedial test runs needed to validate fixes against Product Scope & Deliverables targets.
• Restate accepted targets and outstanding remediation items
• Confirm which acceptance remediation items are closed and which have committed dates for closure, without re-running the formal acceptance decision.
• Determine if first-pass yield and 30-day warranty return rate are meeting the targets recorded in Product Scope & Deliverables or require extended remediation.
• Agree the final set of stabilization actions and the schedule for posting verification evidence to the shared channel.
• Deliver final verification evidence for each closed remediation item to the shared channel and mark the item closed.
• Publish a mitigation plan and timeline for any supply chain continuity risks identified.
• Schedule targeted retests for components or assemblies that failed initial verification and record pass/fail outcomes.
• Reconfirm acceptance criteria and owners
• KPI trends and targets review
• Confirm warranty return rate and mean time to repair trends are acceptable or that a corrective program with milestones is in place.
• Validate there are no unresolved IP or exclusivity issues that could disrupt production continuity.
• Publish the prioritized improvement backlog with target completion dates and verification criteria to the shared channel.
• Produce a quarterly supplier risk summary with mitigation steps for any single-source or long-lead items.
• Update the warranty returns triage process to reduce mean time to repair and document the new process flow.
• Deployment match to the locked manufacturing configuration documented in Product Scope & Deliverables is verified or gaps are listed.
• Critical production or launch blockers are identified and remediation actions with target dates are recorded.
• A shared issue channel is established and accessible to both parties for ongoing defect and warranty reporting.
• Log all open pilot defects in the shared issue channel with impact and target resolution dates.
• Produce and circulate a short checklist verifying firmware/BSP and BOM match the manufacturing configuration within 48 hours.
• Schedule targeted retest of failed smoke-test items and document pass/fail evidence in the issue channel.
• Present first-production KPI snapshot
• Clear view of whether first-pass yield and early field failure rate are on track versus the targets recorded in Product Scope & Deliverables.
• Root causes for the top metric gaps are identified and prioritized for remediation.
• A timebound corrective action plan is agreed for each high-priority issue that affects acceptance targets.
• Present 90-day outcome data vs targets
• Open issue backlog and enhancement requests
• Deployment and pilot validation
• Root-cause diagnosis for KPI gaps
• Acceptance remediation closure review
• Early QA and inspection findings
• Supply chain and parts continuity update
• Warranty and returns early signal review
• IP, exclusivity, and continuity check
• Early usage and activation signals
• Firmware and field-update incident log
• Supply chain and continuity risks update
• Open blockers and escalation paths
• Agree quarterly improvement actions
• Agree corrective actions and timeline
• Agree final stabilization actions
• Agree immediate remediation actions