How to Pick Firmware Design Services That Won't Cost You Later

9 Things to Look for in Firmware Design Services

Here are nine things you can look for when evaluating firmware design services. Each one is the specific gap that can show up after signing.

1. Experience With Your Hardware Platform

A team can be fluent in either STM32 or ESP32. Being fluent in one doesn't automatically make one fluent in another. The two skill sets don't transfer as cleanly. First, evaluate what they have actually shipped to your class of chip. The gap between those two answers shows up fast once real hardware is in the room.

2. Strong Firmware Architecture

Architecture is the hardest decision to reverse once code sits on top of it. We've shipped firmware on a Cortex-M0 with 16KB of RAM, where every byte had to earn its place. A services provider should be able to walk through that kind of constraint in detail. Ask whether your project needs a from-scratch architecture or fits inside a narrower custom firmware development scope. That call changes the quote, and a real partner can make it in the first conversation. 

3. Board Bring-Up and Hardware Integration

Board bring-up is where the schematic and the firmware either agree or don't. This is the stage that exposes whether something worked in a demo or actually works. Ask about a bring-up they've done recently. A chip from three years ago doesn't tell you much about today's hardware.

4. RTOS and Real-Time Expertise

FreeRTOS and Zephyr solve overlapping problems in different ways. Picking between them is an architecture decision, not a preference. A real partner explains the tradeoff for your specific timing constraints. If they can't do that clearly, the rest of the technical calls, including the actual firmware programming choices, were probably made the same way. 

5. Testing and Debugging Process

Ask specifically about hardware-in-the-loop testing. A vague answer here means the whole testing process is vague, and that gap surfaces after launch, when it's expensive to fix. JTAG and logic analyzers should come up on their own, without you having to ask what tools they use.

6. Manufacturing Readiness

Bench-tested firmware and manufacturing-ready firmware are different deliverables. Ask whether this team has taken firmware through an actual production run or only ever handed off a demo. Calibration routines and factory test modes never reach the customer, but skipping them is how unit two hundred stalls the line.

7. Long-Term Maintenance and OTA Updates

Ask who patches this device in eighteen months, once the original engineers have moved on. Get that answered before you sign. A device shipped without an OTA path built into the architecture usually needs a hardware revision to get one later.

8. Communication and Documentation

Firmware without documentation becomes unmaintainable the day the person who wrote it leaves. Ask to see a documentation sample before signing. If a provider can't produce one, that tells you what a handoff with them will actually look like.

9. Security Standards and Secure Boot

OTA updates are one of the most common attack surfaces on a connected device. Ask exactly how updates get signed and verified before they run on hardware already in the field. Security built in at the chip, with secure boot and encrypted storage, holds up differently than security added at the API layer after the architecture is locked.

Questions to Ask Before Hiring a Firmware Development Company

Ask these six directly, in the first call, and listen for an answer that names a real project instead of a general capability.

1. What have you actually shipped on hardware like mine?

Not what they've studied. What they've shipped. The answer should include a chip family, a rough unit volume, and ideally an industry, because a team that's only shipped consumer gadgets will make different mistakes on a medical device than a team that's done both.

2. How do you handle it when the schematic and the firmware disagree?

Every experienced team has a story here, because it happens on nearly every project with real hardware. If they can't produce one, they haven't been through a bring-up that actually tested them.

3. What does your testing process look like before code reaches production?

Push for specifics like unit tests, integration tests, and whether hardware-in-the-loop testing is standard practice or an upsell. A vague answer here is one of the strongest predictors of a rough manufacturing run.

4. How do you sign and verify OTA updates?

If the answer doesn't mention secure boot or signed firmware images, the update path probably wasn't designed with security in mind from the start, and retrofitting it later usually means a hardware revision.

5. Who owns the documentation, and can I see a sample?

You're not just buying working firmware. You're buying the ability for someone else to maintain it after the original team moves on. A provider with nothing to show here is telling you what year three looks like.

6. What happens if the timeline slips, and who absorbs that cost?

This is the question most teams forget to ask, and the answer separates a partner from a vendor. A firmware delay usually traces back to a hardware revision nobody budgeted time for, and how a provider handles that, honestly, tells you more than anything on their capabilities page.

Firmware Development Costs: How Much Do Design Services Cost?

Firmware design services costs depend on scope more than anything else, and the honest range is wide enough that a flat number quoted before anyone's seen your schematic is close to meaningless. A design-only engagement on an existing, well-documented board can run $15,000 to $40,000. Add board bring-up from a blank schematic, certification support, or a full connectivity stack, and the same project can climb past $150,000 before manufacturing firmware even enters the conversation.

None of these move in isolation. A medical device with a new board and a full connectivity stack stacks three of these at once, which is why certified projects routinely run several times the cost of a simple consumer device on a known chip.

A few numbers worth having in your head before a call:

• Design-only, existing board, no certification: $15k to $40k

• Full build, new board, consumer-grade: $40k to $90k

• Certified build (medical, automotive, industrial safety): $90k to $250k or more, driven mostly by compliance testing rather than engineering hours

• Manufacturing firmware and factory test modes: usually 10 to 20% on top of the base build

These are ranges, not quotes, and any provider that gives you an exact number before seeing your schematic is guessing. A 30-minute conversation about your specific board gets you a real number faster than any range in a blog, including this one.

Conclusion

The eight criteria above and the six questions aren't a scorecard where more checkmarks wins. A provider who's honest about which of these they're weak on is more trustworthy than one who claims strength on all eight in the first call.

If your project sits on an established board with no certification and a short field life, price is a fair way to choose. If it doesn't, price is the least useful signal you have, and the questions matter more than the quote.

Send the schematic to two providers, ask the six questions above, and pay attention to which one names a real project instead of a general capability. That answer will tell you more about the next eighteen months than any proposal will.