How an electronics project runs
Every project starts with the task, not with a finished specification. We review what you need and what already exists, agree a paid first stage with defined deliverables, and decide the next step on the basis of its results. Development, redesign and troubleshooting follow the same principle but different engineering processes.
Confidential task? We sign an NDA before you share technical files.
Starting without a complete specification
Most projects begin with a partial picture: a list of functions, an existing board, a prototype that does not behave as expected, or a module that can no longer be bought. That is enough to start. The first conversation establishes what is known, what is missing and which engineering stage will close the gap.
Project stages
- Task description. You describe what needs to be developed, replaced or fixed and what result you expect.
- Initial technical review. We check whether the task fits our engineering scope and ask the questions needed to define it.
- Defined first stage. We propose a paid stage with its own result, for example a feasibility assessment, a design review, an analysis of an existing board or a first prototype.
- Commercial proposal. Scope, deliverables, verification method, timing and price of that stage are set out in writing.
- Engineering work in iterations. Design, prototypes, tests and revisions, each checked against the agreed requirements.
- Agreed result and handover. Deliverables are handed over in the format agreed in the project agreement.
The first paid stage
The first stage is a self-contained piece of engineering work with a result you can use even if the project stops there. Its findings show whether to continue into development, redesign or further testing, and make the estimate for the next stage more precise.
Iterations and changing requirements
Prototypes reveal things that requirements do not. When a test result or a new requirement changes the scope, we describe the change, its effect on deliverables, timing and cost, and agree it in writing before continuing.
Deliverables, files and rights
The list of deliverables is defined in the project agreement: for example schematics, PCB design files, BOM, manufacturing files, firmware, test procedures and test reports. Rights to deliverables are set out in the project agreement and our Terms of Service.
For firmware work, two results are different and are agreed separately: an extracted executable image of existing firmware, and new or migrated firmware delivered with its source code. Extracting an image does not recover the original source code.
Confidentiality and NDA
Client work is carried out under NDA. If your task involves confidential information, tell us before sending technical files and we will put an NDA in place first. Read more about project confidentiality and NDA.
Pricing
Development, recovery of design data and diagnostics differ too much in scope for a single price list. Each stage is quoted after its scope is defined, with deliverables and verification stated in the proposal.
Common questions
Do we need a complete specification to start?
No. A description of the task, the existing hardware or documentation and the result you expect is enough for the initial review. Defining the specification can itself be the first stage.
How do you price a project?
Each stage is priced separately after its scope is defined. You decide whether to continue after reviewing the result of each stage.
Do you sign an NDA before we send files?
Yes. Tell us that the task is confidential and we will agree an NDA before you share technical information.
Who owns the results?
Ownership and the list of deliverables are defined in the project agreement. Our general position is described in the Terms of Service.
Where are you located?
Micro Digital Engineering is based in Bucharest, Romania, and works with clients by email and online meetings.
Start with your requirements
Choose the situation closest to yours: developing a new device, replacing obsolete electronics or troubleshooting an existing design. Or describe the task directly.
Confidential task? We sign an NDA before you share technical files.