We can work from your product requirements or an existing design. With a customer-led design, the discussion focuses on drawings, interfaces, manufacturing and verification. With joint development, we help define the hardware and turn the concept into a buildable product. The project agreement defines engineering responsibilities, deliverables, approvals and production scope so both teams understand what is included.

Yes. A description of the problem, a sketch or a reference product is enough to start a development discussion. Share the intended use, approximate dimensions, target quantity, budget and timing if known. We work through the requirements with you and identify the information needed for the next step. Detailed drawings and prototype work follow an agreed development scope.

Yes. A development project can focus on a cabinet, a module or its supporting electronics, as well as a complete LED product. Share the parts and interfaces that must remain compatible. We review the mechanical envelope, mounting, connections, power and control requirements together, then define the component supply, prototype work and validation needed for that particular development.

The development quantity and production quantity are considered separately. A prototype batch supports validation, while a production order must account for component purchasing, tooling, assembly and testing. Share your expected first order and repeat demand so we can assess a suitable approach. The quotation sets the quantities for each stage, together with the relevant pricing and supply assumptions.

NRE means non-recurring engineering: one-time work to develop your product, such as mechanical design, PCB adaptation or prototype validation. The quotation defines deliverables, included revisions and approval milestones. Samples, tooling and testing are itemised as included or separately charged. Production unit pricing is quoted separately. Any credit of NRE against future orders must be agreed in writing.

The schedule depends on the starting design, engineering scope, component availability, tooling and the number of sample revisions. A hub board adaptation and a new die-cast cabinet follow different development paths. We plan the milestones after reviewing your brief, including the time needed for your approvals and testing. Share the target launch date early so priorities can be assessed.

These terms are agreed for the individual development project. Identify any customer-owned drawings, pre-existing designs and requested deliverables before work begins. The agreement should specify the scope of file delivery, tooling ownership and storage, permitted use, and any exclusivity arrangements. Tell us about confidentiality requirements at the start so the information-sharing process can be agreed before detailed files are exchanged.

Agree the production drawings, component list, accepted sample, inspection criteria, quantity and delivery plan before releasing the production order. Prototype or pilot issues should be resolved against the agreed requirements. If a design or component changes later, review its effect on fit, performance, testing, cost and timing before proceeding. The approved configuration provides the reference for subsequent production discussions.