Administration is where the hours go.
In a clinic the clinical work is the work. Everything around it (intake forms, scheduling, reminders, referrals, the same call three times) is overhead that has to happen and that nobody trained for years to do. That overhead is what should come off your team, and the clinical side is what should be left alone.
- Typical first build
- Intake and scheduling
- Touches
- Forms, calendar, reminders, referrals
- Never touches
- Triage, advice, clinical decisions
- Compliance
- Yours to verify; we build to it
Where healthcare & clinics loses inquiries.
Intake, scheduling and reminders taken off your team. Clinical work left alone.
Intake happens twice
Once on a form, once again verbally because the form did not reach the right place or was not read before the appointment.
No-shows are scheduling, not attitude
Most missed appointments are a forgotten date rather than a decision. Reminder sequences and easy rescheduling move the number; blaming patients does not.
Referrals fall between two systems
Sent, then unaccounted for. Nobody owns the follow-up because the follow-up lives in whichever system is not currently open.
The phone competes with the room
Whoever is answering calls is also doing something else. Call volume does not arrive in the gaps.
The builds that fit this sector.
Each of these is bought on its own. Most practices start with whichever one is costing them the most right now.
- 01
Intake collected once, before the appointment
Digital intake that arrives where it is needed, in a structured form, so the appointment starts on the clinical question rather than on data entry.
- 02
Appointment reminders and easy rescheduling
Timed reminders on the channel the patient actually uses, with rescheduling that does not require a phone call at 9am.
- 03
Referral follow-up that has an owner
Referrals tracked to an outcome, with a flag when one has gone quiet for longer than it should have.
- 04
Phone overflow answered
Routine scheduling and access calls handled automatically, everything else routed to a person quickly, nothing left to voicemail.
- 05
Administrative workflows connected
The tools the clinic already runs, wired together so the same information is entered once.
Out of scope, deliberately
Clinical judgment stays with clinicians.
We automate administration. These systems do not triage, do not assess symptoms, do not advise on treatment and do not influence a clinical decision. Anything presenting as urgent reaches a person immediately. We will decline work that asks a model to stand between a patient and a clinician.
Our experience here
Braav Labs has not yet delivered a completed healthcare engagement. The dental build currently in progress is the closest adjacent work. We would rather say that here than imply a history in a sector where a false claim of experience is a genuine risk to patients.
AI in healthcare & clinics, this week
From the news, daily
- More time for patients with Ambient AI ScribeMetro South Health · Oct 21
- Israel launches AI system for communication with children in hospital — Jerusalem PostUA.NEWS · Oct 20
- New study reveals AI chatbots recognize unnecessary medical tests, but stumble where human doctors disagreeMedical Xpress · Oct 20
- AI model predicts cancer patients’ death risk from single photoThe News Pakistan · Oct 20
- Iowa hospital expands colon cancer screening with AI technologyAmerican Hospital Association · Oct 20
- Building the AI HospitalAmerican Enterprise Institute - AEI · Oct 20
Questions from healthcare & clinics.
Compliance is a property of a specific deployment, the tools in it and the agreements around it, not something a service can claim in advance. We build to the requirements your compliance advisor sets, keep the data a system touches to the minimum, document where everything lives, and support your review. We will not tell you a system is compliant on your behalf.
Not in anything we build. Symptom discussion, triage and urgency assessment are clinical, and they escalate to a person. The systems handle scheduling, access and logistics.
It escalates immediately on defined triggers, and 'I am not sure what this is' is one of them. The design assumption is that the cost of an unnecessary escalation is far lower than the cost of a missed one.
In systems you own and control. We scope what a system touches before it is built and document it. Nothing lives in a tool only we can see.
Want this looked at against how your practice actually runs?
Get my free auditHow an engagement runs.
The same five steps whatever we are building, so you always know which one you are in.
- Pricing
- Fixed price, quoted after a scope call
- You have the number before anything is built. Nothing is billed by the hour.
- Timeline
- A date at quote time
- Stated as a commitment, not an estimate that drifts once work starts.
- Ownership
- Everything stays in your name
- Domains, hosting, inboxes and every account, on your billing, documented.
- 01
Scope call
Twenty minutes on how inquiries reach you today. No deck, no discovery package.
- 02
Written scope and a fixed quote
What gets built, when it lands, what it costs. Fixed before anything starts.
- 03
Build and review
You see it working on your own content, not a screenshot of it working.
- 04
Launch and handover
Accounts in your name, a written record of what runs where, a walkthrough.
- 05
Support, if you want it
A separate decision, made after something is already running.