Questions founders ask before hiring a firmware team
Straight answers to the questions that come up before a first firmware review, including the ones about money, ownership and what we will not promise.
Key characteristics
- Questions
- 13, in four groups
- Prices
- Quoted in writing per engagement
- Code
- In your repository from day one
- Signing keys
- Held by you
These are the questions we expect from founders, CTOs and first firmware hires before a first conversation. If yours is not here, write to hello@fumbar.com or use the contact page.
Cost and contracts
How do you charge if there are no prices on the site?
Every engagement is quoted in writing before work starts. A firmware review, a bring-up sprint, an update pipeline setup and a team handover are quoted for a fixed scope. A product firmware build is quoted milestone by milestone, and sustaining releases are an ongoing arrangement. The price depends on the hardware, the state of the code, the radios and the update path, which is why we do not publish one.
Who owns the firmware you write for us?
You receive the source code in your own repository from the first commit, along with the build instructions, the signing setup and the documentation. Ownership and licensing terms are set out in each signed agreement. Open-source components such as an RTOS or a bootloader keep their own licenses, and the software bill of materials for each release lists them.
Will you sign an NDA before we share details?
Yes. We can sign your NDA or send a mutual one before you share schematics, code or plans. Please do not put confidential material in the contact form; a short description of the device is enough to start.
Working together
Do you only work with startups in Denver?
No. Our office is in Denver, and we work remotely with startups anywhere in the US. You can ship boards to the office, and in the Denver area we can work at your site by arrangement. Because status is written down every week, most of the work does not depend on being in the same room. More on the Denver office page.
How long will our project take?
We do not promise durations before we have seen your hardware. The firmware review ends with the order of work and an estimate for each next step, based on your boards, your code and your launch date. Board revisions, radio test lab slots and decisions waiting on someone move schedules most. Our fictional example project shows one shape an engagement can take; it is an illustration, not a quote.
What does a firmware review deliver?
A written plan. We read your schematics, current code, flash layout and update plan, and you receive our findings, the risks ranked by what they would cost you, a flash and update budget, a recommendation for the update path, the order of work and a proposed next engagement. The review is short and fixed in scope, and the plan is yours to use with any team. See all engagement types.
Is Fumbar a new company?
Yes. Fumbar LLC filed its Articles of Organization in Colorado in November 2026 and has its office in Denver. We have no past projects to show you yet, so we show our method instead: the example project is fictional and labeled as such, and the free tools and checklists on this site are the ones we work from.
Technical
Which chips, operating systems and radios do you work with?
Microcontroller firmware in C and C++, and Rust where it fits, on Zephyr RTOS, FreeRTOS or bare metal, with MCUboot as our usual bootloader. Embedded Linux built with the Yocto Project or Buildroot. Radios include Bluetooth LE, Wi-Fi, LTE-M and NB-IoT cellular, Thread and Matter, and LoRaWAN. The microcontroller is your choice, for example a part from the STM32, nRF52 or ESP32 families, and the review checks whether it fits the product.
We already have firmware. Do you start over?
No. The review reads your code first, and the written plan says what to keep, what to fix and what to replace, with the reasons. Rewrites are expensive and usually unnecessary. If the missing piece is the update path, it can usually be added around the code you have, as long as the flash has room for two image slots. The flash budget calculator shows whether yours does.
Do we need over-the-air updates for a small pilot?
Usually, yes. A device that ships without a way to accept, verify and undo an update will never gain one, and a pilot is where you find the problems worth fixing. Even a small trial benefits from signed images, a second image slot and a rollout in small waves. See over-the-air updates.
Who holds the signing keys for our devices?
You do. Production signing keys are created in a signing service in your cloud account or in a hardware security module you own. They are never stored on laptops or in repositories, and we never hold the only copy, so you can sign releases without us. Details are on the security page.
Compliance and after handover
Can you get our device certified or make it compliant?
We do not certify products or declare them compliant. We help you prepare: the test firmware that radio test labs need, and evidence such as a signed update mechanism, a software bill of materials per release, a vulnerability handling process and a stated support period. Program status changes, so check dates with the regulator. As of November 2026 the FCC’s U.S. Cyber Trust Mark was not yet accepting product applications, and the main obligations of the EU Cyber Resilience Act apply from December 11, 2027. This is not legal advice. See firmware security.
What happens after handover?
Your team runs the releases. Before handover is signed off, your engineer builds, signs and ships one release with us watching, then our access is removed and shared credentials are rotated. After that you can ask questions during the follow-up period in your agreement, or move to sustaining releases. Existing clients reach us at support@fumbar.com.
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.
Or email sales@fumbar.com, or call (720) 675-4202.