Start Here: Tell Us About the Product and Why Now

• Briefly describe the product or assembly you want us to build and the immediate reason you’re exploring an external integrator today.
• Which of these triggers best captures why you’re evaluating outsourcing this assembly right now? Options: Volume ramp exceeds internal capacity, Shutting down in-house line to cut overhead, New variant or process we lack in-house (potting, coating, complex routing), Intermittent quality problems, Strategic refocus of core capabilities, Other
• What is your target timeline for validating a partner and beginning pilot production? Options: Immediately (0–4 weeks), Within 1–3 months, 3–6 months, 6+ months, Flexible/Undecided
• How many units per month do you expect after the pilot if we become your production partner? Options: <100, 100–499, 500–1,999, 2,000–10,000, 10,000+
• Who on your team will drive this initiative day-to-day (title/role)?

Is This Keeping You Up at Night?

• When you imagine handing us final assembly, what single fear makes you hesitate the most? Options: Workmanship defects on complex assemblies, Configuration/variant errors, Loss of schedule or missed deliveries, Supplier inbound failures, Warranty/field failures
• Tell us about a recent defect or mistake that caused real customer impact—what happened, and how did it land on your team?
• How often do configuration or variant mistakes occur today (e.g., wrong firmware/image, wrong harness variant)? Options: Never, Rarely (1–2/year), Occasionally (quarterly), Often (monthly), Regularly (weekly+)
• When those issues occur, who absorbs the cost or consequences (ops, warranty, customer credits, recalls)? Options: Operations, Warranty/after-sales, Sales, Shared across departments, We track but don't allocate consistently
• What’s the emotional impact on your team when a pilot or production run introduces unexpected configuration errors?

Who Really Decides — And How Risk Is Allocated

• If production goes south with a contract manufacturer, who on your side is ultimately held accountable? Options: VP of Manufacturing, Director of Supply Chain, Quality Director, Product Manager, CEO/COO, Other
• Which stakeholders must sign off on the pilot acceptance results before we move to production? Options: Manufacturing/Operations, Quality/Regulatory, Engineering, Supply Chain/Logistics, Sales/Customer Success, Procurement
• Describe a past decision where procurement chose a partner but operations resisted—what broke the impasse?
• Who will be our daily point of contact for decisions during the pilot (role and availability)?
• What governance cadence do you prefer for pilot reviews (weekly, twice-weekly, ad hoc, milestone only)? Options: Weekly, Twice-weekly, Milestone only, Ad hoc as issues arise

If We Could Deliver Perfection — What Would That Look Like?

• Imagine you never had to worry about workmanship or wrong variants again—what would change for your team, customers, and metrics?
• Which measurable outcomes would convince you this partner is successful (select top 3)? Options: First-pass yield, Configuration accuracy, On-time delivery, Functional test pass rate, Warranty rate/field failures, Time-to-recover from defects
• What maximum defect or configuration error rate is acceptable for the pilot to be considered successful? Options: 0%, <0.5%, 0.5–1.0%, 1–2%, >2%
• Beyond metrics, what would make you emotionally confident in a partner (examples: transparency, rapid root-cause, hands-on governance)? Options: Full transparency & daily updates, Defined escalation owners, On-site ramp support, Agreed corrective action timelines, Shared QA audits
• What are the absolute non-negotiables for workmanship, labeling, and configuration before a unit ships to your end customer?

Where Could Hidden Complexity Surprise Us?

• What parts of the assembly feel simple on paper but have historically caused the most pain in production?
• How many distinct inbound suppliers and discrete BOM lines do you typically have for this assembly? Options: 1–5 suppliers / <50 BOM lines, 6–15 suppliers / 50–200 BOM lines, 16–40 suppliers / 200–1,000 BOM lines, 40+ suppliers / 1,000+ BOM lines
• How many active product variants need to be managed on the line, and how frequent are variant-driven changes? Options: Single variant, 2–3 variants, 4–8 variants, 9–20+ variants
• Describe any single-point supplier or part that would stop assembly if delayed (part numbers and impact).
• How do you currently manage firmware/images and variant rules (manual spreadsheets, PLM, ERP, custom tool)? Options: Manual spreadsheets, ERP/PLM controlled, Version control system / Git-like, Hybrid (manual + system), Other
• Have you had surprises from sub-suppliers during a ramp (e.g., changed harness routing, different connector crimp, mislabeled packs)? If yes, give an example.

