How a project runs

Five steps, the same every time. You always know what we're doing, what comes next, and what you'll have in your hands at the end of each step.

Step 1: Brief
You tell us what the device must do, where it will live and what constraints apply. The short form on our contact page is enough to start.
You get: Our questions back by email, or an honest no if it isn't a fit.
Step 2: Scope
We write down what we'll build, how we'll test it, what it costs and the milestones. Work starts only when you've agreed to it in writing.
You get: A written scope with test criteria, milestones and a price proposal.
Step 3: Build
We build in short increments and send bench notes as we go, so you see progress and problems while they're still cheap to fix.
You get: Access to the code as it grows, and regular bench notes.
Step 4: Test
We test against the criteria in the scope and record how each number was measured: the device, the conditions, the instrument and the date.
You get: A test report with methods, results, and what failed on the way.
Step 5: Hand over
Source, documentation and a walkthrough, so your team can build, flash and maintain the device without us in the room.
You get: A handover pack: source files, build steps, documentation and test results, as scoped.

Inputs, outputs and acceptance

What each step needs, produces and is accepted against
Step	We need	You receive	Accepted when
Brief	A short technical brief: the device or idea, the problem and any constraints.	Our questions back by email, or an honest no if it isn't a fit.	You confirm we have understood the problem.
Scope	Answers to our questions, and any existing design files or code.	A written scope with test criteria, milestones and a price proposal.	You agree the written scope, milestones and acceptance criteria.
Build	Decisions and access you owe us, by the dates in the scope.	Access to the code as it grows, and regular bench notes.	Each milestone is signed off against the scope.
Test	A build that meets the milestone, and the test criteria from the scope.	A test report with methods, results, and what failed on the way.	Results meet the written criteria, or the gaps are listed and agreed.
Hand over	Passing results and your agreement on the final deliverables.	A handover pack: source files, build steps, documentation and test results, as scoped.	You can build, flash and maintain the work using the handover pack.

Before work starts

When work ends

What do you deliver?: Depending on the project: editable schematics and PCB files, firmware and application source code, deployment instructions, technical documentation and test results. The exact list is agreed in a written scope before work begins.
Do you manufacture or assemble boards?: No. We design them. For PCB work we deliver digital output such as Gerber and drill files and a bill of materials, plus fabrication and assembly data when scoped, so a fabrication house of your choice can build them. “Manufacturing-ready files” means that digital output, not a manufacturing service.
How do you work with clients?: Remotely. We deliver designs, source files, integrations, documentation, advisory and remote testing assistance. We do not offer installation on site.
Who owns the work?: Access, ownership and handover terms are agreed in writing before work begins, and each engagement’s deliverables are subject to the agreed scope and test criteria.