The team

The founders.

You deal directly with the two of us, from the first conversation to the hand-over.

Rodrigo Oliveira Zacarias

Rodrigo Oliveira Zacarias

Founding partner — software & delivery Rio de Janeiro, BR

Doctor in Informatics (UNIRIO, Rio de Janeiro) and a systems engineer by training. Since 2019 he has built and maintained software inside a Brazilian federal university: thousands of users, systems older than the people using them, and no option to switch anything off. That is where you learn to deliver in increments, to test against reality and to document while you build rather than afterwards. His peer-reviewed research on requirements engineering and software ecosystems is why a Marrod project begins by writing down what the software must actually do — and why the hand-over is part of the assignment instead of a separate quote.

LinkedIn profile
Marcus Ferreira de Moura

Marcus Ferreira de Moura

Founding partner — data & automation Amsterdam, NL

Master in Information Science, following Business IT and Management at the Hogeschool van Amsterdam. He has worked as a data analyst, data-visualisation specialist and data engineer across several industries, where the pattern is always the same: reporting assembled by hand, and processes that stall between systems. He builds the pipelines, the data models and the AI-driven workflows that take that work away, and has delivered automated platforms that run in production rather than in a demo. Dutch and Brazilian — your point of contact in the Netherlands, and the bridge to the engineering in Rio.

LinkedIn profile
Why Marrod

What sets us apart.

Five working agreements, with the details we put in writing before a project starts.

Marrod Agreed with you
Who builds it

The two founders

Responsibilities and availability

Running costs

No recurring fee for our own components

Separate budget for hosting, cloud/API usage, external licences and maintenance

Cost

Ceiling agreed in advance

Scope changes approved before extra work

Hand-over

Part of the assignment

Code, access and documentation in the scope

Scope

One defined project, then expand

Deliverables and an agreed launch date