Call · 15 min

Custom AI systems
for Italian SMEs.

Every business pays a price it can't see.
We find it, measure it, and build the system that ends it.

·What's on the bill

No business pays every item.
We can start with just one.

Your accounts record what happened. There's no entry for the order that never came, or for the customer who quietly stopped buying. Open an item to see how it shows up, and which number tells you it's been fixed.

Enquiries that come in and go nowhere

The enquiry that came in on Saturday morning and got a reply at nine on Monday.

They arrive on WhatsApp, through the website, by email, by phone. The first to answer wins the order.

Time to first response
The lead that goes cold without ever saying no

The quote that was sent and never followed up. The customer who bought only once.

Nobody said no. That contact was simply never given a next step.

Leads with a next step assigned
Money that's already yours, arriving late

The March invoice, paid in May.

Overdue invoices get chased when someone remembers, and someone remembers when the day leaves room.

Average days to get paid
Hours spent doing the same things by hand, every day

Data retyped from one spreadsheet into another, with the odd error that slips through and turns up later.

A machine would do it exactly the same way, and it wouldn't skip a line when the phone rings.

Documents processed hands-free
People searching for you who can't find you

They search for exactly what you do, and click on someone else's website.

It happens on search engines and inside AI assistants, which increasingly give an answer instead of a list of results.

Conversions, average position, leads generated
Deadlines that slip past while you're working

The renewal spotted the day after, the grant you read about once it had closed.

Nobody checks them, because they're nobody's job.

Days of notice

Two numbers to give a sense of scale, from the market rather than from us: replying within five minutes makes contact up to a hundred times more likely (InsideSales.com/MIT study, 2007), and European businesses lose seventy-three working days a year on average chasing payments (Intrum, European Payment Report).

·What you've been told

You've been told you need to go digital.
It's true, but only where it's needed.

81%

of Italian SMEs already use AI tools.

Sibill · Astraricerche, Osservatorio 2026, 500 SMEs up to €10M
25%

have built it into their processes. The rest use a chatbot now and then.

Sibill · Astraricerche, Osservatorio 2026

The difference between the two isn't the software they bought. It's that they looked at where the business was losing money before buying anything. The other numbers, with sources →

·How we work

First we count. Then we build.

WhenWhat happensWhat you get
15 minutes We look at how you work and list the steps where you're losing out. The costliest item, and what it costs you.
Day 1 We agree on the number we'll measure by, and take a reading before touching anything. The baseline, in writing.
Days 2 to 30 We build a single process: the one we chose, not four at once. A working system, credentials included.
Day 30 We measure the same number again and put it in front of you. Before and after. No renewal, no penalty.

How this differs from a web agency or a consultancy, point by point, and the four things we never do: it's all in the method →

·Three guarantees

Three commitments we keep.

Systems are monitored, even at night

A system that works for you needs someone keeping an eye on it while you sleep. Monitoring is automatic, 24/7; the response is human. No exceptions.

If a process doesn't need AI, we say so

We use a different technology, or nothing at all. We don't sell AI, we sell results: put AI where it isn't needed and the bill won't go down, and on day thirty the number will show it.

What we use, and where your data goes, is in writing

Every tool, supplier and limit is listed, and any of them can be changed. AI transparency →

·The evidence

Some results from our systems.

What they actually do, timed. Open a row to see what it was measured on.

·Time recovery
From enquiry to ready reply: in 7.3 s

A hundred real enquiries: orders, reorders, complaints, customs questions, reminders. Four channels, five languages.

A hundred real enquiries across four channels and five languages: this is the time from arrival to a draft ready for approval, as a median over the hundred. Twenty that arrived in the same second were all closed, every one of them, in twenty-one seconds, which is exactly when a person would have to choose which one to ignore. A hundred in, a hundred out with their replies, and the right priority assigned a hundred times out of a hundred: complaints and customs at the top, payments and junk at the bottom.

By hand, the same enquiry takes four to ten minutes, and that's a stated estimate: read, understand, look up the data, write, reread. The seconds are timed; the minutes aren't.

