The waiting room starts on the homepage.
Taking a private-practice therapist from zero online presence to a live site built to earn trust before it asks anything of an anxious visitor.
Scroll to begin ↓"The hardest thing to design isn't a layout. It's the moment a hesitant person decides whether to reach out, or close the tab."
The Problem
My client, a solo private-practice therapist, had no website at all. Every new patient came through word of mouth, and there was nowhere online for someone to learn what she treated, decide if she was a fit, or figure out how to reach her.
That gap mattered more than a typical small-business site problem. The people landing on a therapist's site for the first time are often anxious, hesitant, or in crisis. They aren't comparison-shopping a service so much as deciding whether to trust someone with something difficult. So the site needed to earn trust before it asked for anything.
Research & Discovery
This wasn't formal user research, and I want to be upfront about that rather than dress it up. There was no patient interviewing, no survey, no analytics to mine, because the practice had no digital footprint yet, so there was nothing to measure. What I had instead was direct, recurring access to the one person who understood the audience best: my client herself.
We met weekly over Zoom for the life of the project. It wasn't a single intake call but an ongoing brainstorming cadence. Each session, I brought design questions and rough direction, and she brought her read on what mattered to the people who'd be landing on this site, drawn from years of sitting across from them.
That input was real, but it was limited in a specific way: it was her general impressions of patients, not documented patient feedback. I treated it as informed stakeholder discovery rather than a substitute for talking to users directly, and that distinction shaped how much weight I put on any one opinion versus my own judgment as the designer.
Define & Ideate
One disagreement defined this phase. My client's instinct, based on her sense of her patients, was that a hesitant visitor needed to see her services first. I saw it differently. Someone arriving anxious isn't ready to process a clinical list in the first five seconds; they're scanning for an emotional signal first, something closer to does this feel safe?
"Show services first, what I treat, who I work with. That answers 'is this person right for me?' fast."
Lead with tone and trust, and let services follow once the emotional bar is cleared. One click away, not page one.
Trust before information, for an audience whose primary barrier isn't confusion, but hesitation.
Design Decisions
There are no wireframes to show here, and I want to be direct about why. Given the scope, four pages, one stakeholder, a fixed builder platform, and the weekly live-feedback cadence, I designed directly inside the GoDaddy builder and iterated with my client in real time on calls rather than presenting static mockups first. That's a faster loop for a project this size, but it's a different, lower-fidelity process than a wireframe-to-final-UI progression, and I'm not going to manufacture wireframes after the fact just to make it look like one.
Information architecture
Four pages, deliberately minimal: Home, About, Services, Contact. Anything more would have added decision fatigue for a visitor who is already hesitant. Every page carries one clear next action toward Services or Contact, never two competing calls to action on the same screen.
Visual tone
The calming blue palette and typography were chosen specifically to read as low-stimulation, the opposite of a clinical or corporate feel. This was the most deliberate lever I had to support the trust-before-information decision above: the page has to feel safe before it says anything.
Resolving the stakeholder tension
Rather than picking a side and dropping it, I kept her instinct intact. Services information stayed complete and easy to find, but I moved it a layer deeper than page one. That way, an anxious visitor isn't confronted with a clinical list before they're ready, and a visitor who is ready can still find exactly what she treats in one click.
Results & Reflection
I don't have a measured outcome for this project. No inquiry counts, no booking data, no follow-up survey. What I have is that the site shipped, has been live since spring 2025, and my client is still using it as her practice's primary online presence. I'd rather flag that limitation directly than imply a result I can't back up.
What I'd do differently: ask her to gather patient feedback, even informally, with a quick question like "how did you find us, and what almost stopped you from reaching out," instead of relying on her general impressions. That single change would turn a stakeholder opinion into real evidence, and it would tell me whether the trust-before-services bet paid off, instead of leaving it as a decision I still believe in but can't prove.