The work is hard enough. The tools shouldn’t be the part that breaks you.
It’s 10 p.m. on a Tuesday. Tomorrow’s session starts at 8:30 in the morning. Somewhere on a kitchen table, between a half-finished cup of tea and a pile of laminating sheets, a behavioural consultant is cutting out a new choice board for a client who decided the old one “doesn’t feel friendly anymore”. The character on the card needs to match the one from last week’s social story, except now he’s holding a toothbrush. There’s no version of that anywhere. No template. No shortcut. So she makes it again.
If you work in this field, you probably don’t need this scene explained. You’ve lived it yourself. Maybe last night. Maybe an hour ago.
We started Wheva because we kept watching this happen.
The work doesn’t fit the tools
The people doing this work like behavioural consultants, interventionists, speech and language pathologists, occupational therapists, and educators carry an enormous amount of responsibility.
Every client is different. Every routine matters. Every visual, social story, cue card, or schedule has to make sense for one specific person, on one specific day. But the tools were never really built for that reality.
Visuals live in one app. Notes live somewhere else. Goals are tracked in spreadsheets. Session plans sit in documents. Files get buried in shared drives and email threads. Teams spend their days jumping between tabs, rewriting the same information, and rebuilding materials that should already exist.
The cost of that fragmentation isn’t measured in software licenses. It’s measured in evenings, missed dinners, in exhaustion. In the quiet feeling that too much energy is being spent preparing for the work instead of doing the work itself.
The work is hard enough. The tools shouldn’t be the part that breaks you.
Wheva started at a kitchen table
Wheva didn’t begin in a strategy meeting or a startup incubator. It started because my partner, Aisling, is a behavioural consultant, and I kept watching her spend late evenings preparing for the next day.
Cutting and pasting visuals. Rewriting social stories. Organizing notes across paper documents and disconnected systems. Spending an hour making something that would only take five minutes if the right tools existed.
I’m a software engineer, so eventually I did what engineers tend to do: I built a small tool to help her generate social stories faster.
She used it immediately. Then the requests started growing:
- Could it make visuals too?
- Could the same character appear across multiple stories?
- Could the whole team access the same materials?
- Could I upload documents to keep them in one place?
Slowly, the idea became bigger than a single feature.
It became Wheva.
Built with clinicians, not just for them
One of the rules we followed from the beginning was simple:
If it creates friction for clinicians, we rethink it.
Aisling uses Wheva every day with her own clients and helps shape the product from a clinical perspective. That matters more than any feature list we could write.
Because the reality is: most tools in this space weren’t designed around how care teams actually work. Wheva was.
Today, Wheva helps teams create visuals and social stories with AI, organize client information, collaborate across providers, and track progress in one shared workspace.
You can describe a visual in plain language and generate it in seconds. You can keep the same familiar character across stories and routines. You can review session notes, goals, and documents without digging through folders or switching between tabs.
The goal was never to replace the human part of care. It was to give people more time and energy for it.
Technology should feel accessible
There’s a strange disconnect happening right now.
AI is advancing incredibly quickly, but many of the people who could benefit from it most still feel locked out of it. Not because they aren’t capable. Because they don’t have time.
Care teams don’t need another complicated tool to learn. They don’t need to become prompt engineers. They need something practical that fits naturally into the way sessions already run.
That’s what we’ve tried to build. Not AI for the sake of AI. Just tools that genuinely remove friction from the day.
Trust matters here
In this field, trust isn’t optional. Client information is deeply personal, and we strongly believe technology should treat it with the same level of care that clinicians do.
Wheva is built with role-based access, encrypted storage, and clear control over who can access what. We do not sell client data, and we do not use client records to train any external AI model.
Your clients’ information belongs to you. Always.
Why we’re sharing this
We’re still early. Wheva is growing every day alongside the clinicians and teams helping shape it. Some of our best ideas still come from conversations after sessions, late-night messages, or small frustrations someone mentions in passing.
But we wanted to share the story behind it because this product was never created in a vacuum. It came from real work, real exhaustion, and real people trying to do their best for the clients who depend on them.
If you’ve ever wanted to share your experience, feedback, or simply say hello, we’d love to hear from you at hello@wheva.com.
Cheers,
Rachid
Wheva is free to start.