Work
The final product is only part of the story. Behind every meaningful piece of software are problems understood, assumptions challenged, decisions made, trade-offs accepted, and lessons learned.
This is some of the work that has shaped how we think about Product Engineering.
Beyond the output
A screenshot can show what a product looks like. It can't show why it exists, what alternatives were considered, which trade-offs shaped it, or what we learned once it reached the real world.
That's the part of the work we're most interested in.
Start with the product context, not only the requested output.
Name the trade-offs and choose what deserves investment.
Design and engineer the product with the right level of quality.
Let real usage, constraints and outcomes inform what happens next.
Selected Work
These are the products currently represented on the website. Where context is limited, the case stays intentionally concise.
A travel experience platform built around destination content, exploration and booking flows.
Travel and tourism web platform.
Product design, UX/UI, full-stack engineering.
Published product.
A web app for comparing fuel prices in Portugal by location and fuel type.
Consumer utility product for fuel comparison.
Product engineering, web development, data presentation.
Published product.
A shared expense management product for groups, balances and settlement flows.
Fintech-adjacent web app.
Product design, full-stack development, interface systems.
Published product.
An AI-powered GitHub review assistant for reading pull requests, explaining risky changes and supporting code review.
Developer experience and engineering workflow.
AI engineering, GitHub app development, developer experience.
Internal product.
What work teaches us
Products create more than features. They create evidence. Decisions that worked, assumptions that didn't, technical choices that scaled, and things we'd approach differently today.
That accumulated context is part of what we bring into every new product decision.
Your product
You don't need to arrive with a finished specification. Tell us what you're trying to solve, what already exists, and what you're uncertain about.
Start a conversation →