A clinic website where the booking stays put.
A clinic website has one job before all others: to make a stranger comfortable enough to book. That means saying what the treatment is, who it is for, and who stands behind it. You probably already have the booking, and it should not be replaced just so the site can be new.
What a clinic actually needs
What the treatment is, in plain words. Not the clinical term alone. What happens in the room, how long it takes, and what you feel afterwards.
Who it is for. A reader decides in seconds whether the site is talking to her. A list of what you treat does that job; a list of what you are capable of does not.
Who stands behind it. In a clinic, trust attaches to a person, not to a company name. Name, years in the field and background belong at the top, not in a footer.
And a route to the booking that is not a detour. One tap, the same place on every page, and into the system the clinic actually uses.
What is hard here in particular
The booking already exists, and it should not be touched. A clinic that has run the same booking system for years has routines, cancellation rules and reminders inside it. A website that replaces it replaces something that works in order to get a prettier button.
Results cannot be promised. What you can write is what the treatment is, who it is for, and who performs it. Anything beyond that is a claim nobody can honour, and a clinic has more to lose on it than most.
The form must not become a medical record. A free-text field on a clinic site gets used to describe symptoms. At that moment an ordinary contact form has started collecting health information, and that is a different matter from an email address. The answer is not to ask for it: the form asks for a name and a way to reach you, and the rest happens in the room.
And references are almost always someone else’s words. If the clinic has well-known clients, it usually already says so on its own page. The right form is to quote what is there, with the sentence that says where it comes from, rather than rewriting it into something stronger.
Building around a booking calendar rather than replacing it
It is a technical decision that looks like a matter of taste, and it always goes the same way when the system is in use.
A booking system is not a calendar. It is cancellation deadlines, reminders, payment status and a routine somebody at the clinic knows by heart. None of that moves with the calendar; it has to be recreated, and it is never recreated fully.
Nor does the website need to own the booking in order to do its job. It has to make a stranger comfortable and then send her one place. That the one place is the clinic’s own system rather than a new one is an advantage to everybody except whoever would have sold the new one.
What there is to do is to make the route there short and identical on every page. The rest is to leave it alone.
The project as evidence
Toms Arena is a client project. The sentences below are the register’s own, taken from the project list and not rewritten for this page. Note how the first one ends: it says where the information comes from.
The clinic is Tom Skjønnhaug’s. He has treated elite athletes since 1985, and Thor Hushovd, Lars Monsen and Nusa are among the clients. That is what the clinic says on its own page.
I built the clinic’s landing page: what the treatment is, who it is for, and who stands behind it. The booking is the clinic’s own, and it is untouched.
The booking is the only place in the register where a third-party solution is deliberately left standing. The project is in progress, and the site sits on a preview domain.
The way onward
The scoping call is free. It is about what goes on the page and what stays untouched, and it takes twenty minutes. A written quote afterwards.
Book a scoping call