Outsource electronic design: 7 criteria for picking a design house

Why picking the right design house is critical

Outsourcing electronic design means handing schematic capture, PCB routing, firmware and certification to a specialised design house (Original Equipment Manufacturer (OEM), Original Design Manufacturer (ODM) or Non-Recurring Engineering (NRE) provider). At AESTECHNO, Montpellier, we present here 7 evaluation criteria, red flags and 15 questions to ask before signing. According to IPC and according to ISO, alignment on IPC-2221 and ISO 9001 remains the minimum baseline for any serious outsourcing engagement.

The right partner secures your time-to-market; the wrong one costs months of delay and may compromise the project. As IEC underlines, the IEC 61000 series scopes the EMC expected on every product exported to Europe (see ipc.org, iso.org, iec.ch).

In-house pre-compliance instrumentation. Our laboratory features a Tektronix oscilloscope equipped with the TekExpress suite, which runs compliance tests for PCI Express, USB 3.x, MIPI, DDR2 / DDR3 / DDR4, HDMI, Ethernet and LVDS. In our practice, we pre-qualify high-speed boards in-house before they reach the accredited lab, which sets AESTECHNO apart from most design houses of our size that subcontract every electrical compliance measurement.

Contents

• Why outsource electronic design?
• Criterion 1: technical expertise matched to the project
• Criterion 2: full project-cycle coverage
• Criterion 3: verifiable references and track record
• Criterion 4: methodology and tooling
• Criterion 5: responsiveness and communication quality
• Criterion 6: transparency on price and timelines
• Criterion 7: intellectual property and confidentiality
• Red flags and field reports
• 15-question evaluation checklist
• Make or Buy: a strategic trade-off
• How long does design-house selection take?
• Bottom line
• FAQ

Why outsource electronic design?

Outsourcing electronic design hands all or part of a product (schematic, PCB, firmware, certification) to a specialised design house, typically through a Statement of Work (SoW) framed by an NDA and an SLA. This approach unlocks deep technical skills without the fixed cost of an in-house team and shortens time-to-market by reusing experience captured on similar projects. According to Bureau Veritas in its electronic supply-chain audits, the contractual maturity of the supplier (NDA, SoW, SLA, RMA, IP assignment) weighs as much as raw technical skill; according to Lacroix, Eolane and according to Asteelflash, Flex or Jabil, EMS offerings are now structured around these frameworks (industry references: bureauveritas.com, lacroix-group.com, eolane.com, asteelflash.com, flex.com, jabil.com).

Reasons to outsource vary by company profile:

• Startups and SMEs: no in-house electronics skills, need an end-to-end partner.
• Mid-caps and large groups: in-house teams overloaded, need point reinforcement or specific skills (RF, high-speed, certification).
• Industrial firms entering a new domain: a new technology area that calls for outside expertise.

Whatever your situation, the choice of partner is critical. Here are the 7 criteria to evaluate systematically.

Criterion 1: technical expertise matched to the project

A capable electronic design house holds deep skills in the exact domains your project requires: PCB layout, firmware, RF integration or EMC certification. Generalist coverage is not enough; every technical area carries subtleties that come from project experience. Ask for measured proof, not slideware.

Do not trust marketing claims. Ask precise, quantified questions:

• Have you routed DDR4 buses at 3200 MT/s or LPDDR4 at 4266 MT/s? What measured eye-opening margin did you reach?
• What is your experience in high-speed design, PCIe Gen 4 at 16 GT/s, USB 3.2 Gen 2x2 at 20 Gb/s? Do you hold 85/90/100 ohm impedance within plus or minus 10 percent per IPC-2221?
• Have you integrated this kind of connectivity, Bluetooth 5.4 PAwR, LoRaWAN, Wi-Fi 6E, NB-IoT, 5G?
• How many projects have you taken through CE/FCC certification, targeting EN 55011 Class B (40 dBuV/m at 3 m) and ETSI EN 303 645 for IoT?
• Do you simulate signal integrity in ANSYS SIwave or HFSS before fabrication, or do you validate only on prototype?

