Leaf — Modular Business Platform

The problem

Italian SMEs rarely lack software. They have an accounting package, a CRM, a warehouse system — and none of them talk to each other. The gaps get filled by people: someone re-types the invoice number, someone reconciles two exports in a spreadsheet, someone notices on Thursday that Tuesday’s order never reached production.

The commercial answer is to sell them a suite that replaces everything. That answer is wrong for this market. The systems already in the building are load-bearing, the staff know them, and migration budgets do not exist. What is missing is not another system of record — it is the layer between them.

What I built

Leaf is the platform that layer is built on: business modules that plug into one host and one deployment, sharing identity, messaging, telemetry and a common set of primitives. A customer runs the whole thing on a single modest server, and a new module arrives without redesigning what is already there.

Two rules hold it together. No module ever reaches into another module’s domain, and any module can be pulled back out later if a real operational reason ever appears. Everything else follows from those two.

Where it stands

Three business modules run on the platform today, booted from one deployment. New module work starts from a defined skeleton with the boundaries already drawn — which is the difference between a platform and a folder of related projects.