Amplify
A product initiative developed inside Global Health Solutions. The work ran from a refresh of the parent brand and its marketing website through the product's own identity, its member and employer interfaces, and into early React Native implementation.
A service business with no product to stand on
Global Health Solutions delivered biometric screening and onsite wellness services to employers. The results landed as reports, and the relationship with the employee ended there — nothing carried the insight forward into behaviour, and nothing gave the employer a picture of what their program was doing.
The original concept was a basic wellness offering. Our work was to evolve it into a personalized, intelligent employee health experience: something worth opening more than once a year, with benefits, services and rewards attached to it.
The work started at the company, not the product
Before the product experience expanded, I helped evolve how Global Health Solutions presented itself — refreshing the brand and rebuilding the marketing website so the company had a clearer, more cohesive foundation for the work it was already doing.
That foundation mattered later: when Amplify needed its own identity, it had something credible to sit next to rather than start from.
Amplify emerged inside Global Health Solutions
The concept began as a fairly conventional employee wellness offering. As it evolved toward a personalized, AI-assisted health and benefits experience, it outgrew what the parent brand alone could carry.
Amplify needed to read as its own product without cutting itself off from the credibility of the company behind it. That constraint shaped both the identity and the interface work that followed.
Its own voice, borrowed credibility
I established the product's visual identity and applied it across presentation material and the digital experience.
Vision, brand and system — then enough code to make it real
Insight, then a next step
Participation, aggregated
One vocabulary across two products
The employee app and the employer console share one type scale, one spacing rhythm and one component library, so a change to a card or a form field lands in both. The system was documented alongside the screens rather than after them.
Designed against the build, not beside it
My involvement did not stop at static design. I began translating the product into React Native, which meant the design decisions were made with implementation constraints already in view rather than discovered afterward.
Navigation, the reusable foundations and a set of early screens ran on placeholder data. Working in both places kept the visual system close to the thing actually being built, and kept the handoff short.
Delivered: a brand, a product system and a running front end
The initiative was paused before backend development, when funding for the next phase did not materialize. What exists is the parent brand refresh and marketing site, the Amplify identity, the product direction, the design system and high-fidelity screens across both audiences, plus a React Native front end running on placeholder data. The AI capabilities are product direction, not shipped functionality.