AI for the part of your practice
nobody wants to do.
Most “AI for dentists” pitches are imaging AI you can already buy from your X-ray vendor. The bigger opportunity is the unglamorous front-desk and billing work nobody wants to do. We build that.
Two AI conversations, not one.
Radiograph reading and chairside diagnostics
Overjet, Pearl, Dentina — specialized vendors with FDA clearances and direct integrations into imaging suites. Caries detection, bone loss flagging, treatment plan validation.
If you want this, you buy a product. You don’t need a consultant.
Front desk, billing, scheduling, recall
The appointment reminder that gets answered. The insurance verification that runs overnight. The recall scheduling that surfaces lapsed hygiene patients you didn’t know you had. The billing follow-up that doesn’t forget patients in collections.
5–10x improvement available. Almost nobody is helping.
Specific workflows. Specific outcomes.
| Workflow | What AI does | What it’s worth |
|---|---|---|
| Insurance verification | Pulls eligibility, plan details, frequency limits before each appointment. Surfaces patient responsibility before the chair time. | 5–10 hrs/week per FTE (vendor-reported, varies by payor mix) |
| Appointment reminders | Multi-channel (text/email/voice) with smart retry, two-way confirmation, no-show prediction. | 15–30% reduction in no-shows (industry range; depends on existing discipline) |
| Recall scheduling | Identifies lapsed hygiene patients, scores reactivation likelihood, drafts personalized outreach including benefit-reset timing (year-end use-it-or-lose-it). | Often 10%+ recall “ghost list” recovery, depending on practice age |
| Treatment plan docs | Treatment plan letter drafting from the chart. Insurance narrative drafting to support claims. Optional voice-to-note transcription for dentist-reviewed clinical notes. | 10–20 min/case saved on the admin layer, more clinical time |
| AR follow-up + billing | Aging-bucket prioritization, payment-plan offers, dispute documentation drafting. | Smaller AR, faster collections, less front-desk emotional labor |
| TOTAL ADDRESSABLE | 5 workflows · operational layer only | |
Every one of these has measurable ROI in the industry data, but what you’d actually capture depends on your specific patient volume, payor mix, and current workflow. A solo practice billing $700K/year and a four-doctor group billing $4M/year both have AI opportunities — just different sizes. That’s what the Consult engagement maps out.
Every AI tool has to talk to your practice management system.
That’s the integration question, and it’s the question most “AI for dentists” pitches refuse to answer concretely. Here’s what we know about the major systems:
The friendliest to integrate
Open source-ish, well-documented developer API. The cleanest integration path of any mainstream dental PMS.
Doable but heavier
Henry Schein’s dominant suite. Integration via Dentrix Developer Program or third-party connectors like Henry Schein One. More structured, more paperwork.
Cloud-native, documented API
Modern stack. Integration patterns are familiar to anyone who’s worked with modern SaaS APIs.
Heavier than Open Dental or Curve
Patterson’s historically closed ecosystem. API access has improved but integration tends to be heavier work.
Smaller install, variable
Smaller install base. Integration story is more variable than the mainstream platforms.
Multi-location and ortho-adjacent
Denticon (Planet DDS) and Carestream PracticeWorks come up in DSO-adjacent and ortho-adjacent practices. Both are doable, both are case-by-case in scoping.
If your practice runs on something not listed here, that’s a conversation. Some legacy PMS systems we’d advise against trying to integrate with — the cost of forcing an integration exceeds the value of the AI workflow it would enable. Honest answer in scoping beats a heroic build that fights the platform for two years.
BAAs are tedious. We do them anyway.
Every AI workflow that touches Protected Health Information needs a Business Associate Agreement with every vendor in the chain. Most AI consulting firms don’t talk about BAAs because BAAs are tedious. We do.
Off-the-shelf AI tools
ChatGPT and generic LLM APIs generally do NOT come with BAAs by default. Enterprise tiers sometimes do, with limits. You can’t just dump patient data into a chatbot and call it innovation.
BAA-covered workflows
HIPAA-covered AI workflows require either a BAA-covered AI vendor, OR infrastructure where the AI never sees identifiable PHI — de-identification before processing, re-identification after, with strict audit trails.
Different posture per workflow
A front-desk insurance verification workflow has different BAA requirements than a clinical note transcription workflow. The compliance posture has to be designed in, not bolted on.
The BAA execution workflow isn’t theoretical. We have it built out — DocuSeal template, redline process, signed-copies archive, BAA chain framework — built and used in our active healthcare scoping work. The HIPAA framework is the same across dental and other healthcare specialties; the specialty-specific details are what scoping is for.
DENTAL-SPECIFIC CONSIDERATIONS
We’re aware of these. The Consult engagement maps your specific exposure. For the broader HIPAA / BAA framework across healthcare practice types, see our healthcare practices overview.
A Build engagement, week by week.
Scoping
Read-only access to your PMS, billing, and existing automation. Workflow mapping: where time actually goes, which tasks are AI-amenable, which aren’t. Vendor and tech-stack decisions.
Output: written build plan, fixed end date, fixed price
Build
Integration work against your PMS (API or middleware). AI workflow development in a non-production environment. BAA execution with vendors that touch PHI. Internal staff walkthroughs as the build progresses.
Output: tested workflow ready for pilot
Pilot & iteration
Live deployment on a single workflow — we don’t ship eight things at once. Real-data validation, error catching, edge case handling. Iteration until it actually works at your volume.
Output: production workflow at your real volume
Expansion or handoff
Either we ship the next workflow on the original plan, or we hand off the system — fully documented — for your in-house team or any other vendor to take over.
You own everything we build
You own the code, the data flows, the integration points. The Manage service (ongoing monitoring, retraining, updates) is optional. A practice can either take Manage or hand off to in-house IT or MSP after a transition period.
Published numbers. No “starting at” trickery.
$5K–$15K
2–4 weeks · written build plan
For a dental practice scoping engagement. Output is a written build plan with prices. Best if you want an unbiased read before you commit to a Build.
$25K–$150K
4–12 weeks · per scope, not per hour
For a typical single-practice dental AI build. Multi-location groups run higher because integration complexity scales with sites and systems.
$3K–$8K/MO
Optional · ongoing
For ongoing operations on what we built. Most one-doctor practices don’t need this; multi-doctor groups usually do. Not required.
Where in the range you land depends on the PMS you’re on, how many workflows we’re building, how clean your existing data is, and whether you have anyone in-house who can co-own the system.
Ironworks AI is an early-stage Virginia startup. Our first live Build engagement shipped in 2026 — operations infrastructure for a professional services firm — and we have healthcare proposals in motion. If you’re talking to other dental AI consultants, ask them what they’re going to do with your insurance verification when the payor changes their portal layout, and how they handle BAAs when the AI vendor changes their terms. The good ones will have answers. The not-good ones will pivot to talking about transformation.