Built by Movement,
Betting on AI.
I'm an AI product manager who has rebuilt her life more than once — across the Philippines, Australia, Japan, Singapore, and now Germany. Nine years across product and operations taught me the same lesson every move did: the future belongs to whoever can turn ambiguity into a working system. Since 2023 that's meant AI — LLM-assisted tools, autonomous agents, and workflow automation — run with real product discipline, not just a chatbot bolted on.
A Narrative of Movement
Every place I've lived has left a mark on how I build. Here's the map of how a breadwinner from Cebu ended up building AI products in Germany — and why I believe this is exactly where the world is headed.
Where it started — I became my family's breadwinner young, rebuilding after we lost our home.
The leap — moved with 5,000 pesos and no safety net, right as the pandemic hit.
The scholarship — the only student sent from the Philippines that year.
Into tech — love brought me here, and it brought me into product.
Present day — building AI products, and a life with balance, from Germany.
Hover any pin for the story behind it.
How I Work Under Pressure
The honest version — how my working style lands with other people when things get tense, and the small adjustments that keep it collaborative.
I move straight at the problem and want to own the fix — not just fast, but right. Chaos doesn't rattle me; it kind of wakes me up. And under real pressure, I get steadier, not louder.
Where it clashes — and what works
Moves fast, wants to call it done
The friction — in a crisis they speed up and I get pickier; the room can get tense fast.
What works — a yes plus one quick check: "we move, but let's validate this one thing first."
Needs the plan to hold still
The friction — I pivot fast when it's messy; they freeze or push back, and I misread it as being difficult.
What works — name the change out loud: "this shifted — here's the new shape of it." They need the map before they can move.
Protects the mood over the facts
The friction — they read me as cold when I push; I read their smoothing-over as avoidance.
What works — lead with the relationship, then the issue: "I value what you built here, and we still need to fix this part."
Wants the room before the decision
The friction — if I move without them, they feel left out and quietly check out of the work.
What works — a five-minute heads-up before I act — it costs me little and reads as respect, not delay.
Still processing after I've moved on
The friction — I've already moved forward, so I can come across as dismissive without meaning to.
What works — close the loop first — a simple "are we okay?" goes a long way.
It's never competence — it's pace and standards
I move with purpose, hold a high bar, and don't need much emotional runway. Most friction is other people needing more time, consensus, or reassurance than I offer in crisis mode.
The fix isn't lowering the bar — it's briefly naming what I'm doing, so others can follow.
How I
Got Here
Not a list of job titles — the actual chain of decisions that got me from breadwinner to AI Product Manager.
AI Product Manager · Independent Contractor
Clients: HR.com, Advanced Human Technologies, Ironbridge AI Advisory
This is the longest-running thread in my career, and the widest. Since 2023 I've worked as an independent product manager for client businesses, fully remote and sometimes alongside a full-time role. Today I own the roadmap for the AI agents and workflow automations we ship to clients through a fractional Chief AI Officer service. That covers discovery with the people who'll actually use the thing, scoping and prioritisation, delivery with engineering and design, and the follow-through after launch.
Before the AI work took over, the same contract work was about operations. I rebuilt how a distributed team actually worked, replacing scattered process with Notion and Slack and cutting operational costs by 25% along the way. It sounds tidy in a sentence. In practice it was a lot of unglamorous meetings and a lot of people trusting a process I was still figuring out as I went. It's the same job I've been doing ever since, with better tools.
Chief Operating Officer
And before any of that, I was COO of a company mostly because someone needed to hold operations together while it scaled, and I said yes before I felt fully ready. I built out our systems — Jira, CRM, SPSS-backed research — the way you learn to swim: by being in the water. That's more or less how every chapter on this list started.
Why AI. Why Me.
Betting on AI
I didn't arrive at AI because it was trending — I arrived because it's the first tool I've used that matches the pace I've always had to move at. Every role I've held has been about turning a mess of manual, human-bottlenecked work into something that runs itself: a document generator instead of manual updates, a script instead of a dev-team backlog, an SOP instead of tribal knowledge.
AI is just the next, much bigger version of that same instinct. I believe the products that win over the next decade are the ones that use AI to remove friction, not bolt a chatbot onto an existing workflow — and that's the only kind of product I want to build. This isn't a detour in my career. It's the path I'm staying on.
What Makes Me Different
I've been the breadwinner, the COO, the trainer, and the product manager — often at the same time. Most PMs haven't run a company's day-to-day operations; most operators haven't shipped their own automation tools. I move between the human side of a problem and the technical side of the fix without needing a translator in between.
I've also rebuilt my life from scratch enough times — Philippines to Australia to Japan to Singapore to Germany — to know that resilience isn't a personality trait. It's a system you build under pressure. That's what I bring to every product I touch.
AI Agents & Automations I've Built
Proof that "Why AI" isn't just a belief I hold — it's a habit I practice. These are tools I've prototyped on my own time, built the same way I build at work: start with the annoying manual task, automate it, then see how far it can go.
Inbox Triage Agent
Reads incoming support and research emails, classifies intent, and routes each one to the right queue — with a drafted first response waiting for a human to approve.
Meeting-to-Roadmap Agent
Turns a raw meeting transcript into a structured product brief — decisions, open questions, and roadmap updates — formatted and ready to share.
Survey Insights Agent
Codes open-ended survey responses into themes automatically, so qualitative research doesn't get shelved just because nobody has time to read 800 free-text answers.
Client Doc Sync Agent
Watches a single source-of-truth document and automatically keeps every downstream client-facing file in sync — the AI-agent cousin of the tool I hand-built at HR.com.
A Few Stories
I'm Proud Of
Not highlight-reel stats — just two moments where I saw a mess nobody was fixing, and fixed it.
TWO I'D TELL YOU OVER COFFEE
Scaling Performance and Efficiency
Problem: Rapid pandemic-era growth at Authority Titans outpaced alignment — writers, sales, and customer success were all moving fast without a shared standard, leading to rushed, inconsistent output.
Action: I built content guidelines with our top writers, promoted them into editor roles, and turned the whole process into one SOP the company signed off on.
Result: Shared accountability across teams, and a visible lift in output quality.
The Key-Document Fix
Problem: At HR.com, our internal "date builder" and our client-facing key documents lived separately — every change meant updating both by hand, with real risk of the two drifting out of sync.
Action: Rather than wait on a dev team with limited bandwidth, I built an automated key-document generator in Python myself.
Result: Manual rework disappeared, and client-facing materials stayed accurate by default.
"Automation isn't about replacing the human touch; it's about removing the friction that prevents us from being human."— SHAN LLAMIDO