Case Study: A Telehealth Site Built for Two Very Different Patients

Wismar Med is a telehealth practice serving patients across Georgia, founded by a board-certified preventive medicine physician. The brief was not “build us a website.” It was closer to: a patient who needs a prescription refilled and a patient looking into medical cannabis certification arrive with completely different questions, and one page cannot serve both.

The problem: one site, two patients who share nothing

The practice runs two service lines. Someone arrives needing a medication refill evaluation because they moved, or lost their primary care physician, or cannot get a timely appointment. Someone else arrives to ask whether they qualify for a Georgia medical cannabis certification. Those are different mindsets, different questions, and different anxieties.

The default agency answer is a single “Contact us” form and a services page listing both. That fails both patients. The refill patient wants to know how fast this can happen and whether it is legitimate. The certification patient wants to know whether they are even eligible before spending anything. A shared form asks both to self-translate their situation into a blank message box, which is exactly where people abandon.

What we built

Each service line got its own route through the site: its own explanation in plain language, its own eligibility framing, and its own path into booking. A visitor never has to work out which half of the site applies to them. The nav names the two services outright rather than hiding them under a generic “Services” dropdown.

Everything then hands off into the practice's secure client portal, where the actual clinical interaction happens. The website's job stops at the door of the portal, and knowing where that boundary sits mattered more than any visual decision on the project. A marketing site that tries to do clinical work is a liability; one that leaves patients unsure where to go is useless.

Bilingual English and Spanish, not a bolted-on translation

Georgia has a substantial Spanish-speaking population, and a telehealth practice that only speaks English to them is choosing not to serve them. The language switch sits in the header on every page. More importantly, the layout was built expecting Spanish copy to run longer than English, because it usually does. The common failure is a design locked to English line lengths that breaks the moment real translated copy arrives.

Speed, because healthcare traffic is mobile and impatient

People looking for medical help are often doing it on a phone, sometimes on a bad connection, frequently while stressed. We measured the live site at a 1.14 second largest contentful paint and a 541 millisecond full load across 211KB and 13 requests. Google's threshold for a “good” LCP is 2.5 seconds, so the site sits comfortably inside it with room to spare as the practice adds content.

What this case study does not tell you

It does not report the practice's booking volume, revenue, or conversion rate. We do not have permission to publish a client's business performance, and we would rather show you a smaller set of numbers you can verify than a larger set you cannot. Everything measured here comes from a public URL and can be re-run by anyone reading this.

That is a deliberate trade. Most of our work — government design systems, national portals, airport platforms — sits under NDA and produces case studies you have no way of checking. This one you can check in about thirty seconds.

Frequently asked questions