Owning a proprietary infrastructure layer in AI right now is closer to owning a diamond mine than owning a piece of software, yet most mental health apps still choose to live inside the wrapper pool rather than build their own. That observation comes from years spent building at the intersection of artificial intelligence, behavioral psychology, and neuroscience, evaluating every frontier AI model available, both general-purpose and mental-health-specific, until I could predict a model’s character well enough to trace a product’s cadence back to whatever sits underneath it. Within that pool, most products sit at the intersection of two things: a static CBT script that gets served to every user regardless of their history, and a handoff point to a live human therapist once the script runs out of road. Even the tools that insist they are not wrappers tend to implicitly assume what I call the fingerprint model, where fixed inputs like keywords and sentiment scores get mapped onto fixed emotional categories, and a general-purpose model then generates a fixed-style response from that category. This architecture can feel novel to a first-time user, particularly to someone less familiar with AI products, but the novelty tends to wear off within days, because the user begins to predict what the tool is going to say before it says it, and the conversation starts to feel like a loop rather than a relationship. What follows is a familiar cycle for builders in this space: engagement drops, retention weakens, and the customer acquisition cost that brought the user in stops being justified by a lifetime value that never materializes.
This is also where the most common objection in the AI mental health care space comes from: the question of what a given app is doing that Claude or ChatGPT is not already doing for free. It is a fair question on the surface, but it misses what those general models are actually built to do. Claude and ChatGPT can validate a user in the moment, and depending on how a given model generation gets tuned, that validation can swing in either direction, from over-affirming everything a user says to becoming distant and combative. The sustained scale of online mental health communities suggests that accessible conversational AI has not eliminated the need for ongoing emotional support.
r/depression draws roughly 203,000 weekly visitors. r/SuicideWatch draws around 101,000 weekly visitors. r/mentalhealth draws around 271,000 weekly visitors, with a large share of that volume made up of posts describing unmet mental health care needs and people asking for help they aren’t finding elsewhere. There is a real difference between a tired person typing “today sucks and I’m exhausted” and someone with clinical depression typing the exact same sentence, and a model built on the fingerprint assumption has no architectural way of telling the two apart.
Granularity as a core computing metric
Barrett’s research points to a concept called emotional granularity, which is the degree to which a person can accurately distinguish between their own internal states rather than lumping them together under broad labels. A person with high granularity can tell the difference between anxious and disappointed and ashamed, because each of those states carries a distinct physical signature for that individual, while a person with low granularity uses words like anxious and depressed interchangeably because they are not accurately reading the cues their own body is giving them. The mistake most AI mental health tools make is assuming the opposite direction of this problem, treating emotion as though it has a fixed fingerprint that is the same across every user, rather than recognizing that granularity itself varies by person and has to be learned about that person over time. Once you accept that variation is the norm rather than the exception, a fixed classification schema stops being a reasonable design choice, because it is built to recognize a fingerprint that does not actually exist.
Real physician voices, twice a week
Free, and one click to unsubscribe.
We engineered Wolfe’s architecture from day one to codify this reality, treating population-level variation as a foundational starting condition rather than an edge case. In practice, this ruled out generic, static inference entirely. Because emotional granularity is hyper-individualized, a wrapper built on a foundation model lacks the coordinate system required to interpret a specific user’s inputs accurately; what is required instead is an evolving model of how that individual expresses shifts in their own state.
Renting intelligence versus owning the stack
This is where the wrapper model breaks down structurally rather than just competitively. Many wrapper-first architectures remain largely stateless at the inference layer, treating each interaction as an independent prediction. While they can layer memory systems around a foundation model, the prediction engine itself has no native understanding of an individual’s evolving longitudinal state. Instead, prior conversations must be repeatedly reconstructed through expanding context windows or external retrieval, an approach that becomes increasingly brittle as histories grow. As a result, maintaining a rolling model of a user’s historical patterns, computing meaningful deviations from that baseline, and continuously refining predictions over time requires an owned state and inference layer beyond prompt orchestration alone. Those capabilities are architectural, not prompt-level. A capability rented per call can be switched off, repriced, or duplicated by any competitor renting the same call. An owned infrastructure layer compounds instead, becoming more valuable as it learns from every interaction.
I strongly believe this is a matter of ambition, not just architecture. A person in a mental health crisis needs to be treated with the same urgency and infrastructural seriousness as a patient walking into a clinic, not with the soft, wellness-first framing that most of this category has settled into. Amazon did not remain a bookstore after its launch simply because a bookstore was the first viable use of e-commerce; it used that starting point to build the supply chain, logistics, and infrastructure that eventually supported everything else, and that is the scale of ambition mental health technology needs right now rather than another app that treats itself as a one-stop wellness shop. Building that requires starting from the assumption that the problem is global, multidimensional, and different for every person and every culture, and a system that responds to every user in the same way is not just a weaker product but a careless one for the population it claims to serve. This is why Wolfe’s architecture is built as a coordinated network of systems that track and compute shifts in an individual’s linguistic and emotional baseline over time. The theory is not a slide in a deck justifying a technical decision after the fact; it is the reason the architecture exists.
The scale of ambition: beyond the wellness app
The commercial reality of this distinction is that it completely redefines how a company in this space survives. Because the performance gap between frontier foundation models shrinks toward zero with every major AI lab release, any product relying on rented intelligence is trapped on a commoditization treadmill. The true defensibility belongs to the architecture that maps individual pattern trajectories over time, creating an unreplicable, compounding predictive accuracy that a competitor cannot shortcut simply by deploying a newer model or a sharper prompt. That is the fundamental divide between a point-solution app chasing a fleeting wellness trend, and an enterprise built to become the core infrastructure layer that the rest of this category will eventually have to run on top of.
This essay is cited in the KevinMD record on mental health.
Ronke Lawal is the founder of Wolfe, an AI-native mental health infrastructure that combines neuroscience, behavioral psychology, and safety-focused AI to eliminate clinical blind spots in global mental health care. Her career spans Bain and Company’s social impact and private equity practices and finance leadership at technology startups, a three-year arc that revealed what she identifies as a $20 billion failure in digital mental health: cultural incompetence at scale.
As the architect behind Wolfe’s clinical intelligence, Lawal builds clinically intelligent systems that integrate neuroadaptive signal processing with therapeutic architectures, designed to detect clinical risk and intervene on trauma before the cascade reaches crisis. She is focused on solving what she calls “algorithmic malpractice” in mental health care: the industry’s willingness to deploy AI that engages vulnerable populations without the clinical intelligence to do no harm.
An MBA graduate of the University of Notre Dame, Lawal writes on AI, neuroscience, behavioral psychology, and health care equity, dedicated to wielding AI to reduce human suffering and save lives. Her work is cataloged on ORCID and Zenodo, and she shares updates on LinkedIn.