Engineering process
From Requirement to Functional Product
Every project follows the same eight stages, so you always know the current stage, the next decision and what is required from each side.
Timeline
Eight development stages
Horizontal on desktop, vertical on mobile — each stage highlights as you scroll through it.
Initial Enquiry
The client submits the requirement, problem statement, references, available files, expected quantity, timeline and intended application.
Discovery and Feasibility
Review technical feasibility, project risks, required engineering disciplines, material options, expected deliverables, testing requirements and potential limitations.
Scope and Proposal
Prepare a structured proposal covering deliverables, exclusions, estimated timeline, development stages, revision limits, payment milestones and quotation validity.
Design and Engineering
Develop mechanical concepts, CAD models, circuits, PCB layouts, embedded architecture, firmware logic, control systems and documentation as required.
Prototype Development
Manufacture or 3D print parts, assemble electronics, integrate firmware and produce the agreed functional or appearance prototype.
Testing and Iteration
Evaluate form, fit, function, electronics, reliability, usability and agreed test criteria. Refine the design using test results and client feedback.
Final Handover
Provide the approved deliverables according to the accepted quotation, including relevant files, prototype units, reports or documentation.
Production and Continued Support
Support further refinement, print-farm production, low-volume manufacturing, maintenance or a subsequent engineering phase when separately agreed.
Before we start
What clients should provide
The more of this you can share at enquiry stage, the more accurate the feasibility review and quotation will be.
- A written description of the problem and the intended application
- The current stage: idea, sketch, CAD model, schematic or existing prototype
- Any available files — CAD, mesh, drawings, schematics, datasheets or photographs
- Functional requirements: loads, environment, power, interfaces and expected life
- Expected quantity for prototype and any later production
- Target timeline, key dates and the reason behind them
- Constraints already fixed: components in hand, mounting points, enclosure size or standards
- The decision-maker and preferred contact method for approvals
Deliverables
Typical project deliverables
The exact deliverable set for your project is defined in the accepted quotation. Not every item below applies to every project.
- Concept notes and a recommended development approach
- 3D CAD models and, where agreed, 2D manufacturing drawings
- Circuit schematics and PCB layouts, where electronics are in scope
- Firmware or control logic for the agreed functionality
- Printed or fabricated mechanical parts
- An assembled functional or appearance prototype
- Test observations and revision notes against the agreed criteria
- Handover documentation, bill of materials or production files where included in the quotation
Pricing inputs
Factors affecting quotations
Engineering work is quoted per project. We do not publish automatic prices.
- Technical complexity and the number of engineering disciplines involved
- Design maturity of the information supplied at enquiry stage
- Material and component selection, and current availability
- Part size, geometry, tolerances and required finish
- Quantity — a single prototype versus a repeat batch
- Testing and validation requirements
- Number of revision cycles included
- Documentation and source-file deliverables requested
- Delivery timeline and any expedited handling
Revisions
How revisions are handled
- The number of included revision cycles is stated in the quotation before work begins.
- A revision is a change requested within the agreed scope, based on review or test results.
- Requests that change the requirement, add features or alter the deliverable set are treated as scope changes and are quoted separately.
- Feedback is consolidated per review round so that changes are applied in a controlled sequence.
- Revisions after final handover are handled as a new phase unless the quotation states otherwise.
Confidentiality and NDA discussion
Project information is handled on a need-to-know basis within the engineering team, and uploaded files are stored privately rather than published.
Confidentiality terms are not automatic. Sending an enquiry, an email or a file does not create an NDA. Formal confidentiality requires a written agreement signed by both parties, and we are happy to discuss one before detailed information is shared.
Read the full position on project confidentiality.
Intellectual property and source files
You retain rights to the designs, drawings and files you supply to us. Ownership of work created during the project — CAD models, schematics, layouts, firmware and documentation — is defined by the accepted written quotation or project agreement.
Source-file delivery is a separate deliverable. Native CAD, schematic and firmware source files are supplied only where the quotation states so explicitly.
Nothing on this page transfers ownership, licences or rights. See our terms.
Project timelines and quotations depend on technical complexity, material and component availability, revisions, testing requirements, quantity, and the completeness of information supplied.
Submitting an enquiry does not create a contract. Final scope, ownership, source files, revisions, pricing, timelines and deliverables are governed solely by the accepted written quotation or project agreement.
FAQ
Frequently asked process questions
Start Your Project
Send the requirement, any files you have and the intended application. We will review feasibility and respond with a structured scope.