Designing the Pilot: What Would Seal the Deal?

• What pilot quantity do you normally use to validate a contract manufacturer, and why that size? Options: 5–10 units, 10–25 units, 25–100 units, 100+ units, We decide case-by-case
• If we run your pilot, will you provide a reference unit and access to original assembly documentation for comparative audits? Options: Yes — both reference unit and full docs, Reference unit only, Docs only, No, we'll need you to document
• Which acceptance checks must pass on every pilot unit before you sign off (choose all that apply)? Options: Cable routing & harness checks, Torque & mechanical specs, Label placement & part number, Functional test pass, Firmware/configuration verification, Environmental/aging tests
• What sample size and audit method do you expect for pilot validation (100% visual, sample-based inspection, full functional test)? Options: 100% inspection of pilot units, 100% functional test with sample visual audits, Statistical sampling (AQL based), Custom checklist audit vs reference unit
• What gate criteria would immediately block conversion to production (e.g., >X% config errors, failed functional tests, supplier inbound failure)?
• Who signs the pilot acceptance certificate on your side and who signs ours? (names/roles)

If We Move Forward, How Will We Work Together?

• How do you prefer to share technical artifacts and BOM updates during ramp (secure portal, SFTP, PLM access, email)? Options: Secure portal/CM system, SFTP, PLM/ERP access, Email with attachments, Other
• What cadence and format of updates make stakeholders feel informed without being overwhelmed (dashboard, weekly call, daily standup during pilot)? Options: Daily standup during pilot, Twice-weekly email + weekly call, Dashboard + weekly executive summary, Ad hoc as needed
• Who should be included in major escalation emails or calls if a defect or supplier outage occurs? Options: VP Manufacturing, Director Supply Chain, Quality Lead, Engineering, Procurement
• What SLAs or response times do you expect for corrective actions and root-cause updates? Options: 24 hours, 48 hours, 5 business days, Depends on severity
• Are there contractual or regulatory requirements we must know about up-front (e.g., FDA, ISO 13485, export controls)? If yes, list them.

The Real Risks: Financial, Operational, and Reputational

• If a pilot produces field failures, what is the maximum financial exposure you’d expect a supplier to accept before pausing the relationship? Options: Supplier covers costs up to a cap, Shared cost model, OEM retains financial responsibility, Depends on root cause
• How would a quality or configuration failure during pilot affect your go-to-market commitments or customer SLAs? Options: Minor delay, manageable, Delay causing penalties, Major customer impact/recall risk, Unsure
• What corrective-action governance has worked well for you in the past (RCA + CAPA timelines, joint task forces, on-site remediation)? Options: RCA + 30-day CAPA, Joint on-site task force, Supplier-led corrective action with OEM oversight, Other
• What reputation concerns keep you up at night if an integrator ships wrong-configured units to your end customers?
• If we uncover systemic issues during pilot, what level of visibility and control would you expect from us to restore confidence? Options: Daily transparent updates, Shared dashboards with root-cause tracking, On-site OEM involvement until closed, Executive-level summary + monthly reviews

• Current State & Acceptance Alignment
• Hands-On Assembly Mapping (Line Walk with Reference Units)
• Variant & Configuration Control Workshop
• Inbound Logistics & Supplier Readiness Review
• Pilot Execution Plan & Acceptance Validation

