Product strategy
A roadmap you can defend.
- Roadmaps tied to business goals
- Market and competitor scans
- Feature prioritisation
- Build, buy or borrow
Product consulting
Turn an idea into a product people actually use.
I help teams get from a rough idea to something shipped, used and maintained — inside the team, not advising from a distance.
-
4M
people using the parking app I led. The #1 app in Spain and Portugal.
-
200k
teachers and students on learning platforms at a Portuguese publisher.
-
17+
years building products, from startup to enterprise.
Is this for you?
- You have a product that works, but the roadmap is guesswork.
- You're starting something new and want someone who has shipped before.
- Your team is stuck between business, design and engineering.
What I do
Delivery
Ship on a rhythm, not in a panic.
- Scrum and Kanban in practice
- Cross-team workflow fixes
- Release planning
- Stakeholder management
Decisions from data
Numbers instead of opinions.
- KPI design
- User research
- Product analytics
- A/B testing
Technical direction
Modernise without a rewrite.
- Legacy architecture reviews
- Technical debt plans
- Performance and cloud cost
- Hands-on with the team
How it works
-
Discovery
I read the product, the data and the code, then write down what is actually wrong.
-
Plan
A short roadmap with the few decisions that matter, and what we are not doing.
-
Build
I work inside the team: priorities, reviews, unblocking. Weekly demos, no status theatre.
-
Handover
Documentation, metrics, and a team that keeps going without me.
Formats and duration
- Advisory
- A day or two a month. Roadmap reviews, hiring, hard calls.
- Project
- Three to six months, part-time or embedded with the team.
- Workshop
- One to three days with the team, on product or delivery.
Questions
Do you write code?
Yes, when it is the fastest way to settle a decision. I am not there to take the team's work, but I am not there to draw diagrams either.
We already have a product manager.
Good. Most of my work is with the people around that person: priorities, trade-offs, and the gap between business and engineering.
How does it start?
A call about what you are building. If it looks useful, I send a short written plan: what I would do in the first month, what it costs, and what I need from you.
What if we do not know what we want?
That is the usual starting point. The first weeks exist to find out.
Other services
What are you working on?
Tell me about the product and where it is stuck.