Define
Requirements, constraints, risks, and acceptance criteria.
Process
How a project runs
Development is managed through stage deliverables, issue lists, and acceptance criteria. Required changes are confirmed for impact before they enter scope.
03 / THE DELIVERY PATH
What each stage confirms
Each phase has agreed outputs and acceptance criteria. Changes are assessed before they become part of the scope.
Design
Circuit, PCB, BOM, and integration decisions.
Validate
Prototype testing, issue tracking, and revisions.
Pilot
Build preparation, test procedures, and first-article review.
Handover
Agreed files, revision records, and support boundaries.
Process
What each stage confirms
Stages are not identical for every project. The table below is an adjustable contractual framework.
| Stage | Main deliverables | Client confirmation / stage gate |
|---|---|---|
| Requirements and feasibility | Function list, interface, size and power constraints, architecture, risks, preliminary test plan | Requirement baseline, exclusions, and named decision-maker confirmed |
| Circuit and PCB | Schematic, PCB, BOM, design review, manufacturing requirements | Design review and board release approval for the specified revision |
| Prototype and integration | Agreed quantity of prototypes, firmware or interface integration where included, issue records | Functional test results and known limitations confirmed |
| Engineering validation | Agreed functional, power, and communications tests, with revision records | Pass against agreed conditions, or written acceptance of exceptions |
| Pilot preparation | Programming and test flow, fixture requirements, pilot data, defect handling | First-article and pilot results confirmed; approval to produce or rework |
| Delivery and transfer | Prototypes or batch units, agreed design source files, revisions, BOM, manufacturing and test documentation | Checklist acceptance and confirmation of maintenance and follow-up responsibility |
Gerber, BOM, and CPL/coordinate files are important for PCB/SMT manufacturing handover, but they are not equivalent to full product validation or proof of regulatory compliance.
How scope stays under control
Work outside the agreed baseline is recorded as a change with its impact, rather than absorbed silently. Acceptance is a written confirmation from a named decision-maker, not a unilateral assumption that a file delivery counts as approval.
Agreed separately
Mechanical enclosure, industrial design, tooling, app or cloud development, formal certification, third-party laboratories, shipping and duties, import responsibility, additional revisions, production tooling and fixtureing, and after-sales support. Firmware, RF, power safety, security, special environments, and safety-critical functions are assessed according to capability and specialist partner arrangements.
Not sure which fits?
Describe the problem and current stage. We will confirm the suitable engagement type before any work is scoped.