Work
I build practical software for messy real-world systems.
My work sits between product, engineering, and operations. I started in digital payments, managing complex technical delivery inside a large regulated environment, then moved closer to implementation by building products, internal tools, automations, and integrations myself.
That shift was intentional: I wanted to go deeper into the technical trade-offs, delivery constraints, infrastructure decisions, testing, deployment, integrations, and production problems behind the systems I had previously managed.
Today, I am strongest where the problem is not perfectly defined yet: turning unclear processes into usable systems, connecting business needs with technical execution, and shipping tools people can rely on.
Product & operations systems
Cosa Faccio a Piacenza
A local event discovery platform for Piacenza.
I worked on the product and technical system behind a public events platform: structuring event data, improving discovery, supporting mobile usage, and making the platform easier to maintain across web and mobile.
The work involved product decisions, content workflows, event data, public-facing UX, and the technical foundations needed to make local discovery useful.
Client operations tools
Custom software for small businesses with real operational problems.
I have built internal tools and automations for businesses that had outgrown spreadsheets, fragmented tools, or manual processes. This includes ERP-style systems for managing commesse, restaurant ordering flows, public-tender monitoring, CRM/API integrations, analytics setups, and production fixes across web platforms.
The work is rarely just building a website. It is usually about understanding how the business actually works, finding the bottleneck, and shipping a system that reduces friction.
AI product experiments
Chiara AI
An AI study assistant for turning learning materials into structured study workflows.
Chiara was built to help students transform lectures, PDFs, notes, and recordings into useful study material: cleaned notes, summaries, mind maps, flashcards, quizzes, document chat, and guided explanations.
I built the product around a React/Firebase stack with LLM, transcription, OCR, and document-processing workflows. The project is now archived, but it shaped how I think about useful AI products: AI needs structure, context, constraints, and a clear workflow — not just a chat box.
I continue to explore AI agents and workflow automation where the system needs clear boundaries between reading, reasoning, computing, and taking action.
Enterprise and fintech experience
UniCredit — Digital payments and technical delivery
Digital payments delivery inside a large, regulated banking environment.
My role involved coordinating complex technical initiatives across business, product, engineering, external vendors, and regulated infrastructure. I worked on modernization and delivery efforts where reliability, stakeholder alignment, risk, and operational continuity mattered.
That experience gave me a systems-level view of technical delivery. Working independently afterward gave me the hands-on depth: building, testing, deploying, integrating, debugging, and dealing with production reality myself.
Idospay
A fintech product concept focused on SME cash-flow visibility and payment behavior.
I worked on the product direction and early execution of an Open Banking concept designed to help small businesses understand payment patterns and financial pressure more clearly.
The project combined SME finance, product validation, fintech infrastructure, and startup execution.
Earlier work
TVSION
An early consumer app project with significant public traction.
I contributed to an iOS app and supporting backend that reached a large user base and ranked in the App Store. It was an early experience in shipping consumer software, handling product iteration, and learning from real users at scale.
The through-line
My path has not been linear, but the pattern is consistent: I work best when a team needs someone who can understand the business context, reason through the product problem, go deep enough technically, and turn ambiguity into something that works.
I am strongest in roles where product, operations, and technical execution overlap.