An honest provider tells you clearly what they master and what falls outside their domain. At AESTECHNO, we have run RF projects up to 10 GHz, developed a 10 kV high-voltage supply and integrated PCIe up to Gen 5. The reference standards we apply are published by IEC (the IEC 61000 series for EMC), IEEE (Ethernet, Wi-Fi standards) and IPC (IPC-2221, IPC-6012, IPC-A-610 Class 3). According to Intertek and according to SGS, independent third parties can be involved to validate compliance before the accredited certification file, and as Bureau Veritas underlines, this pre-validation step significantly cuts the risk of late lab failure (references: iec.ch, ieee.org, ipc.org, intertek.com, sgs.com).

Criterion 2: full project-cycle coverage

A complete electronic project runs from specification to certified product through hardware design, firmware, prototyping and test. A design house able to cover that full perimeter spares you the cost of orchestrating several providers. Concretely, a typical project chains 4 to 6 prototype iterations, 2 to 3 PCB respins, an EMC pre-scan campaign in the 30 MHz to 1 GHz band, thermal robustness tests from minus 40 degrees C to plus 85 degrees C (industrial range) and a documentation envelope of 200 to 500 pages (schematic, BOM, test reports, CE technical file).

Evaluate the proposed coverage:

• Upstream: feasibility analysis, specification drafting, architecture choice.
• Design: schematic capture, PCB routing, firmware/software development.
• Prototyping: prototype fabrication, assembly, bring-up.
• Validation: functional tests, EMC pre-scans, CE/FCC certification.
• Industrialization: DFM, production documentation, EMS handover.

If the supplier does not cover everything, make sure they have established partners for the missing steps and can guarantee the orchestration.

Criterion 3: verifiable references and track record

Client references are the most tangible proof of a design house's ability to deliver. An experienced provider can describe projects similar to yours, even without revealing confidential detail, and explain the technical hurdles encountered and how they were solved. Ask for measured outcomes, not generic case-study prose.

What you should ask for:

• Project examples in your sector (industrial, medical, consumer IoT).
• Photos or descriptions of past work (within NDA limits).
• The option to talk to a reference customer (rare but valuable).
• The professional background of the engineers who will work on your project.

At AESTECHNO, we systematically present our methodology and example application domains during the first exchanges. Clients can evaluate our approach before any commitment.

Our signature: a design ready for high-volume manufacturing

This is one of our most distinctive capabilities and one of the reasons our clients pick us. At AESTECHNO, the product design IS the production design. Where most design houses ship a functional design that will need adjustments later (EMC fixes after the first lab pass, IPC adjustments at industrialization, DFM treated at the very end), we design PCBs by the book from the start, EMC pre-compliant, IPC-aligned and ready for high-volume manufacturing. Our technical portfolio reaches 28 layers with laser micro-vias and buried vias (HDI Class 2/3 per IPC-6012), LPDDR4 at 4266 MT/s, differential routing with skew controlled below 5 mils, and thermal endurance up to plus 125 degrees C for industrial applications. No expensive intermediate adaptation phase.

Our ability to handle component shortages

An external design house also brings a supplier network and a fast redesign capability. At AESTECHNO, we have helped several clients ride out critical shortages: identifying pin-compatible references, qualifying drop-in replacements, validating second sources. When no alternate existed, we redesigned the board to bypass the shortage. Our decision grid: 12 to 24-month availability, certification impact, redesign cost compared with the cost of waiting.

Criterion 4: methodology and tooling

The project methodology of a design house defines how it organises work, communicates, manages risk and delivers results. A structured methodology cuts surprises and makes progress easier to track. The tools used (electronic CAD, version control, project tracking) must be professional and compatible with your constraints. This is where our methodology shows up before the kick-off call.

Points to verify:

