Skip to content

Custom website design

A practice website that explains your care and books the visit

Most practice sites are brochures. This one is infrastructure: it answers the questions patients arrive with, opens fast on a phone, works for everyone, and hands every booking to PulseTrack so you can see what produced it.

Included in every plan · You own the site and the domain

Book a visit

New patients welcome

Care explained, before you call

Book a visit

Conditions

Visits

Insurance

Hours · Location · New patients

Illustrative
Illustrative composition, drawn in our own materials: care explained up top, one way to book, the three facts patients check kept in sight. No practice name, no stock photography.
  • WCAG 2.1 AA
  • Core Web Vitals
  • Hand coded, no page builder
  • Schema.org on every page
  • You own the code and the domain
  • Measured before and after
  • WCAG 2.1 AA
  • Core Web Vitals
  • Hand coded, no page builder
  • Schema.org on every page
  • You own the code and the domain
  • Measured before and after
  • WCAG 2.1 AA
  • Core Web Vitals
  • Hand coded, no page builder
  • Schema.org on every page
  • You own the code and the domain
  • Measured before and after

The mechanism

Most sites wait. Yours books.

A practice site has one job: help the next patient choose you and book. Four properties do most of that work, and each one is a build decision rather than a matter of taste.

  • 01 of 04

    Clarity

    One question answered per screen

    Patients arrive with three questions: do you treat this, do you take my insurance, how do I book. The structure answers them in that order on every page, so nobody has to call the front desk to find out.

  • 02 of 04

    Speed

    Core Web Vitals, tested on throttled connections

    Patients look you up on phones, in parking lots and waiting rooms. A page that appears at once gets read; one that lags gets closed. We build to Core Web Vitals, Google’s public speed thresholds, and we test on slowed connections that match real phones rather than lab conditions.

  • 03 of 04

    Accessibility

    WCAG 2.1 AA, treated as a build gate

    Your patients include older eyes, low vision, tremor, and screen readers. A site everyone can use is basic respect for the people you treat, so we hold every page to the AA accessibility standard and verify it before launch, not after a complaint.

  • 04 of 04

    Machine-readability

    Structured data on every page

    Before patients call, they ask Google, and increasingly they ask AI assistants. Structured data describes your services, your locations, and your answers in a format machines parse reliably. Invisible to patients, load-bearing underneath.

What ships

What ships with every build

Six commitments in plain English. They are not options to select; every one ships in every build, on every plan.
  • 6commitments in every build

    Not options to select. Every one ships on every plan.

  • 2.1the WCAG version we build to

    Level A and AA, the version the federal rules point at.

  • 3core web vitals measured

    Loading, responsiveness, and visual stability, on a throttled connection.

  • 0accessibility failures allowed

    Pages do not ship failing the check. You get what we tested and what we found, dated.

  • Drawn for your practice

    Never a template. Layout, art, and palette start from your actual practice and specialty, which is why no two sites we ship look alike.

  • Written for patients

    Every page in the words patients actually use, not clinical shorthand. You review each sentence for clinical accuracy before it publishes.

  • Measured before and after

    The morning we launch, we speed test your old site and the new one on the same connection, and you get both numbers side by side.

  • Usable by everyone

    Contrast, keyboard, and screen reader support built to the AA accessibility standard, verified on every page before launch.

  • Readable by machines

    Structured data on every page, so search engines and AI assistants can read what you treat and where you are, and have something worth citing.

  • A monthly page you can read

    One page a month in plain English: what changed, what it did, what we do next. Numbers explained, never dumped.

The engagement

The build, phase by phase

Four phases, each ending in something you can see and a term you can hold us to.

  1. Design

    Art direction from your practice: a palette drawn from your brand, drawn scenes instead of stock photos, every section composed on purpose.

    Revision rounds until it reads like your practice. Two rounds is typical.

  2. Build

    The approved design becomes a fast, accessible site, hand coded on a modern framework rather than assembled in a page builder.

    Progress visible on a private staging link from the first week.

  3. Content

    We write every page for patients and about your care, structured for search engines and AI assistants as we go.

    Nothing publishes without your clinical sign-off.

  4. Launch

    Redirects from every old address, profiles pointed at the new site, and the same morning speed test of old against new.

    You own the site, the code, and the domain, documented in the handover.

Kickoff

Live

  1. Design

  2. Build

  3. Content

  4. Launch

No phase starts until you have signed off the one before.

We do not quote one day count for every practice, because scope differs. Your schedule is agreed in writing at kickoff; the typical range is in the questions below.

Measured

Every build wires into PulseTrack

A site that cannot show its work is a brochure with better typography.

The measurement platform, in every package. Every inquiry, click, and booking, measured plainly.

From launch day, calls and bookings carry the page that produced them, so the site’s contribution stops being a matter of opinion.

PulseTrack · attribution

Illustrative

  1. Page read

    Knee replacement, non-surgical options

    Organic search · mobile

  2. Request sent

    New patient appointment request

    From the form on the page above

  3. Visit booked

    New patient consult, Thu 9:40 am

    Attributed to the page above

