TONY’S / SYSTEMS

BUILT WITH CURIOSITY + CAFFEINE + CODEX

Back to directoryTONY’S / ABOUT

Hi, I’m Adewale.

I build operations &workflow automation.

I naturally see patterns and systems everywhere. I’m introverted, intensely curious, and probably more interested in how things work than is reasonable.

Book a call
Portrait of Tony
TONY / ADEWALE ADEWUYILAGOS, NIGERIA
01Let’s meet quicklyThe 20-second version of me.Systems, automation, design, curiosity, and the current chapter.

I’m Adewale.

I’m an introverted systems thinker with an unusually strong tendency to notice patterns, inconsistencies, and things that could work better.

I build operations and workflow automation, and I bring a design background into the parts that humans eventually have to read, understand, or interact with.

Outside work, I’m probably lifting something, attempting to get better at tennis, reading about geopolitics, law or psychology, or talking to the handful of people I genuinely enjoy talking to.

Right now, I’m building aggressively, documenting the journey, and seeing how far I can take it.

02The person outside the workI’m an introverted perfectionist, and I love ambitious goals, difficult problems, and getting better at things.Life, tennis, rabbit holes, and a strangely specific goal.

I tend to notice relationships between things quickly.

Where something breaks, why one process keeps producing the same problem, which small detail is affecting everything else, or where a system could be structured differently. That tendency follows me almost everywhere, from the way I organize my own life to the things I choose to build.

I’m also a perfectionist. It comes with disadvantages, but it has given me a useful sensitivity to details, inconsistencies, and things that could work better. I’ve learned that I need structure around myself—routines, organization, and clear priorities—or I can disappear too deeply into the problem in front of me.

Oddly enough, learning to manage that became one of the things that made me good at building systems for other people.

Most of my life is actually pretty quiet.

I’m a chronic introvert, so I spend an unreasonable amount of time behind a desk. If I’m not there working or learning, there is a good chance I’m at the gym or playing lawn tennis.

Tony holding a tennis racket against a blue sky
A recent obsession: lawn tennis.

Tennis is a fairly recent interest, but I’ve grown to love it. Tiny adjustments matter: timing, positioning, repetition, and consistency. You can immediately feel when something is slightly off. Apparently I managed to choose a hobby that also rewards obsessing over systems.

Outside that, you’ll probably find me talking with my family or my girlfriend. I keep my circle small, and I like it that way.

I fall into rabbit holes very easily.

My interests are broader than technology. I can lose hours reading about geopolitics, law, psychology, history, institutions, incentives, and why people or countries behave the way they do.

They look unrelated at first, but the attraction is the same: systems. Law is rules and interpretation. Geopolitics is incentives, geography, power, and history. Psychology is full of patterns in how people think. I like understanding what sits underneath the visible outcome.

03ProfessionalEventually, I started building systems instead of only noticing them.Automation, pressure, design, documentation, and useful work.

Pattern recognition is probably one of my strongest abilities.

I notice inconsistencies quickly, connect information across different parts of a problem, and keep pulling on something until I understand why it works the way it does.

Under pressure, this becomes especially useful. When there are several moving parts and something needs to work, I’m usually good at reducing the noise, identifying what matters, and working through the system.

That is where automation became particularly interesting to me. I build operations and workflow automation for repetitive work, messy processes, information moving between tools, reporting, and tasks people keep doing manually because nobody has stopped to rebuild the process.

Depending on the problem, I might write software in Python, connect platforms through their APIs, structure the data they exchange, or introduce an AI model where flexible interpretation is genuinely useful. The implementation changes; the goal is always to make the system dependable.

What actually needs a human here?

That is the question I keep returning to. Once the genuinely human part is clear, I can design the rest around it.

I still care a lot about how things are presented.

Before going deeper into automation, much of my professional work revolved around design. That background still shows up in the systems I build.

A technically correct automation can produce a terrible report. A powerful internal tool can still be confusing. Documentation can still be unreadable, and data can still be presented badly. So I care about the layer between the system and the human using it.

For me, design is increasingly less about decoration and more about making complex systems easier to use and understand.

I’m still building.

I don’t want this website to become a museum of things I have already done. I’d rather it document what I’m becoming good at: building, experimenting, recording what works, recording what doesn’t, and publishing the process as I go.

If there is a system underneath something, I probably want to understand it. If it repeats often enough, I probably want to automate it.

WorkflowsReportsDocumentationDashboardsInterfacesAutomation