Skip to content
European companyFounded in 2014Built and operated in EuropePayments secured by Stripe
Gradax

The empty chair is the whole problem

Websites, booking and recall systems for dental practices, built around the two things that decide a practice's revenue: new patient registrations and people who actually come back.

Sold as
One contract
Starts with
A free review

The vendors we build on, operate and resell.

  • Cisco
  • HPE
  • Dell
  • Lenovo
  • Veeam
  • WordPress
  • WooCommerce
  • Google
  • Stripe
  • Zoho
  • Atlassian

A dental practice has a fixed capacity and a fixed cost base. Every hour a chair is empty is revenue that cannot be recovered later, which makes no-shows and lapsed recalls far more expensive than they look on a spreadsheet.

Most practices spend on attracting new patients and almost nothing on the recall list they already own. A patient who last attended fourteen months ago is the cheapest appointment in the building and the one nobody chases, because chasing means somebody sitting on a phone.

The search side is not separate from that. "Dentist near me", "emergency dentist" and specific treatment searches like implants or invisible braces, all with a town attached. Ranking for those means the pages exist, the business is verified where it operates, and the reviews are real and recent.

How a patient moves through a dental practice

From the first search to the six-month recall, most lost revenue sits between the steps, not inside them.

  1. Booking the first visit

    It stalls when the only route is a phone line busy with the morning rush, and it moves when the patient can book a real slot at nine in the evening.

  2. Confirming the appointment

    It stalls when nobody confirms and the patient forgets, and it moves when a message the day before lets them confirm or move it with one tap.

  3. Accepting the treatment plan

    It stalls when the plan leaves the chair as a verbal estimate, and it moves when the patient goes home with a written plan and a clear way to pay.

  4. Coming back for recall

    It stalls when the recall list lives in the software and nobody works it, and it moves when reminders go out on the due date without a receptionist dialling.

Software we built for businesses like yours

A product we designed, built and run, shown here as the work we do.

Neodent

Neodent is clinic software we built for dental practices: patient records, appointments, treatment plans and billing in one system.

A dentist treating a patient in a bright dental surgery

What people in this trade ask us

Is patient data safe?
Clinical records stay in your practice management system. What we build handles booking and communication and holds the minimum it needs to do that, hosted in the EU, with access logged.
Will it connect to our practice software?
Usually yes, and if the vendor has no interface, we say so before you buy rather than after. Some systems are genuinely closed and it is better to know.
Do we have to publish prices?
You do not have to, but the practices that publish a clear range get better enquiries and waste far less chair time on consultations that were never going to convert.
Can patients pay for larger treatment in instalments?
The payment side can be set up so a plan is split and collected automatically. Whether you offer it, and on what terms, is your decision, and we build to the policy you already use at the desk.
What should the site say about emergency appointments?
Exactly when you keep emergency slots and how to get one, in a line a patient in pain can find in seconds. A vague promise of same-day care creates calls you cannot honour.

The infrastructure under it

Managed by the engineers who build the software, on the same contract and the same bill.

Backup & Recovery

X-rays, charts and signed consent forms must survive a failed surgery PC, and restoring them cannot wait a week.

A storage unit with a row of drive bays.

Cyber Security

Practice networks with old imaging PCs are an easy way in, and a ransomware lockout empties every chair at once.

Two monitors showing security logs in a dark room.

What one contract covers

  • One contract. The build, the infrastructure and the work that brings people to it, on one invoice.
  • A named team. The person on the first call stays on the project. No account managers, no handoffs.
  • Operated, not delivered. We keep it running after launch: patching, backups, monitoring and the phone when it breaks.
  • European hosting. Servers in Europe, run by us, with the data staying where you expect it to.
  • Monthly reporting. What changed, what it cost and what it produced, in language you can forward to a board.
  • No lock-in. The code, the domains and the accounts are yours. Leaving is a handover.

See what is costing you customers before you spend anything.

A senior engineer walks your site, your search presence and the way enquiries reach you, then writes down the three things worth fixing first.

  1. 01You tell us what is not working
  2. 02We review the site, the search presence and the enquiry path
  3. 03You get the three fixes worth doing, and what each is worth