Discovery Sprint
Firmware Discovery Sprint
Two Weeks to Know What Your Device Takes to Build.
Send us your requirements, or just tell us what the device has to do and we write them. Your tech lead hands you a clickable prototype of the app or dashboard within 48 hours, then the MCU and RTOS choice, the connectivity and update path, the test rig and a build estimate you can take to your board.
What you get
- Clickable prototype. The app or dashboard your users will touch, within 48 hours of the first meeting, then adjusted with you during the two weeks.
- Device architecture. MCU and RTOS choice, connectivity, the OTA and secure-boot path, data flow to the cloud, and where certification cost lands.
- Test rig design. The hardware-in-the-loop (HIL) rig that will test every build on your real board: what it checks, the parts list and the cost. We build it in the project, and it stays with you.
- Build plan and estimate. Phases, team and timeline: what we build, what you keep in-house, what nobody should build yet.
The terms
- Value guarantee: if you don't see value in what the Sprint delivers, you get your money back.
- Sign a build or retainer within 30 days and the full fee comes off it. For anyone who builds with us, the Sprint was free.
- Your tech lead runs it from the first call.
- Prototype, documents and estimate are yours either way, even if our honest answer is that you should hire in-house.
For: Hardware founders with a device to build, or a firmware build that has stalled.
What you walk away with
- Something people can click. Within 48 hours your team, users and investors react to the app or dashboard, and we adjust the screens with you until they match what you have in mind.
- Hardware choices with the reasoning written down. MCU, RTOS, radios, OTA and secure boot, each with the option we rejected and why.
- A number you can take to your board. A build estimate by phase, including the test rig, with a fixed-price option once the scope is locked.
How the two weeks run
- Day 0. You send a requirements document under NDA, or you meet with us and explain what you need and we write the requirements. Your tech lead is on that first call.
- Within 48 hours. Clickable prototype in your hands.
- Weeks 1 and 2. We adjust the prototype screens with you until they match your vision, while the architecture, MCU and RTOS decisions get written down.
- End of week 2. Test rig design, build plan and estimate, then a readout call. You decide: build with us, hire, or stop.
A good fit
- Hardware founders with a device to build or a firmware build that has stalled, Seed to Series B.
- Connected products: sensors, gateways, monitoring devices with an app or dashboard.
- Teams about to hire a firmware engineer who want the plan before the first hire.
Not a fit
- Your boards are back from fab and need firmware now: start with a Board-Up Sprint.
- Safety-certified medical or automotive firmware: we scope that separately.
Our work
“Yes, they delivered what was needed in the time frame that was required.”
“ByteNaNa's programmers firmware skills are very strong and they are willing to go the extra mile to make it work.”
“The team at ByteNana is top tier. They always know how to accomplish whatever programming project I throw at them.”
Read the full client reviews →
Start a Firmware Discovery Sprint
Questions
Firmware Discovery Sprint: what teams ask first.
Do we need a requirements document?
No. Send one under NDA if you have it. If not, meet with us, explain what the device has to do, and we write the requirements.
Who does the work?
The tech lead who would run your build, from the first call to the readout.
What is the test rig?
A hardware-in-the-loop (HIL) bench wired to your real board that runs the tests on every firmware build. The sprint designs it; the build project makes it, and it stays with you when the project ends.
Can firmware be done remotely?
Most of it. Ship us a dev board and we work it with live debug sessions during your working day. When something needs hands, your hardware person runs the test while we drive, or one of us flies in: an overnight flight with no jet lag.
What if the answer is "don't build this yet"?
Then that is the result, written down with the reasoning.
Can we skip the sprint and go straight to a build?
Yes, on a monthly retainer. A fixed price needs a locked scope, and the sprint is how the scope gets locked.
Tell us what the device has to do.
A tech lead reads it and replies within one business day with what we would do first.
Other sprints
2 weeks · US$ 900
Software Discovery Sprint
A clickable prototype within 48 hours, then the architecture, the stack decision and a build estimate you can take to your board.
See it →2 weeks · US$ 2,800
Board-Up Sprint
Your board running a firmware base on a test rig you keep: drivers, connectivity, update path, and a punch list to pilot.
See it →2 weeks · US$ 3,600
CRA-Readiness Sprint
Your product classified, its threats modeled, every Annex I requirement checked on the device (secure boot, flash encryption, signed updates) and reporting ready.
See it →2 weeks · US$ 900
Maps Cost Reduction Sprint
Ranked strategies to cut your Google Maps or Mapbox bill, each with its monthly saving, and a fixed price to put them in.
See it →2 weeks · US$ 900
Cloud Cost Reduction Sprint
Ranked strategies to cut your cloud bill, from the device to the database, each with its monthly saving and a fixed price.
See it →2 weeks · US$ 900
App Rescue Sprint
Your AI-built app read end to end: critical risks flagged in 48 hours, a keep, fix or rebuild map, and a fixed price for the rescue.
See it →2 weeks · US$ 900
AI Automation Sprint
Your business rules mapped and a team of AI agents designed around them, with a fixed price to build it on the tools you already use.
See it →