I turn repetitive work into reliable automations and messy operations into clear, decision-ready systems.
500+ automations shipped across 10 platforms. Every one of them monitored, documented, and still running.
09:15 daily brief sent
09:31 recap batch complete
10:02 no failures in 24h
Meet Drix
I'm Drix, an AI and systems engineer based in the Philippines, working US hours. I turn repetitive work into reliable automations and messy operations into clear, decision-ready systems: CRM pipelines, onboarding and offboarding flows, recordings archives, payout systems, recap generators, executive reporting, and the monitoring that tells you when any of it breaks before a customer does.
What I do best is connect systems and simplify complexity. I design, build, and maintain scalable automations across n8n, Zapier, Make, Power Automate, HubSpot, Airtable, Supabase, Power BI, AWS, and Google Cloud, using APIs, webhooks, and structured automation design to make operations smoother and more dependable. My work has grown from hands-on automations to designing the higher-impact systems that support business-critical workflows, cross-functional operations, and executive visibility.
What matters most to me is durability. I care about automations that are secure, well documented, maintained, monitored, and stable in production. If a system cannot be trusted in real-world use, it is not done.
I also handle the unglamorous work that keeps a company safe: email authentication, mailbox forensics after a phishing incident, access control, and deliverability when invites stop landing.
Background
- 2025: Computer engineering graduate, Pampanga, Philippines.
- 2025 to early 2026: Workflow automation at an offshoring firm, promoted from intern to associate. 400+ automations across eight platforms cut about 60 hours of manual work a week.
- 2026: Embedded remotely with a coaching company and a staffing agency, plus a finished six-month project for a healthcare billing company. The nine case studies on this site come from this year.
How I work
- Root cause first. A workaround is offered only after the cause is understood.
- Every system I ship carries its own alarm. If it fails, someone hears about it within minutes.
- Plain language for the people who use the thing. Technical detail for the people who maintain it.
- Verified means verified: the run finished, the row landed, the person got the message.
- A human stays at every decision point where the consequences matter.
How an engagement runs
- 01
Discover: what breaks, who feels it, what "done" means.
- 02
Map: the systems, the data, the handoffs, on one page.
- 03
Build: minimal, verified on real data, documented.
- 04
Alarm: every system ships with its own monitoring and a human who hears it.
- 05
Hand over: runbook, walkthrough, and a clean exit.
Selected work
See all workWhat I work with
The stack behind 500+ automations across 10 platforms.
Orchestration
Where the work gets wired together. n8n first, the others where a team already lives in them.
AI in production
Language models inside real workflows, with a human at every decision that matters.
Data
The tables, buckets, and sheets the automations read from and write to.
CRM and ops tools
The systems teams actually work in, connected so nobody copies data by hand.
Cloud and infrastructure
Hosting the automations and the archives they depend on, with cost and access under control.
Security and email
The unglamorous work that keeps a company safe and its mail landing.
Building and reporting
Code when a node is not enough, and dashboards so leaders see the numbers without asking.
Off the clock
Resume, on request
Leave an email and, if it helps, a line on who you are. Drix replies from his personal email, not this site.