Grow Therapy Innovation & Technology Culture

AI products in mental health vary widely — from conservative tools that operate in the background to fully automated therapy bots. At Grow, we take a more thoughtful and responsible path. Our focus is on support, not replacement. These tools are designed to enhance care, not deliver it alone.

How does innovation show up in your company culture?

At Grow, innovation starts with imagination — but it’s grounded in data, research and real-world outcomes.

Each year, we build our “concept car” — a bold, future-state prototype of where our product and experience should be 12 to 18 months from now. It’s not incremental. It’s intentionally boundary-pushing. We synthesize provider and client research, marketplace data, behavioral insights and category trends. Then we ask: If we were building this from scratch today, what would “best in the world” look like? Not just best in health tech, but the best, period.

That vision sets our strategy. We don’t want to be compared to other healthcare platforms; we hold ourselves to the standard of the most loved consumer brands.

Innovation also shows up in how we execute. Engineers shape strategy. Designers influence systems architecture. Product pushes for craft. We all shape strategy and outcomes. We challenge the status quo in how we build, not just what we build — constantly evolving our operating model to move faster, raise the bar and deliver experiences that feel modern, intuitive and trustworthy.

In healthcare, that kind of ambition matters. Access to care deserves nothing less.

What’s one recent innovation that improved user or employee experience?

One recent innovation I’m especially proud of is how we reimagined our marketplace experience.

Mental healthcare is deeply personal. Choosing a provider isn’t a transactional decision. We asked ourselves: How do we make it genuinely easy to book, while also honoring the human connection at the center of care? And how do we showcase providers in a way that reflects who they really are and not just a list of credentials?

We started with bold end-state concepts: What would it look like if finding a therapist felt as intuitive and confidence-building as the best consumer booking experiences? Then we worked backwards. Product, design and engineering partnered closely to bring that vision to life — elevating provider profiles, improving discovery and matching logic and streamlining the path to booking.

It’s an early step toward a much bigger vision for our marketplace, but it stands out because it lets us show, not tell, how Grow works: transparent, human-centered and built with intention.

How do you balance experimentation with stability?

Healthcare demands trust, so stability is non-negotiable. But standing still isn’t an option either.

We balance this by separating where we experiment from what must remain resilient. Core infrastructure and compliance-sensitive systems have high reliability standards, clear ownership and strong observability. Around that foundation, we create room for experimentation in defined surfaces: new matching logic, workflow optimizations, AI-assisted tooling and experience enhancements.

We also anchor experiments to outcomes. We’re not experimenting for novelty — we’re testing hypotheses tied to access, quality and provider efficiency. Small bets, fast feedback loops and clear success metrics.

The key is alignment. When teams understand the long-term vision and the quality bar, experimentation becomes easier. That allows us to move quickly without eroding the trust our providers and clients depend on.

How Grow Therapy Approaches Tech-Stack Upgrades:

"When we decide to adopt a new pattern or tool, the question is always whether it makes the next feature easier to build and safer to ship, not just whether it solves today’s problem."

What new technologies or frameworks are helping your teams move faster and build smarter?

The biggest shift for us has been treating AI as part of the engineering workflow. We are deep into a beta of background coding agents that open and land routine pull requests, paired with AI-assisted code review so engineers spend their time owning harder problems end to end instead of boilerplate. Underneath that, the quiet enabler is ephemeral preview environments: every pull request spins up a full, testable version of the app, which lets engineers and stakeholders validate changes in isolation before anything merges. We operate in mental healthcare, so the interesting problem was never whether AI can write code. It’s how we capture that speed without ever compromising the trust patients and providers put in us. Building for that constraint is what actually made us faster.

How do you balance experimentation with reliability in your development process?

For us, reliability is what earns the right to experiment. The agent rollout is the clearest case. Letting agents open and land pull requests is the bold part; the bar we held them to was throughput at the same or better quality, measured in fewer regressions, not just more pull requests landed. So we’re rolling out deliberately instead of all at once: started the beta with three teams, expanding to six now, going broader in quarter four, checking quality metrics at each step before widening access. That only works because the safety net came first: test coverage, preview environments, eval harnesses to measure agent output, AI-assisted review and above all the rule that whoever ships the code owns its quality and carries the pager for it. Change is the job here, so we’d rather run many small reversible experiments than a few big swings we can’t walk back.

What role does collaboration play in turning innovative ideas into products? 

In our domain no single function has the whole picture, so ideas that don’t cross functions tend to die. Coach, our AI support tool for mental health, is a good example. Clinically grounded AI between sessions only shipped because engineering, clinical experts and our safety and eval teams built it together from day one: clinicians defined what safe guidance looks like, engineers turned that into architecture, guardrails, eval systems that could measure it at scale and none of them could have shipped it alone. We run the internal work the same way. The agent beta went from three teams toward six because each cohort’s feedback changes what the next one gets, which is also how we caught issues early instead of at scale.