A single AI engine running every workflow behind your practice — front desk, scheduling, billing, hiring, growth — whether you operate one location or fifty.
Each agent runs its own workflow but writes to a shared canonical substrate — so a recall booked by Patient automatically threads through Schedule, Treatment, Revenue, and Finance without anyone reaching across systems.
72%
A single execution engine reading from a canonical data contract, indifferent to which practice management system feeds it. Switch sources without restarting agents. Add new ones without rebuilding.
Affetto is source-agnostic. Connect to any practice management system, EHR, billing platform, imaging system, or custom internal tool. The list above is illustrative — the architecture supports n+1 sources.
The next decade of dentistry will be defined less by the care delivered and more by the operations that make care possible at scale.
Five forces are reshaping dental at once — and converging on the same problem: the operational layer between the practice floor and the business that runs it.
Roughly a hundred thousand independent practices will change hands this decade. The capital is there. The integration playbook is not.
Every acquired practice arrives with its own PMS, its own coding habits, its own front-desk rituals. The work that decides the deal isn't due diligence — it's the operational thread that has to run, day one, across systems that were never designed to talk.
Each transition is a six-month operational rebuild — fee schedules renegotiated, statements rewritten, payment plans reworked, every patient re-explained the math. About a quarter of practices that start the conversion abandon it before it finishes.
The bottleneck is not strategy. It is bandwidth.
A two-operatory practice runs four nonclinical roles: front desk, scheduling, billing, and an office manager who covers everything that breaks. The cost of those roles has outpaced the cost of the care delivered inside the rooms behind them.
Turnover at twelve to eighteen months is the operating norm. Every departure is another integration, in miniature.
Until recently, software described work. It surfaced fields, ran reports, kept the books — and waited for a human to act. That contract held for forty years.
Foundation models can now perform the work, not only describe it: read the message, decide the response, draft the claim, schedule the call, follow up on the answer. The interface is now optional.
The tooling layer has multiplied without unifying. A mid-size practice runs eleven active subscriptions on average. Every one of them is good at the slice it owns. None of them speak to each other.
Adding a twelfth tool does not make the stack better. It makes the seams between tools the dominant cost.
None of these are new on their own. What's new is that they're all landing in the same place at the same time.
Operational headcount no longer scales linearly with footprint. The same engine that runs one practice runs ten.
The same engine spans diligence, transition, and steady-state. New practices go live in 21 days, not 6 months.
Practice operations and business operations on the same data substrate. No reporting cycle. No spreadsheet truth wars.
Open to practice owners, group operators, DSOs, and institutional investors. We are taking on a small number of partners ahead of public release.
Founders read every reply.