Manual operational work
Repetitive copying, re-keying, and status chasing that consume time without creating proportional value.
AI AUTOMATION SPECIALIST · CHICAGO
I bring clinical-grade process discipline to workflow automation—translating operational reality into reliable code, explicit controls, and systems people can trust.

PROBLEMS I SOLVE
I look beyond individual tasks to find the broken handoffs, hidden rules, and missing controls affecting the wider system.
Repetitive copying, re-keying, and status chasing that consume time without creating proportional value.
Business data trapped across tools that do not communicate reliably or preserve one clear source of truth.
Automations that depend on ideal inputs and fail without clear recovery paths when reality changes.
Processes with limited monitoring, unclear ownership, and no usable record of what happened or why.
Critical rules held in people’s heads instead of being expressed in maintainable processes and software.
Clinical research made process discipline non-negotiable. Work must be traceable. Exceptions must be visible. Human accountability cannot disappear behind software.
I now apply that operating mindset to AI automation—starting with the process, encoding business rules in software, and validating the system before calling it reliable.
WHY MY BACKGROUND MATTERSEight years in regulated clinical research taught me that systems must be accurate, traceable, documented, and accountable. I bring that same discipline to AI automation.
Current-state mapping, waste diagnosis, requirements, risk, and future-state design.
n8n, APIs, JSON, Supabase, structured model outputs, routing, and failure recovery.
Human approval boundaries, audit trails, data controls, tests, and observable execution.
Study startup through closeout, CTMS/eTMF, monitoring, data quality, and inspection readiness.
SELECTED WORK
Each case study shows the business logic, implementation evidence, and current proof boundary.
View case study ↗Evidence produced
View case study ↗Evidence produced
View case study ↗Evidence produced
FIXED-SCOPE SERVICES
Diagnose before changing. Design before building. Implement one bounded workflow before expanding into an operating system.
01 · DIAGNOSE
Identify failure modes, missing controls, exception paths, and prioritized remediation before changing production systems.
02 · DESIGN
Turn one process into a decision-ready future state, architecture, phased backlog, acceptance criteria, and ROI assumptions.
03 · IMPLEMENT
Engineer one bounded workflow with approved rules, integrations, validation, exception handling, testing, and documentation.
04 · SYSTEMIZE
Begin with paid discovery, then design a tested prototype or bounded multi-system MVP with clear human accountability.
Specialized workflows are also available for invoice intake and reconciliation, AI lead qualification and CRM routing, and agriculture procurement operations.
HOW I WORK
AI is not the starting point. The work begins by understanding how value moves through the business and where waste, risk, and unclear decisions interrupt it.
See how work actually happens.
Quantify the waste and baseline.
Simplify before adding software.
Prove value and protect judgment.
Encode the approved logic reliably.
Monitor evidence and iterate.
EXPERIENCE
MBA, Healthcare · Careerist AI Automation Specialist Program
Building governed AI operational systems that begin with process discovery and measurable waste, then translate approved business rules into version-controlled software with validation, exception handling, human approval boundaries, observability, and documentation.
Mapped manual workflows and operational bottlenecks, built n8n and Make.com automations using the OpenAI API, and documented system performance, error handling, and client handoffs.
Progressed from structured study intake and site coordination to oversight of clinical-trial execution. Monitoring protocol deviations taught me to design explicit error handling, escalation paths, and human review into software. Source-data verification and discrepancy resolution became validation, reconciliation, and traceable decision records. CTMS/eTMF discipline shaped how I approach audit logs, documentation, access controls, and change history. Coordinating sites, vendors, and stakeholders reinforced the need for clear ownership, reliable handoffs, and visible operating status in every system I build.
WORKING STACK
LET'S BUILD SOMETHING USEFUL
I'm open to AI automation, clinical technology, operational excellence, and systems implementation opportunities.