IN DEVELOPMENTDental Acquisition is in development. The launch showcase practice is Dr Max Dental CareJoin the waiting list
IN DEVELOPMENTEARLY ACCESS · SHOWCASE PRACTICE: DR MAX DENTAL CARE

A clearer route from a treatment search to a practice reply.

Dental Acquisition is being built for the gap between a patient searching for a treatment and a practice replying to them: treatment pages that answer the question, an enquiry that carries context, and a queue the practice can work through.

PATIENT LAYERTreatment discovery and enquiries
PRACTICE LAYERRouting and follow-up
INFRASTRUCTURESemantic structure and search readiness

Interactive 3D scene. Move the pointer, or choose a state, to step through the journey.

SCROLL-DRIVEN 3D SCENE · FOUR STATES

Four views of the same journey.

Scroll, or pick a state, to move between how a patient finds a treatment and how a practice receives the enquiry.

ACTIVE CAMERA STATE01 · Discovery
CONCEPTUAL PATHWAYTreatment question → informed choice
STATE 01 // DISCOVERYACTIVE VIEW

State 1 — Discovery

“A patient should be able to work out what they need before being asked for their details.”

Most practice sites begin with a list of treatments and no context. This layer is designed to explain what a treatment involves, what the appointment looks like and who provides it, so a patient can decide whether to go further.

THREE-QUARTER VIEW · FULL MODELTreatment question → informed choice
STATE 02 // PATIENT JOURNEYCLICK TO FOCUS

State 2 — Patient journey

“Reading about a treatment and asking about it should not be two separate journeys.”

The view moves closer as the pathway nodes light up. This is the route from a treatment page to a sent enquiry, kept on one domain so the patient does not have to hunt for a phone number.

PATHWAY NODES · CLOSE VIEWRead → compare → enquire
STATE 03 // PRACTICE ACQUISITIONCLICK TO FOCUS

State 3 — Practice acquisition

“An enquiry should reach the practice with enough detail to answer it well.”

The view turns to the practice side, where a structured enquiry carries treatment interest and preferred timing. Reception starts with context instead of a name and a blank note.

PRACTICE-FACING VIEWEnquiry → practice queue
STATE 04 // CONNECTED INTELLIGENCECLICK TO FOCUS

State 4 — Connected intelligence

“The useful part is the loop, not any single screen.”

Pulling back shows what patients search for, what they read, what they send and what the practice does with it. That loop is the product. Everything else on this page is presentation.

FULL NETWORK · WIDE VIEWSearch · reading · enquiry · reply
SECTION 01 // WHERE ENQUIRIES GO WRONG

Where dental enquiries go wrong.

The problems are consistent: treatment pages that do not answer the question, enquiry forms that arrive with no context, and follow-up that depends on who is at the desk. None of it is about clinical skill.

CHALLENGE 0101

Treatment information is spread thin

Someone comparing implants across five practices is reading five versions of the same procedure, at different levels of detail, with no way to compare like with like.

OPPORTUNITY AREA · PLATFORM ROADMAP
CHALLENGE 0202

Finding the right clinician takes work

Registration, specialisms and referral routes are rarely presented in a form a patient can use when deciding where to go.

OPPORTUNITY AREA · PLATFORM ROADMAP
CHALLENGE 0303

Enquiries arrive without context

A form that says “tell us about your needs” gives reception very little to work with, and the reply depends on who picks it up.

OPPORTUNITY AREA · PLATFORM ROADMAP
CHALLENGE 0404

Being visible is not the same as being chosen

Ranking for a treatment term helps. A patient still has to trust the page, understand the options and take the step.

OPPORTUNITY AREA · PLATFORM ROADMAP
SECTION 02 // WHAT IS BEING BUILT

Three layers, built so the product does not rely on one practice.

Patients need one route through treatment information. Practices need enquiries they can act on. The two share a data model but ship separately, and Dr Max Dental Care is the launch showcase rather than the product owner.

PILLAR 01 // PATIENT EXPERIENCEIN DEVELOPMENT

Patient discovery

Patients see what a treatment involves, how long it typically takes and which practices offer it, before they hand over an email address.

  • Treatment pages built around patient questions
  • Practice and clinician profiles with real detail
  • An enquiry form that asks only what is needed
CORE ARCHITECTUREFollow Development →
PILLAR 02 // PRACTICE EXPERIENCEIN DEVELOPMENT

Practice growth

Enquiries arrive in one place with the treatment interest attached, so the front desk knows what the call is about before it answers.

  • A queue ordered by treatment interest
  • Follow-up status the whole team can see
  • Practice pages that read like a practice, not a template
CORE ARCHITECTUREFollow Development →
PILLAR 03 // TECHNOLOGY FOUNDATIONPLANNED

Technical foundation

The layer underneath: semantic markup, crawlable content and structured data that search engines and AI assistants can actually read.

  • Schema written for dental services
  • Content structured around real searches
  • Routing that extends to a second site
CORE ARCHITECTUREFollow Development →
INTERACTIVE MOODBOARD · ILLUSTRATIVE CONCEPTS

Drag the cards to see how discovery, enquiry capture and practice routing sit together. These are concepts, not screenshots of a working product.

CONCEPT 01 · TREATMENT DISCOVERY CARD

