For Marketing

The headline, and the caveat that has to come with it

"Ask Claude about your clinic" is a genuinely compelling story — but this is Phase 1 of a multi-phase build, marked draft by its own author, and not deployed anywhere yet. Nothing here should be marketed as available. When this does ship, the honest scope of what it can do on day one is narrow:

A doctor can connect Claude to their clinic and ask about inventory — current stock, what's been used recently, and what's being spent with suppliers. That's it, for now.

Do not imply Claude can answer questions about patients, appointments, finances, or clinical notes. The groundwork for those exists (the scope system already has finance:read, appointments:read, patients:read, and clinical:read defined), but zero tools use any of them yet. Overpromising here is the kind of gap a customer discovers on day one of actually trying it.

What's genuinely a good story

• "Ask, don't export." The realistic before/after is: exporting a stock

report to a spreadsheet and eyeballing it, versus asking "what's running low?" in plain language and getting a direct answer.

• Security-first framing is earned, not just asserted. This isn't a

chatbot with database access — it's a read-only database role that physically cannot write, plus row-level security that fails closed. That's a genuinely strong, specific claim, and it's backed by an actual test suite (a two-clinic data-leak suite) rather than marketing language. See Tenant isolation and the read-only role.

• No new login to learn. The doctor connects with the same credentials,

the same 2FA, the same everything they already use. There's a real "nothing new to teach" angle here for onboarding messaging, once it ships.

• Permissions carry over exactly. If a clinic has decided a receptionist

shouldn't see stock values, that's still true when they ask Claude. This is a subtle but real trust point for owners worried about staff overreach.

What to avoid saying

• Anything implying this works today — it's an unmerged, unreleased draft PR.
• Anything implying Claude can write, edit, or delete records. It cannot, by

design, in every phase currently planned as "Phase 1."

• Anything implying broad data access ("ask Claude anything about your

clinic"). Today it is inventory only.

• A specific list of supported questions as exhaustive — the three tools

(stock levels, consumption, supplier spend) support a range of natural phrasings of the same underlying report, not a fixed command list, but they don't cover topics outside inventory at all.