Custom AI implementation

What this quote is not

Not an AI phone product, not ambient clinical notes, not imaging tools, and not a compliance audit. You contract your own vendors. PXC does not take patient information and does not sign your vendor agreements.

What kinds of work get quoted?

Small, named jobs that the AI Audit already said were safe. Examples PXC will talk about: a callback queue that a tool can sort only after a human owns the clock; reminder language your staff approve; a training checklist a new hire can open on day one; a draft reply a manager still has to send. Examples PXC will not quote: anything that needs a patient chart, a diagnosis, or a clinical decision.

The article where AI helps the front office is the plain version of that line. The guide is your practice ready for AI is the long version. Neither one is a statement of work.

How does pricing work?

Jennifer writes the scope from the findings: what will be built, what will not, who at the practice has to approve words, how you will know the trial is done, and what happens to the work if you stop. The fee is one number tied to that scope. If a vendor has to configure a system, you hire the vendor. PXC can write the workflow the vendor should support. PXC does not become your EHR consultant, your phone vendor, or your biller.

There is no minimum published here on purpose. A minimum becomes a dare to stuff the scope. If the honest fee is small, the quote is small. If the honest answer is "not yet," there is no quote.

What has to be true first?

An owner for the job the tool would touch. A clock staff already try to hit. A close state, meaning someone can say the item is done. A way to test with fake examples. If those are missing, the AI Audit's recommendation is the Practice Audit and the Reset, not a build. You can ignore that advice. PXC would rather not take the work.

Jennifer's AI Hero certificate sits next to 21 years of running practices, not instead of them. The certificate does not mean every desk needs a model. It means she can tell a demo from a workflow.

What does a statement of work have to say?

The job in one sentence. The inputs, which will be fake or de-identified workflows, never a chart. The person at the practice who approves words before anything reaches a patient. The stop condition, meaning how you both know the trial is over. What PXC will not configure. What a vendor still has to do, under your contract with that vendor. The fee as one number.

If those lines cannot be written, there is no project. Jennifer would rather return you to the AI Audit than invent scope in a kickoff. A fixed fee protects both sides from a wandering pilot. There is no rate card hiding under the quote, and no minimum designed to fill a week.

What kinds of trials stay small on purpose?

A callback sort that a human still closes. A reminder draft a manager edits. A checklist for day one of a new hire. Each of those fails safely, because a person still owns the close. A trial that sends messages with no human is out of scope until the readiness note says the clock and the owner already exist. Even then, public review replies stay human. Privacy rules are not a feature you toggle off.

What does done look like?

The trial ran on fake or approved examples. The named approver signed the words. Staff can point to the close, meaning a human still finishes the job or the readiness note already said a human did not need to. You have a written stop, not a subscription you forgot. If a vendor configured something, you hold that contract, and PXC's scope did not quietly become "call the vendor for us every week."

If done is fuzzy, the quote is not ready. Send it back. A second draft of a quote is cheaper than a wandering build. Jennifer would rather delay the kickoff than start on a metaphor. The AI Audit is the document the quote has to match. If the audit said not yet, implementation does not start, even if a vendor is offering a discount this month.

Prices for the audits stay on their own pages. This page stays unpriced on purpose. When a number appears, it will be in a statement of work for one practice, not in a menu.

Ask these questions before you sign a quote. Who approves words? What is the stop date? What is fake data, and who checks that no real patient detail slipped in? Which vendor contract stays in the practice's name? If the quote cannot answer those in sentences a manager can repeat, it is not ready. Jennifer would rather rewrite it than start. The Reset remains the right scope when the real problem is three dominoes, not a tool. Say that out loud if the quote starts to look like a second Reset with a software label. Budget a manager's time in the quote as well as the fee. Someone at the practice has to approve words and watch the first week. If that person does not exist, the project waits. A build with no approver becomes a vendor default, and vendor defaults are how front desks end up apologizing for messages they did not write. Keep the first trial small enough that stopping is easy. A small stop is a success condition, not a failure. If the first trial needs a second phase, that phase is a new quote, not an assumption. Say what changed, what the approver learned, and what you will not expand. Expansion without a new stop date is how a small trial becomes a retainer you did not mean to buy. PXC will not slide into weekly hours. The offer is a fixed scope or no scope. Take the Reset if the honest need is training and ownership. Take implementation only when the readiness note named a job that is safe to try. Those are different purchases, and the site keeps them on different pages so the choice stays visible. If you are unsure which page you are on, you are not ready to sign a build.

Questions people ask