Ceramic and restorative pathway explorer

A treatment overview a patient can actually read

PATHWAYRead → compare → enquire

Illustrative concept · showcase practice

CONCEPT 02 · PATIENT ENQUIRY CARD

Guided enquiry capture

Records treatment interest and contact preference, nothing clinical

PRIVACYNon-clinical intake · recorded consent

Illustrative concept · planned module

CONCEPT 03 · PRACTICE ENQUIRY INBOX

Practice enquiry queue

Incoming enquiries grouped by treatment interest

STATUSReceived → followed up

Illustrative concept · in development

CONCEPT 04 · ACQUISITION OVERVIEW

Discovery and search readiness layer

Semantic markup, crawlable content and routing

ARCHITECTUREBuilt for more than one site

Illustrative concept · planned infrastructure

SECTION 03 // HOW IT IS MEANT TO WORK

From a treatment search to a practice reply.

STATUS: CONCEPT AND PLANNED WORKFLOW. ONLY THE WAITING LIST IS LIVE.
01In development

01 — DISCOVER

A patient searches for a treatment and lands on a page that answers the question they typed.

02Concept stage

02 — EXPLORE

They compare options, read what the appointment involves and check who provides it.

03Planned workflow

03 — ENQUIRE

They send an enquiry with the treatment and preferred timing already attached.

04Planned routing

04 — CONNECT

The practice receives it with that context and follows up.

INTERACTIVE EDITORIAL CAROUSEL
01
STAGE 01 · DISCOVER

Discovery

Patients find a treatment page that answers the question they searched for.

Instead of five practice sites and a directory listing, a patient gets one page explaining what the treatment involves, what the appointment looks like and who provides it.

  • Treatment pages organised by what patients search for
  • Plain explanation of each treatment before any enquiry
  • Practice and clinician details on the same page
ILLUSTRATIVE CONCEPT · IN DEVELOPMENTUI PREVIEW 01/04

Patient discovery page concept

Dental Acquisition · showcase campaign

TREATMENT DISCOVERY FILTERCONCEPT UI
Dental ImplantsClear AlignersComposite BondingGeneral Restorative
SHOWCASE CAMPAIGN IDENTITY

Dr Max Dental Care — Restorative & Implant Pathway

STAGE 01 OF 04 · PLANNED PLATFORM WORKFLOW
SECTION 04 // FOR PRACTICES AND CLINICIANS

For practices that want to know what the enquiry is about.

The plan is plain: treatment pages that answer real questions, an enquiry form that captures intent, and a view of incoming enquiries a reception team can work from.

Transparent Product Scope: The platform is in development. Registering practice interest puts you into early pilot conversations and product updates. No contract, no lock-in, and no promise of patient numbers.

FOUNDATION 01

Pages that answer real questions.

Treatment and practice pages are built around what patients search for, with the markup search engines need to understand them.

DESIGNED FOR CLINICIANS & PRACTICE TEAMS
FOUNDATION 02

Enquiries that arrive with context.

Treatment interest, timing and contact preference are captured up front. No medical history is requested at this stage.

DESIGNED FOR CLINICIANS & PRACTICE TEAMS
FOUNDATION 03

A queue rather than an inbox.

The planned practice view groups enquiries by treatment and shows what has been followed up, so nothing sits unanswered.

DESIGNED FOR CLINICIANS & PRACTICE TEAMS
FOUNDATION 04

Built to add a second site.

The data model is designed for groups and multi-site clinics from the start rather than retrofitted after the first acquisition.

DESIGNED FOR CLINICIANS & PRACTICE TEAMS
SECTION 05 // EARLY ACCESS WAITING LIST

Join the waiting list.

Registration takes about a minute. We will email when early access opens, and you can ask us to remove your details at any time.

WHO THE LIST IS FOR

  • Patients: Hear when treatment discovery pages go live for the showcase practice.
  • Dentists & Dental Professionals: Ask about clinician profiles and the first pilot cohort.
  • Practice Owners & Managers: Follow the enquiry routing and multi-site work.
EARLY ACCESS REGISTRATION

Registration is not open yet.

The waiting list is being prepared and is not accepting registrations. No details are being collected through this page. When it opens, the privacy notice will set out exactly what is stored and for how long.

Staging preview - not the live site

INDEPENDENT WEB ENGINEERING
COMMISSIONED DIRECTLY BY PRACTICES
INDEPENDENT DEVELOPER

Zubair Chowdhury

Independent Web Developer

Dental websites · technical SEO · enquiry systems

Zubair Chowdhury is an independent software and web developer, not a dentist or clinical provider. Website, SEO and consulting work is commissioned separately from any future platform subscription.

DIRECT COMMISSIONS

Need a dental site that handles enquiries properly?

Built for practices that answer their own phone.

Website design and development.

Sites for private and specialist practices, with the enquiry path treated as part of the design rather than an afterthought.

Technical SEO and search readiness.

Structured data, crawlable pages and content that search engines and AI assistants can read without guessing.

Enquiry handling.

Forms that ask only what the practice needs, with consent recorded properly and enquiries arriving in one place.

Ongoing technical work.

Measured against enquiries and booked consultations, not traffic charts that never turn into patients.

Commission a dental site, or start with a technical SEO review

You deal with Zubair Chowdhury directly. No account managers.