Most AI companies choose their problem based on market size, technical feasibility, or founder experience. The frameworks are rational. Find a large addressable market, build something technically differentiated, apply what you know.
iAVATARS was built around a different starting point. A question that one of our founders had been asking for over two decades before a product existed to answer it: what do you do with the silence that follows loss?
That question does not lead naturally to a TAM calculation. It leads to a hospital waiting room, an empty house, a phone you keep picking up before remembering there is no one to call. It leads to the specific, irreplaceable absence of one person, and the realisation that no existing technology was built to address that absence directly.
Grief is not a market segment. But the people who experience it are. Fifty-five million people lose a loved one every year. That number includes every demographic, every geography, every income level. What they share is not a consumer profile. It is a human experience that technology has never taken seriously as a design brief.
Building for grief is hard for reasons that go beyond the technical.
It requires understanding that the user is not in a neutral emotional state. That the bar for something feeling right is much higher than the bar for something being functional. That a generic, pleasant voice is not the same as the voice of someone specific and irreplaceable, and that a user who knows the difference will feel the gap immediately.
It requires building an AI engine that is not trying to impress anyone with its capabilities. iSoul 1.0 is not optimised to sound smart or to complete tasks efficiently. It is optimised to be recognisable. To sound like one person. To hold conversational memory in a way that feels like continuity rather than database retrieval.
It requires hardware, because grief does not live on a phone screen. It lives in rooms. In the spaces where someone used to be. A device that sits in a room and carries a presence into it is categorically different from an app you open when you feel like it.
Most companies will not build for this problem. It is too emotionally complex, too technically constrained, too far from the standard playbook. That is why the category is open. And that is why iAVATARS chose it.
The hardest problems are where the most lasting companies get built. We believe this is one of them.
Top comments (0)