Skip to content

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.

Built for one chair, not for the clinic in the brochure169.2%218.1%36.4%42.7%51.4%6+2.2%n = 98.315

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.

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.
One record from the first click

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.

Six states, and two of them are final

What a practice pays for this today

Assembled from what each vendor publishes on its own pricing page, with the date we last read it. Nothing here is an estimate of what "the market" charges — those aggregates contradict each other, so we do not quote them.

Typical stack, per month

R$ 550 – 11.000


Nitentia, per month

R$ 197 – 297

The bracket is Brazilian, because Brazil is where the product is in production. It is a negotiation bracket rather than a list price, and it does not include the practice-management system a clinic already runs — Nitentia is the presence and the patient path, not the clinical record.

Two different products wearing the same category name

Software sold to “clinics”What one chair needs
The default screenA 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 stepAdd your rooms, resources and team.Answer who you are and what you treat. There is one of you.
The missed appointmentA 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 toA 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. 1

    A conversation

    Thirty minutes. We ask what the practice is, what it treats and where its patients come from now.

  2. 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. 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. 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?

In production: the website generator, the patient capture endpoint, the lead pipeline, the portal, discovery and the compliance gate. The agenda exists as a screen — one column, the states of the day — and does not yet save, because writing patient data depends on the server. The agents have the screens, the gate and the review, and do not yet write, for the same reason. The odontogram is designed and not shipped. We would rather tell you that than show you a screenshot of something that does not exist.

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 take the config file and the patient records. The config is a plain document describing your practice; there is no proprietary format holding it hostage.

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.