A working hospital doesn’t greet you with a brochure. It greets you with signs. Big ones. “Emergency.” “Admitting.” “Radiology.” Not because patients don’t deserve a story — because at the moment they walk in, a story would cost them time, and time is the one thing they don’t have.
We spent a decade inside clinical and operations environments before we built websites for a living. That experience changed what we think a homepage should do. Not inspire. Not explain. Direct.
Your homepage has about eight seconds before a visitor decides whether they’re in the right place. Eight seconds is less than an elevator pitch — it’s a hallway glance. If the first thing a visitor sees isn’t a clear answer to “what do you do, and can you help me?”, they leave. Not because your story is bad. Because they never got to it.
The triage framework
Here’s the framework we borrow from the hospital floor:
- Biggest sign first. Your H1 should answer the “what” in plain words. Not a tagline. Not a metaphor. A sentence a tired person understands.
- Next-step signage, always visible. One primary CTA. One secondary. No more.
- Proof in-line with the decision point. Testimonials next to the CTA, not buried on page 4.
- No waiting rooms. Cut anything the visitor has to wade through to find their answer.
The reason most small business homepages underperform isn’t design — it’s that they’ve confused “tell” with “show the way.” Clinical environments learn this the hard way: when signage fails, people get hurt. Online, the cost is quieter. Visitors don’t complain. They just don’t come back.
When we build a homepage, we open the file and imagine someone walking through a hospital door at 2 a.m. They’re tired. They’re stressed. They don’t want to scroll. What are the two or three things they need to find in under ten seconds?
That’s the homepage. Everything else is a side corridor. If you want to see how we structure website design and development around that same triage instinct, that’s where we lay out the process end-to-end.