Case Study
HerbaLink
The hard part was never search. It was making sure the person you found is real, in a category where being wrong lands on someone's health.
- AI-Assisted Product
- Healthcare
- Trust & Safety
- Solo Build
- Role
- Lead UX Designer & Developer
01
Anyone Can Claim Anything
This started as an idea. People go looking for a herbalist because of anxiety, or fatigue, or something their doctor hasn't been able to help with. Then they land in a swamp where anyone can claim anything. I wanted to know whether I could build the version that doesn't do that to them.
The job was never a bigger directory. It was making the safe path the easy one, in a category where getting it wrong lands on someone's health.
02
Verification Is a Door, Not a Sticker
Most directories let anyone list, then put a badge on whoever passed a check. I flipped it. Nobody is visible until they're verified against the American Herbalists Guild. Smaller catalogue, far more honest one.
I tested it the other way round. I added 200 unverified practitioners and the product got worse: every listing now needed a judgement call from the one person who came here because they couldn't make one.
03
What I Cut, and What Survived
A tester said the filter panel felt like WebMD, which is about the worst thing you can say about a health product. It's guided intake now: one focused question instead of a search box and two filter menus.
I also took out open-ended search entirely. Asking someone to describe what they need assumes they already know, and not knowing is the whole reason they're there.
The symptom diary is the one I got wrong twice. I built it full, daily logging and history and the lot, and people opened it twice and never came back. I cut it down to a single follow-up question, and what's left of it is the tracker that's still in the product. Building the big version first is how I found out nobody wanted it.
04
The Design System
There is no unverified state in this colour system because there are no unverified listings in the product. The palette ended up recording the verification decision as much as the code does.
05
Where It Actually Is
On hiatus, and I'll say why plainly. The product is built and it works: verification gate, guided intake, booking, herb library, the database and auth underneath all of it. The directory is empty because no herbalists have signed up yet.
That gap is an honest picture of what I'm good at and what I'm not. I can take an idea and come out the other end with a functional product on my own. Marketing it has always been the weaker half for me, and this is the clearest example I have: a platform that works, with nobody on it.
So this is here for the thinking, not as a win. The research, the decision to gate verification instead of badging it, the things I cut and what cutting them cost. If what you need is someone who can design the thing and then actually build it, this is what that looks like end to end.
Want something like this built?
I design and ship products end to end. Tell me what you're working on, or grab a time and we'll talk it through.