[ About ]
Hello.
This page gives you the reasoning behind me as a person, which translates into my work. If there's a way this portfolio could be improved, let me know. E ṣe (that's ‘thank you’ in my native language).
This is the reasoning behind the work, not a list of it.
02[ The Observer ]
“Every request is a symptom. The system underneath it is the actual problem.”
Before a solution gets named, the shape of the system gets mapped: who is asking, what they are actually blocked on, and which constraint is load-bearing versus which one is just habit. That ordering, system before solution, is the one thing that does not change between a regulatory mandate and a Saturday side project.
03[ Everything Is A System ]
Six layers, one dependency chain
01 / the mandateBusiness
02 / who carries itPeople
03 / what carries itTechnology
04 / how it runs dailyOperations
05 / where it compoundsAI
06 / what disappearsAutomation
04[ Who I Am ]
Make something interesting.
Click or tap any region of the diagram
to explore what it means.
Currently thinking about
Why humans make things more complicated than they need to be.
Currently building
Too many things.
Currently learning
Whatever catches my attention.
Current weakness
Starting a new idea before finishing the previous one.
05[ Operating Principles ]
Identity, stated plainly
Technology should disappear.
The best system is the one no one has to think about while using it.
Systems beat shortcuts.
A shortcut solves today. A system solves today and the next fifty of today.
Complexity belongs behind the interface.
The interface earns simplicity by absorbing complexity, not by hiding from it.
Build trust before features.
A feature no one trusts is a feature no one uses. Trust ships first.
Every decision compounds.
Small decisions made well, repeatedly, outperform one big decision made perfectly.
06[ The Toolkit ]
What the work actually runs on
No tool on this list is a position. They are what happened to fit the constraint in front of me, and most of them will be replaced by something better before long.
- Claude API
- OpenAI
- Gemini
- n8n
- LangChain
- TypeScript
- Python
- SQL
- Power BI
- Power Automate
- Azure DevOps
- Jira
- Figma
- Confluence
- ClickUp
- MixPanel
- Power Apps
- Microsoft Project
- Draw.io
07[ Building The Future ]
One ecosystem, not a project grid
AI
Supplies the leverage: agentic workflows with deterministic guardrails, not magic.
Automation
Turns leverage into disappearance: operational load that no longer needs a person.
Business Analysis
Keeps every build anchored to a real decision and a real constraint, not a feature wish list.
Product
Shapes what ships into something a user actually adopts, not just something that works.
Project Management
The governance and cadence that turns a working prototype into something delivered on a date.
Where AI, automation, and delivery discipline meet. Every strand exists to feed this one build, not to stand alone.