FlightTracker
A Telegram bot that tracks flight prices. It runs on Cloudflare Workers with a D1 database, Telegram webhooks and a check every 15 minutes. Versioned migrations, 58 tests, two independent audits.
Engineer by training. Eight years across gaming, iGaming and sport, the last five on digital products.
Clients and sponsors on one side, technical vendors on the other, and the requirements in between.

Product Manager at the Italian Tennis and Padel Federation since 2025. Before, tournaments, sponsors and a tournament platform at QLASH, and TipKlub, a sports prediction app. I read APIs and webhooks and turn them into requirements.











A Telegram bot that tracks flight prices. It runs on Cloudflare Workers with a D1 database, Telegram webhooks and a check every 15 minutes. Versioned migrations, 58 tests, two independent audits.

A web app to fix the date of a fantasy football auction. AI-assisted development; I chose the model and the price.

Gross to net salary in Italy, every figure with its source. AI-assisted development.
I read and review TypeScript and SQL, and write them with AI assistance.
Three digital products built by vendors. I set the priorities, review what is delivered and decide what goes live.

The eSports section of the federation's app. Tournaments are played inside the app, through the game developer's APIs.

A subscription streaming platform with a free tier, linked to the federation's identity, membership and payment systems.

The tournament's consumer app. It includes the SuperTennis+ streaming.
Release criteria are agreed with the vendor and the internal technical team before the deadline, so nobody has to negotiate them under pressure.

Tournaments and sponsored campaigns for clubs, agencies and game publishers, on QLASH's own tournament platform, which passed 300,000 registered users.

A sports prediction app with some of Italy's best-known tipsters, from concept to launch.
One metric, how it is defined, what I discarded, and the second calculation that can stop the report.
North Star Metric of myFITP eSports, calculated on data from the partner's API. The discarded metrics are written down, each with its reason.
Dashboards rebuilt every week, automatically. If the two calculations disagree, publication is blocked.
What the data says: players who join come back. The limit is how many join.
The customer's environment: who owns what, which workflows matter most, what breaks first.
A rhythm for health reviews, an escalation path and release criteria with the customer's technical owners, before the first incident.
One list of recurring issues and requests, each with a priority and an owner on the product side.
Which workflow it touches, what the customer's own data shows, who on the product side takes it.
Tell me which account you would start fromNothing is a finding until it has a baseline, and the baseline comes from the customer's own data.
I am a technical product manager, an engineer by training. I read APIs and webhooks and turn them into requirements, keep vendors and deliveries under control with priorities, release criteria and progress reports, work with clients, sponsors and publishers, and check the data before it is published.