• Seller to issue a supplier readiness checklist and request ASNs and lead-time confirmations from each inbound supplier.
• Seller to produce a variant decision matrix with part numbers, pick rules, label templates, and firmware mappings.
• Customer to provide golden firmware/image files and any rules for image-to-SKU assignment.
• Seller to draft kitting SOP and recommended segregation/kitting fixtures for pilot.
• Agree validation scenarios for pilot that will exercise variant controls and detect configuration drift.
• Supplier Roster & Lead Times
• Confirm that inbound supply chain can support pilot schedule with acceptable risk.
• Agree receiving and kitting processes that preserve part traceability and prevent mis-kits.
• Assign owners and SLAs for critical suppliers and inbound control points.
• Introductions & Meeting Objective
• Customer to designate supplier owners and provide any supplier-specific quality docs or approval requirements.
• Seller to draft receiving inspection plans for critical components (sampling/100% checks as required).
• Create an expedite/alternate supplier list with contact and SLA details for pilot-critical parts.
• Pilot Scope, Quantity & Schedule
• A complete pilot runbook (scope, schedule, line setup, training) is finalized and owned.
• Audit checklist and measurement plan that map directly to the customer's acceptance criteria are finalized.
• Go/no-go decision rules and signatories for pilot acceptance and production gating are agreed.
• Owners for pilot execution, QA audits, and post-pilot corrective actions are assigned.
• Seller to publish the pilot runbook including line layout, tooling list, operator training schedule, and detailed build steps.
• Seller to finalize and circulate the audit checklist and a template pilot report format that shows KPI pass/fail against acceptance criteria.
• Customer and Seller to sign the pilot acceptance and go/no-go decision matrix before pilot start.
• Assign owners for defect triage, corrective actions, and continuous improvement backlog post-pilot.
• Customer has stated the current state in one clear sentence.
• Business and operational consequences are quantified and documented.
• A single-sentence future-state outcome and measurable pilot acceptance criteria are agreed.
• List of artifacts required for the Solution Experience is agreed (reference unit(s), BOMs, variant matrix, acceptance protocol).
• Customer to deliver one or more reference units and associated build documentation (assembly drawings, torque specs, labeling instructions).
• Customer to provide variant list, BOMs, expected volumes, and any special-process requirements (potting, coating).
• Seller to prepare a short summary document capturing the one-sentence current state, consequence metrics, and the one-sentence future state.
• Agree date and logistics for the hands-on assembly mapping session.
• Recap Preconditions
• A step-by-step assembly process map tied to the customer's reference unit is created.
• Critical workmanship inspection points and measurement methods are defined and linked to acceptance criteria.
• Customer validates that the proposed processes would eliminate or detect the failures they currently experience.
• List of required tooling, fixtures, and operator training topics is produced.
• Seller to produce annotated operation map and draft work instructions for each critical operation.
• Seller to produce an inspection checklist and proposed measurement methods for each audit point.
• Customer to mark any deviations on the reference unit and confirm which features are absolute must-pass vs cosmetic tolerances.
• Seller to list required tooling/fixtures and propose procurement or build plan for pilot.
• Variant Landscape Recap
• A clear variant decision matrix linking SKU, BOM, kitting, and firmware/image is produced.
• Kitting and sequencing approach is selected and validated by the customer for pilot-scale volumes.
• Serialization, labeling, and firmware control approach aligned with customer's traceability needs.
• Failure modes for variant/config errors are listed with assigned prevention or detection controls.
• Customer Current State Statement (Customer speaks)
• Line Setup, Fixtures & Training Plan
• BOM-to-Assembly Mapping
• Physical Reference Unit Inspection
• Critical Component Controls
• Consequence Quantification
• Receiving, Storage & Kitting Flow
• Kitting, Sequencing & Pick Rules
• Map Operation-by-Operation
• Audit & Test Plan Mapping to Acceptance Criteria
• Labeling, Serialization & Firmware/Image Control
• Expedite & Contingency Plan
• Go/No-Go Gates and Decision Rules
• Define Inspection & Audit Points
• Reference Unit & Acceptance Criteria Review
• Customer Validation of Mappings

• Inbound component kitting and trace labeling
• Variant-specific BOM kitting (build-to-order)
• Mechanical sub-assembly fabrication
• Wire-harness fabrication and crimping
• Cable routing and harness integration
• PCB installation and connector assembly
• Torque-controlled fastener assembly
• Conformal coating application and cure
• Potting and encapsulation
• Firmware programming and image loading
• Functional test execution
• Environmental burn-in and stress cycling
• Serialization and UID/barcode labeling
• Final packaging and palletization
• ESD-controlled cleanroom assembly

Inbound component kitting and trace labeling

• Do you require inbound kitting and trace labeling for this program? Options: Yes, No
• At what traceability level do you need labeling? Options: Supplier lot-level, Pallet/box-level, Unit-level (serial), None
• Which label standards or formats must we support? Options: GS1/128, QR code, Custom human-readable, Other
• Do components arrive in vendor trays/tape/boxes or loose — any special handling?
• Are there temperature, humidity, or shelf-life constraints for inbound parts? Options: Yes, No

Variant-specific BOM kitting (build-to-order)

• Do you have multiple product variants that require distinct BOMs? Options: Yes, No
• How many variants and how often do variant rules change? Options: 1-3, 4-8, 9-20, 20+
• Do you need kitting driven by customer orders (BTO) or forecasted kits? Options: Build-to-order (BTO), Forecasted kitting, Hybrid
• Are variant selection rules deterministic (single choice) or conditional/complex? Options: Simple (single choice), Conditional rules (if/then), Matrix of options
• Do you require automated BOM reconciliation against incoming parts? Options: Yes, No

