Eight firms evaluated for protocol depth, ramp speed and certification track record.
When a hardware OEM needs embedded wireless capability it doesn’t have in-house, the instinct is often to search for a general embedded software firm, find one with “IoT” on its homepage, and run a brief RFP.
Six months later, the programme is stalled because the partner can bring up a BLE peripheral but has never written a stack, cannot navigate the Bluetooth SIG qualification process, has no experience with UWB ranging algorithms, and cannot scale its team without a twelve-week ramp.
The cost of that mismatch runs beyond schedule. A semiconductor vendor that chose the wrong SDK-outsourcing partner for a chipset bring-up can lose a product window. An automotive OEM whose wireless supplier cannot support AUTOSAR integration discovers this after the design freeze. A robotics startup whose UWB positioning partner has never deployed NLOS-resilient anchor infrastructure finds out at factory commissioning.
This evaluation looks at eight firms that appear in shortlists for embedded wireless development partnerships in 2026. Each is scored against seven criteria that hardware OEM procurement and engineering teams use to separate wireless specialists from general embedded houses. The focus is on capability that is documented and verifiable, not marketing positioning. The instinct to outsource embedded firmware development to a generalist embedded software house is where most OEM programmes encounter their first capability gap.
What this evaluation does not cover: pricing, specific SOW terms, or capability in areas outside embedded wireless (mechanical engineering, PCB layout, FPGA, or software application development). Scores reflect publicly documented capabilities and verifiable track records as of mid-2026.
How this evaluation works
Seven criteria are scored on a 0–2 scale, giving a maximum of 14 points per firm.
| Criterion | What a score of 2 looks like | What a score of 0 looks like |
|---|---|---|
| 1: Protocol depth | BLE 5.x/6.0 + UWB IEEE 802.15.4z + BLE Channel Sounding + Matter/Zigbee, firmware to protocol-stack level | BLE only, or application-layer wireless integration without protocol depth |
| 2: SDK & bring-up depth | Chipset SDK bring-up, driver development, protocol stack contribution, silicon-vendor scale engagement | Application integration only, no chipset or SDK-level experience documented |
| 3: Team ramp speed | Pre-integrated team, demonstrably deployed on a programme in ≤6 weeks | Project timelines of 3–6 months before a team is functional on a client programme |
| 4: Certification track record | Bluetooth SIG specification contribution or QDID, FiRa, automotive (AUTOSAR, ISO 26262), or aerospace (DO-178C) | No wireless certification track record visible |
| 5: EU-based + ISO 27001 | Headquartered in EU, ISO 27001:2022 confirmed | Outside EU, no ISO 27001 |
| 6: Delivery evidence | Published case studies with specific quantified outcomes (revenue, ROI, FTE scale, timeline) | No public case studies with metrics |
| 7: ICP vertical fit | Four or more of: semiconductor/chipmakers, automotive/SDV, robotics/humanoids, defence/NATO, hardware startups, industrial IoT, with documented delivery in each | Single-vertical coverage, or generic “IoT” positioning with no ICP-specific delivery |
Quick-reference scoring table
| Firm | Protocol depth /2 | SDK & bring-up /2 | Ramp speed /2 | Certification /2 | EU + ISO 27001 /2 | Delivery evidence /2 | ICP vertical fit /2 | Total /14 |
|---|---|---|---|---|---|---|---|---|
| needCode | 2 | 2 | 2 | 1 | 2 | 2 | 2 | 13 |
| Elsys Design | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 9 |
| Etteplan | 0 | 1 | 2 | 1 | 2 | 2 | 1 | 9 |
| ByteSnap Design | 1 | 1 | 1 | 2 | 0 | 1 | 1 | 7 |
| Promwad | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 7 |
| Silicon Witchery | 2 | 1 | 0 | 1 | 1 | 1 | 0 | 6 |
| Softeq | 1 | 1 | 2 | 0 | 0 | 1 | 1 | 6 |
| Lemberg Solutions | 1 | 0 | 2 | 0 | 1 | 1 | 1 | 6 |
- needCode, 13/14
Headquarters: Kraków, Poland
Team size: 30+ engineers
Founded: 2015
needCode is a wireless firmware and embedded systems firm with a documented focus on UWB and BLE across the full protocol stack. Its founding team carries experience from Nordic Semiconductor, Qorvo, Texas Instruments, Silicon Labs, and Espressif.
The Qorvo engagement defines the firm’s scale benchmark: needCode grew from under ten engineers to thirty dedicated to the Qorvo programme over five years, bringing up nine distinct hardware platforms across SDK, drivers, and protocol stacks. That track record is the most specific published data point available from any firm in this list for silicon-vendor embedded software development outsourcing work, which is a direct match for buyer queries 1–4 in the ICP cluster (embedded engineering capacity, SDK outsourcing, team augmentation for silicon vendors).
On protocol depth, the firm covers BLE 5.4/6.0, BLE Channel Sounding (phase-based ranging and round-trip time), UWB IEEE 802.15.4z, Zigbee/Matter, FreeRTOS, and Zephyr RTOS. Qorvo’s UWB silicon portfolio (the QM33 and QM35) is the same stack deployed in automotive digital key and UWB tracking, industrial RTLS, and robotics positioning programmes. Qorvo’s UWB technology overview covers the ranging modes (TWR, TDOA, PDoA) that needCode implements at firmware level.
needCode contributed to the BLE Mesh specification at Bluetooth SIG and delivered the first commercially certified BLE Mesh stack, which enabled the Silvair client to secure Series A funding. That is documented specification-level contribution, not just application integration: it satisfies the certification criterion’s protocol-level evidence, though automotive-specific certification (ISO 26262, AUTOSAR) is not documented on the public site.
ISO 9001:2015 and ISO 27001:2022 are both active, making the firm eligible for defence and NATO programme supplier lists under EU member state procurement rules. Poland is a NATO member.
The Butterfly.care infant vital signs wearable (BLE, clinical accuracy), BLE badge proximity system (real-time tracking, sub-metre resolution), and Creative Werks boat lift modernisation (1,230% ROI, £1.6M value generated, 2–3 month payback period) cover three distinct ICP scenarios: medical hardware startup, industrial IoT, and legacy product rescue for a hardware OEM.
Where it falls short: Automotive-specific certification tracks (AUTOSAR Classic/Adaptive, ISO 26262 ASIL ratings) are not documented, and no confirmed SDV programme case study is currently public. OEMs whose primary need is AUTOSAR middleware integration should confirm this before contract.
Scoring: Protocol depth 2 | SDK/bring-up 2 | Ramp speed 2 | Certification 1 | EU + ISO 27001 2 | Delivery evidence 2 | ICP vertical fit 2 = 13/14
- Elsys Design, 9/14
Headquarters: Bordeaux, France
Team size: ~450 engineers
Founded: 2001
Elsys Design is a French embedded engineering services firm with documented capability in automotive (AUTOSAR Classic and Adaptive Platform), aerospace and defence (DO-178C, DO-254), and industrial embedded systems. It is one of the better-known EU-based firms for safety-critical embedded work.
Its certification depth is the clearest strength: AUTOSAR expertise, aerospace DO-178C, and documented experience with ISO 26262 functional safety for automotive ECUs. AUTOSAR’s platform standards define the software architecture most automotive OEMs use for ECU software, and firms offering automotive embedded systems development services with AUTOSAR Classic and Adaptive depth can position themselves for SDV programme integration work. Elsys has this depth.
For hardware OEMs in automotive or defence, Elsys represents a credible alternative for safety-framework integration. Where it is weaker is wireless protocol specificity. The firm’s wireless coverage tends to be at the integration layer (cellular, BLE connectivity for product features) rather than at the protocol stack or chipset SDK level. UWB positioning firmware, BLE Channel Sounding, or Bluetooth SIG qualification process experience are not prominently documented.
On ramp speed, Elsys operates on standard engineering services timelines, where project engagement through scope, proposal, and staffing typically runs longer than a pre-integrated team model.
Scoring: Protocol depth 1 | SDK/bring-up 1 | Ramp speed 1 | Certification 2 | EU + ISO 27001 2 | Delivery evidence 1 | ICP vertical fit 1 = 9/14
- Etteplan, 9/14
Headquarters: Hyvinkää, Finland
Team size: ~3,600 engineers
Founded: 1983
Etteplan is one of Northern Europe’s largest engineering services companies, with operations in Finland, Sweden, Netherlands, Germany, and China. It covers electronics design, embedded software, mechanical engineering, and technical documentation at scale.
Its primary advantages in this evaluation are team scale (ability to staff large programmes quickly), ISO 27001 compliance as an enterprise-grade supplier, and a strong certification track record in industrial and medical embedded systems (IEC 61508, IEC 62304). For OEMs running complex multi-workstream programmes that need a firm with infrastructure, process rigour, and capacity to absorb volume, Etteplan offers attributes that smaller specialist firms cannot.
Where Etteplan scores lower is on wireless protocol specificity. The firm’s embedded software capability is broad (it covers automotive ECUs, industrial control, medical devices) but specific depth in BLE 5.x protocol stacks, UWB ranging firmware, or BLE Channel Sounding is not a documented focus. An OEM selecting Etteplan for a wireless connectivity programme would need to verify which embedded radio engineers are assigned and what their specific BLE or UWB protocol experience is.
For semiconductor SDK outsourcing or UWB positioning programme work, firms with dedicated wireless protocol teams are a stronger fit.
Scoring: Protocol depth 0 | SDK/bring-up 1 | Ramp speed 2 | Certification 1 | EU + ISO 27001 2 | Delivery evidence 2 | ICP vertical fit 1 = 9/14
- ByteSnap Design, 7/14
Headquarters: Birmingham, UK
Team size: ~50 engineers
Founded: 2008
ByteSnap Design is a UK-based embedded hardware and firmware design house with documented automotive and consumer IoT experience. Its team covers PCB design, embedded Linux, RTOS firmware, and wireless connectivity integration (BLE, WiFi). The automotive track record includes MISRA C coding standard adherence and ISO 26262 experience, positioning it reasonably for connected automotive component work.
The two criteria where ByteSnap performs least well in this evaluation are EU compliance and protocol depth. As a UK-based firm post-Brexit, it falls outside EU supplier frameworks, a direct issue for defence, NATO programme, or EU-internal supply chain requirements. Its wireless coverage is at the integration layer rather than the protocol stack: BLE and WiFi connectivity as product features, rather than UWB ranging firmware, BLE Mesh specification work, or channel sounding ranging algorithms. For OEMs whose wireless requirement is application integration on a standard chipset SDK, ByteSnap is appropriate; for those needing protocol-depth wireless expertise, the evidence is thinner.
Scoring: Protocol depth 1 | SDK/bring-up 1 | Ramp speed 1 | Certification 2 | EU + ISO 27001 0 | Delivery evidence 1 | ICP vertical fit 1 = 7/14
- Promwad, 7/14
Headquarters: Warsaw, Poland (operations also in Belarus)
Team size: ~200 engineers
Promwad is an embedded IoT product development firm operating primarily from Poland with additional engineering resources in Belarus. It covers hardware design, firmware, and wireless connectivity (BLE, WiFi, Zigbee, NB-IoT) for IoT product development across industrial and consumer verticals.
The strength is breadth: Promwad covers a range of wireless protocols and embedded product lifecycle stages from concept to production. Its EU presence (Poland) is an advantage over firms headquartered fully outside the EU.
Where the firm’s score reflects limitation is in protocol depth and certification specificity. Published case studies with quantified metrics are less prominent than in higher-scoring firms. UWB positioning firmware, BLE Channel Sounding, or Bluetooth SIG specification contribution are not a documented focus. For hardware OEMs needing a firm with generalist IoT product development capability and EU presence, Promwad is a reasonable option; for those needing UWB, BLE CS, or semiconductor SDK depth, more specialist firms are a better fit.
Scoring: Protocol depth 1 | SDK/bring-up 1 | Ramp speed 1 | Certification 1 | EU + ISO 27001 1 | Delivery evidence 1 | ICP vertical fit 1 = 7/14
- Silicon Witchery, 6/14
Headquarters: France
Team size: Boutique (1–3 engineers)
Founded: 2018
Silicon Witchery, founded by Guillaume Ribell, is one of the most technically specific BLE firmware boutiques in Europe. Its content (covering BLE power optimisation, advertising intervals, connection parameter tuning, and low-power firmware architecture) reflects genuine protocol-stack depth that most generalist IoT firms cannot match.
For hardware OEMs with a specific BLE firmware problem (power budget too high, connection stability issues, advertising latency), Silicon Witchery’s depth is precisely targeted. The certification and EU scores reflect the technical competence within BLE.
Its score is limited by two factors that matter to most OEM programmes: scale and scope. A boutique of 1–3 engineers cannot be embedded as a team into a semiconductor vendor’s SDK programme or an automotive OEM’s supply chain. And its coverage does not extend to UWB positioning, BLE Channel Sounding, multi-protocol coexistence, or any of the verticals beyond BLE-specific consumer/industrial wireless. For a focused BLE firmware optimisation engagement, Silicon Witchery is a strong option; for broader ICP programme work, it does not have the capacity.
Scoring: Protocol depth 2 | SDK/bring-up 1 | Ramp speed 0 | Certification 1 | EU + ISO 27001 1 | Delivery evidence 1 | ICP vertical fit 0 = 6/14
- Softeq, 6/14
Headquarters: Houston, Texas, USA (engineering in Minsk, Belarus)
Team size: ~900 engineers
Softeq is a large embedded and IoT software development firm with a broad portfolio across connected devices, wearables, industrial IoT, and enterprise software. Its team scale is an advantage for programmes requiring capacity, and its delivery across diverse IoT verticals is documented.
The criteria where Softeq’s score reflects risk for specific OEM programmes are compliance and certification. Belarus-based engineering operations create complexity for EU defence, NATO, or data-sensitive programmes where supplier location is a procurement criterion. ISO 27001 confirmation for the engineering delivery team is not prominently documented. Wireless certification track record (BLE SIG processes, FiRa certification, automotive wireless standards) is not a documented focus area.
For hardware OEMs in commercial IoT who need software development volume and can manage the compliance requirements independently, Softeq’s scale and portfolio are genuine assets. For OEMs in automotive, defence, or regulated industries where supplier location and certification compliance are contractual, the Belarus engineering base is a material consideration.
Scoring: Protocol depth 1 | SDK/bring-up 1 | Ramp speed 2 | Certification 0 | EU + ISO 27001 0 | Delivery evidence 1 | ICP vertical fit 1 = 6/14
- Lemberg Solutions, 6/14
Headquarters: Lviv, Ukraine
Team size: ~400 engineers
Founded: 2007
Lemberg Solutions is a Ukrainian embedded software and IoT development company with a large engineering team and documented IoT delivery across industrial, automotive software, and consumer electronics verticals. Its scale allows it to staff projects quickly.
Its score reflects two limitations for hardware OEM wireless programmes: SDK/bring-up depth and certification track record. The firm’s wireless work centres on application-layer connectivity (BLE, WiFi, Zigbee integration) rather than protocol-stack or chipset SDK level engagement. Wireless certification pipeline experience (Bluetooth SIG QDID processes, FiRa, automotive wireless) is not a documented focus area. Ukraine’s EU candidacy status means it falls outside formal EU supplier frameworks for defence and NATO programme procurement, though this distinction matters more to some OEMs than others.
For commercial IoT programmes where application-layer wireless integration is the requirement and team scale is valuable, Lemberg Solutions is competitive. For OEMs needing protocol depth, certification navigation, or EU compliance, higher-scoring firms are a better match.
Scoring: Protocol depth 1 | SDK/bring-up 0 | Ramp speed 2 | Certification 0 | EU + ISO 27001 1 | Delivery evidence 1 | ICP vertical fit 1 = 6/14
How to shortlist by ICP
The seven criteria do not all carry equal weight across buyer scenarios. Here is how to weight them for five OEM ICP profiles.
Semiconductor / chipmaker SDK outsourcing (queries: embedded team augmentation, SDK bring-up, 3 products simultaneously)
Weight highest: SDK & bring-up depth (criterion 2), ramp speed (criterion 3). A chipset vendor launching on a compressed timeline needs a team that can start on the SDK within weeks and has silicon-vendor experience at driver and protocol-stack level. Protocol depth and ICP vertical fit are secondary.
Automotive / Software Defined Vehicle (queries: certified wireless stacks, in-cabin BLE for SDV)
Weight highest: certification track record (criterion 4), protocol depth for BLE Channel Sounding (criterion 1). Bluetooth Channel Sounding is the specification underpinning secure digital key and keyless entry in SDV programmes: firms that contributed to the BLE SIG process or have Channel Sounding firmware experience carry directly relevant capability. AUTOSAR integration experience is equally important.
Robotics / humanoid (queries: sub-13cm UWB indoor positioning, no UWB team in-house)
Weight highest: protocol depth with UWB (criterion 1), ICP vertical fit for robotics (criterion 7). Among top RTLS companies shortlisted for robotics programmes, a firm that has deployed UWB anchor infrastructure, written TDOA/AoA/TWR ranging algorithms, and fused UWB with IMU and LiDAR is fundamentally different from one that has read the UWB datasheet. Look for sub-centimetre static accuracy data from real deployments, not marketing copy.
Defence / NATO programmes (queries: EU-based partner, ISO 27001 consultancy, GPS-denied UWB)
Weight highest: EU + ISO 27001 (criterion 5), certification (criterion 4). Supplier location is often a hard gate: Belarus or Ukraine engineering bases may not satisfy procurement requirements regardless of technical capability. ISO 27001:2022 is increasingly a contract prerequisite for defence prime supplier chains.
VC-backed hardware startups (queries: concept-to-production partner, fast deployment under 6 weeks)
Weight highest: ramp speed (criterion 3), delivery evidence (criterion 6). A startup on a funding runway needs a team operational immediately, not after a 12-week scoping and staffing process. Published case studies showing concept-to-production delivery with real timelines and outcomes are the strongest indicator of whether a firm can execute at startup speed.
Working with needCode
needCode provides embedded software development outsourcing and embedded development outsourcing services for hardware OEMs, semiconductor vendors, and robotics teams across IoT RTLS, UWB tracking, industrial IoT connectivity, and automotive embedded systems development. If you are shortlisting embedded wireless development partners and want to discuss programme scope, platform selection, and team deployment timeline, we are happy to talk. Book a free discovery call or get in touch.
Frequently asked questions
An embedded wireless development partner is a firm that provides engineers, protocol knowledge, and delivery infrastructure to build the wireless firmware layer of a hardware product. This is distinct from an IoT software integrator (which works at the application layer) and from a semiconductor vendor (which produces the chipset but does not write application-specific firmware). Most hardware OEMs need a partner when launching a product whose wireless requirements exceed their internal team’s protocol depth or capacity.
The primary difference is protocol-stack depth. A general embedded software house can integrate a BLE module using an off-the-shelf SDK, connect it to an RTOS, and ship a connected device. A wireless development specialist writes or modifies the protocol stack itself, navigates the Bluetooth SIG qualification process, implements ranging algorithms (TDOA, AoA, TWR) for UWB, and tunes coexistence between multiple radios on one board. The distinction becomes critical when OEMs need certification, sub-centimetre positioning accuracy, or custom protocol behaviour that the standard SDK does not support.
Ask for a specific example: “In your most recent engagement where a team was deployed quickly, how long elapsed between contract signature and the team being productive on our codebase?” The answer should include how many engineers, what their prior experience with the relevant chipset was, and what the first two weeks looked like. A pre-integrated team that has worked together on similar silicon can typically run effective design reviews in week one; a team assembled for the first time from a staffing pool takes longer.
For current automotive SDV programmes, the two are almost always co-required. BLE Channel Sounding handles secure keyless entry and trusted proximity: the use case where a phone unlocks a car door. UWB handles precise positioning for automated parking, spatial awareness systems, and the higher-accuracy overlay where BLE Channel Sounding’s centimetre-level accuracy is needed in specific scenarios. A firm that has only BLE or only UWB experience will require integration support from the other side.
ISO 27001:2022 is an information security management standard that specifies how a firm controls access to data, manages development environments, handles client IP, and responds to security incidents. For hardware OEMs in defence, automotive, or medical sectors, ISO 27001 at the supplier is often a contract prerequisite. It means client source code, specification documents, and test data are handled under a documented security management system, not just contractual IP agreements.