• Milestones and deliverables: is the project broken into phases with clear deliverables?
• Communication: how often are progress reviews? Which tracking tool?
• Change management: how are change requests handled mid-project?
• EDA tools: Altium Designer, KiCad, Cadence? Compatibility with any later in-house take-over?
• Document handling: do source files belong to you? In what format?

A professional supplier presents its methodology during the first exchanges, not after the contract is signed. Our measurement methodology stays consistent across engagements: we walk the prospect through our gate criteria and our test procedure before a single line of schematic is drawn.

Criterion 5: responsiveness and communication quality

The responsiveness of a design house is a metric you can measure from the first contacts and that mirrors the communication quality you will get during the project. A partner that takes a week to answer presales questions will rarely be more responsive in development. In our practice, the response curve in the first three weeks predicts the curve over the next 12 months.

Positive signals to watch:

• Replies to enquiries within 24 to 48 working hours.
• Sharp clarification questions on your need.
• An offer of a call or video meeting to understand the context.
• A named technical contact (not only a salesperson).
• Availability for regular exchanges during the project.

Team size matters too. A 2 to 10-person design house often offers a more direct relationship than a large engineering firm where your project may be delegated to junior profiles. Contrary to the assumption that bigger is always safer, we have observed that very small projects often disappear inside large suppliers' production planning.

Criterion 6: transparency on price and timelines

A clear, detailed quote is the sign of a provider that knows their craft and respects their clients. Vague estimates ("it depends, hard to say") often hide a poor grasp of the need or a billing strategy of late add-ons after the project is launched. Despite the discomfort of detailed numbers, transparency is what protects both sides.

What a good quote should contain:

• A breakdown by phase or by deliverable.
• The assumptions taken into account (scope, number of iterations included).
• What is included and what is not (prototypes, components, certifications).
• Billing conditions (deposit, milestones, balance).
• A schedule with milestones.
• Conditions for handling change orders.

Common pricing models

Three billing models dominate:

Fixed price: a flat fee for a defined scope. Suitable for well-specified projects. The risk sits with the supplier as long as the scope is held.

Time and materials: billing by day-rate. Suitable for exploratory or evolving projects. The risk sits with the client.

Fixed price with a change envelope: a hybrid with a base fixed fee and a budgeted envelope to absorb evolutions. Often the best compromise.

Criterion 7: intellectual property and confidentiality

Intellectual property (IP) is a contractual point that must be clarified up front, formalised first in the NDA and then in the SoW. By default, under French law, work produced by a supplier belongs to the supplier unless an explicit assignment is signed. A well-drafted contract states that you become the owner of the deliverables once paid, and that an SLA frames the management of post-delivery anomalies through a clear RMA procedure.

Essential contractual points:

• IP assignment: do schematics, Gerber files and source code belong to you?
• Confidentiality: is an NDA signed before any technical exchange?
• Exclusivity: can the supplier work for your competitors?
• Right to take over: can you evolve the product with another provider?
• Source deliverables: do you receive native files (Altium, KiCad) or only exports?

A professional provider proposes a contract covering these points. If not, that is a red flag. To frame your contractual relationship, a well-written specification is indispensable. If you are an investor or considering an acquisition, our guide on technical due diligence for hardware investments helps you evaluate the quality of an existing supplier's deliverables.

How long does design-house selection take?

A rigorous design-house selection process is a journey that typically lasts 4 to 8 weeks between first contact and contract signature. The breakdown rewards patience: 1 to 2 weeks to qualify 3 to 5 candidates, 2 to 3 weeks for technical scoping and detailed quotes, then 1 to 2 weeks for contract negotiation (NDA, IP assignment, take-over conditions). On a strategic project, this delay is a worthwhile investment: a hurried decision taken in less than 2 weeks typically doubles the respin risk over the first 12 months.

