How I Build a Dental Practice Back Office from a Clean Greenfield
Most practices don’t get designed. They accumulate. A software subscription here, a filing habit
there, a firewall someone set up in 2016 and nobody has logged into since. By the time it’s
running, the “system” is really just the sum of everyone’s workarounds.
A greenfield build is the rare chance to do it the other way — to decide, on purpose, how a
practice will operate before the first patient walks in. I’ve now built the entire back office and
technology stack for a practice from nothing, single-handedly, and the discipline it forces is the
best operations education there is. Here’s the order I build in, and why.
Start with the operating model, not the software
The most expensive mistake in a new practice is buying tools before you’ve decided how you work.
Every practice management system, payroll platform, and firewall has an opinion baked into it, and
if you adopt three tools with three conflicting opinions, your staff spend their careers
translating between them.
So before I evaluate a single product, I write down the operating model: who does what, what
happens between a patient booking and a paid claim, where money and data move, and who is
accountable at each hand-off. It’s unglamorous — mostly a whiteboard and a lot of “and then what
happens?” — but it’s the spec that everything else has to serve. Software should conform to your
operating model, not the reverse.
The back office is billing, HR, payroll — and the seams between them
Through the build-out phase I run the back office myself, and that’s deliberate. You learn where a
practice actually leaks by doing the work, not by reading a dashboard someone else built.
Three functions carry the load:
Billing and claims. This is the practice’s bloodstream. The goal is a clean path from
treatment to submitted claim to reconciled payment, with as few manual re-entries as possible.
Every place a human retypes a number is a place errors and delays are born. I map that path first
and design to minimize the hand-offs.
HR and payroll. In a new practice these feel small — a handful of people — right up until
they’re not. Building the structure early (clear roles, documented hours, compliant payroll)
costs almost nothing at five staff and is a nightmare to retrofit at fifteen. I stand up the HR
system before I need it, not after.
Patient financing. Accessibility is an operations decision, not just a marketing one. Getting
financing options in place early means treatment plans don’t stall at the front desk, and it
changes the practice’s cash rhythm in ways you want to design for, not discover.
The theme across all three: the value isn’t in any one function, it’s in the seams between
them. A back office that runs itself is one where billing, payroll, and scheduling share the same
truth instead of three copies of it.
Build the technology foundation like you’ll be audited — because you will
Here’s where my build differs from most. I don’t treat IT as something you outsource and forget.
The infrastructure is part of the operating model, so I design and run it directly.
For a modern practice that means a real foundation: a Windows Server 2022 domain so identity
and access are centralized rather than a pile of local logins; a properly configured FortiGate firewall as the perimeter, actually managed rather than installed-and-abandoned; and the
practice management system — Open Dental in my most recent build — administered as the
database it is, with backups you’ve tested by actually restoring them.
I also lean on self-hosted infrastructure where it earns its place — file storage, HR, and
training platforms you control rather than rent. That’s partly cost, but mostly sovereignty: your
patient data and your operational knowledge shouldn’t live somewhere you can’t see.
The test I hold every technology decision to is simple: if a regulator or a security incident forced me to explain exactly where patient data lives, who can touch it, and how it’s protected, could I answer without flinching? If the answer is no, it’s not built yet.
Compliance is an operating standard, not a binder
In Ontario that means PHIPA and PIPEDA — the privacy obligations around patient data. The
mistake I see everywhere is treating compliance as a document you produce once and file away. Real
compliance is a property of how the system behaves day to day: access is limited to who needs it,
data moves over channels you control, and there’s an actual answer to “who saw this record and
when.”
I build that in from the first server, because compliance retrofitted onto a running practice is
ten times the work and never quite fits. When it’s baked into the operating model, it stops being
a liability and becomes a quiet competitive advantage — the practice that can prove it protects
patients is the practice patients and partners trust.
Presence comes last, and it’s still operations
Only once the machine runs do I build the practice’s public face — service-page architecture for
the treatments that matter (implants, veneers, aligners, whitening, All-on-4), structured data so
search engines understand the site, an optimized Google Business Profile, and ongoing technical
SEO to close the indexing gaps that quietly cost visibility.
I put this last on purpose. A marketing engine pointed at a practice that can’t operate just
generates demand you’ll fumble. Get the operations right, then turn on the tap.
What “get out of the way” actually requires
My whole philosophy is build the conditions for staff and practices to perform, then get out of the way — but the “get out of the way” part is earned, not assumed. You can only step back from a
system that was designed to run without you. That means documentation staff can actually follow,
tools that share one source of truth, and infrastructure that doesn’t need a hero to keep it alive.
The measure of a greenfield build isn’t how impressive it looks on opening day. It’s whether, six
months in, the practice is running well on days you’re not there. That’s the whole job.
I build and secure dental practices from the ground up — operations, IT, and compliance. If you’re planning a build-out or trying to get an existing practice’s systems to finally pull together, I’m at byronemmons.com.