Building systems that work.
Custom platforms, integrations, webshops, and websites. Built properly, delivered on time.
Minuar
Named after the Minuano, a cold, dry wind that sweeps across the south of Brazil. It arrives after the rain, once the storms have passed.
Steady and persistent, it clears the air and leaves everything sharper than it found it. Anyone who grew up in the region knows the feeling. You don't see it, but you notice when it's there. And you definitely notice when it's not.
That's how technology should feel. Almost invisible when it's running well. Obvious when it's missing. The best systems are the ones nobody has to think about. They just clear the friction and let people focus on their work.
From fixing computers to building platforms
I've always been drawn to figuring out how things work. That started with taking apart computers as a kid, turned into fixing them professionally, and eventually led me to writing code. I got a degree in internet systems in Brazil and landed my first agency job in 2011.
In 2015 my wife was offered a PhD position in the Netherlands. We moved, fell in love with the country, and decided to stay. After a few years working remotely and then joining a Dutch web agency, I found myself wanting to take on more complex work than the typical agency pipeline could offer. That's how Minuar started.
WordPress has been at the core of my work for most of that journey. Over the past few years I've been expanding beyond it, picking up new stacks, tackling more complex integrations, and generally following the curiosity that got me into this in the first place.
From question to solution
Understand the problem
What are you trying to accomplish? What's getting in the way? Most projects start with a conversation, not a spec document.
Scope and quote
Clear deliverables, transparent pricing. If something is complex, that's communicated upfront. No surprises three weeks in.
Build and deliver
Direct communication throughout. You talk to the person doing the work. Problems are surfaced early, not buried until launch day.
Support and iterate
The best work happens with context built over time. Long-term relationships preferred over one-off handoffs.
How the work gets done
Clarity over promises
Realistic assessments, not optimistic sales pitches. If a timeline is tight or a solution is overkill, that gets said upfront. Trust is built by being right, not by being agreeable.
Direct communication
No account managers, no layers. Questions get answered by the person writing the code. Issues are flagged the moment they appear, not packaged into a status report a week later.
Code that outlasts the project
Maintainable by others afterward. Documented where needed. No dependency on one person's setup to make it run. The work should hold up long after the invoice is paid.