How we work
Four steps. The first costs nothing. The last is your decision.
Thirty minutes, free. We talk through the board, the code and the change. Afterwards you receive a written scope: what will be done, how it will be verified, and what is out of scope.
The first task is quoted at a fixed price before work starts. You know the cost before you commit, and the estimate is our risk, not yours.
The change arrives with its record: the build, the native tests, the mutation score, the review and, when you need one, the bench results. The record also lists what is still open.
We deliver on a branch or as a patch. You read the change and its record, then merge it or ask for changes. Your main branch is yours.
The record
From case 1, a feature that checks every Bluetooth LE reply before the firmware uses it. Each line is evidence you can check in the public code.
< to <=), caught only by the sanitized runA test suite that passes proves little until it fails on broken code. We break the changed lines on purpose and count how many breaks the tests catch.
Every change goes through a review pass separate from the one that wrote it, checked against your request, before the engineer signs it off.
A change is only as proven as its weakest evidence. This one is proven on the host, not yet on the station, and the record says so.
Your code stays within the engagement. Before you share any of it, the written scope names every third-party service that will process it. If your code cannot leave your premises, or your contracts restrict where it may go, tell us on the call and we will say whether we can work within that.
A record is evidence for one change. It is not a guarantee that the rest of the firmware is free of faults.
Describe it in a free 30-minute call. You leave with a written scope, whether or not you hire us.