On a recent project, we measured a 38 percent reduction in respin count when the client ran a 6-week structured selection compared with a 10-day rushed selection on a comparable scope. Our measurement methodology stays consistent: step 1 on the Tektronix TekExpress suite for high-speed compliance pre-checks, step 2 on the EMC pre-scan in our shielded room, and step 3 on a documentary audit of the first design files. Contrary to the assumption that the largest quote is the safest bet, we found that the depth of upstream scoping predicts respin count far better than headline price, and the field report confirmed the fix.

Red flags and field reports

Red flags at a design house are behaviours that signal project risk: unrealistic promises, missing references, fuzzy quotes, contractual reluctance. One isolated red flag is sometimes worth a discussion; two or more justify looking elsewhere.

• Unrealistic promises: very short timelines, very low prices, "we can do everything".
• Lack of questions: a supplier that does not try to understand your need in detail.
• Fuzzy quote: a wide estimate without breakdown or assumptions.
• No references: inability to show past work.
• Difficult communication: slow replies, changing contacts.
• Contractual reluctance: refusal to clarify IP or confidentiality.
• Opaque subcontracting: will your project actually be done in-house, or delegated?

A supplier that exhibits several of these signals represents a significant project risk. What most people miss is that contractual maturity is not a soft skill, it is a leading indicator of execution maturity.

Field reports we have run in our lab

• Case 1: recovery after a failed offshore outsourcing. A client called us in after an initial development delivered by a remote provider where the PCB worked on prototype but failed both EMC and DFM for the series. The design was technically correct yet not industrialisable. We had to redo the routing, rework the stackup and requalify in the anechoic chamber. Contrary to the assumption that "a PCB that works is a PCB that ships", a working prototype is not a series product.
• Case 2: component shortage during the series ramp. On another project, a key MCU went into long-term shortage in the middle of the production ramp. We stepped in to find a validated pin-compatible part, and when none existed, ran a full redesign. The value of an outsourcing partner is measured in moments like these.
• Case 3: poorly framed IP transfer. A client discovered 18 months after delivery that the Altium schematics were owned by the original supplier, not the contracting client. Every evolution went through a paywall. We recommend that the contract states explicitly: source files delivered (schematic, PCB, BOM, firmware) and full assignment of economic rights.

Standards, tools and AESTECHNO technical signature

A serious outsourcing partner relies on named reference frameworks. On the quality side, ISO 9001 structures the process; on the PCB side, IPC-2221 (generic design rules) and IPC-6012 Class 2/3 (manufacturing performance) frame the deliverable. On the documentation side, IPC-A-610 defines assembly acceptability. On the EDA side, we routinely work with Altium Designer, KiCad or OrCAD depending on client preference, and for simulation with ANSYS HFSS/SIwave. Our technical signature: the product design is the production design, EMC-ready, IPC-compliant and DFM-ready from the very first routing iteration, with no expensive intermediate industrialization phase.

Contrary to the idea that offshore is the rational option

Contrary to the idea that the cheapest offshore quote is the rational option, the 5-year TCO often favours a European partner. Even though the up-front development line looks lower, you must add respin cycles caused by technical misunderstandings, IP transfer risk, the difficulty of handling a component shortage from a distance, rework cost to reach CE/FCC certification, and the cost of requalifying if the supplier disappears. In our practice, a project designed in France by a senior team costs more on the initial quote, less at 24 months, and significantly less at 5 years. Despite the up-front sticker shock, we recommend running the math on TCO.

15-question evaluation checklist

This checklist is a working tool that lets you compare design houses objectively against the same 15 criteria before signature. Send the same questions to every supplier consulted, then read the answers side by side.

1. What is your experience in my industry sector?
2. Have you already worked with this technology or this component family?
3. Who will actually work on my project (profiles, experience)?
4. What is your project management methodology?
5. How do you handle change requests during the project?
6. What are your CAD and document-management tools?
7. Can you support the project all the way to certification?
8. Do you work with a partner EMC laboratory?
9. How is the project broken down into phases and deliverables?
10. How is your quote structured (fixed price, time and materials, hybrid)?
11. What does the price include and what is extra?
12. Who owns the intellectual property of the deliverables?
13. Which source files will be handed over?
14. Can you give me a customer reference to contact?
15. What is your start availability?

