How TreatPath was made, who shaped it, and what we believe about software that sits between a doctor and a patient.
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 is accurate, complete — and nearly unreadable to the person whose mouth it describes. Patients respond the way anyone responds to a confusing document with a large number on it: "I'll think about it."
TreatPath began at Coastal Dental Arts in San Diego — a father's practice, a son who builds software — as an attempt to fix that one moment. Not the dentistry, not the diagnosis, just the conversation: what if the same plan were presented as a choice between clear paths, in language the patient understands, on a screen they 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.
TreatPath wasn't designed in mockups and handed to a practice. It was built inside one — shaped by the people who actually touch a treatment plan on its way to a patient. The doctor, yes. But 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.
That changed the software — you can trace team members' fingerprints on specific features, a few of which are on the right.
Our working rule is simple: if a feature needs a training manual, we rebuild the feature. Staff at our beta practice learn TreatPath between patients, not in a seminar — that's the test, and it gets applied to every release.
Software that sits between a doctor and a patient carries responsibility in both directions. Each of these is a decision you can find in the product.
The tiers are built from the doctor's own diagnosis — the software has no opinion about what treatment a patient needs, and no incentive logic that favors bigger cases.
Real insurance amounts where the plan provides them, the pre-insurance price shown struck through rather than hidden, monthly financing labeled with the practice's actual terms. No number a patient sees is massaged.
What a patient signed is stored exactly as they signed it. Later changes are additions with their own history — never edits to the record.
Every team member signs in as themselves, every plan credits the person who actually presented it, and the access log names individuals — because a practice's compliance program deserves software that participates in it.
No date of birth, no Social Security number, no insurance member ID, no medical history. A first and last name, the procedures, and the signature — what the conversation needs, and nothing else. Our privacy policy and security page say this in detail, including what we deliberately do not store.
Designed and built TreatPath — the planner, the patient experience, the behavioral model, 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 full security posture — every control, and how it works — because trust should be checkable.