Consumer electronics & connected products
Wearables, audio, smart-home devices, companion apps, and useful everyday experiences.
PRODUCT DESIGN & SYSTEMS ENGINEERINGComplex products.
Complex products.
Engineered to work.
We develop integrated hardware and software, then verify the design against performance, reliability, usability, and manufacturing requirements.
Explore engineering capabilities ↘
THE SYSTEM IS THE PRODUCT
Structure. Sensing.
Signal. Software.
CONSUMER / MEDICAL / INDUSTRIAL / AEROSPACERequirements / Integration / Verification / Transfer
PRODUCT DEVELOPMENTProduct design and
Product design and
systems engineering
The enclosure, electronics, firmware, and user experience share one set of requirements.
Consumer electronics, medical devices, industrial instruments, robotics, drones, and microsatellites demand different kinds of engineering. We define the operating conditions, critical interfaces, and verification work before committing to a development architecture.
A product program brings those disciplines into a shared roadmap, with named responsibility for interfaces, reviewable design files, and evidence at each development gate.
ENGINEERING METHOD / ILLUSTRATIVE DOCUMENT STRUCTUREFrom a requirement
From a requirement
to a verification record
A requirement has a target, a verification method, and a record of the result. The thresholds and test conditions are defined for the actual product.
| Requirement | Acceptance definition | Verification approach | Evidence produced |
|---|---|---|---|
| Battery operating time | Runtime target and duty cycle agreed in the product brief | Measure current across operating modes; confirm with a runtime test | Power profile, calculation, and recorded test result |
| Recovery after connection loss | Fallback behavior and recovery conditions defined in the interface specification | Exercise disconnect, reconnect, restart, and failure cases | Test cases, device logs, and resolved defect records |
| Production test coverage | Critical functions testable before dispatch | Review fixture access and test coverage during pilot builds | Test procedure, coverage review, and pilot-build findings |
Example structure only. These are verification-planning examples, not completed tests or product performance claims.
ENGINEERING SCOPE / FROM REQUIREMENTS TO RELEASE
Engineering capabilities
A defined scope. Inspectable outputs.
A decision at every review.
The program is built around the product’s maturity, technical risks, commercial targets, and evidence requirements. Each workstream has an agreed owner, deliverables, and acceptance criteria. The first two scopes are open below; expand the remaining scopes for their outputs and review decisions.
01Systems architecture & feasibility
＋
Translate the product brief into measurable requirements. Allocate functions across mechanical, electronic, embedded, and software subsystems. Resolve architecture choices through focused experiments and explicit performance, power, cost, and risk budgets.
TYPICAL DELIVERABLES
- Requirements and interface definitions
- System architecture and technical budgets
- Feasibility evidence and development risk register
02Industrial design & mechanical engineering
＋
Develop the physical product around use, assembly, manufacturing, and service. Explore form and interaction alongside mechanisms, materials, tolerances, structural behavior, thermal paths, and environmental protection.
TYPICAL DELIVERABLES
- Design direction and appearance prototypes
- CAD assemblies, drawings and tolerance analysis
- Material, assembly and manufacturing recommendations
03Electronics, sensing & communications
＋
Define circuit architecture and component choices against signal quality, power, size, availability, and cost. Develop schematics and PCB layouts, integrate sensing and communications, and use board bring-up to characterize actual behavior.
TYPICAL DELIVERABLES
- Schematics, PCB layout and component BOM
- Bring-up records and measurement results
- Power, sensing and communications integration evidence
04Embedded software & connected systems
＋
Develop firmware, device drivers, control logic, and communication interfaces around the hardware architecture. Plan provisioning, update paths, failure recovery, and the application or service interfaces needed for the complete product.
TYPICAL DELIVERABLES
- Firmware source and build configuration
- Interface specifications and integration tests
- Provisioning, update and operations responsibilities
05Human factors, usability & product validation
＋
Map user workflows and the physical and digital interactions that matter. Evaluate prototypes with representative users. For medical programs, establish intended use, risk responsibilities, and qualified quality and regulatory support within the agreed scope.
TYPICAL DELIVERABLES
- User workflows and interaction specifications
- Usability study plans, findings and design actions
- Validation plan and responsibilities for required evidence
06Verification & manufacturing transfer
＋
Trace requirements to test methods and results. Prepare reliability and environmental testing, resolve design-for-manufacture and design-for-test needs, and support pilot builds and transfer to the agreed manufacturing partner.
TYPICAL DELIVERABLES
- Verification matrix, protocols and results
- Controlled BOM, drawings and production files
- Test access, fixtures, pilot-build findings and handoff package
AT EVERY REVIEW
What has changed. What has been demonstrated. What remains open. What the next investment will resolve.
SECTOR REQUIREMENTS
Industries we develop for
From everyday experiences to specialist systems.
The right disciplines for each challenge.
EVERYDAY TECHNOLOGY
Medical devices & scientific instruments
Connected care, diagnostic concepts, laboratory tools, usability, and defined evidence pathways.
Industrial products & robotics
Instrumentation, automation, mobile platforms, controls, and the tools people use to operate them.
Aerospace, microsatellites & remote systems
Drones, microsatellite concepts, floating stations, sensing, communications, and integrated platforms.
Inside the development work
A closer look at system decisions, design artifacts, and the evidence needed to advance. These are digital design and planning studies, with their scope and verification status stated explicitly.
AEROSPACE / SCIENTIFIC INSTRUMENTS
Living Loom
A contained biological experiment developed into an instrument architecture, editable CAD, and tested reference control logic.
Read the digital design study ↗CONNECTED DEVICES / BIOMETRICSContactless palm
A workplace-access concept with separate acquisition paths and a defined plan for security, usability, and privacy evaluation.
Read the pilot planning study ↗Development stages
Define the program.
Set requirements, intended use, target economics, scope, and the highest-priority technical risks.
Gate / Agreed brief & feasibility planProve the essentials.
Build focused experiments around the assumptions that could change the architecture.
Gate / Architecture supported by evidenceIntegrate and learn.
Develop the physical and digital layers together; test against defined requirements.
Gate / Requirements demonstrated in prototypesPrepare for reality.
Plan validation, production transfer, maintenance, and software evolution.
Gate / Documented release & transfer decisionHOW THE PROGRAM IS RUNProgram management
Program management
and handoff
Ownership across interfaces
Define who owns each subsystem, integration boundary, supplier relationship, and unresolved risk. Specialist partners are identified in the scope.
Design control and change review
Track design revisions, decisions, requirements, and test evidence. Review changes against schedule, cost, performance, and downstream impact.
Production and lifecycle planning
Consider tooling, component availability, test strategy, service access, software maintenance, and cost reduction while the design is evolving.
A defined transfer package
Agree source files, build instructions, drawings, BOMs, test records, IP terms, and support responsibilities before the handoff. Volume production sits with the selected manufacturer.
GET IN TOUCH
Discuss your project.
An initial conversation about feasibility, scope, and the next stage of development.
Tell us what you’re working on, where the project stands, and what you need help with. We’ll review your inquiry and get in touch to discuss a practical next step.
What we can cover
Your product and intended users
Technical feasibility and development risks
Scope, priorities, and a path forward