You work directly with me, Clemens Elflein. We start with the next useful milestone for your device and make the scope, costs and expected results explicit before development begins.
What you receive
The deliverables depend on the work package. These examples give us a starting point for the proposal:
| Work package | Typical handover |
|---|---|
| Hardware and PCB design | Schematics, PCB layout, bill of materials, agreed manufacturing files, and notes from prototype bring-up. |
| Embedded firmware | Source code, build and programming instructions, interface documentation, and results of the agreed checks. |
| Flashing or functional test setup | The agreed fixture and software, programming and test sequence, operator instructions, and a definition of pass/fail criteria and result handling. |
| Investigation or technical review | Findings, remaining uncertainties, prioritized recommendations, and a proposed next development step. |
The proposal identifies which files, prototypes, fixtures and checks are included. It also states what you need to provide, such as existing designs, source access, representative hardware or bench instruments.
Scope, billing and changes
Before paid work starts, we agree the work package and its billing basis in writing. The proposal sets out the price or estimate, how additional effort is approved, and any separate costs for components, manufacturing or equipment. Share a budget constraint early so we can choose a useful scope around it.
If an investigation reveals more work, we discuss the findings, cost and timing before expanding the scope. A review, prototype revision and production release are separate decisions; you can commission the next step when its purpose is clear.
Milestones and progress
We define a concrete result for each milestone and how to review it. For a new board, that might be a design review before manufacture followed by a bring-up review. For firmware, it might be agreed device behavior demonstrated on representative hardware.
We agree the update schedule and identify dependencies at the start. Progress updates cover completed work, open questions and decisions needed from you. Hardware availability and outside manufacturing lead times are considered when setting dates.
Handover and use of the work
The handover includes the agreed editable files and the information needed to build, program or use them. We review the results against the agreed scope and document remaining limitations or open items.
Ownership and usage rights are set out in the proposal, including any pre-existing code, designs or third-party licenses. The public projects in my portfolio have their own licenses; they do not determine the terms of your commissioned work.
Confidential information
Start with a non-confidential overview of the device and the help you need. If the next step requires sensitive designs or source code, we clarify confidentiality arrangements and any NDA before exchanging those materials. Publication of customer work is something to agree separately.
After delivery
We define the handover review and any follow-up support in the proposal: what it covers, how to request help, and its duration and billing. Further features, additional hardware revisions and ongoing maintenance can be scoped as follow-on work.
Start with your current situation
Tell me what the device should do, what already exists and where you need support. I reply personally within one business day to clarify the fit, missing information and availability. The development schedule is agreed with the scope.
Discuss your project, or explore hardware design and embedded firmware development.