About

I’m Trinh Vo — I build tools that solve real problems.

My background

I grew up in Vietnam, moved to Switzerland for my master’s degree, then came to Canada for an MBA at Schulich School of Business. Each move taught me the same lesson: when you’re navigating something complex, the right information at the right time makes all the difference.

That lesson stuck with me when I started my career in technology and operations. I quickly noticed that most organizations don’t have a problem with a lack of information — they have a problem with finding, organizing, and acting on the information they already have.

What I’ve built

Over the past several years, I’ve designed and shipped solutions that serve thousands of users:

A firm-wide search tool that consolidated multiple databases into a single interface, cutting search time from hours to minutes. Practitioners use it daily to identify client relationships and manage risk.
Workflow automation systems across multiple teams — custom forms, approval processes, and dashboards that reduced manual effort by 70% and gave managers real-time visibility into operations.
AI training programs for 200+ team members, covering everything from practical prompt engineering to building local LLM environments. My goal: move people from “AI is a buzzword” to “here’s how I use it today.”

In my current role, I focus on enablement — operational support, AI advisory, problem solving, solutions architecture, and product ownership. The part of the work I care most about is finding better ways to solve problems through technology.

What I’m building now

I’m currently building Zenmori, an AI assistant that turns your thoughts into tasks, contacts, and structured knowledge. The idea came from watching how much mental load people carry — remembering follow-ups, tracking conversations, organizing ideas — and how most tools make you do the organizing instead of doing it for you.

Zenmori is designed for people who want to capture their thoughts without the overhead of folders, tags, and databases. You dump your thoughts. The assistant figures out what’s a task, what’s a contact, what’s knowledge — and follows up.

How I think about building

I’m a self-taught technologist. I don’t have a computer science degree — I learn by building. My approach is practical:

Start with the problem, not the technology. I don’t reach for AI because it’s trendy. I reach for it when it actually solves something better than what exists.
Prototype before committing. I build a working version fast, test it with real users, and iterate. If the prototype doesn’t work, I haven’t wasted much time. If it does, I have evidence.
Simplicity wins. The best tools are the ones people actually use. Complex systems that require training fail. Simple systems that solve the core problem stick.
Document and share. Building in isolation limits impact. I train my teams, write documentation, and create materials that let others carry the work forward.

What you’ll find here

This site is where I share what I’m learning about technology, knowledge, and building products. I write about practical lessons from real projects — not theoretical frameworks or abstract patterns.

If you’re a fellow builder, someone looking for AI consulting, or just curious about what I’m working on — feel free to reach out.