How this works, and what happens to your data.

Common questions

01 Do you sign a BAA?

Not today. I am not taking on work that involves protected health information yet, so there is nothing for a BAA to cover. When I do, signing one before I touch a single record is a precondition, and so is having the same agreement in place with every provider in the path, as spelled out in the Privacy Policy. I would rather say that plainly than promise a signature I cannot deliver this week.

That said, right now I'm not taking on medical or dental practices while I get professional liability coverage in place first. See the note on insurance below. If that changes for your business, ask and we'll talk through it honestly.

02 Does it connect to my scheduling software or point-of-sale system?

Be honest about this before anything else: today, no. The AI receptionist books onto its own dashboard, not into a third-party system like a salon booking app, a shop's point-of-sale, or a practice management system.

In practice that means one of two things, and I'll tell you straight which one applies before we build anything:

• If your team is comfortable checking one more screen (the dashboard) alongside what you already use, this is a non-issue.
• If everything has to live in one system or your staff will end up double-entering appointments, say so up front. That's a real cost, not a detail, and I'd rather scope around it or tell you it's not a fit yet than oversell it.

If you don't have any digital calendar at all today, paper book, whiteboard, whatever, that's fine too. The dashboard can be the first digital system you get, not a replacement for one you already trust.

03 Where does my data live, and who touches it?

A short, honest list of every category of company that ever sees anything, with no vague "trusted partners" language:

• The AI itself: Claude, running through Amazon Bedrock. Bedrock is covered by AWS's own Business Associate Agreement, so PHI-capable infrastructure sits under AWS's compliance program, not a bolt-on.
• Hosting: Amazon Web Services (AWS), industry-standard cloud infrastructure with encryption in transit and at rest.
• Telephony: Twilio, which routes the text messages themselves.

Your data is never used to train AI models, mine or anyone else's. It's used only to run the thing you asked me to build, nothing more.

04 What insurance do you carry?

I don't have general/professional liability insurance in place yet, and I'm being upfront about that rather than implying coverage I can't back up. It's why I'm currently not taking on medical or dental clients, where that coverage matters most. For the kind of work I take on, the risk is bounded by what I actually touch: I don't hold your money, I don't have access to systems beyond what a build specifically requires, and you can turn the whole thing off at any time by reverting your call forwarding.

05 What happens if either of us walks away?

You own what gets built. If you want to stop working with me, you can turn it off by reverting your call forwarding, and I export your data for you. There's no lock-in contract on the build itself, and the optional care plan cancels anytime, no penalty, no exit fee.

If I need to step away from your account for any reason, you get advance notice and a full export of your data before anything is deleted. Nobody gets surprised.

06 Do you have a reference I can call?

Not yet, and I won't pretend otherwise. I'm early. If you work with me, you'd likely be among my first clients in your line of work. What I'll do instead of a fake testimonial: a fixed price agreed up front, a written one-page scope before I start, and a direct line to me the whole way through, not a support queue. If a reference matters to your decision, ask me who I've built for so far and I'll tell you straight, good or bad.