Practicing dentist · systems builder

A dental operating system, built where it has to work.

I practice dentistry, and around the chair I have built one connected system: operating companies that do the work, a shared data plane that measures it, and a fleet of software agents that carry the repetitive parts — under rules that keep money, patient data and anything irreversible in human hands. This site explains how the pieces connect, the method behind them, and the logic that decides what runs.

Nothing here is a demo. Every component described is in production in the practices and companies it was built for, or is named as unfinished.

Cases and conditions

Clinical writing for dentists on hospital cases, sedation, special needs and the medically compromised patient — unusual presentations, the precautions that matter, and the decisions behind them. Read the pieces.

How this site is paid for: no sponsors, no display ads, no paid tiers. The full commitment.

The thesis

One practice does not break in one place.

Marketing, the front desk, clinical documentation, claims, supplies and the numbers are one loop. A missed recall is a marketing problem and a scheduling problem and a hygiene-production problem. Most dental software treats each as a separate product. The operating system treats the practice as a whole, measures it as a whole, and automates only what repeats — clinical judgment, patient relationships and capital decisions stay with people.

Operate first

The work starts inside owned practices, where the constraints are real: staff bandwidth, insurance friction, provider time, supply drift, documentation burden. Nothing is productized until it has survived that.

Measure before building

Every site, form and workflow reports into one warehouse. Decisions are made on measured numbers, and the measurement itself gets audited — twice this year the "problem" turned out to be a broken meter.

Automate what repeats

Agents take research, monitoring, drafting and repair work. They cannot spend, send, touch patient data or merge code without a person. What they produce must be published where the next agent can find it.

Credentials

Where the clinical authority comes from.

The writing on this site is about the patients most practices refer out. What follows is the training, licensure and privileges behind it, stated plainly enough that a reader can weigh it rather than take it on tone.

  • Degrees

    DDS · MBA

    Doctor of Dental Surgery, and an MBA with a healthcare concentration. Undergraduate degree in construction management, cum laude.

  • Fellowship

    FAGD, working toward Mastership

    Fellow of the Academy of General Dentistry — awarded on continuing education and examination rather than on years served. Currently working toward Mastership.

  • Licensure

    Five states, eighteen years

    Active dental licenses in five states and eighteen years in practice. Member of the American Dental Association and the Academy of General Dentistry.

  • Sedation

    Parenteral sedation permit, formal training behind it

    State-issued permits for parenteral moderate sedation and for nitrous oxide and minimal sedation, held on the back of a completed formal sedation and anesthesia training program. ACLS and PALS current.

  • Hospital

    Hospital and surgical-center privileges

    Staff appointment and privileges to treat dental patients under general anesthesia in both hospital and ambulatory surgical settings — which is where the cases that cannot be finished in a chair are actually finished.

  • Scope

    The case that gets referred out

    Sedation and hospital dentistry, patients with special needs, and patients whose medical history turns an ordinary appointment into a planning problem. The working thesis is complete treatment inside one sedation event rather than one procedure at a time.

State licenses and sedation permits are verifiable through the issuing dental boards. Hospital and surgical privileges are verifiable on credentialing request.

How the writing is held

Evidence first, and the places it runs out named.

Every claim is sourced

Guidelines and systematic reviews before case series, with a DOI or a PubMed record for each. Where a source is thin, small, or reaches a different conclusion than the practice built on it, the piece says so in the text rather than in a footnote.

My own rules are tested, not asserted

The heuristics I work by are written down and then checked against the published standard, including where they turn out to be stricter than the evidence requires or to break outside the patient they were built for.

Scenarios, not patients

Nothing is written from a real chart. The cases are constructed to carry the decision, and every piece carries a standing notice saying so. No pictures, no identifying detail, no operative technique.

The map

Four layers, two databases, one set of gates.

Read it bottom-up: the practices generate the work; the operating companies do it; everything reports into a data plane split by whether it can contain patient information; the agent fleet works off that data and back into the companies, through gates.

Start a conversation

Practice operations, growth systems, documentation, or a transition.

Send two minutes of context on the practice, the bottleneck or the opportunity. The form prepares an email in your own mail app — nothing is stored on this site.

Prefer email directly? blane@avantmarketingrevolution.com

Advisors — CPAs, attorneys, consultants — can make introductions with confidence. Context goes straight to email and stays there.

Do not include patient information (PHI) or financial statements — context only. This static form does not store your information; it prepares an email you send yourself.

Your email app should have opened with a prepared note. If it did not, copy the note below and send it to blane@avantmarketingrevolution.com.