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. That was my early exposure to how messy service delivery gets at scale, and the first time I remember thinking someone should just build something to catch this automatically.

At AfyA Care / R-Jolad Hospital Network, I led hospital operations and billing across seven facilities with a team of 40+. That's where I got obsessed with the gap between the systems clinics use and the systems they actually need.

At Dabik Technologies, I moved from running operations to building the tooling for it, helping healthcare and service businesses optimize and automate their processes to increase productivity and reduce revenue leakage. 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.