S3 Connected Health vs Plexus: full comparison for 2026
Quick verdict
S3 Connected Health (4.2/5) edges ahead of Plexus (3.8/5) overall. S3 Connected Health is the better choice for pharma companies adding connectivity to drug delivery. Plexus is the stronger option for complex capital equipment needing build and sustaining. The right choice depends on your project size, budget, and required tech stack.
S3 Connected Health vs Plexus: head-to-head summary
| Criterion | S3 Connected Health | Plexus |
|---|---|---|
| Founded | 2001 | 1979 |
| HQ | Dublin, Ireland | Neenah, WI, USA |
| Team size | 200–300 | ~20,000 |
| Rating | 4.2 / 5 | 3.8 / 5 |
| Primary differentiator | Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs | Engineering, NPI and sustaining services for low-to-mid volume, high-complexity medical equipment |
| Pricing model | Fixed project, time and materials, managed service | NPI contract, manufacturing supply agreement |
| Min. engagement | Not disclosed | Not disclosed |
| Primary tech stack | BLE, Embedded C/C++, iOS | PCB design, PCB assembly, Embedded C/C++ |
| Industries served | Drug delivery, Digital health, Wearables & remote monitoring | Surgical & robotics, Diagnostics & lab devices, Aerospace, Industrial |
S3 Connected Health vs Plexus: overview
S3 Connected Health
S3 Connected Health is the connected health business of Dublin's S3 Group (Silicon & Software Systems), which dates to 1986; the connected health unit itself is listed as founded around 2001. After the group sold its semiconductor unit to Adesto, it concentrated on this business. It works with pharma and medtech companies on connected drug delivery, SaMD, IoMT platforms, wireless connectivity and data security, and partnered with Ypsomed on connected injection devices. Employee figures range from about 200 to 300.
Plexus
Plexus Corp. is a NASDAQ-listed company headquartered in Neenah, Wisconsin, that offers design and development, supply chain, new product introduction, manufacturing and sustaining services. Healthcare and life sciences is one of its three markets alongside aerospace and defense and industrial. Its healthcare work includes surgical equipment, imaging equipment and diagnostic instruments. The company has around 20,000 employees in total, though only part of that is healthcare.
Services and capabilities: S3 Connected Health vs Plexus
| Capability | S3 Connected Health | Plexus |
|---|---|---|
| Electronics & PCB design | ✗ | ✓ |
| Firmware & embedded software | ✓ | ✗ |
| SaMD & companion apps | ✓ | ✗ |
| Connected devices & IoT | ✓ | ✗ |
| Industrial design & human factors | ✗ | ✗ |
| Mechanical engineering | ✗ | ✓ |
| Device cybersecurity | ✓ | ✗ |
| Regulatory & QMS support | ✓ | ✓ |
| Manufacturing & scale-up | ✗ | ✓ |
Tech stack comparison: S3 Connected Health vs Plexus
| Framework / platform | S3 Connected Health | Plexus |
|---|---|---|
| Embedded C/C++ | ✓ | ✓ |
| Embedded Linux | N/A | N/A |
| RTOS | N/A | N/A |
| BLE | ✓ | N/A |
| Cloud (AWS/Azure) | ✓ | N/A |
| IEC 62304 | ✓ | N/A |
| ISO 14971 | N/A | N/A |
| ISO 13485 QMS | N/A | ✓ |
| Qt | N/A | N/A |
Pricing comparison: S3 Connected Health vs Plexus
| Criterion | S3 Connected Health | Plexus |
|---|---|---|
| Minimum engagement | Not disclosed | Not disclosed |
| Engagement models | Dedicated team, Fixed project, Time & materials | Fixed project, Manufacturing contract |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: S3 Connected Health vs Plexus
| Dimension | S3 Connected Health | Plexus |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Drug delivery, Digital health, Wearables & remote monitoring | Surgical & robotics, Diagnostics & lab devices, Aerospace |
| Best use cases | Adding Bluetooth connectivity to an autoinjector, Building a patient adherence app and backend | Building and sustaining a diagnostic imaging subsystem, Electronics redesign for component obsolescence |
| Typical project type | Dedicated team | Fixed project |
S3 Connected Health vs Plexus: pros and cons
| S3 Connected Health | |
|---|---|
| + | Long experience in wireless and embedded software from its S3 Group background |
| + | Works directly with pharma on connected injectors and inhalers, such as the Ypsomed partnership |
| + | Covers apps, cloud and the device connectivity module |
| + | Delivery team includes a site in Poland, which helps with cost |
| - | Founding date and history are tangled with the wider S3 Group, so check which entity you contract with |
| - | Not a mechanical or industrial design firm |
| - | Pharma focus means pure medtech hardware projects are less common |
| Plexus | |
|---|---|
| + | Strong with complex, lower-volume capital equipment such as imaging and surgical systems |
| + | Offers product engineering as well as manufacturing |
| + | Sustaining engineering over long product lives |
| + | Public company with transparent financial reporting |
| - | Generalist manufacturer; healthcare competes with aerospace and industrial for capacity |
| - | Not a fit for early-stage concept work |
| - | Most engineering engagements lead toward a manufacturing contract |
Who should choose S3 Connected Health?
A typical fit: adding Bluetooth connectivity to an autoinjector.
Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs. Minimum engagement is not publicly disclosed. Works best with clients in Drug delivery, Digital health, Wearables & remote monitoring.
Who should choose Plexus?
A typical fit: building and sustaining a diagnostic imaging subsystem.
Engineering, NPI and sustaining services for low-to-mid volume, high-complexity medical equipment. Minimum engagement is not publicly disclosed. Works best with clients in Surgical & robotics, Diagnostics & lab devices, Aerospace, Industrial.
Decision matrix: S3 Connected Health vs Plexus
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | S3 Connected Health |
| You need a large dedicated team for an ongoing programme | S3 Connected Health |
| Your budget is at the lower end | Compare: S3 Connected Health (Not disclosed) vs Plexus (Not disclosed) |
| You need specialist depth in a specific vertical | Plexus |
| You need staff augmentation or team extension | Neither; consider alternatives that offer staff aug |
| You need consulting before committing to a build | Both may offer discovery engagements |
Use case fit: S3 Connected Health vs Plexus
| Use case | S3 Connected Health fit | Plexus fit | Winner |
|---|---|---|---|
| Adding Bluetooth connectivity to an autoinjector | Strong | Limited | S3 Connected Health |
| Building a patient adherence app and backend | Strong | Strong | Both equally |
| Building and sustaining a diagnostic imaging subsystem | Strong | Strong | Both equally |
| Electronics redesign for component obsolescence | Limited | Strong | Plexus |
Verdict: S3 Connected Health vs Plexus
S3 Connected Health (4.2/5) is the stronger overall choice for most Medical Device Development projects. Combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs.
Plexus (3.8/5) is worth a look if you need electronics redesign for component obsolescence. If your situation matches that, Plexus is a competitive option.
Related comparisons
S3 Connected Health vs Plexus FAQ
Is S3 Connected Health better than Plexus?
S3 Connected Health (4.2/5) scores higher overall, but "better" depends on your use case. S3 Connected Health's strongest advantage: long experience in wireless and embedded software from its S3 Group background. Plexus's strongest advantage: strong with complex, lower-volume capital equipment such as imaging and surgical systems.
How do S3 Connected Health and Plexus differ in pricing?
S3 Connected Health uses fixed project, time and materials, managed service pricing. Plexus uses npi contract, manufacturing supply agreement pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: S3 Connected Health or Plexus?
S3 Connected Health is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each company before shortlisting.
What are the main differences between S3 Connected Health and Plexus?
S3 Connected Health's primary differentiator is: combines embedded wireless engineering with patient-facing apps and data platforms for pharma programs. Plexus's primary differentiator is: Engineering, NPI and sustaining services for low-to-mid volume, high-complexity medical equipment. They also differ in team size (200–300 vs ~20,000), minimum engagement (Not disclosed vs Not disclosed), and primary industries served (Drug delivery, Digital health vs Surgical & robotics, Diagnostics & lab devices).
Verify all details directly with each company before making a decision.