AI that answers new patients and clears the referral and prior auth paperwork.
We build AI for medical and dental practices that answers new patient questions at any hour, reads incoming referrals and faxes into your practice system, and fills in prior authorization forms for your staff to check. The records and paperwork work runs on a machine in your practice or in your own cloud account, so patient files stay in systems you control.
What we hear from medical and dental practices
The fax machine is where referrals go to wait.
Prior authorizations take a person most of every afternoon.
We cannot send patient details to some AI company's server.
The work we take off your team's desk first.
Each of these is a service we build on systems you control, test on your own data, and look after. A person stays in charge of every decision that matters.
- 01AI phone line
New patient questions, at any hour
New patients ask the same few things: are you taking patients, do you take my insurance, where are you, and what should I bring. The voice agent answers those from your own material on your website or your phone line, takes the caller's details, and hands the front desk a clean list in the morning. Scheduling into your calendar and transfer to a person are connected as part of the build, set up the way your front desk works.
AI that talks to your customers
- 02AI integrations and custom software
Referral and fax intake
Referrals, records requests and lab results arrive by fax and email in every layout there is. We build intake that reads each one, matches it to the patient, pulls out the referring provider, the reason and the insurance, and files it in your practice system or queues it for the person who handles it. Anything it cannot match waits for your staff.
AI that does the work
- 03AI staff
Prior authorization paperwork
The same clinical details retyped into each payer's web form, then a status check every few days until it moves. The agent fills in the form from the chart, stops for your staff to review before it submits, and checks back on the status so nobody has to remember to.
AI that does the work
Patient information stays in systems the practice controls.
Protected health information is the whole conversation in this trade, and the right instinct is to keep it away from services the practice has not vetted. The AI we build runs on a workstation in your practice or in a cloud account in the practice's own name. The record moves from your practice system to that machine and back, and no AI vendor holds it.
Your clearinghouse and payer portals are outside the building already. The agent works them from a machine inside your network with the same logins your biller uses, and it gets only the accounts the task needs. That list is written down before the build starts and is short enough for your privacy officer to read in a minute.
HIPAA compliance is something a practice does, through its policies, its risk analysis and its agreements, and your privacy officer owns it. We make that work easier: a written description of where the model runs, what it can reach, what it logs and who has support access, ready for your risk analysis. Any support access is agreed with your privacy officer in writing before it begins.
Other work we build for medical and dental practices.
Once the first job is running, these are the next ones worth handing over. Each links to the service that does it.
Eligibility on tomorrow's schedule
Tomorrow's list run against each payer's portal and the answer typed back into the chart, so the front desk starts the day knowing who needs a conversation about coverage.
Posting remittance advice
Allowed amount, adjustment and patient responsibility posted line by line into the practice management system, with anything that does not balance stopped for a person and denials sent to a work queue.
Policy and protocol questions for staff
Office policies, payer rules and clinical protocols searchable and answerable on a machine in the practice, so staff can ask a question in plain words without pasting anything into a public tool.
An AI policy for staff already using chat tools
A short inventory of the AI tools your staff already use, a written policy your privacy officer can adopt, and a private tool that replaces the consumer ones.
The services that do the most for medical and dental practices.
Ranked by how much of the day each one gives back, with the reason beside it. The free AI review ends with a written page that puts your own firm in this order.
- 01
AI phone line
AI that talks to your customers
The after hours calls are the ones that turn into new patients when somebody answers.
- 02
AI integrations and custom software
AI that does the work
Referral and fax intake that reads the document and files it where it belongs.
- 03
AI staff
AI that does the work
Prior authorizations, eligibility and remittance posting, each ending on a person's check.
- 04
Private AI
Private AI
Policy questions and chart summaries answered on a machine in the practice.
- 05
AI readiness and policy
AI strategy and leadership
A written AI policy and a plan, for the practice whose staff are already using chat tools.
The engine under the AI staff is ours.
Most firms selling AI to an office resell somebody else's tool. Our engineering team writes and ships its own, and the agent that would work your screens runs on it.
DeskVNC
In active developmentRemote desktop access and tools that let AI agents see and operate computers, with permission and human takeover.
- Remote desktop connections
- MCP tools for viewing and input
- Human takeover controls
Computer control connected to an AI workflow
psmux
A native Windows terminal multiplexer for persistent sessions and coding agents.
- Native Windows terminal sessions
- Panes and layouts
- Detach and reattach workflows
Engineering tools built around how developers work
What medical and dental practices ask us first.
- Is this HIPAA compliant?
- HIPAA applies to what a practice does rather than to a product. What we give you is architectural and checkable: the model runs on a machine you own or in your own cloud account, and protected health information is not sent to an outside AI service. We document that for your privacy officer's risk analysis.
- Would we need a business associate agreement with you?
- That depends on the access you give, and your counsel decides. A model running on your own hardware keeps patient data in your hands. If you want a support plan that includes remote access to that machine, we settle the paperwork with your privacy officer before it starts.
- Can the voice agent book an appointment?
- Yes. The AI phone line books into your calendar and passes urgent calls to your phone. It runs on our ElevenLabs voice account, so we agree with your privacy officer what callers are asked and what is kept before it goes live.
- Which systems does the agent get logins to?
- Only the ones the task needs, with the same permissions as the person who does that job now. An agent submitting prior authorizations gets the payer portals and the chart access that task requires. The list is written down before the build starts.
Start with a free AI review.
Thirty minutes with the engineers who would build it. Bring the job your team most wants off its desk, and you leave with a written page you keep: what we would build first, which systems it touches, and where your data stays.