The pattern I kept seeing, across different employers and different EAP providers, was always the same. An employee reaches out. A form goes in. Someone from the EAP calls back, sometimes a day later, sometimes a week, sometimes three weeks later, to schedule an intake appointment. The intake appointment happens, and if everything goes well, the employee is connected with a counselor two to four weeks after they first asked for help.
That's the standard model. For many situations, the wait is survivable. For some situations, it isn't. And the standard model has no way to tell the difference.
What we kept noticing
The problem isn't that EAPs are bad. The counselors in these networks are generally excellent. The problem is that the intake process -- the part that happens before anyone actually sees a counselor -- doesn't do any triage. It collects demographic information, an insurance number, and a brief description of what brought you in. It doesn't assess urgency. It doesn't differentiate between someone who's struggling with work stress and wants to talk to someone in the next few weeks, and someone who's been having thoughts that concern them and needs to talk to someone today.
Both of them submit the same form. Both of them go into the same queue. Both of them wait the same amount of time.
The HR professionals managing these benefits often know this. They watch utilization numbers and worry about the people those numbers don't capture. They field calls from managers asking what to do when someone on their team seems to be struggling and isn't responding to the EAP referral. They know the system has gaps. They don't have a way to fix them that doesn't require a complete replacement of the EAP, which is a procurement project most benefits teams aren't set up to run.
What the timing problem actually costs
Three weeks is a long time in mental health. The person who submitted an intake form during a difficult moment may have stabilized, or may have gotten significantly worse, by the time the intake appointment arrives. Either way, the counselor who finally meets them is starting from a form description of a situation that may no longer match what's in the room.
There's a compounding problem: the experience of waiting teaches employees something about the benefit they're supposed to trust. A three-week wait communicates that the system doesn't know what you're dealing with, doesn't distinguish between cases, and isn't organized around helping you quickly. That's a lesson that stays with people. It affects whether they recommend the benefit to a colleague, whether they try again after a frustrating first experience, whether they tell their manager to refer someone they're worried about. The trust damage from the intake experience isn't measured in utilization data, but it's real.
What we decided to fix
We decided to build the layer that's missing: a structured, AI-assisted first contact that asks the right questions, makes a calibrated assessment of urgency, and routes accordingly. For someone in crisis, that means getting to a higher level of care immediately, not after a three-week wait. For someone who would benefit from a structured self-help program, that means routing there directly rather than into a therapist's intake queue they don't need.
The routing decision, made correctly, at first contact, with good information, is where most of the value in a mental health benefit actually lives. Not the sessions themselves, but the decision about what kind of session (or non-session) is appropriate. That decision is currently being made badly or not at all, and we built Lullgrove to make it well.
We're based in Portland. We're a small team: three people who've spent our careers at the intersection of behavioral health and employer benefits. We're not trying to replace therapy, EAPs, or the clinical workforce. We're trying to fix the middle part -- the gap between someone deciding they need help and the right help finding them. That part is broken, and it's fixable. We think it's worth fixing.
Why we chose employer benefits rather than direct-to-consumer
The direct-to-consumer mental health app market is crowded and, in our view, structurally limited. The people who need mental health support most are often the least likely to seek it out independently, download an app, pay a subscription, and build a habit around using it. Consumer mental health products tend to attract the moderately-anxious early adopters who would have figured something out with or without the app. They're less likely to reach the person who is genuinely struggling but who hasn't framed their situation as a "mental health problem" worth addressing.
Employer-provided benefits reach everyone in the company, including the people who wouldn't have sought out a mental health tool on their own. That's a different population with different needs and different barriers. It requires a different kind of first contact -- one that meets people where they are rather than assuming they've already decided they have a mental health need that requires addressing. That's the population we care about reaching, and the employer channel is where they are.
The practical consequence is that we've built something that works for the person who isn't sure they need support, not just the person who has already decided they do. The first question isn't "what brings you in" with an implicit assumption that you're here for clinical care. It's closer to "how are you doing" -- an opening that has a low barrier to honest engagement and that can route to anything from high-urgency care to a set of self-paced resources, depending on what the conversation reveals.
We're early. We're learning from every pilot. But the core of what we built -- triage at first contact, routing that matches presentation to level of care, privacy architecture that separates employee records from employer reporting -- that core was right from the beginning. The intake wait is a problem we know how to fix. We built Lullgrove to fix it.