Barr Group vs EES: full comparison for 2026
Quick verdict
Barr Group (4.5/5) edges ahead of EES (3.8/5) overall. Barr Group is the better choice for teams wanting engineers whose published technical work they can vet before hiring. EES is the stronger option for teams deliberately avoiding a large delivery organization in favor of senior-led staff. The right choice depends on your project size, budget, and required tech stack.
Barr Group vs EES: head-to-head summary
| Criterion | Barr Group | EES |
|---|---|---|
| Founded | 2012 | 2012 |
| HQ | Gaithersburg, MD, USA | Tempe / Chandler, AZ, USA |
| Team size | 51–200 | 3–50 |
| Rating | 4.5 / 5 | 3.8 / 5 |
| Primary differentiator | Led by Michael Barr, a recognized embedded software author and former magazine editor-in-chief, giving prospective clients a public body of work to evaluate first | Explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation |
| Pricing model | Consulting engagements, training courses, expert-witness services | Contract engineering engagements |
| Min. engagement | Not published | Not published |
| Primary tech stack | C, C++, RTOS Architecture Review | C, C++, Industrial Embedded Systems |
| Industries served | Medical devices, Industrial, Consumer electronics, Legal / litigation support | Industrial |
Barr Group vs EES: overview
Barr Group
Barr Group was founded in 2012 and is headquartered in Gaithersburg, Maryland, with a team in the 51 to 200 employee range. Led by CTO Michael Barr, a former editor-in-chief of Embedded Systems Design magazine and author of multiple embedded software books, the firm's identity centers on training, firmware process and architecture work, and legal technical expert-witness services rather than volume staffing. For an engineering leader deciding who to bring onto a team, working alongside people whose technical writing they've likely already read is a different kind of hiring signal than a generic vendor profile.
EES
Embedded Engineering Solutions (EES) was launched in 2012 and is based in Tempe, Arizona, with reported headcount varying across sources from roughly 3 to 50 employees, most consistently described as a small, senior-led firm. The company specializes in contract firmware, embedded systems, and hardware design engineering for the industrial sector, and its own positioning leans on being senior-led rather than layered with junior staff. For a hiring buyer specifically avoiding a large delivery organization, that's the stated value proposition, not an incidental trait.
Services and capabilities: Barr Group vs EES
| Capability | Barr Group | EES |
|---|---|---|
| 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: Barr Group vs EES
| Framework / platform | Barr Group | EES |
|---|---|---|
| C | ✓ | ✓ |
| C++ | ✓ | ✓ |
| FreeRTOS | N/A | N/A |
| Zephyr | N/A | N/A |
| FPGA | N/A | N/A |
| Embedded Linux | N/A | N/A |
| LVGL | N/A | N/A |
| AWS IoT | N/A | N/A |
| ARM Cortex-M | N/A | N/A |
Pricing comparison: Barr Group vs EES
| Criterion | Barr Group | EES |
|---|---|---|
| Minimum engagement | Not published | Not published |
| Engagement models | Firmware process & architecture consulting, Training, Expert-witness services | Contract firmware and hardware engineering |
| Rate transparency | Not public | Not public |
| Price tier | Mid-market | Mid-market |
Target audience comparison: Barr Group vs EES
| Dimension | Barr Group | EES |
|---|---|---|
| Best company size | Startup to mid-market | Startup to mid-market |
| Best industries | Medical devices, Industrial, Consumer electronics | Industrial |
| Best use cases | Bringing in a recognized technical authority to review an in-house team's architecture decisions, Firmware process training for engineers already on staff | Hiring a deliberately small, senior-led team for an industrial firmware program, Combined hardware and firmware engineering without separate specialist vendors |
| Typical project type | Firmware process & architecture consulting | Contract firmware and hardware engineering |
Barr Group vs EES: pros and cons
| Barr Group | |
|---|---|
| + | Michael Barr's public technical writing and books give a prospective client a way to evaluate the team's judgment before ever making contact |
| + | Training as a core business line means the firm's engineers are practiced at explaining their reasoning, not just doing the work silently |
| + | 13 years of operating history built specifically around expert technical judgment rather than headcount growth |
| + | 51 to 200 employees give real bench depth for a firm this specialized |
| - | Volume firmware development capacity is not the firm's stated focus, so a large parallel build program may need a second team |
| - | No published consulting rate or minimum engagement figure |
| - | Expert-witness work is a distinct practice from product engineering; confirm which team a specific inquiry reaches |
| EES | |
|---|---|
| + | Explicit senior-led positioning means the small team size is a deliberate choice, not just a growth-stage limitation |
| + | 13 years of operating history as a contract engineering firm for the industrial sector |
| + | Combines firmware, embedded systems, and hardware design in one team, covering multiple disciplines without separate specialist hires |
| + | Small size means a client's engagement represents a meaningful share of the firm's total capacity |
| - | Reported employee counts vary widely across sources, from roughly 3 to 50, worth confirming current headcount directly |
| - | Small team size caps capacity for a large or multi-workstream program |
| - | No published pricing or minimum engagement figure |
Who should choose Barr Group?
A typical fit: bringing in a recognized technical authority to review an in-house team's architecture decisions.
Led by Michael Barr, a recognized embedded software author and former magazine editor-in-chief, giving prospective clients a public body of work to evaluate first. Minimum engagement is not publicly disclosed. Works best with clients in Medical devices, Industrial, Consumer electronics, Legal / litigation support.
Who should choose EES?
A typical fit: hiring a deliberately small, senior-led team for an industrial firmware program.
Explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation. Minimum engagement is not publicly disclosed. Works best with clients in Industrial.
Decision matrix: Barr Group vs EES
| 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: Barr Group (Not published) vs EES (Not published) |
| You need specialist depth in a specific vertical | Barr Group |
| You need staff augmentation or team extension | Neither; consider alternatives that offer staff aug |
| You need consulting before committing to a build | Barr Group |
Use case fit: Barr Group vs EES
| Use case | Barr Group fit | EES fit | Winner |
|---|---|---|---|
| Bringing in a recognized technical authority to review an in-house team's architecture decisions | Strong | Limited | Barr Group |
| Firmware process training for engineers already on staff | Strong | Strong | Both equally |
| Hiring a deliberately small, senior-led team for an industrial firmware program | Limited | Strong | EES |
| Combined hardware and firmware engineering without separate specialist vendors | Limited | Strong | EES |
| Fixed-price build | Limited | Limited | Both equally |
| Staff augmentation | Strong | Limited | Barr Group |
Verdict: Barr Group vs EES
Barr Group (4.5/5) is the stronger overall choice for most Embedded Firmware Development projects. Led by Michael Barr, a recognized embedded software author and former magazine editor-in-chief, giving prospective clients a public body of work to evaluate first.
EES (3.8/5) is worth a look if you need combined hardware and firmware engineering without separate specialist vendors. If your situation matches that, EES is a competitive option.
Related comparisons
Barr Group vs EES FAQ
Is Barr Group better than EES?
Barr Group (4.5/5) scores higher overall, but "better" depends on your use case. Barr Group's strongest advantage: michael Barr's public technical writing and books give a prospective client a way to evaluate the team's judgment before ever making contact. EES's strongest advantage: explicit senior-led positioning means the small team size is a deliberate choice, not just a growth-stage limitation.
How do Barr Group and EES differ in pricing?
Barr Group uses consulting engagements, training courses, expert-witness services pricing. EES uses contract engineering engagements pricing. Neither firm publishes a full rate card; a discovery call is required for project-specific quotes.
Which is better for enterprise: Barr Group or EES?
Barr Group 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 Barr Group and EES?
Barr Group's primary differentiator is: led by Michael Barr, a recognized embedded software author and former magazine editor-in-chief, giving prospective clients a public body of work to evaluate first. EES's primary differentiator is: explicitly positions itself as senior-led, keeping the team small by design rather than as a growth-stage limitation. They also differ in team size (51–200 vs 3–50), minimum engagement (Not published vs Not published), and primary industries served (Medical devices, Industrial vs Industrial).
Verify all details directly with each developer before making a decision.