I came to fintech from the operations side, not from the rulebook.

I started at Telecom Italia and then at Atlanet, in the years when Italian telephony was moving from monopoly to competition: the authority set the access conditions and the company had to build something commercially viable on top of them. The rule was not an external constraint to endure, it was the playing field. At Retevisión I saw the same dynamic in another European market, from the position of a company entering a system already occupied. Then the marketing leadership at H3G, where the regulatory constraint was joined by an industrial one: going to market in a crowded sector, under continuous supervision.

It reads like a succession of different industries. It is not: in all three cases the work was translating a body of rules into decisions a company can actually execute, and standing behind those decisions in front of the people supervising them. In fintech I found the same shape of problem — authorisations, capital and governance, supervisory expectations, dossiers that have to stay consistent over time — with a younger body of regulation moving faster.

That is why my advisory is called operational and not legal: it does not come from reading the rules in the abstract, but from having to make a company work inside them, with the people and the timescales it actually has.

At Bizando I work with fintechs, electronic money institutions, payment institutions and crypto-asset service providers, in Italy and across the Union, on three recurring clusters: preparing an initial authorisation, supporting the scaling of those already authorised, and keeping the setup aligned over time.

Concretely: structuring the dossier, drafting technical and regulatory annexes, handling the authority's requests for further information, designing internal processes and delegations, preparing for inspections. The client does not start from zero — from day one my templates for the recurring sections come with me, along with the gap-analysis checklists for EMI, PI and CASP applications, the comparative matrices across EU jurisdictions, and a curated library of European regulatory precedent.

I work alongside the internal team, not above it. On complex dossiers the pattern that works is a clean split: the lawyer signs the formal opinion and handles the exchange with the authority, I build the scaffolding of the dossier and the documentation itself.

CAI stands for Collective Artificial Intelligence: an internal methodology, developed on years of real regulatory advisory work. I set it out at length because in a business that sells compliance, saying how the documents are produced is part of the moral contract with the client.

The principle: senior judgement stays human, production is amplified. Specialised AI systems handle fast regulatory research, first drafts of the recurring sections, comparison across versions, and the synthesis of extensive material. I make the choices that carry consequences — strategic approach, non-standard interpretation, wording addressed to an authority — and I validate every section before it goes out.

Three safeguards on every deliverable. Two review passes of mine, first on regulatory content and then on readability for the actual recipient. A red-team pass with CAI systems on the draft, to surface logical gaps and internal contradictions: an additive control, not a substitute. And full versioned traceability, which makes it possible months later to reconstruct the reason behind every documentation choice.

Two things CAI does not move. Every regulatory claim is anchored to an identifiable primary source — legislative text, technical standard, opinion, published Q&A — not to a generated summary. And professional responsibility for the deliverable is mine: when a document reaches the authority with my signature under it, it means I built it, I validated it, and I answer for it.