The person behindthe systems.
A little about who I am, how I think, and why I do this work.
Meet the human behind the systems.
I've always loved organizing chaos.
Long before I started consulting, I found myself naturally drawn to untangling things that didn't quite make sense — scattered information, unclear processes, workflows that felt heavier than they needed to be.
What excites me most is that moment when things finally click.
When structure appears, information connects, and work starts to feel lighter.
Today, that's exactly what I help people do:
I work with small teams, solopreneurs, and startups to build custom Notion workspaces that reflect how they actually work — not how a generic system expects them to.
I take the time to understand your needs, your vision, and your constraints, and translate all of that into a system that supports you in a real, practical way.

What I care about most
Building systems that genuinely help you.
Not rushed solutions.
Not templates forced to fit.
But thoughtful setups that bring clarity, save time, and make your day-to-day work feel more manageable.
I care deeply about efficiency — not just in the systems themselves, but in how we work together. I want you to feel supported, understood, and confident that the time and money you're investing are creating real value.

A little peek into how my brain works
I don't really turn this part of my brain off — even outside client work.
One of my favorite personal projects is a meal prep system I built in Notion.

Good systems set people free.
I believe that when your tools work for you — not against you — you get to focus on what actually matters. You get your time back. You move with confidence instead of anxiety.
I also believe in honesty, simplicity, and long-term thinking. I won't over-engineer a solution just to impress you. I'll build what you need, explain how it works, and make sure you own it — not depend on me forever.

How I got here.
A few milestones that shaped the way I think about systems, people, and work.
It started with engineering
My relationship with systems didn’t start with Notion — it started with engineering.
I studied **Industrial IT and Automation**, where I learned how systems work, how processes connect, and how small inefficiencies can ripple through an entire organization. That foundation still shapes how I think today: structured, analytical, and always attentive to flow.

Where theory met reality
After graduating, I moved into **operations and product roles**, where theory quickly met real-world complexity.
As an **Operations Manager**, I worked hands-on with messy workflows, scattered information, and teams struggling to stay aligned. I mapped processes, built training materials, and eventually implemented a company-wide workspace in Notion to centralize knowledge and operations.
That was the first moment I thought: *this tool actually works.
Later, as a **Product Manager**, I deepened that skill set — translating vague ideas into clear requirements, prioritizing what truly mattered, and improving processes through iteration and feedback. I spent a lot of time understanding how people work, not just what tools they use.

Going deeper into systems & knowledge
That mix of operations, product thinking, and systems design naturally led me deeper into Notion and knowledge management.
For nearly two years, I worked as a Notion Admin & Knowledge Manager for a U.S.-based company, owning documentation, SOPs, permissions, and the continuous improvement of internal systems. I saw firsthand what works — and what breaks — when systems need to scale with a team.
This experience taught me the importance of adoption, clarity, and building systems people actually want to use.

What I do today
Today, I work as a Notion Consultant, collaborating with startups, agencies, and small teams to design systems that bring clarity to their work.
Alongside my independent consulting, I’m part of a non-code studio, where I work as a consultant embedded in the team. In this role, I support the design and development of Notion-based products — contributing to system architecture, database design, workflows, and overall product logic.
Working within a studio environment has sharpened how I think about:
- Building reusable yet flexible systems
- Designing Notion setups that scale across different clients
- Balancing structure with ease of use
It’s a different kind of work than solo consulting — more collaborative, more product-driven — and I really enjoy the mix. It keeps me close to both strategy and execution.
Alongside this work, I’m currently pursuing a Master’s degree in Information Management, deepening my understanding of data, knowledge systems, and digital transformation.
Looking back, the thread is pretty clear:
I’ve always been drawn to turning complexity into something understandable, usable, and meaningful.

Ready to work together?
If something on this page resonated with you, I'd love to hear your story. Let's figure out together what a better system could look like for you.