What I build

Software for healthcare and clinics

Online booking and reminders

Patients book, reschedule and cancel online, with SMS and email reminders that cut no-shows and phone calls.

Digital intake forms

Intake, consent and history forms completed before the visit and waiting in the record, instead of clipboards at the desk.

Patient portal

A secure place for patients to see appointments, documents, invoices and messages.

Front-desk and admin tools

One view of the day: who is booked, who has paid, which forms are missing and what needs a follow-up.

Recall and follow-up workflows

Automatic recall reminders and follow-ups so returning patients don't slip through the cracks.

Practice reporting

Bookings, cancellations, revenue and capacity in one dashboard, from the data you already have.

AI, right now

Where AI genuinely helps

Small practices run on a mix of a practice system, phone calls, paper forms and spreadsheets. The pressure points are the same everywhere: booking and no-shows, intake paperwork, follow-ups and a front desk stretched thin. AI scheduling, digital intake and automated reminders are now standard expectations, according to recent buyer guides for small clinics.

I haven’t built for healthcare yet, so I won’t pretend otherwise. What I bring is the same building blocks I’ve shipped for real clients, shown below.

  • An assistant for patient questions

    Answers opening hours, preparation and policy questions from your own documents, and hands anything clinical to a person.

  • Smarter scheduling

    Suggests slots based on provider availability and appointment type, and fills cancellations from a waitlist.

  • Paperwork into data

    Referral letters and scanned forms read and turned into structured fields for staff to check.

  • Admin drafting

    First drafts of routine letters and follow-up messages for staff to review before anything is sent.

Similar work

Data, security and access

  • Patient data (PHI) is only stored with providers that sign a Business Associate Agreement, for example Supabase's HIPAA add-on, with its required settings switched on.
  • Access is limited by role and enforced on the server, with audit logs on sensitive actions.
  • AI never makes clinical decisions; it drafts and sorts, and staff decide.
  • HIPAA and GDPR compliance is shared: the software supports it, and your practice's own policies complete it.

How a project runs

  1. Call

    A 30-minute call about what you need, who it is for, and what success looks like.

  2. Scope

    A written scope: features, architecture, timeline, price range and risks.

  3. Build

    Working increments you can click through, not a big reveal at the end.

  4. Ship

    Live on your domain and hosting, with a handover so you know how it runs.

More in how I work, or see mvp and saas development.

Questions

Common questions

Can you build HIPAA-compliant software?

I build software that supports HIPAA requirements: patient data only on providers that sign a BAA, encryption, role-based access and audit logs. Full compliance also depends on your practice's policies, training and risk analysis, which stay your responsibility.

Why custom instead of an off-the-shelf practice system?

If a practice system fits, use it. Custom tools make sense when your workflow is unusual, when you need to connect several systems, or when you need a patient-facing experience the off-the-shelf tools don't offer.

Can it work alongside our existing EHR?

Often, through the EHR's API or exports. Which data moves where is decided in the scope, after looking at what your system allows.

How much does it cost?

A focused first version is a fixed-price project, scoped and priced after a 30-minute call (MVPs start from $3,000). Ongoing work can run on a monthly retainer.

Want booking, intake or admin that fits your practice?

A 30-minute call is enough to tell whether it fits, what the first version should include, and how long it takes.

Book a 30-minute call