ARCH-Embedded vs CMD MedTech: full comparison for 2026
Quick verdict
CMD MedTech (4.0/5) edges ahead of ARCH-Embedded (3.8/5) overall. CMD MedTech is the better choice for small teams needing close, senior-level medical device engineering with supplier-diversity credentials. ARCH-Embedded is the stronger option for teams needing engineers with direct prior positioning-technology experience. The right choice depends on your project size, budget, and required tech stack.
ARCH-Embedded vs CMD MedTech: head-to-head summary
| Criterion | ARCH-Embedded | CMD MedTech |
|---|---|---|
| Founded | 2022 | 2016 |
| HQ | Amsterdam, Netherlands | Columbus, OH, USA |
| Team size | 2–10 | 13 |
| Rating | 3.8 / 5 | 4.0 / 5 |
| Primary differentiator | Team includes engineers with prior experience at TomTom and in micro-mobility products, a specific and checkable positioning-technology background | Woman-owned small business built specifically around medical device systems, software, and regulatory support |
| Pricing model | Project-based embedded consultancy engagements | Project-based medical device engineering engagements |
| Min. engagement | Not published | Not published |
| Primary tech stack | Nordic nRF, Cellular Connectivity, RTOS | C, C++, Medical Device Software Standards |
| Industries served | Micro-mobility, Positioning and location technology, Industrial IoT | Medical devices |
ARCH-Embedded vs CMD MedTech: overview
ARCH-Embedded
ARCH-Embedded was founded in Amsterdam in 2022 by CEO and co-founder Mark Riemersma and operates with a team of 2 to 10 people, several with prior experience at TomTom and in micro-mobility products. As a Nordic Semiconductor partner, the team covers hardware through embedded software, RTOS, Linux, security, and connected-device architecture. For a hiring buyer building a location-aware or cellular-connected product, a team whose specific prior employer built commercial positioning technology at scale is a differentiated, checkable credential rather than a general claim of IoT experience.
CMD MedTech
CMD MedTech was founded in 2016 and is headquartered in Columbus, Ohio, with roughly 13 employees as of mid-2025. The firm specializes entirely in medical device development, covering systems engineering, software and firmware, and regulatory and quality support. Its status as a woman-owned small business can matter to a hiring buyer with supplier-diversity requirements, and the small team structure means a client works directly with the senior engineers doing the work rather than being routed through a larger delivery organization.
Services and capabilities: ARCH-Embedded vs CMD MedTech
| Capability | ARCH-Embedded | CMD MedTech |
|---|---|---|
| Firmware development | ✓ | ✓ |
| RTOS development | ✓ | ✗ |
| Hardware co-design | ✗ | ✗ |
| Embedded GUI development | ✗ | ✗ |
| Medical device firmware | ✗ | ✓ |
| Functional safety | ✗ | ✓ |
| Technical training | ✗ | ✗ |
| Expert-witness services | ✗ | ✗ |
| Staff augmentation | ✗ | ✗ |
Tech stack comparison: ARCH-Embedded vs CMD MedTech
| Framework / platform | ARCH-Embedded | CMD MedTech |
|---|---|---|
| C | ✓ | ✓ |
| C++ | N/A | ✓ |
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| FPGA | N/A | N/A |
| Embedded Linux | ✓ | N/A |
| LVGL | N/A | N/A |
| AWS IoT | N/A | N/A |
| ARM Cortex-M | N/A | N/A |
Pricing comparison: ARCH-Embedded vs CMD MedTech
| Criterion | ARCH-Embedded | CMD MedTech |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Project-based consultancy, Architecture and project management | Project-based engineering with regulatory support |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: ARCH-Embedded vs CMD MedTech
| Dimension | ARCH-Embedded | CMD MedTech |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Micro-mobility, Positioning and location technology, Industrial IoT | Medical devices |
| Best use cases | Hiring engineers with direct positioning-technology experience for a location-aware device, Nordic Semiconductor-based connected product architecture and firmware development | Hiring a small, senior medical device engineering team with regulatory expertise, Systems and firmware engineering for a medical device FDA submission |
| Typical project type | Project-based consultancy | Project-based engineering with regulatory support |
ARCH-Embedded vs CMD MedTech: pros and cons
| ARCH-Embedded | |
|---|---|
| + | Team includes engineers with prior experience at TomTom, a specific and checkable positioning-technology background |
| + | Nordic Semiconductor partner status backs its cellular and positioning-technology hardware claims |
| + | Full-stack scope from hardware through RTOS, Linux, and security architecture covers more than firmware coding alone |
| + | Small team size means direct senior engineering involvement on every engagement |
| - | Founded in 2022 with 2 to 10 employees, giving it one of the shortest track records and smallest teams on this list |
| - | Capacity for large or multiple concurrent programs is limited by team size |
| - | No published pricing or minimum engagement figure |
| CMD MedTech | |
|---|---|
| + | Medical device development is the firm's sole focus, not one vertical among several |
| + | Woman-owned small business status can satisfy supplier-diversity requirements in enterprise and government hiring |
| + | Regulatory and quality support is built into the delivery process rather than treated as a separate service |
| + | Small team size gives direct access to senior engineers rather than being routed through account layers |
| - | 13 employees is one of the smallest teams on this list, which caps how many concurrent programs the firm can run |
| - | 9 years of operating history is shorter than several competitors with 20-plus years in medical device work |
| - | No published pricing or minimum engagement figure |
Who should choose ARCH-Embedded?
A typical fit: hiring engineers with direct positioning-technology experience for a location-aware device.
Team includes engineers with prior experience at TomTom and in micro-mobility products, a specific and checkable positioning-technology background. Minimum engagement is not publicly disclosed. Works best with clients in Micro-mobility, Positioning and location technology, Industrial IoT.
Who should choose CMD MedTech?
A typical fit: hiring a small, senior medical device engineering team with regulatory expertise.
Woman-owned small business built specifically around medical device systems, software, and regulatory support. Minimum engagement is not publicly disclosed. Works best with clients in Medical devices.
Decision matrix: ARCH-Embedded vs CMD MedTech
| Your situation | Recommended choice |
|---|---|
| You need full-ownership delivery on a defined project scope | Both offer fixed-price models |
| You need a large dedicated team for an ongoing programme | Check each company's engagement model |
| Your budget is at the lower end | Compare: ARCH-Embedded (Not published) vs CMD MedTech (Not published) |
| You need specialist depth in a specific vertical | ARCH-Embedded |
| You need staff augmentation or team extension | Neither; consider alternatives that offer staff aug |
| You need consulting before committing to a build | CMD MedTech |
Use case fit: ARCH-Embedded vs CMD MedTech
| Use case | ARCH-Embedded fit | CMD MedTech fit | Winner |
|---|---|---|---|
| Hiring engineers with direct positioning-technology experience for a location-aware device | Strong | Strong | Both equally |
| Nordic Semiconductor-based connected product architecture and firmware development | Strong | Limited | ARCH-Embedded |
| Hiring a small, senior medical device engineering team with regulatory expertise | Strong | Strong | Both equally |
| Systems and firmware engineering for a medical device FDA submission | Limited | Strong | CMD MedTech |
| Fixed-price build | Limited | Limited | Both equally |
| Staff augmentation | Limited | Limited | Both equally |
Verdict: ARCH-Embedded vs CMD MedTech
CMD MedTech (4.0/5) is the stronger overall choice for most Embedded Firmware Development projects. Woman-owned small business built specifically around medical device systems, software, and regulatory support.
ARCH-Embedded (3.8/5) is worth a look if you need nordic Semiconductor-based connected product architecture and firmware development. If your situation matches that, ARCH-Embedded is a competitive option.
Related comparisons
ARCH-Embedded vs CMD MedTech FAQ
Is ARCH-Embedded better than CMD MedTech?
CMD MedTech (4.0/5) scores higher overall, but "better" depends on your use case. ARCH-Embedded's strongest advantage: team includes engineers with prior experience at TomTom, a specific and checkable positioning-technology background. CMD MedTech's strongest advantage: medical device development is the firm's sole focus, not one vertical among several.
How do ARCH-Embedded and CMD MedTech differ in pricing?
ARCH-Embedded uses project-based embedded consultancy engagements pricing. CMD MedTech uses project-based medical device engineering engagements pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: ARCH-Embedded or CMD MedTech?
ARCH-Embedded is the larger team and typically the better enterprise-scale choice. For very large programmes, verify team size and compliance coverage directly with each developer before shortlisting.
What are the main differences between ARCH-Embedded and CMD MedTech?
ARCH-Embedded's primary differentiator is: team includes engineers with prior experience at TomTom and in micro-mobility products, a specific and checkable positioning-technology background. CMD MedTech's primary differentiator is: woman-owned small business built specifically around medical device systems, software, and regulatory support. They also differ in team size (2–10 vs 13), minimum engagement (Not published vs Not published), and primary industries served (Micro-mobility, Positioning and location technology vs Medical devices).
Verify all details directly with each developer before making a decision.