Product Launch
Hardware & Electronic Engineering
Connected hardware, engineered from the inside out.
For teams developing a connected device, wearable or custom electronic product.
Contact us
The engagement
A clear scope. A useful outcome.
Take your electronic product from requirements to a working, testable design. We develop the architecture, electronics and embedded firmware together, with mechanical integration, testability and the production route considered from the start. An engagement can cover a first prototype, a board redesign or the engineering path towards production. Deliverables include design files, firmware, a bill of materials and the agreed validation evidence.
Capabilities
Schematic design and PCB layout
Multi-layer boards with controlled impedance, a deliberate power distribution network, and a grounding strategy settled before routing begins. Layout is reviewed against emissions, thermal behaviour and assembly reality, not only against connectivity.
Firmware and embedded software
Bare-metal and RTOS firmware in C and C++, with the bootloader, field update path and diagnostics designed in from the first commit instead of retrofitted after the first unit comes back from a customer.
RF and antenna design
Antenna placement, matching and tuning for BLE, Wi-Fi, LTE-M and sub-GHz links, characterised on the bench with a spectrum analyser and a near-field probe long before the design meets an accredited chamber.
Sensor integration and signal processing
Analogue front ends, filtering and calibration for weak signals, so a measurement stays trustworthy across temperature, supply variation and the units that sit at the far end of the production tolerance band.
Mechanical design and enclosures
Housings designed for the process that will make them: draft angles, wall thickness, fastening, sealing and tolerance stack-up resolved together with the electronics instead of negotiated around them once the board is frozen.
Design for manufacture
Panelisation, test point coverage, assembly sequence and component sourcing risk reviewed with the factory that will build it, so the first production run is not the first time anyone reads the design critically.

A practical starting point
Start with the question
you need to answer.
Bring an idea, an existing product or a technical constraint. We’ll discuss the scope, dependencies and right first milestone before planning the build.
Contact us ↗Project scope
| EDA tools | Altium Designer, SolidWorks, Fusion 360 |
|---|---|
| Firmware | C, C++, RTOS, bare metal |
| Wireless | BLE, Wi-Fi, LTE-M, sub-GHz, custom RF |
| Prototyping | Functional units in 6–10 weeks typical |
| Handover | Full design package, BOM, test fixtures |
Frequently asked questions
Can you take over a design someone else started?
Frequently. The first step is a paid audit: we read the schematic, the layout and the firmware, bring the existing hardware up on the bench, and report what is sound, what needs rework and what should be discarded. You receive that assessment as a written document with costs attached, and you are free to take it elsewhere.
How early should certification requirements affect the schematic?
From the first architecture review. Filtering, shielding, creepage distances, the radio module and the mains input all become expensive to change once layout is frozen, and most emissions failures trace back to decisions taken in that first week. We fix the target standards before component selection and design the board against them from the outset. The discipline costs about a week of analysis; skipping it costs a respin and the schedule around it.
Do you cover the mechanical side as well as the electronics?
Yes, and we prefer to. Board outline, connector position, thermal path and antenna keep-out are mechanical decisions as much as electrical ones, and splitting the two disciplines is what produces a board that will not fit its housing. Where you already have an industrial design partner, we work to their intent and flag early what physics will not allow.
What do we own at the end?
All of it. Source schematics, layout files, firmware source, mechanical CAD, the bill of materials with approved alternates, test fixture designs and the documentation a contract manufacturer needs. There is no licence back to us and no dependency on our tooling, so another engineering team can continue from the handover package without calling us.
How long until we have a working prototype in our hands?
Six to ten weeks is typical for a board of moderate complexity, assuming components are available and the requirements hold still. That covers architecture, schematic, layout, fabrication, assembly and bring-up. Long-lead parts and custom mechanics extend it, which is why sourcing risk is assessed in the first week rather than at the point of ordering.
Let’s make it happen