Mechanical sub-assembly fabrication

• Do you require mechanical sub-assembly work (stamping, bending, welding, machining)? Options: Yes, No
• What is the expected volume for each sub-assembly during pilot and production? Options: Pilot: <100, Prod: <1k/mo, Pilot: 100-500, Prod: 1k-5k/mo, Pilot: 500+, Prod: 5k+/mo
• Are CAD/DFM files and tolerances available for fixtures and tooling? Options: Yes, No
• Do sub-assemblies require secondary operations (plating, heat treatment, finishing)? Options: Yes, No
• Any regulatory or material constraints (RoHS, medical-grade, UL)?

Wire-harness fabrication and crimping

• Do you need in-house harness fabrication and termination? Options: Yes, No
• What is the harness complexity (# of circuits, shielded pairs, lengths)? Options: Simple (<=10 circuits), Moderate (11-30), Complex (31+)
• What termination types are required (crimp, solder, IDC, connector)? Options: Crimp, Solder, IDC, Pre-assembled connector, Other
• Do harnesses require 100% electrical test or continuity verification? Options: Yes, No
• Are harness routing diagrams and QA acceptance criteria available? Options: Yes, No

Cable routing and harness integration

• Does the assembly require precise cable routing and retention (clips, ties, channels)? Options: Yes, No
• Are reference units available to validate cable routing against? Options: Yes, No
• What are the critical routing checks (label placement, bend radius, shielding contact)?
• Do routing instructions include photographs, diagrams, or step-by-step work instructions? Options: Photos, Diagrams, Written steps, All of the above
• Is there an expectation for torque, clip setting, or distance tolerances for routed cables? Options: Yes, No

PCB installation and connector assembly

• Will PCBs be delivered as tested/qualified and require mechanical installation only? Options: Yes, No
• Are there press-fit, staked, or glued components during PCB installation? Options: Press-fit, Staked, Adhesive/Glue, None
• Do connectors require insertion force limits or polarity checks? Options: Yes, No
• Are there specific ESD or handling procedures for the PCB level assembly? Options: Yes, No
• Do you require barcode/UID linking of PCB serials to the final assembly BOM? Options: Yes, No

Torque-controlled fastener assembly

• Do assemblies require torque-specified fasteners with calibrated tools? Options: Yes, No
• How many unique torque values and fastener types are in the product? Options: 1-3, 4-7, 8+
• Are torque sequences or cross-torque patterns required (e.g., for enclosures)? Options: Yes, No
• Do you require torque data logging per unit for traceability? Options: Yes, No
• Are there fastener locking compounds or adhesives that must be applied? Options: Yes, No

Conformal coating application and cure

• Is conformal coating required on PCBs or assemblies? Options: Yes, No
• Which coating type and process is specified (spray, dip, selective)? Options: Spray, Dip, Selective, Other
• Do you have specific cure times, temperatures, or VOC restrictions? Options: Yes, No
• Are coating inspection criteria and acceptable defect levels defined? Options: Yes, No
• Do coatings need certification for environmental or safety standards? Options: Yes, No

Potting and encapsulation

• Is potting or encapsulation required for any assemblies? Options: Yes, No
• What potting materials and pot-life requirements apply?
• Are there constraints for demolding, rework, or inspection access? Options: Yes, No
• Do potted units require leak testing, X-ray inspection, or cure validation? Options: Leak testing, X-ray, Cure validation, None
• What environmental or safety controls are needed for potting operations?

Firmware programming and image loading

• Do you require firmware programming during assembly? Options: Yes, No
• How are images provided and managed (single golden image, per-variant images, or customer portal)? Options: Single golden image, Per-variant images, Delivered per-order, Other
• Do you require secure provisioning, signed images, or rollback protection? Options: Yes, No
• Will programming require access to customer networks or cloud services? Options: Yes, No
• Is per-unit verification required after programming (checksum, boot test)? Options: Yes, No

Functional test execution

• Do you require a defined functional test for the product? Options: Yes, No
• What is the scope of functional tests (power-on, RF, network, sensors)?
• Are reference/test jigs, fixtures, and test software available? Options: Yes, No
• Do you require automated pass/fail logging and integration to MES? Options: Yes, No
• What acceptable failure rates or retest policies should be enforced?

Environmental burn-in and stress cycling

• Is burn-in or stress cycling required before shipment? Options: Yes, No
• What duration and environmental profiles are required (temp, humidity, vibration)?
• Do burn-in units need continuous functional monitoring during stress? Options: Yes, No
• Are there limits on throughput or space for burn-in capacity? Options: Yes, No
• Do you require burn-in data reports per lot or per unit? Options: Per lot, Per unit, Summary only, No reports

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Service Level Agreement (SLA)
• Commercial Terms & Pricing Schedule
• Pilot Acceptance Agreement
• Change Order & Variant Management Agreement
• Governance & Escalation Charter
• Quality & Inspection Plan Attachment
• Configuration Management & Firmware Handover Agreement
• Tooling & Capital Equipment Agreement
• Supplier & Inbound Logistics Responsibility Schedule
• Warranties, Returns & Corrective Action Agreement
• Data Privacy & Intellectual Property Agreement (DPA/IP)
• Termination, Transition & Renewal Terms

• Final Acceptance Review & Sign-off
• Lessons Learned & Continuous Improvement Workshop
• Defect Triage & CAPA Governance Meeting
• Configuration Control & Variant Management Handover
• Ongoing Success Review & Partnership Cadence

• Ensure traceability and labeling methods meet customer requirements and auditability.
• Defect Categorization & Severity Matrix
• Establish a defensible, repeatable defect triage and CAPA governance process.
• Assign immediate CAPA owners for open pilot defects with timelines and verification steps.
• Agree SLAs and escalation rules for ongoing defect management.
• Create CAPA tickets for each prioritized defect with owner, target date, and verification criteria.
• Configure the shared defect channel templates and notification rules in the platform.
• Publish SLA and escalation matrix to all stakeholders and include in the governance folder.
• Master BOM and Variant Rules Review
• Lock the production master BOM and variant rules or document controlled exceptions.
• Assign custodians for configuration items (BOM, firmware, labeling) and define change-control steps.
• Introductions & Meeting Objectives
• Publish the locked master BOM and variant rule document in the shared repository.
• Set up the firmware/image repository access and versioning policy with custodians.
• Schedule the first change control board (CCB) meeting and circulate charter and membership.
• KPI Dashboard Review & Targets
• Establish a repeatable review cadence and KPI reporting that keeps both parties aligned on production health.
• Agree communication and escalation rules to ensure rapid response to quality or supply disruptions.
• Ensure continuous improvement actions are visible in the scorecard and tracked to closure.
• Publish KPI dashboard access and set up automated weekly reporting to stakeholders.
• Schedule recurring governance meetings (monthly ops review, quarterly executive review) with invites.
• Distribute emergency escalation contact list and confirm primary/secondary responders.
• Obtain formal customer acceptance or documented conditional acceptance for the pilot build.
• Agree dispositions and owners for any open defects that affect final acceptance.
• Document sign-off artifacts and next steps required to move toward production gating.
• Publish formal acceptance sign-off document with signatures and place in shared channel.
• Create disposition tickets for each open issue with owners, required actions, and verification dates.
• If conditional acceptance, define metrics and timeline required to clear conditions.
• Recap Pilot Highlights and Top Findings
• Document a prioritized continuous improvement backlog tied to pilot findings.
• Assign owners, target dates, and success metrics to each improvement item.
• Agree how improvements will be validated (sample plans, re-audit, KPI thresholds).
• Publish the prioritized CI backlog into the shared channel with owners and due dates.
• Schedule short execution sprints for high-priority quick wins and assign resources.
• Update work instructions, inspection plans, and training material for validated changes.
• Review Cadence & Meeting Roles
• Firmware/Image and Software Control
• Review Acceptance Criteria
• Root Cause Analysis (RCA) Breakouts
• Shared Defect Channel Workflow
• Pilot Results vs Reference
• Communication Protocols & Emergency Escalation
• CAPA Assignment & Verification Process
• Change Request & Gating Process
• Improvement Idea Generation
• Open Issues and Dispositions
• Prioritize Improvement Backlog
• Continuous Improvement Tracking
• Labeling, Serialization & Traceability
• Agree SLAs, Escalation Path, and Reporting
• Wrap-up Commitments & Next Review
• Customer Confirmation & Sign-off
• Audit Trail and Evidence Requirements
• Define Success Metrics & Validation Plan
• Assign Configuration Custodians and Sign-off
• Next Steps & Immediate Actions