The problem this tests
Clinic websites tend to open with a smile and a slogan and hide the one thing a visitor came for — asking for an appointment — three screens down, behind a form that emails someone. Nothing about that form knows whether the slot is free, whether the same request was sent twice, or what the patient agreed to.
NAKE was built to test the inverse: put the appointment request first, by treatment, and make what happens after the click as careful as a clinical record.
The homepage as the request
The first screen asks what you need. Implants, invisible orthodontics, aesthetics, rehabilitation, whitening, general care, or something else — each one opens the request with that treatment already set, so the visitor's first action is the one that matters, and the rest of the page exists to reassure, not to redirect.
The booking is two steps: choose a published slot when one exists, or state a preference when it does not. The confirmation arrives by the channel the patient chose, and the clinic receives a request it can act on rather than a message it has to interpret.
Engineering the moment after the click
A slot and the request that claims it are written in the same transaction, so two patients cannot book the same time. Each submission carries an idempotency key, so a retry after a dropped connection does not create a duplicate. Abusive traffic is rate-limited without storing network addresses.
Consent is versioned — the clinic can prove what text was agreed to — and personal data expires on a schedule instead of accumulating. The private panel lets the team see appointments and inquiries, search without leaking data into URLs, and move each request from new to contacted, confirmed or closed.
What the build proves
NAKE is bilingual on a single codebase, with a managed relational database, an authenticated back office and an operational contract — health checks, structured logs, request IDs — that a clinic's IT or a future developer can rely on.
It shows the studio treating a small business form as what it is: the entry point to someone's health data, designed for the patient and engineered for the people responsible for it.
