For dental practices
Built for one chair, not for the clinic in the brochure
Practice software is sold with a picture of a six-chair clinic and a reception team. Measured on the open Brazilian health registry, 69.2% of private practices have one chair and 76.9% have one dentist. Nitentia builds the website, catches the patients it brings in, and keeps both in one place — for that practice.
Both of the above are free, ask for no sign-up and run in your browser — the site is assembled on screen by the real generator. Nothing is saved until you create an account, and the screen says so while you build.
The measurement the category is missing
Nobody publishes revenue per dental practice, so the genre invents it. Installed capacity, though, is public and had not been measured. We measured it on the open registry, and it moves the whole argument.
69.2%
of private dental practices in Brazil have exactly one chair.
n = 98,315 practices with at least one chair and none offered to the public system.
76.9%
have exactly one dentist. The bottleneck is one person’s clinical hour, not the room.
62%
of two-chair practices still run with a single dentist. A second chair rotates one person’s day; it does not double output.
Six things, and they know about each other
Not a suite. Six surfaces with one contract between them, so a patient who arrives on the website is the same record the practice answers in the morning.
In production
The clinic website
A fast, static site under the clinic’s own brand — generated from a config file, not assembled in a page builder.
In production
The patient inbox
Every enquiry lands in one place, with where it came from and what the person actually agreed to.
In production
Discovery
A 0–100 score you can recount: eight checks over the site’s own configuration, each with its weight declared.
Draft generation with review; availability checked in the portal
The agents
Five assistants that draft for the practice. None publishes: there is no automatic mode, not even one shipped switched off.
In production
The clinic portal
The owner’s side: read the inbox, move a patient forward, change the site without calling anyone.
In production, and closed where it cannot judge
The compliance gate
Automated checks can block missing professional identification and selected prohibited claims. They support the clinical lead’s review; they do not certify compliance.
How the pieces hand off
The handoffs are where the stack a practice buys today leaks: the site does not know the inbox, the inbox does not know the calendar, and the practice becomes the integration.
One record from the first click
The website captures the enquiry, the inbox holds it, the portal answers it. There is no export step and no copying a phone number between two tabs, because there is one contract underneath all three.
- Where the patient came from travels with the patient.
- The states only move forward, so counting them twice is not possible.
- Consent is stored against the exact wording that was shown.
Six states, and two of them are final
A patient enquiry moves captured → contacted → scheduled → attended, and ends at converted or lost. It cannot move backwards. That is a modelling choice with a boring, valuable consequence: the numbers you read at the end of the month cannot double-count.
Compare the scope before the price
Nitentia provides a clinic website and organizes incoming contacts. Keep your practice-management system. A directory listing, paid advertising and ongoing agency work are separate services; their prices are not savings promised by Nitentia.
Two different products wearing the same category name
| — | Software sold to “clinics” | What one chair needs |
|---|---|---|
| The default screen | A multi-column resource grid, one column per chair. | One column. The grid appears only when the config says there is more than one chair. |
| The first setup step | Add your rooms, resources and team. | Answer who you are and what you treat. There is one of you. |
| The missed appointment | A filter on a status field. | Its own state, in its own colour, on the day view — it is the largest revenue leak a single-chair practice has. |
| Who the website belongs to | A template with the vendor’s badge in the footer. | The practice’s own brand. Nothing of ours appears on a page a patient sees. |
How it starts
1
A conversation
Thirty minutes. We ask what the practice is, what it treats and where its patients come from now.
2
A config, not a project
Your practice becomes one config file — professionals, registrations, services, hours, brand. It is reviewed by a person before anything is built.
3
The site is generated
The build refuses an incomplete or non-compliant config, so what goes live is complete by construction, not by review.
4
The inbox opens
From the first day, every enquiry lands in one place with its source attached.
Questions worth asking us
Is this a practice-management system?
No, and we are careful about the word. Nitentia is the practice’s public presence and the path a patient takes from finding it to sitting in the chair. The clinical record, the treatment plan and the billing ledger stay in the system you already run.
How much of this is actually built?
The site generator, editing, publication, patient inbox, agenda and AI drafts are available. The portal checks service availability. Image generation, AI search ranking measurement and an odontogram are not available.
Who owns the site and the patient data?
The practice does. The website is built under the practice’s brand with no mark of ours on it, and patient enquiries are the practice’s data, held on its behalf.
Why is the website static?
Because a marketing site with no server has no cold start, no idle cost and nothing to keep patched. A patient on a phone in a waiting room gets HTML that was already built, from a CDN.
What happens if I leave?
You can request an assisted export of received contacts and the published site configuration. We verify your authorization before delivery, in any plan. Draft history, agenda and a ready-to-host website are not part of this export.
See it, including the parts that are not finished
A demo shows the working software and names what is still being built. If it is not a fit, that is a useful thirty minutes for both of us.