DraughtMaster's real value wasn't the hardware on its own, it was what became visible once its data connected to Hopfolio, Carlsberg's platform for managing the draught beer business end to end. Pressure, temperature and volume readings only mattered if they turned into something a client could act on: no stock surprises, consistent quality, maintenance handled before it became a problem. The challenge was designing a system that made sensor data legible at both the device level and the business level.

I designed both sides of the experience, the operator-facing device interface and how that data surfaced inside Hopfolio. Raw readings weren't the goal, clear action was. That meant turning pressure and temperature data into maintenance alerts before something failed, and connecting quality data to the stock visibility clients needed to run their business with confidence. It was a full stack problem: hardware signal, service visibility and business data all had to resolve into one coherent picture.

- Piloted with real operators, and the feedback validated a specific design bet: this audience is beer-expert enough to want detailed quality metrics, not a simplified summary. Pilot users responded well to the depth, not despite it.

- Alerts around pressure and pipe cleaning addressed a real, everyday gap, operators said these were easy tasks to forget, and having the system flag them meant staying on top of maintenance without relying on memory.

- The pilot was still running when I left Carlsberg, so this reflects validated direction and early real world feedback, not a full launch. The core hypothesis, that connecting device data to Hopfolio would make quality and maintenance visible rather than reactive, held up in practice with the people actually using it.