By OBI IGBOKWE When we set out to build WellNewMe, the temptation was to call it a “wellness platform” and leave it there. Everyone nods along to the idea that healthier employees are more productive employees. But somewhere in the early build, we made a decision that has shaped everything since: WellNewMe would not be a wellness app.
It would be a workforce health-risk intelligence platform, closer in spirit to a credit reference agency than to a fitness tracker. That distinction matters more than it might sound. A wellness app tells an individual how many steps they took.
A risk-intelligence platform tells an employer, a broker, or an insurer something they can actually act on: where risk is concentrated in a workforce, how it is trending, and what it means for underwriting, benefits design, and cost. That is a fundamentally different product, aimed at a fundamentally different set of buyers, and it has taken real discipline to keep the platform pointed in that direction rather than drifting back toward the more familiar, more crowded “wellness” category. Four users, one platform One of the harder architectural lessons has been that workforce risk intelligence is not a single-user problem.
WellNewMe serves four distinct constituencies – employees, employers and HR teams, brokers, and insurers – each of whom needs a different view of the same underlying data. An employee needs a personal risk picture they can trust and act on. An HR director needs an aggregated, anonymised view of organisational risk.
A broker needs renewal-pipeline intelligence. An insurer needs a portfolio-level heat map and company risk profiles they can underwrite against. Building all four portals properly, on a shared data foundation, across more than eleven assessment domains, has meant resisting the urge to over-engineer.
Some features we designed, including parts of the original quote-management workflow, were deliberately simplified once it became clear they were adding complexity without adding decision value. Knowing what to defer has turned out to be as important as knowing what to build. Data sensitivity is not optional Because the platform touches health data, we have had to be unusually careful about what we ask for and how we frame it.
Summary from source