// AI AUTOMATION ENGINEER
Your team is spending hours on work that should take minutes. I build working AI Automation systems in your stack, used by your team, and I keep them running.
// ABOUT
I’m Rodruey, an AI Automation Engineer based in the Philippines, working with teams around the world.
I came into this from an unusual angle. I studied Civil Engineering. That’s where I learned to think in systems. Where things connect, where they break, and what has to hold when the load is real. So you learn to design for the failure before it happens, because a structure doesn’t get to fail quietly.
Then came data analysis, which taught me the other half. How a business actually stores and moves its information. Pulling it out of one system, cleaning it until it can be trusted, getting it somewhere it can be used. Unglamorous work. But it’s where most of a business’s day quietly disappears.
So when AI automation came along, it turned out to be both of those at once. Moving information between the tools your business already runs on, with AI doing the judgment someone used to do by hand, built to hold when the load is real. None of it was planned. But every step was preparing me for this one, I just didn’t know it at the time.
And once I was actually in it, working with real clients, one thing kept standing out. This space is loud right now. A lot of hype, a lot of demos that never leave the demo. What I keep coming back to is simpler than that. AI automation isn’t a tool, and it isn’t a single workflow you hand someone. It’s infrastructure, because your business ends up running on it.
I did one-off builds as a freelancer, one-time projects with agencies. And it always ended the same way. It gets built, everyone moves on, and when it breaks nobody remembers how it works or who to call. I’ve watched it happen from the inside, more than once, and it stopped sitting right with me.
So I don’t work that way anymore. I stay with what I build, keep it running, and keep shipping the next thing as the business grows.
Staying only works if I keep getting better, though. So outside of client work, I study. The AI inside AI automation is machine learning, so I go learn the actual thing: how models behave, how AI applications get built, whatever is new that month. I do it so the people paying me get someone who knows what he’s putting into their business.
That same itch is why I build my own products, free and paid, and why I teach this online. Some of it for business owners working out where AI fits, some of it for people trying to break into the job.
And really, at the end of all this, I want to be someone worthy of the trust that people provide me, because they hand over the AI automation infrastructure of their business. And I just really love what I do!
PH · WORKING WORLDWIDE
// HOW I WORK
Understanding first. Then working systems. Then compounding.
Listen
Access, intros, listening. I learn the tools, the workflows, the places things break. I’d rather be the new person who asks too many questions early than ship the wrong thing later.
Build
Once I know enough, I start. Not polished demos, actual systems going into actual workflows. A running system beats a slide deck every time.
Compound
We measure, adjust, ship the next round. Each system that runs frees capacity for the next. The work compounds.
Lead project
Prospect research that used to take a team several days now takes under 15 minutes, started with two clicks inside HubSpot. It replaced the work of a whole team, and the brief lands the same morning it’s asked for.
Architecture and design
A content agency was running on three tools that didn’t talk to each other. I designed the system that connects Google Workspace, Trello, and Slack into one, with a phased rollout and a forecast of what each phase pays back, so they could approve it one stage at a time. No vendor lock-in, so it survives whatever they switch to next.
Project
Email that sorts, drafts, and handles itself, with nothing going out until a person approves it from their phone. Three rounds of checking run before a draft ever reaches you, so the hours saved don’t come at the cost of something wrong going out under your name.
Project
A manufacturing client’s numbers sat locked inside a legacy ERP that nobody could see into. Now the data gets pulled out, cleaned up, and put on screen as a live interface the floor reads at a glance. A system nobody can see is a system people keep checking by hand.
// FORMALLY CERTIFIED