Kind Health, Rebuilt for Where Benefits Is Going
The site is new. The bigger change is where employee benefits is heading, and the version of this work we think comes next.
Our new site is live. If you knew the old one, the redesign is the first thing you'll notice. But the reason we rebuilt it has almost nothing to do with how it looks. It has to do with where employee benefits is heading, and the version of this work we think comes next.
We'll start with what's changing, because the product only makes sense against it.
What's actually shifting in benefits
Three things have been true for a while, and they're finally colliding.
First, employers have more data about their health plan than ever, and it hasn't made the plan any clearer. A claims dashboard can tell you pharmacy spend went up. It can't tell you which contract term drove it, whether the program you added last year actually worked, or what to do about it before the next renewal. More reporting has not produced more understanding.
Second, the people accountable for the plan are under more scrutiny than they used to be. Employers are increasingly expected to govern healthcare spend the way they govern any other major expense, with evidence, decisions, owners, and outcomes they can point to. "We trusted our vendor" is wearing thin as an answer.
Third, employees quietly raised the bar. They expect a clear, specific answer to a benefits question the same way they get one from every other service in their life. Not a PDF. Not a callback in three days. An answer, now, about their plan.
There's a fourth force underneath all of it. Capable AI is now everywhere, which means generic benefits answers are about to be cheap and roughly worthless. What stays valuable is the current, governed context of a specific plan. The model is a capability anyone can buy. The plan's own record is the asset.
Put those together and you get a plan that is data-rich and understanding-poor, carried by a few experienced people, and experienced by employees one confusing question at a time. The industry doesn't lack systems. It lacks a shared record that connects what the plan says, how it's performing, what work is underway, and what people are actually living.
What we rebuilt Kind Health around
So the new Kind Health is organized around one idea. The employer health plan should have a single living record, and the people who run it should work from the same underlying truth.
That means four roles, one plan. The advisor works from the broadest strategic view and keeps the judgment. The service team keeps ownership and continuity, so the reason a decision was made travels with the work instead of leaving when someone does. The employer sees reviewed priorities, decisions, and outcomes, not every raw signal. And the employee gets clear, plan-specific guidance without ever touching the analysis behind it.
The redesign is really that argument made visible. When you and your advisor see the same plan, the conversation changes. When the employee's question and the employer's decision are drawn from the same record, the plan stops telling four different stories to four different audiences.
None of this replaces the systems already doing real work. Claims platforms should keep holding claims. Benefit administration should keep managing enrollment. What's been missing is the connective layer, the operating record that ties them together and remembers what the organization has learned about its own plan.
Kio is live today!
Kio answers employee benefits questions from the actual terms of their plan. Secure, specific, in plain language, without making anyone hunt through documents or wait for a callback. That's valuable on its own, and it's the piece employees feel first.
But Kio is not a chatbot sitting off to the side of the plan. It's the employee-facing edge of the broader record. Every question an employee asks also tells the plan something. A cluster of questions about the deductible is usually a communication gap. Repeated questions about one drug are usually vendor friction. A life-event rule people keep stumbling over may be technically correct and practically unusable. Answered once, those questions are support tickets. Seen as a pattern, with the right privacy and governance controls, they become some of the most honest intelligence a plan has about itself.
We built the employee experience first because that need is here right now. Everything after it connects the same plan truth into the advisor, service, and employer work around it.
Where this goes from here?
This is the direction we're building toward, with an advisor and employer beta coming in Q4. We're pressure-testing it with people who manage and advise on plans every day, because the model has to hold up in the real work, not just in a demo.
For now, the new site is the clearest version of the argument we've made yet. If you advise employer plans, lead benefits for an employer, or run the service work behind one, we'd genuinely like to know what resonates and what you'd push back on. The best version of this gets shaped by the people already doing the job.
Have a look at kindhealth.ai, and tell us what you think!