Internal projects and experiments

Not everything I build has a public address. Part of the work is born inside, as a prototype or a Proof of Concept: it checks whether an idea holds, tries a tool before adopting it, or solves a concrete problem without waiting for a formal project. This page collects a selection, by family. No company and no client is named: what matters is the kind of problem and the way it was approached.

A selection

• AI document processing prototypes — reading documents of different shapes and extracting their information into a reusable structure.
• CRM workflow experiments — trials of processes, states and automations in the CRM before they go to production.
• Power Automate business workflows — notifications, approvals and hand-offs between systems built as flows.
• Data transformation utilities — small tools to convert, clean and reorder data between one format and another.
• Internal reporting dashboards — views on company data for those who need to read it without querying it.
• Microsoft 365 governance projects — rules, permissions and structure of a Microsoft 365 tenant.
• AI-assisted knowledge bases — collections of documents that can be queried in natural language.
• API integration prototypes — links between systems that need to exchange data.
• Document generation systems — documents produced from data, with a template and no manual filling.
• Information architecture projects — how to organise documents and information so that they can be found.
• Web prototypes — web pages and applications built to try an idea or an interface.
• Automation scripts — scripts that take a repetitive task off a person’s hands.
• Data migration projects — moving data from one system to another without losing its meaning.

Some of these stayed prototypes. Even a trial that does not go on says something about how to approach the next one.