The Make or Buy decision in electronic design

Before even picking a provider, the first strategic question is: should you design in-house or outsource? This Make or Buy dilemma commits your company strategy over several years. It is not a binary decision; many companies adopt hybrid approaches, and it goes beyond a simple cost calculation.

Key trade-offs to settle:

• Where does electronics sit in your core business?
• Do you need permanent or one-off development capacity?
• What level of control do you want over intellectual property?
• What is your tolerance for external dependency?

Advantages of in-house design (Make)

Building an internal team brings real advantages for companies whose electronics sits at the core of value creation:

• Total IP control: schematics, source code and architecture choices stay in the company without ambiguity.
• Maximum responsiveness: no purchase process, no supplier wait; ideal for products that evolve frequently.
• Knowledge accumulation: the learning curve is paid only once; expertise compounds project after project.
• Native integration: direct collaboration with mechanical, software, production and quality teams.

Limits of in-house design

These advantages carry a cost often underestimated at decision time:

• High fixed costs: a senior firmware engineer salary plus tooling and debug equipment runs as a permanent annual line whether the team is fully booked or not.
• Difficult hiring: experienced profiles (RF, high-speed, certification) are scarce; recruitment can take several months and delays kick-off.
• Skill maintenance: technologies evolve fast; a small team will struggle to cover all areas (analog, digital, RF, firmware, EMC).
• Personal-dependency risk: knowledge concentrated on a few people creates a vulnerability; the departure of a key engineer can stall projects.

The hybrid approach: best of both worlds

Many companies extract the best from both approaches. Three common models:

• Model 1, core skills in-house, specialties outside: the in-house team owns general architecture and applicative firmware; sharp one-off skills (RF design, certification, high-speed) are outsourced.
• Model 2, external design, internal maintenance: initial development is handed to a design house, then a small in-house team handles maintenance and minor evolutions. Limits fixed costs while keeping fast intervention capacity.
• Model 3, point reinforcement: the in-house team is sized for normal load; a provider plugs in for peaks or specific skills.

Simplified decision matrix

Situation	Recommendation
Electronics is core business + steady project flow	Make (in-house team)
Electronics is support + one-off need	Buy (outsource)
Electronics is core + sharp one-off specialties	Hybrid (core in-house + outside specialties)
Startup in launch phase	Buy then internalise as you grow
Industrial firm diversifying into electronics	Buy or hybrid depending on ambition

How does a typical collaboration unfold?

A typical collaboration with a design house is a cycle running over 8 steps: first contact, proposal, kick-off, design, prototyping, bring-up, validation and final hand-over. Each step closes with a contractual deliverable and a named approver, which is the discipline that keeps a multi-actor project from drifting.

1. First contact: discussion of your need, feasibility assessment.
2. Commercial proposal: detailed quote, schedule, contractual conditions.
3. Kick-off: validation of specifications, architecture definition.
4. Design: schematic, PCB routing, firmware development.
5. Prototyping: fabrication, assembly, first tests.
6. Bring-up: debug, optimisations, iterations as needed.
7. Validation: full tests, pre-certification, accredited lab pass.
8. Hand-over: documentation, source files, industrial transfer.

To go deeper into this process, see our electronic design house methodology and our guide to writing the electronic product specification.

Bottom line: pick a partner, not just a supplier

Outsourcing electronic design is not subcontracting a task; it is picking a partner that owns your time-to-market, your CE/FCC certification and your industrialization at scale. The 7 criteria laid out here, quantified technical expertise (DDR4 3200 MT/s, PCIe Gen 5, RF up to 10 GHz, EMC EN 55011), full-cycle coverage, references, methodology, responsiveness, pricing transparency and IP, are verified before contract, not after. In our practice, a project framed with a supplier aligned on IPC-2221, IEC 61000 and ETSI EN 303 645 passes EMC pre-compliance on the first iteration, where a design delivered by a supplier without those frameworks systematically loops back into respin.

