Request a firmware review
Menu
Founders and engineering leads working out where firmware help fits

Firmware needs by product type

The method is the same for every product. What changes is the radio, the rules, the length of the field life and what a failed update would cost you.

Key characteristics

Works with
Startups from first prototype to first production run
Same everywhere
Signed releases, tested rollback, written handover
Changes by product
Radios, rules, field life and update windows
First step
A firmware review that ends in a written plan

Fumbar works with hardware startups that need device firmware written, an update path built, or both. Most are small teams somewhere between a working prototype and a first production run. Often there is a hardware engineer on staff and nobody yet whose whole job is the code on the device. Sometimes there is a firmware engineer who needs a second pair of hands, or an update pipeline that nobody has had time to build.

The method does not change with the product. Every engagement moves through the same five stages (Review, Bring-up, Build, Ship and Sustain), described on how we work. Every product ends up with signed releases, a rollback that has been tested by breaking it, and documentation your own team can run with. One technical lead writes you a short status every week and a release report after every release.

What changes is everything around the method:

Product type What tends to drive the firmware
Hardware startups at seed or Series A Decisions that are cheap before the first production run and expensive after it
Connected consumer products Phone apps, Bluetooth LE, Matter, and security rules in the US, UK and EU
Medical devices FDA cybersecurity expectations, SBOMs and a plan for updates after launch
Climate and energy Long field lives, cellular data costs and clear lines around safety functions
Robotics Real-time control, Linux and microcontroller splits, and updates on machines that move
Industrial IoT Long service lives, low-power wide-area radios and narrow update windows

Each page below explains what usually matters for that kind of product, which decisions to make early, and which services and engagement types tend to fit. None of them describes past client work. Fumbar is a new company, and where a page needs an example it uses our clearly labeled fictional one: the Loamwick probe on the example project page.

If your product does not sit neatly in one row, that is normal. A soil sensor is both a climate product and an industrial one. A wearable can be a consumer product until it makes a medical claim. The first step is the same either way: request a firmware review. We read your schematics, current code, flash layout and update plan, and send back a written plan with the risks and the order of work.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.