About Ryan

Healthcare IT experience. AI-first development.

I spent 20 years around hospital systems, pharmacy technology, EHR workflows, clinical software, implementation projects, support teams, and operational users, including work connected to Cerner, Epic, and VA systems. That experience taught me how complex businesses actually run and where technology usually breaks down.

Background

Built from real operational experience.

My work has included pharmacy systems, clinical software, EHR/EMR workflows, interfaces, technical support, QA, end-user training, client requirements, and healthcare implementation environments. That background is why RPR-DEV starts with operational reality before recommending any AI tool.

Practical first

AI should make the work easier, not harder to explain.

Business-aware

Tools need to fit the actual operation, not just look good in a demo.

Builder-led

RPR-DEV is a consulting practice and a product lab.

Why RPR-DEV exists

Practical AI for operators, not demos for demos' sake.

RPR-DEV was started because small businesses do not need another vague AI pitch. They need a builder who can look at the actual workflow, identify the bottleneck, and ship something useful. That may be an AI Business Audit, a website with AI built in, a phone answering system, a document workflow, or a custom internal operating layer.

CanopIQ

Crop intelligence and plant-health systems for controlled-environment agriculture.

Still

Barrel tracking and TTB compliance workflows for craft distilleries.

MIST

AI-assisted sales agents, lead research, and human-approved outbound workflows.

GoKC

Multilingual visitor guidance and local discovery concepts for Kansas City events.