Seven steps from a 20-minute call to a system your team runs without us. The same shape for every offer, so you know what happens next before you've spent a dollar.
You describe the workflow that hurts. We ask what it costs you and what data you have on it. Then you get a straight read: AI problem, data problem, operations problem, or none of the above. If it's real, you hear the fitting offer and its price on the call.
Your situation in your words, what gets delivered, the schedule, what we need from your team, how data is handled, and a fixed price. Every proposal has an expiry date and written acceptance criteria, so "done" is defined before anything starts.
Work starts when the deposit lands. Kickoff is 45 minutes: we restate the acceptance criteria, name one point of contact on each side, collect access and data on the call, and put the mid-point demo and the final readout on both calendars.
On the Sprint and the Diagnostic, if by day three the work clearly won't pay for itself in findings, we say so and refund the deposit. It rarely happens. It's in writing so you can plan around it.
Five lines: done, next, blocked, decisions needed, on track or not. Anything outside the agreed scope becomes a written change order before it's built. Nothing is called finished until it has been watched working on your real cases.
We walk the acceptance criteria one by one, live, on your data. For the Sprint and the Diagnostic, the readout is a board-ready document with three paths forward and an honest recommendation, including "you don't need us for the next step" when that's true.
Your team gets the documentation, a recorded training session, and thirty days of defect fixes after acceptance. Optional maintenance runs $500 to $1,500 a month. The goal is your team running the system on their own.
No. Every engagement is a fixed price or a monthly retainer, with written scope and acceptance criteria agreed before work starts. Scope changes are priced as written change orders, never absorbed silently or billed by the hour.
By default, no. Early engagements are structured to be PHI-free: architecture, roadmaps, de-identified or synthetic data, and operational workflows. When PHI is genuinely required, we work under a signed BAA with active E&O and cyber insurance and documented security basics.
Tyler Kent, personally. AI development tools are used under his review to move fast, and every client-facing deliverable is his. Each statement of work states plainly how and whether AI tools touch your data.
Usually within two to three weeks of a signed agreement and deposit. We run a small number of engagements at a time so each one gets senior attention, so start dates are confirmed in the proposal.
You'll hear that on the first call. Many problems are data problems, operations problems, or policy problems. We say which one it is and point at the cheaper fix when there is one.
Yes. Healthcare is the deepest specialty, but AI strategy, data platforms, analytics, and AI-enabled applications apply to any serious organization. Most non-healthcare work arrives by referral.
If by the end of day three the engagement clearly won't pay for itself in findings, we say so and refund the deposit. The goal is engagements that are obviously worth it in hindsight.
One point of contact, about three hours of interview time across two or three people in the first week, and system access or data extracts by the dates in the statement of work. Access delays are the most common reason timelines slip, so they're agreed up front.
San Diego, California. Engagements run remotely across the United States, with on-site sessions by arrangement when a kickoff or readout benefits from being in the room.
Documentation and training are deliverables, so your team can run what was built. Thirty days of defect fixes are included after acceptance. Optional maintenance runs $500 to $1,500 a month, and many clients continue with a fractional AI lead retainer.
Twenty minutes. Bring the workflow that hurts and what you think it costs you.
Or connect on LinkedIn.