How a father's practice and a son's software came together around one moment in the appointment.
How TreatPath was made, who helped shape it, and the rules we follow when building software that sits between a dentist and a patient.
How a father's practice and a son's software came together around one moment in the appointment.
I grew up around my dad's dental practice. Some nights he'd come home frustrated, and it was never really about the schedule. He'd spent time with a patient, found something they needed for their oral health, explained it, and watched them leave without booking. Usually there wasn't a real reason. They just didn't come back.
What stuck with me was how he talked about it. To him the job was helping people feel confident enough to smile. He knew most of those patients wanted that. So when someone walked out without a plan to fix their teeth, he wasn't thinking about the appointment that didn't get booked. He was thinking about the person who would keep feeling uncomfortable smiling in public, for a reason that didn't have to exist.
Years later he asked me if I thought I could build something to help. I'd heard about this problem at the dinner table my whole life, so I said yes and ran with it. He knew it from the chair. I knew it from the kitchen.
We still build it that way. Every version goes through his operatories first, and he's the one who tells me when something won't work with a real patient in the chair. When a patient understands their options and picks one that works for them, they get the care they came in for.
That's what we're building, together.
Ethan Chotiner · Co-founder

Every dental practice has the same document: the treatment plan printout. A grid of procedure codes, clinical abbreviations and a total at the bottom. It's accurate and complete, and almost unreadable for the person whose mouth it describes. Patients react the way anyone reacts to a confusing document with a big number on it: "I'll think about it."
TreatPath started at Coastal Dental Arts in San Diego, Dr. Chotiner's practice, and it set out to fix that one moment in the appointment. The dentistry and the diagnosis stay the same. We wanted to change the conversation: what if the same plan were laid out as a few clear options, in plain language, on a screen the patient can hold?
The plan didn't change. The way we present it did — and patients finally ask questions instead of asking for time to think.
We didn't design TreatPath in mockups and hand it to a practice. We built it inside one, with the people who handle a treatment plan on its way to the patient. That includes the dentist, and just as much the front-office staff who build and send plans between phone calls and the treatment coordinators who sit with patients while they decide.
A lot of features came straight from them. A few are listed here.
Our rule: if a feature needs a training manual, we rebuild the feature. Staff at our founding practice learn TreatPath between patients, and every release has to pass that test.
Nobody should retype what the practice software already knows. One capture, and the plan is read in seconds.
Coordinators kept translating between two layouts, so now staff review the plan in the same three-path layout the patient sees.
"It didn't work" usually meant one missing field. The checklist names exactly what's left, and takes you to it.
A locked-out front desk before the first patient is not a hypothetical. Admins reset a forgotten PIN in seconds.
Software that sits between a dentist and a patient has to be trustworthy to both. You can see each of these in the product.
The paths come from the dentist's own diagnosis. The software has no opinion about what treatment a patient needs, and nothing in it pushes patients toward bigger cases.
Insurance amounts come from the plan. The price before insurance is shown crossed out instead of hidden, and monthly financing uses the practice's actual terms. We don't adjust any number a patient sees.
A patient's signature and the moment they signed are never changed. If a patient later says yes to more, staff record it as a staff-confirmed upgrade with its own history, kept alongside the original signature.
Every team member signs in as themselves, each plan is credited to the person who presented it, and the access log names who did what. A practice's compliance program depends on knowing that.
No date of birth, no Social Security number, no insurance member ID, no medical history. A plan holds the patient's name (and an optional chart number), the procedures and fees, and the signature, plus the few working details your team adds, like a decline reason or a short note. Our privacy policy and security page go into detail, including what we choose not to store.
Designed and built TreatPath: the planner, the patient view, the behavioral styles and the security program behind them. Runs the company from San Diego.
Practicing dentist at Coastal Dental Arts in San Diego. Every workflow in TreatPath was tested in his operatories first, by him, his front desk and his treatment coordinators.
TreatPath is live in daily clinical use, patent pending, and operated by TreatPath Inc., a Delaware corporation. We publish our security controls and how each one works, so you can check them yourself.
Recognition. Second runner-up of 63 teams in the University of San Diego's Fowler Business Concept Challenge, November 2026.