Six ways to work with us, each with a defined end
Each engagement has a stated scope, a list of what you provide and receive, and a clear way to end. Most start with a firmware review.
Key characteristics
- First step
- Firmware review
- Fixed scope
- Review, bring-up sprint, update pipeline setup, handover
- Milestones
- Product firmware build
- Ongoing
- Sustaining releases
- Prices
- Quoted in writing per engagement
Startups need different things from a firmware team at different moments. Before the first board spin you need someone to check the plan. When boards arrive you need them brought up fast. Before a pilot you need an update path you can trust, and after launch you need releases that keep coming. We package the work into six engagement types so you buy the one that fits now, and you always know how it ends.
All six follow the same method: one technical account lead, a written status every week, a release report after every release, and code that lives in your repository from the first day.
The six engagements compared
| Engagement | Fits when | Shape | You receive | It ends with |
|---|---|---|---|---|
| Firmware review | You are about to commit to a plan, a chip or a contractor | Fixed scope | A written plan with ranked risks | A walkthrough of the plan |
| Bring-up sprint | New boards have arrived | Fixed scope per board revision | Bring-up log, drivers, issue list | Every checklist item checked or listed open |
| Product firmware build | The board works and the product firmware does not exist yet | Milestones | Firmware, tests and release candidates in your repository | The agreed features passing the agreed tests |
| Update pipeline setup | Firmware exists but there is no safe way to update it | Fixed scope | Signing, bootloader, update agent, rollout plan, test evidence | A first staged rollout on your devices |
| Sustaining releases | Devices are in the field and need regular releases | Ongoing | Scheduled releases and release reports | Notice under the agreement, or a team handover |
| Team handover | You are hiring firmware engineers or ending outside help | Fixed scope | Documentation, recorded sessions, a supervised release | Your engineer shipping a release unaided |
Firmware review
When it fits. Before you commit to a microcontroller, a build plan or a contractor. When firmware exists but nobody on the team trusts it. When devices are about to ship, or already ship, without an update path.
What you provide. Schematics and the bill of materials, boards if they exist, read access to your repository, a description of how releases happen today, and your product goals and target markets.
What you receive. A written plan: what we found, risks ranked by consequence, a flash and update budget, a recommendation for the update path, the order of work, and a proposed next engagement with its scope.
How it ends. We walk you through the plan on a call and answer questions. The plan is yours to use with us, with another firm or with your own hires.
Bring-up sprint
When it fits. A new board revision has arrived, or boards power on but nothing else works reliably, and the firmware schedule depends on finding out why.
What you provide. Several boards of the same revision, schematics, layout files, the bill of materials, time with your hardware engineer and any vendor SDK you plan to use.
What you receive. A bring-up log with measurements and board serial numbers, drivers and board support code in your repository, a hardware issue list with evidence, rework notes, and a pin map and clock tree. The board bring-up checklist shows what gets checked.
How it ends. Every checklist item is either confirmed or listed as an open issue with an owner, and the log is delivered. The usual next step is a product firmware build.
Product firmware build
When it fits. The hardware works well enough to build on, and you need the firmware your product will ship with: sensing, the radio link, power management, the state machines and the tests.
What you provide. Requirements, or the time to write them with us (the firmware requirements worksheet is the format), one person who owns product decisions, hardware, repository access and a contact on your app or cloud team.
What you receive. Firmware in your repository, an architecture document, unit and hardware-in-the-loop tests running in CI, measured power figures and tagged release candidates.
How it ends. Each milestone ends with a release candidate and a test report. The build ends when the agreed features pass the agreed tests. An update pipeline setup often runs alongside it.
Update pipeline setup
When it fits. Your firmware works, written by us or by someone else, but there is no safe way to change it after it ships. The best time is before a pilot. The latest sensible time is before production.
What you provide. A choice of update service or server (or the budget to choose one), a decision on where the signing keys will live, test devices and access to the cloud account the updates will come from.
What you receive. A bootloader configuration and flash layout, image signing in CI with keys held in your account, the on-device update agent, a rollout plan with wave sizes and a halt rule, a key ceremony record, a release runbook, and test results for interrupted downloads, power loss during the swap, bad signatures, the wrong hardware revision and rollback. The over-the-air updates page describes the build.
How it ends. A first signed release goes through a staged rollout on your test devices or pilot fleet, with your team following the runbook.
Sustaining releases
When it fits. Devices are in the field, your team is small or focused elsewhere, and you need maintenance releases on a schedule rather than when someone finds the time.
What you provide. Priorities, release approvals, access to fleet data such as update results and battery readings, and a channel for support issues.
What you receive. Scheduled maintenance releases, a release report after each one, a dependency and vulnerability review log, and a plan for the next long-term support migration of your RTOS. Those clocks are real: the Zephyr Project maintains each LTS release for about five years, and the two-year support window for the FreeRTOS 202406 LTS libraries ended on June 30, 2026. See sustaining releases.
How it ends. With notice under the agreement, or with a team handover when you hire your own firmware engineers.
Team handover
When it fits. You are hiring your first firmware engineer, your team is taking over from us, or you are ending another arrangement and want the knowledge to stay.
What you provide. The engineers who will take over, and their time for walkthroughs and one release.
What you receive. An architecture overview, the release procedure from tag to signed image to rollout, hardware notes, a ranked list of open issues, recorded walkthrough sessions, and a check that every key and account is in your name. The handover checklist lists every item.
How it ends. Your engineer builds, signs and ships one release with us watching but not touching. Then the checklist is signed off and our access is removed from every system.
How the engagements fit together
A common path for a startup with prototype boards is review, then a bring-up sprint, then a product firmware build with update pipeline setup alongside, then sustaining releases until the first hire, then a team handover. A team that already has working firmware often goes from review straight to update pipeline setup. Some teams only need the review. The fictional example project follows one path from first board to handover.
How each engagement is agreed
We publish no prices, because the work depends on your boards, your code, your radios and your update path. After a first call or a firmware review, we send a written proposal with the scope, the deliverables, what we need from you, how the engagement ends and how changes are handled, with the price for that scope. Ownership and licensing of the work are set out in each agreement. To start, request a firmware review.
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.