100 enquiries · 4 September 2026
Fields captured correctly per document: 98.7% (there's a reason)

Thirty real business documents: invoices, delivery notes, spec sheets, orders. Five languages, three different layouts.

Two hundred and thirty-four fields right out of two hundred and thirty-seven, and the document type recognised thirty times out of thirty: invoice, delivery note, spec sheet or order, in five languages and three different layouts. We had deliberately hidden an unreadable one in the pile, and it set it aside rather than making up the numbers.

The three missed fields have a reason, and here it is: twice the same issue, a zero amount left blank instead of written as zero, and once a country that wasn't on the document and had to be inferred. None of the three is an invented value.

30 documents · 237 fields · 4 September 2026
Time per document: 6.3 s

Open the PDF, find the fields, key them into the business software, double-check.

Six point three seconds per document, median across thirty. By hand, the same document takes three to eight minutes, and that's a stated estimate: the seconds are timed, the minutes aren't.

30 documents · 4 September 2026
·Operations
From message to queued lead: in 4.3 s

A contact writing on WhatsApp, read and queued with the next step already assigned.

Median across nineteen real contacts, not simulated ones. No one is left without a next step, and that's the point: leads don't go cold on their own, they go cold when nobody touches them.

19 contacts · real traffic, August 2026
·New demand
From a list to ten names worth contacting: 389 profiles in an hour (for a client)

The founder of a management SaaS for the beauty industry was looking for Italian professionals to collaborate with, within a specific follower range. Five professions, six cities, no bought lists.

Twenty-two searches, three hundred and eighty-nine names collected, ten delivered in priority order: 2.6%. In between, two filters, the thresholds he set himself, and a profile-by-profile read of the thirty left. One hour and four minutes from the first search to delivery. By hand, the same job takes a week, and somewhere around the two-hundredth name you stop reading and start scrolling.

Three of the ten had already put the problem in writing, in public: one had asked customers to message him again because he'd lost some of their messages, and two take bookings by hand. For those three, the first message was already written, built on what they had posted.

Delivered 11 September 2026 · 389 names · 22 searches
From list to ready-to-send emails: from 428 candidates to 10 hyper-personalised emails

Five public exhibitor lists. No contacts bought, no paid lists.

Twenty minutes in total, for work that takes a salesperson a whole day. Four hundred and twenty-eight names read, sixty-four websites found and confirmed one by one, and ten emails written, each built on a flaw verified on that company's own website: none of the ten could have gone to anyone else.

Run on 4 September 2026 · 428 names
Wrong companies caught before writing: 19

A maker of tube-bending machines, a restaurant, a domain for sale, a Chinese gaming page.

Nineteen companies had the right name and someone else's website. They were caught before they got onto the list, not after the email had gone out: the step that caught them checks each website against its content, and it's the most valuable step in the whole chain.

Run on 4 September 2026 · out of 428 names
·Monitoring
The server is monitored from outside: for 124 days, 35,700 checks

An external check asks the machine whether the systems are up, every five minutes, day and night.

An external check has asked the machine whether the systems are up every five minutes, day and night, for a hundred and twenty-four days: roughly thirty-five thousand seven hundred checks. It runs from outside, so it doesn't depend on the machine it's watching.

Underneath, every single process is logged: when it started, what it worked on, how it ended. Three hundred and fifty-six log entries between 18 May and 26 August. No engine runs in the dark, and when something breaks, a person responds.

Since 3 May 2026 · a check every 5 minutes

Measured on Itria test systems, except where real traffic or a client delivery is stated. Where a row shows an estimate rather than a measurement, it says so. Items on the bill that don't have a number of our own yet stay off this page until they do.

Fifteen minutes to find out which item is costing you most →

·Questions

The ones everyone asks, and fair enough.

How much does it cost?

There's no price list, and we're not being cagey. The price depends on how large and customised the system is, and how long it takes us to design, test and set it up with your data. All of that depends on your volumes. Quoting a figure now would mean making it up.

How long does it take?

Thirty days at most for the first piece, and the baseline is taken on day one. At the end of the thirty days there's no automatic renewal and no penalty: the system stays yours, credentials included.

What about our data?

It stays yours. Which tools handle what, where the data ends up and how far each supplier's access goes is all written down, and can be changed. The full page →

Do we need to change our business software?

No. We build around what you already use: the system reads and writes where you work today. Changing business software is a project in its own right, and it doesn't fit into thirty days.

Our team isn't technical.

The system works on its own and delivers the result where you already look: email, your phone, the spreadsheet you open every morning. If you have to learn something to use it, it's been built wrong.

We've already tried AI and not much changed.

That's the norm, not the exception: it's the gap between the 81% who use it and the 25% who have built it into their work. A tool in one person's hands helps with that half hour; it doesn't touch the step the business repeats eighty times a month. How to close that gap →

·Who answers

There's no switchboard and no sales team.

Mattia Esposito, founder of Itria
Mattia Esposito
Founder of Itria · Crispiano (TA)

On a call, by phone, on WhatsApp or by email, you speak to the same person who then builds the system and looks after it afterwards.

We agree on the number to watch before we start, and I show it to you again after thirty days.

Phone
350 574 3578
WhatsApp
Even just a couple of lines
Email
info@itria.io
LinkedIn
My profile
On your own
The Diagnostico, 5 minutes (in Italian)

Where we started: food and agricultural exporters, hospitality, restaurants. The method doesn't change with the sector: only the starting point does. · Where I come from →

·The first step

Fifteen minutes, and you'll know what it's costing you.

What happens

The steps where you're losing out, listed. A figure, and the place to start.

What doesn't happen

No quote, no contract, no one chasing you in the days after.