Building and Handing Over a Workplace Safety Platform

Industry

Workplace Safety / Health Technology

Company size

1 - 10 Employees

About

"Their knowledge and passion really play a key role in turning our product into something we are proud of."

Trent Carney

Trent Carney

,

Co-Founder

Co-Founder

The Situation

MyCanary was built for a workplace safety context where health declarations, admin visibility, and location-aware workflows needed to work reliably in the real world. The platform combined a mobile app, an admin portal, and Bluetooth beacon integration so organisations could manage declaration flows and safety records without creating unnecessary friction for staff.

The use case was commercially acute: organisations needed tools that could support workplace safety processes during a period when health screening and operational accountability were front-of-mind. The product needed to be practical, fast to use, and operationally useful from day one.

Why they called us

Trent and Paul needed a delivery team that could translate the concept into a live product and then support the transition toward independent ownership. The technical work was not limited to app screens. It included the admin portal, beacon integration, deployment, operational support, and the eventual handover of platform control.

The engagement required a partner who could build the platform and then leave it in a state another team could understand, maintain, and evolve.

How we worked

The build produced a mobile app, admin portal, and Bluetooth beacon integration. Declaration flows were designed to be short and actionable. Notifications were clear. The admin portal gave administrators the information they needed without overwhelming them with unnecessary data.

The handover was managed carefully. A full handover document was prepared, covering all platform components, credentials, and operational procedures. The codebase was migrated to a GitHub account under the client’s control. AWS access was transferred, with credentials documented and MFA configurations handed over.

The app was removed from the App Store and Play Store at the client’s instruction, in anticipation of a platform evolution they were planning.

Trent engaged with the handover process constructively throughout. His primary post-handover challenge was finding a new technical partner — the expected outcome when the original delivery team transitions away. The handover documentation was designed to make that search as efficient as possible.

WHAT CHANGED

MyCanary went from concept to live platform — mobile app, admin portal, and Bluetooth beacon integration — and maintained operation through the transition from Halcrow to independent ownership.

The platform gave Trent and Paul a functional product to take to market during a window when the use case was commercially acute. The beacon integration, in particular, represented a capability that differentiated them from simpler health declaration tools.

WHY THIS WORKED

Workplace safety technology sits at the intersection of operational need, compliance, and user experience design. Organisations deploying safety tools are not tolerant of friction — if the tool makes the safety process harder than it needs to be, people route around it.

The team kept this front of mind throughout the build. Declaration flows were short. Notifications were clear and actionable. The admin portal gave administrators what they needed without overwhelming them with data.

Law 5: Earlier beats perfect. The platform launched with the features that mattered most to the use case. Bluetooth beacon integration was included because it was genuinely differentiating; features that did not directly serve the core declaration-and-record use case were not.

Get an honest second opinion on your AI or software development problems. Free.

Call with Sam