Outside the record

The match is to the page and the source, never to the contents of a message.

Attribution needs a source and an outcome. It does not need a person.

Standards

Named standards, named stack

Fast and accessible are claims anyone can type. Every standard we build to has a name you can look up, and a way to check we met it.
Accessibility
WCAG 2.1 AA
The public standard for contrast, keyboard use, and screen readers, and the version the federal rules point at. Verified on every page before launch. We build to the newer 2.2 criteria as well, and claim conformance at 2.1.
Performance
Core Web Vitals
Google’s published thresholds for loading, stability, and responsiveness. Measured on throttled connections, before and after launch.
Framework
Next.js 14 + TypeScript
A modern application framework, hand coded and strictly typed. Not a theme, not a page builder.
Structure
Schema.org on every page
Structured data describing your practice, services, and answers, in the format search engines and AI assistants read.

Every line above is verified before launch, and you get the dated audit rather than a badge.

Nobody can promise you a number.

Rankings, traffic, and revenue are outcomes, and outcomes depend on your market and your medicine. What we commit to are the inputs above, in writing. PulseTrack reports what actually happens, in the same plain English as this page.

Accessibility and privacy

Built so the hard questions mostly do not arise

Two things decide whether a practice website becomes a problem later: whether everyone can use it, and whether it quietly collects things it has no business holding. Both are build decisions, so we make them at build time.

Everyone can use it

The standard
We build to WCAG 2.1 Level AA and test every page, in both themes, before it ships. Accessibility is a build gate here, not a line item at the end.
Where the rules point
Federal rules point at the same standard. Section 1557 of the Affordable Care Act reaches practices whose only federal participation is Medicare Part B, and the technical standard it routes to adopts WCAG 2.1 Level A and AA. The compliance dates moved in 2026 and are being challenged in court, so we do not sell a deadline as certain. We build to the standard either way.
What we will not say
Automated testing catches part of the picture, so we tell you what we tested and what we found rather than calling a site fully accessible. We do not install accessibility overlay widgets: they cover the markup instead of fixing it.

Nothing collected that is not needed

The form
Your contact form asks how to reach someone back, not what is wrong with them. Your front desk is better at that conversation, and it keeps medical details out of a marketing inbox.
The page it sits on
Pages with a form on them carry no advertising or analytics code, because that is the page where mistakes happen. Notification emails tell you a request came in; they do not carry the contents around with them.
Every third-party script
No third-party script goes on your site unless you decide it does, and every one that does is inventoried in writing with what it sends and where it goes. A cookie banner is not permission to share health information, and we do not treat it as one. We put no marketing code inside patient portals or logged-in scheduling.

The form we build

What it asks

  • Name
  • Phone
  • Email
  • Preferred time to be called
  • How you heard about the practice
  • Reason category: new patient, existing patient, billing, records, other

What it never asks

  • A free-text box for symptoms or reason for visit
  • Diagnoses, medications, or treatment history
  • Insurance member ID or Social Security number
  • Date of birth, unless booking genuinely needs it
  • File uploads
  • Any menu whose options are conditions

Illustrative · the same page carries no advertising or analytics code

What we do not claim

  • There is no HIPAA certification for software or for agencies, so we do not claim one.
  • We cannot make your practice compliant, and no vendor can. We build the parts we control so they do not put you at risk, and we document them so you can verify it.
  • We are not attorneys and this is not legal advice. Your counsel or privacy officer should review anything that touches patient data, and we will give them what they need to do it.

Before a build

What doctors ask

Direct answers in the same plain English the site will use. Everything else is what the discovery call is for.

  1. Is this a template you customize for my practice?

    No. There is no theme underneath. Layout, art direction, and copy are drawn from your practice and your specialty, which is why no two sites we ship look alike. If two of our sites ever read the same, we treat that as a defect.

  2. Who owns the website when it’s done?

    You do. The domain, the code, and every design asset are yours, and the handover is documented in writing. If you ever leave, the site goes with you.

  3. How long does a build take?

    A typical build goes live in four to eight weeks from kickoff, and review turnaround on your side is usually what moves it within that range. You get a written schedule before work starts, not an estimate afterward.

  4. What happens to my current site?

    It stays live until the moment the new site launches, so patients never hit a gap. We archive a copy of the old site, and every existing address is redirected to its new home so links, bookmarks, and profiles keep working.

  5. Is photography or video included?

    Brand and art direction are included in every build. On-site photography and video are add-ons, scoped once we know your practice and what the design calls for. We audit the images you already own first; most practices have more usable material than they think.

  6. How much of my time does this take?

    A kickoff conversation, a clinical review of every page we write, and a sign-off at the end of each phase. Reviews happen on your schedule; the design, writing, and engineering happen on ours.

Next step

See what your practice’s site would look like

A 30-minute call in plain language. You leave with a roadmap for your practice, whether you hire us or not.