I didn't start out building automations. I started out running the operations that automations are supposed to fix.

At Spectranet, I worked in customer operations, my first real exposure to how messy service delivery gets at scale. At AfyA Care / R-Jolad Hospital Network, I led hospital operations and billing across seven facilities with a team of 40+, which is where I got obsessed with the gap between the systems clinics use and the systems they actually need.

These days that gap gets closed with n8n, Make.com, Zapier, and LLM-assisted full-stack development. The tools came later, the instinct to fix broken systems came first.

At Dabik Technologies, I moved from running operations to building the tooling for it, using n8n, Supabase, and AI agents to help healthcare and service businesses automate the processes I used to run by hand. Some of that work became the Feedback Intelligence System and Healthcare Claims Processing Automation project you can see on the Projects page.

Today, at Primed E-Health, I'm building the harder version of the same problem: getting patient data to move safely between the facilities that need it. That means owning both sides of the system, a patient-facing mobile app in React, Node.js, and Flutter, alongside full Supabase and database implementation handling the actual data sync between hospitals. The tools changed since Spectranet, the problem never did.