Skip to content

Better products happen when one person speaks all three languages.

I didn't start in product management. I got here through design, code, and a lot of building. Here's how.

CAREER PATH

  1. 2012–2018

    Selfrules (2012–2018)

    A web design studio launched at 25 in northern Italy. For 7 years, everything went through one person: sales, design, development, delivery, support. 20+ clients. The first e-commerce site had an award-worthy interface and zero sales. The customer couldn't find the checkout button. €8K in refunds. When you sell, design, build, and support the same product, cross-functional thinking isn't optional. And one rule becomes permanent: if it's beautiful but confusing, it's decoration.
    ↑ overlap

  2. 2016–2020

    FLOWING (2016–2020)

    Joined as a UX Designer, left writing production code. B2B and B2C products for clients including Prometeia, Casavo, CliensPiù. The most formative project: CliensPiù, a legal practice management system used 8+ hours a day. Every micro-interaction matters when someone lives in the tool. Designing the interface, then writing the code that implements it. After 4 years of doing both, the line between "the designer" and "the developer" stopped making sense.

  3. 2020–2023

    ActiveProspect / LeadsBridge (2020–2023)

    LeadsBridge: B2B SaaS platform with 380+ connectors and direct partnerships with Meta, Google, LinkedIn, and TikTok. Solo PM, fully remote from Europe, team of 10. The product's core flow was also its weakest point — the kind of problem everyone had accepted as normal. The redesign cut setup time by 35% and directly unlocked revenue growth.

  4. 2023–present

    QubicaAMF (2023–present)

    600 employees, 90+ countries. Payment systems, platform integrations, and cashless solutions for entertainment centers. A system inherited in critical state. How it was stabilized is a story worth its own case study. Today: a team of 10+ across backend, QA, and analysts. 99%+ uptime, -25% post-release incidents, 116 centers integrated, 5 new per week. Stabilization was step one. The current work is strategic: what to build, what not to build, and why.

WHAT I BELIEVE

The problem is never the one from the first meeting.

The first meeting tells you the symptom. The real work is digging to the cause. Sometimes that means saying "the solution we're evaluating doesn't solve the real problem." It doesn't win you friends in the first meeting. By the third, they agree.

A working prototype beats 100 slides.

An idea, before becoming a ticket, becomes a working prototype. React that users can touch says more than any spec document. The data you need to decide comes from the field, not from meetings.

The best PM is the one the team doesn't notice.

If the team works well, credit goes to the team. But "removing obstacles" isn't enough. The real work is figuring out what to build and why. Giving the team a direction that holds even when priorities shift. Protecting focus isn't saying "no" to interruptions. It's having done the strategic work upfront, so the team already knows what matters. If the PM becomes the bottleneck between builders and decision-makers, something went wrong.

OUTSIDE WORK

Based in northern Italy. When not working, probably at the gym, building something with LEGO, or trying something outside the comfort zone. Latest experiment: embroidery. Will go back eventually, but not before figuring out what's on the other side.

If your product needs someone who gets their hands in it — not just words on top — let's talk. Even just to see if it makes sense.

Read my case studiesGet in touch