I partner with business owners as a Fractional CTO: supervising external vendors, dismantling inflated quotes and lock-in contracts, and restoring architectural order to company systems. Operating margin grows when unnecessary daily friction is removed from the team, not by buying software licenses blindly. I stand on the company’s side: zero conflict of interest, no retainers to push.
Full-Stack Developer, Frontend & Backend Developer, System Architect, SEO & Information Retrieval
Managing technology solely through vendor slides leaves you paying ten times what is reasonable; an isolated developer ignores business processes. I bridge both worlds: over 20 years of experience across systems architecture, code, and operations, creating workflow harmony and freeing up team capacity.
The vendor writes the quote, estimates the hours and picks the architecture: nobody inside can tell whether the job is worth two days or twenty. I read the contracts, decide what to buy and what to build, and manage developers one priority task at a time. Code the company paid for stays with the company.
I built ERPs single-handedly that have run on national networks for years, holding the history of hundreds of companies. That is how I know what a change really costs, and when a closed platform is holding your data hostage. The software should follow people's work, not make them retype data from one screen to another.
A careless migration wipes out years of rankings overnight, and the next day leads are bought on Google Ads. I have studied search engines since 2006: historical URL redirects, crawlability and real browser speed enter the project at the first draft, not after launch.
A language model is good at reading a messy PDF or a confusing email, and bad at arithmetic. I use it to extract and classify data from documents; calculations, commissions and reconciliations stay in deterministic code, wired into the ERP and compliant with GDPR and the AI Act.
Four production ecosystems where software architecture, complex migrations, and organizational clarity produced verifiable business results.
Chief Technology Officer (with company since 2020, CTO since 2026)
I joined in 2020, the year tourism stopped, to rebuild the website. In 2021 the Estate INPSieme tender arrived with a mountain of applications: I wrote a custom module inside WordPress to handle them. It did the job, but it was slow and awkward, and the team had to bend its way of working to its screens. By 2023 Language Travel was over half of revenue and every application still went through it. In 2024 I rewrote it from scratch as a standalone CRM in Svelte and Firebase, starting from how operators actually work: the software adapts to the workflow, not the workflow to the software. In 2025 I added AI to read incoming documents. Since Summer 2026 I am CTO for the whole company.
Filed financial statements. Revenue as an index, 2019 = 100: down 85% in 2020, 2.6 times pre-COVID by 2025. Net profit uses its own scale: read the shape of the curve.
Joined in 2020 (tourism COVID nadir) to rebuild the corporate website.
First custom WordPress module to handle INPSieme tender applications.
The back office leaves WordPress and is redesigned around the operators’ workflow: standalone Svelte + Firebase CRM, automated document handling.
From the Language Travel division alone to technology leadership across all of Il Tuareg.
Division share of total revenue, year by year, and the software it ran on.
Enterprise Architect & Lead Developer (Solo 1-person team, full-stack)
Engineered and developed the entire ERP platform as a solo full-stack developer (frontend, backend, database) across two major phases:
Built to replace legacy software across a 20-partner franchise. Previously they ran 20 disconnected systems on 20 isolated databases with conflicting IDs and separate credentials, forcing manual spreadsheet compilation. Unified all 20 databases into a single centralized proprietary ERP.
Given the operational success at OSM Value, the system was scaled nationally for the entire OSM Group across hundreds of branches and companies, managing multi-tier commissions, Business Intelligence, and analytics.
The national group brought 4 different ERPs used by hundreds of companies. Years of invoices, quotes, deliveries, collections and stats moved into one system, with accounting balances verified on every migrated record.
Aggregated trajectory (OSM Value + royalties): volume growth and 5x net profit in the period following the ERP release.
Every new partner meant one more system to keep aligned by hand.
Designed and built single-handedly: one database, one account per person.
Scaled nationally across hundreds of branch enterprises: multi-tier commissions, BI, and zero per-seat fees.
Commissions, rankings and stats come out of the ERP, not from spreadsheets rebuilt every month.
Fondatore & Lead Systems Architect (Web magazine founded in 2004)
A personal editorial publication I have operated for over 20 years. Rebuilt from scratch in the past year, migrating ~20,000 articles from monolithic WordPress to a fast Svelte + Firebase architecture with proprietary analytics designed without personal data collection and zero tracking cookies.
Direct benchmark on this website’s own architecture: official Google PageSpeed Insights audit with Lighthouse 13.5.0 on emulated Moto G Power under slow 4G throttling. Zero main-thread blocking (TBT 0ms) and zero layout shifts (CLS 0).
Verify live report on Google PageSpeed ↗Real user assessment (CrUX): passed. Lab Speed Index: 0.5s · Total Blocking Time (TBT): 30ms.
Co-founder & Fullstack Architect (Concluded experience)
Multi-tenant corporate welfare platform built from scratch in Node.js and Svelte: wallet ledgers, cryptographic B2B/B2C voucher issuance, and automated accounting reconciliation.
The architecture allowed the startup to scale rapidly across multiple corporate welfare plans, delivering a key market advantage: allowing employees to spend their welfare credits with any merchant or provider chosen by the company or employee, avoiding rigid closed catalogs.
Paying skilled people to act as human photocopiers between spreadsheets and disconnected software burns valuable hours and slows the business down. Drag the three sliders to estimate the financial impact of manual friction on your team:
Capacity redirected to core tasks: Freeing people from repetitive tasks is not just about saving hours: it returns time to customers, cuts errors, and builds a working environment where talent thrives.
Zero hiring tax: With proprietary architecture, when your team doubles licenses do not increase: you compensate the engineering team maintaining the software, not every new user. Under defined conditions, software qualifies as a capitalized asset on the balance sheet.
Original research essays and algorithmic analyses (2006–2007), rewritten and verified by Vincenzo Lombino through the lens of modern distributed systems and AI.
The September 2006 inaugural manifesto: the study of Information Retrieval beyond commercial dogma, equidistant between white and black.
Relevance is direction, not volume: what a 2006 link experiment still teaches today.
The September 2006 conceptual essay: why language, relevance, and spam thresholds are dynamic distributions driven by keyword clustering and collective web shifts.
Mass-generated text fools filters only briefly: from the 2006 Anti-Markov experiment to language models.
Deconstructing the 2006 doorway page generator: stochastic text synthesis, keyword expansion across structural tags, and internal link meshing.
The reference manual for search engineers: boolean operators, scope syntax across URL, title, and body, Julian dates, and wildcard filtering.
A single regular expression can halt production: from form validation to computational complexity.
From negative offsets to User-Agent, Referer and IP cloaking: what the engine saw versus what the user saw.
Updated revision of the January 2007 analysis: the asymmetry between source code and browser, from early search engines to modern AI crawlers.
The landmark January 2007 debate with Agoago and Fradefra: what crawlers actually index, iframe vs JavaScript boundaries, and text selection emulation.
The March 2007 exploit: reading browsing history from the browser cache and profiling users without consent.
Fake identities against consensus graphs: from 2007 links to AI data poisoning.
Dissecting the March 2009 exploit: leveraging XML Binding Language (XBL) in Firefox and HTML Components (HTC) in Internet Explorer for CSS-triggered execution.
