charmthirteen.com
    Build · Training

    Keep the humans.

    You bought the tools, your people barely use them, and nobody can say where AI actually belongs in the work. charmthirteen figures out where it belongs, what problem it should solve, and what has to change for it to work. Then we build it so the people you already have get sharper and stay in charge, and we prove that in healthcare and government, where getting it wrong has a cost.

    status.txt
    Booking builds and training
    Limited spots open

    "AI that makes people more capable and keeps them in charge."

    Schedule a Vibe Check →
    problem.txt
    The real problem

    You don't have an AI problem. You have a systems problem.

    Most teams:

    • Use too many disconnected AI tools
    • Don't know what should (or shouldn't) be automated
    • Risk data privacy, compliance, and accuracy issues
    • Waste time on workflows that don't scale

    That's where I come in.

    Safe, efficient, and usable. In that order.

    how_it_works.exe
    How it works

    You do not have to know what you need before you call.

    Step 01Vibe CheckTwenty minutes, free. You describe what is not working, we tell you what we see, and we decide together whether Discovery is worth your time. Bring the problem, not the diagnosis.
    Step 02DiscoveryThe diagnosis. We sit with your workflows, your constraints, your data, and your rules, then name what is actually broken and what is worth fixing. Discovery decides whether the answer is training, a workflow change, an automation, a build, or a combination, and nothing gets designed before it does.
    Step 03Blueprint, then BuildDiscovery decides what the work is. From there it is a Blueprint you own, a build that runs on your accounts, training for your team, or some mix of the three, and the scope is written down before you commit to any of it.

    Depending on what Discovery finds, it turns into one of these, or a combination:

    • Training your team, so the tools you already pay for get used well
    • A Blueprint you own, so your team or any vendor can build from it
    • A build that runs on your accounts, so the manual work stops being manual

    You do not get sold a service. You get matched to a solution, and the scope comes after discovery instead of before it.

    who_this_is_for.txt
    Who this is for

    Built for teams where a wrong AI output reaches a patient, a claim, or a citizen.

    Compliance, accuracy, and trust aren't optional. Neither is structure.

    Health systems and clinical teamsRolling out ambient scribes or AI inside clinical and revenue cycle work, where a wrong output lands in a chart or a claim.
    Federal health agenciesAdopting AI inside locked-down environments where the tooling, the data, and the oversight are all constrained.
    Healthtech foundersBuilding products that have to survive clinical review, procurement, and a security questionnaire.
    orinyx.exe
    Healthcare · Design partners open

    Orinyx. Independent verification for clinical AI, before it reaches a patient.

    Orinyx is the first product out of the charmthirteen studio, built from a question the advisory work kept running into. Hospitals wanted an independent way to test clinical AI before deployment, and no one could give them one. Orinyx checks every AI assertion against authoritative sources instead of another model's judgment, so each verdict is deterministic and arrives with a citation.

    • Phase 1 runs in a sandbox on synthetic data, no PHI, no EHR connection
    • Deterministic verdicts with citations showing what was checked
    • Findings documented for governance review
    • Design partner pilots open now
    claude_loves_lovable.exe
    Workshop series

    Claude Loves Lovable

    A founder-focused vibe coding series on shipping real product with Claude and Lovable. Five live sessions, and every one ships a Claude skill you keep.

    Build

    You do not have to know what you need yet.

    Discovery decides what the work is. Two lanes, published prices.
    different.txt
    What makes this different

    Most AI consultants have never watched a clinical workflow break in production.

    EHR solution and configuration analysis
    Healthcare data product management
    Clinical AI governance research

    That background is why the recommendations hold up after I leave the room.

    Final call

    If your team is serious about AI, you need a system.

    Let's build it right.