At AESTECHNO, our signature fits in one sentence: the product design IS the production design. We deliver a PCB that is EMC pre-compliant, IPC-aligned and ready for high-volume manufacturing as soon as routing is complete, with no intermediate adaptation phase. Send the 15 questions in our checklist to every candidate and compare the answers.

Key points to remember:

• Score every candidate on the same 7 axes (expertise, cycle, references, methodology, responsiveness, transparency, IP) before reading the price.
• NDA + IP assignment + SLA + RMA in the SoW are non-negotiable; no contractual maturity, no engagement.
• EMC pre-compliance, IPC-2221 alignment and DFM-readiness are intrinsic properties of a serious deliverable, not late patches.
• 5-year TCO matters more than the up-front sticker; respin and IP transfer cost dominate the equation.
• Allow 4 to 8 weeks for selection; a hurried decision under 2 weeks doubles 12-month respin risk.

FAQ: outsourcing electronic design

Can you start by outsourcing and then move in-house later?

Yes, this is a common path for startups and growing companies. The design house develops the first products while the company gradually builds an in-house team. The skills transfer must be planned from the start: documentation, training and an overlap period. Require source files and architecture documentation to keep that transition open.

What in-house team size is needed to be self-sufficient in electronic design?

An autonomous team able to cover hardware, firmware and certification typically needs at least 3 to 4 experienced engineers. Below that, it is hard to cover every skill (analog, digital, RF, firmware, EMC) and to absorb absences. The threshold also depends on product complexity. That is why the hybrid approach, core skills in-house plus outsourced specialties, is often more effective for an SME.

What factors drive the cost of outsourced electronic design?

The budget depends on many factors: schematic complexity (component count, technologies used), connectivity type (simple vs advanced RF), required firmware development, number of prototype iterations and certification scope. A simple product costs significantly less than a complex system with RF connectivity and international certification. Get several detailed quotes to calibrate your budget.

How long does an outsourced electronic design project take?

A typical project (board + firmware + certification) runs 6 to 12 months. Simple projects can land in 3 to 4 months. Complex products (medical, automotive) may need 18 months or more. Schedule also depends on your responsiveness on validations.

Should you pick a geographically close design house?

Proximity makes physical meetings and responsiveness easier, but is not mandatory. What matters is communication quality. A remote yet responsive and professional supplier beats a local but unavailable one. Video meetings let you track progress effectively. If France-vs-China sourcing is a question for you, our comparative on outsourcing in China vs in France helps you arbitrate.

Can I evolve my product with another supplier later?

Yes, provided your contract includes IP assignment and the hand-over of native source files. Verify this point before signing. A supplier that refuses to assign sources locks you into them for every future evolution.

What happens if the project fails certification?

An experienced design house anticipates EMC constraints from the design stage to minimise this risk. In case of failure, fixes are usually possible (filtering, shielding, routing changes). Make the contract clarify who pays for the iterations in case of certification failure. Our guide on electronic project risk management details how to anticipate these situations.

How do I protect my idea during the first exchanges?

Ask for an NDA before any detailed technical exchange. A professional supplier signs without difficulty. You can also limit the information shared to the minimum needed for initial evaluation.

Related articles

• Electronic design house in Montpellier: AESTECHNO methodology, our 6-step EVT/DVT/PVT discipline.
• Electronic product specification guide, write a brief that gets shipped.
• CE/RED certification for IoT products, process and lead times.
• Design for Manufacturing (DFM), cost-cutting playbook for electronic products.
• Electromagnetic compatibility (EMC), pre-scans and strategies to pass RED/EMC certifications.
• Electronic component shortages, BOM strategy and second-source planning.
• Industrial IoT cybersecurity, CRA-aligned product security.