Case studies
Client names stay private. Scope and constraints are stated.
Each profile gives the control target, the delivery scope and the program length; figures are rounded to protect the client.
Europe · Hotel group
One remote for three TV generations and a cleaning schedule.
A hotel operator was replacing room remotes across a mixed estate. Some rooms had older IR televisions, others had newer BLE set-top boxes. Housekeeping used a daily wipe protocol that had already damaged the previous handset’s legends.
The brief was not “design a remote”. It was “stop the replacement cycle and stop the front-desk calls”.
North America · Control platform
A white-label handset with a pairing flow guests cannot break.
A control platform wanted its own handset for installers and end users. The hard requirement was recovery: a handset that lost its binding had to be restored in the room, without a service call or a laptop.
The platform team owned the protocol. We owned the board, firmware integration and the pairing sequence around their service.
Europe · Adjustable bed brand
Low-power control for a product used twice a day, for years.
An adjustable-bed brand had a working RF receiver and a handset that users found hard to read in bed. The new handset had to keep the receiver, improve the key feel and meet a battery target measured on a duty cycle, not estimated from a datasheet.
The existing enclosure tooling could not accommodate the larger keys, so the program included a new mold and two tooling rounds.
More programs
Shorter profiles from other environments.
These programs are shorter because less of the brief is public.
Two remotes into one
IR + BLE handset for a streaming device and the installed TV base. The program started with code coverage and ended with a 38-key map across three device groups.
Scope: code library, key map, certification support
Simplified control for residents
A care operator needed fewer keys, larger legends and a handset that staff could clean and replace quickly. The key map was reduced and the battery door was tooled for controlled access.
Scope: key-map research, sealing, replacement program
Rollout across mixed properties
A management group rolled out one handset across properties with different TV brands and languages. Configuration records were kept per property so spares matched the room.
Scope: batch configuration, language variants, spares
Confidentiality
What we can share.
Client names, exact model codes, volumes and prices stay with the client. What remains is the part a buyer can actually use: the control problem, the constraints and the delivery scope.
If a figure would identify a client, it is rounded or replaced with a range.
Reference calls are arranged with client consent during an active evaluation.
- Program approach and stage discipline
- How issues were found and resolved
- What the client’s team had to own
- Schedule reality versus the original plan
- Whether they would run the program again
Start a project
Your brief does not have to match one of these.
Most programs are a mix: one environment, one constraint we have not seen, and a launch date. That is a normal starting point.