CONSULTING

AI, integration and Industry 4.0 consulting for small and mid-sized companies

I work with companies that already run an ERP, while their processes still go through email, Excel sheets and retyping. I look at how you work, remove the useless steps, connect what doesn't talk and put AI only where it saves real work. I build it and look after it myself, with no hand-offs.

First step · 30 minutes · free · no strings

You tell me how you work, I tell you what I would do.

  • An honest opinion: if software won't solve the problem, I'll say so on the call.
  • A clear idea of where time is lost today and what I would remove first.
  • If it makes sense to go on, a written proposal with costs and timing, split into stages.

Who it's for, and who it isn't

Worth a call if

  • you are a small or mid-sized company, manufacturers included, with an ERP in use for years;
  • the same data gets entered two or three times, in different programs, by different people;
  • orders, delivery notes or requests arrive by email and someone retypes them;
  • you have machines on the shop floor producing data that never reaches the ERP;
  • you are considering Italy's 2026-2028 hyper-depreciation and need someone to build the interconnection.

What I don't do

  • I don't sell an ERP or resell licences: I work with yours.
  • I don't put an AI model where a rule is enough. It costs more and tests worse.
  • I don't sign technical reports or certifications: a licensed professional and your accountant do. I prepare the technical part.
  • I don't leave behind a system only I can touch: code, credentials and documentation stay yours.

What I do

AI

AI in the company

I put AI models inside processes, not beside them: they read incoming documents, route requests, check production photos, and the result lands in the ERP with no manual step.

For each task I pick the smallest tool that does the job: a rule, a classifier, a model running on your premises, or a remote model only where it is really needed. Cost, response time and where the data stays are decided before the code.

For example: orders arriving by email land in the ERP already filled in, with customer and lines recognised.

Processes

Shorter processes

Before writing code I look at how you work: who enters what, where things get retyped, where people wait on someone else. Often removing a step is enough; new software comes only if it's needed.

The output is a short document: what to change, in what order, what it costs. We start from the stage that removes the most work, so results show right away and the decision to continue is based on facts.

For example: the Excel sheet shared by five people that becomes a small app with a history and no more "who deleted the row?".

Integrations

ERP and e-commerce

I get ERP, e-commerce, warehouse and invoicing talking to each other: every piece of data is entered once and stays in sync everywhere, with a log of what went through and when.

I connect to the ERP's API or database when there is one; otherwise with scheduled exports and imports. I coordinate with the ERP vendor for access and documentation.

For example: ERP stock levels kept in sync with the online shop, and shop orders flowing back into the ERP without retyping.

Industry 4.0

Connected machines

I connect shop-floor machines to the ERP: states, part counts, alarms and consumption read over OPC UA, MQTT or Modbus and delivered where they're needed. Data flows both ways.

I start with a site visit to see what each machine exposes. I build the interconnection and its technical documentation, the one the expert needs for the hyper-depreciation report.

For example: the production order goes from the ERP to the machine; the actuals come back on their own, with times and scrap.

Hyper-depreciation 2026-2028

Italy's hyper-depreciation ("iperammortamento") replaces the Transition 4.0 and 5.0 tax credits for investments made between 1 January 2026 and 30 September 2028. It increases the deductible cost of new capital equipment.

+180%on investments up to 2.5 million euro
+100%on the share above 2.5 and up to 10 million
+50%on the share above 10 and up to 20 million

The technical condition. The assets must be interconnected with the company's production management system or supply network, and stay so for the whole period of the incentive. A sworn technical report and an accounting certification are required; filings go through the GSE platform.

My part. I build the interconnection between machines and ERP and prepare the technical documentation the expert needs: which data flows, over which protocol, proof of two-way communication. The report is signed by a licensed professional; whether an asset qualifies and how much it is worth is for your accountant, also because it is a deduction and you need taxable income to benefit from it.

Source: MIMIT, Nuovo piano Transizione 5.0 (iperammortamento), in Italian. Checked on 7 October 2026.

How we work together

  1. Intro call

    Thirty minutes, free. You tell me how you work and where time is lost; I tell you what I would do and whether it makes sense to go on.

    Output: an opinion, no strings attached.

  2. Analysis

    On site or remote. I talk to the people entering the data, look at the ERP, the spreadsheets, the machines. I look for steps to remove before steps to automate.

    Output: a written proposal, with costs and timing, split into stages.

  3. Development in stages

    We start from the stage that removes the most work. Each stage goes to production on its own and you use it before moving to the next; you can stop after any of them.

    Output: software in use, not a demo.

  4. Production and support

    I look after the system in production, with documentation and a log of what went through. Code and credentials stay yours, so nobody depends on me.

    Output: a system that holds up, even without me.

A concrete case

Case study · Miraviso, B2B SaaS in production

Where AI really belongs in business software, and where it doesn't

How I decided what stays on the device, where a classifier is enough and where a big model is needed. And how I put sensitive data where the server cannot read it. The same method I apply to ERPs.

READ THE CASE →

Frequently asked questions

Do we have to replace our ERP?

No. I work with what you already have. If the ERP exposes an API or a readable database I connect to that; otherwise scheduled exports and imports do the job. A new ERP only comes in if the old one really is the problem, and that is your call.

Does our data stay inside the company?

It depends on where the model is needed, and I decide that task by task before writing code. Many things are done with a classifier or a rule, sending nothing out. A remote model is used only where it is really needed, stating which one, where it runs and with what data. The Miraviso case study shows how.

How much does it cost?

After the call and the analysis you get a written proposal with costs and timing, split into stages. Each stage goes to production on its own and you can stop after any of them. I sell no licences and no mandatory fees: the code and the credentials are yours.

Do you work with our ERP vendor?

Yes, and it is often necessary. I ask them for access and interface documentation; the integration itself I write and look after. If the vendor prefers to do their part, I coordinate with them.

How long does it take?

An integration between an ERP and an online shop is measured in weeks. Connecting a machine depends on the protocol it exposes (OPC UA, MQTT, Modbus or something else) and becomes clear during the analysis. Either way the first stage is the one that removes the most work, so results show early.

Can you certify the interconnection for the hyper-depreciation?

No. The sworn technical report is signed by a licensed professional and the accounting certification by an auditor; your accountant handles the tax side. I build the interconnection and prepare the technical documentation the expert needs: data flows, protocols, proof of two-way communication.

Where do you work?

In person in Tuscany, remotely across Italy. Connecting machines needs at least one visit to the shop floor; the rest is done remotely.

Intro call · 30 minutes · free

Is a process wasting your time? Let's talk.