Technology consulting for SMEs · Florence, Italy
Custom software and AI that give people their time back.
I don't automate chaos. First I put the way you work back in order, then I make it run almost by itself. The result is not measured in efficiency: it is measured in the evening you leave at six and bring nothing home.
First call is free. If it is not your case, I will tell you so.
Animation: dozens of scattered, disordered violet blocks slowly arrange themselves into an ordered grid and turn green. Then about half of them dissolve upwards, leaving empty space: the time given back to people.
The day you know
It is not that time is missing. It is that time goes somewhere.
For SMEs running on emergency mode, the problem is almost never a lack of work or capable people. It is that a huge share of the day disappears into activities that produce no value: retyping data, hunting for information, reconstructing what was decided, redoing what was already done.
- The day starts and the first hour goes on working out where things stand.
- The same data gets entered twice, in two places, by two people.
- To know whether an order shipped you have to ask someone. And that someone is on holiday.
- There is a spreadsheet holding up part of the company, updated by exactly one person.
- You use 30% of the system you bought: the rest has nothing to do with you.
- At seven the phone still rings, and you already know it is about something avoidable.
If you recognised at least three of those lines, the problem is not your organisation. It is that people are holding together what the system should be holding together.
The point
You are not behind. You were sold the wrong race.
The dominant message about the technological future is urgency: adopt now or fall behind. It produces the opposite effect. 73% of CEOs report stress or anxiety related to AI, and 60% have deliberately slowed adoption precisely out of fear of getting it wrong.
The fear of taking the wrong step is stronger than the desire to take the right one. It is a normal human mechanism, and no enthusiastic presentation dissolves it — it makes it worse.
The race is not what you need. You need a direction, an order of priorities, and the certainty that you can turn back if something does not work. People who work that way get further than those who adopted everything at once and then had to undo it.
The enemy is not you, and it is not technology. It is the way the work is organised today — a way that was born when you were five people and has never been questioned since.
Where this is going
The future of work is not faster. It is cleaner.
Ten years ago the future was digital: everything connected, everything quicker. That promise came true and produced exhausted people. The vision that makes sense now is different: clean environments, human rhythms, machines taking the mechanical work and giving people back the part that matters.
A company where nobody runs is not a slow company. It is a company that stopped doing everything twice.
A single screen that tells you how the company is doing. No blind spots, no files to open to understand. The full picture, updating itself.
The phone that stops ringing at seven. Nobody calling to ask where things stand, because where things stand is visible to everyone.
One weight less. The ability to be away for a week without anything stopping, because what only you knew is now known by the system too.
Three routes
How you get there
There are three ways in, and you almost always start with just one. You do not need to rebuild everything: in most cases removing the main bottleneck is enough to let the rest breathe.
01
Custom management software
A system built around the way you actually work, not around the way an off-the-shelf product insists you should.
- Process analysis before a single line of code
- Integration with what you already use (accounting, stock, email)
- Historical data migration, nothing left behind
- Up to 2 years of warranty on delivered software
02
Applied artificial intelligence
Not "doing AI". I take the three manual jobs that cost you the most hours every week and hand them to the machine.
- Start from repetitive work, not from the technology
- Automating documents, email, quotes, classification
- Internal assistants trained on your own company documents
- Your data stays yours: never used to train third-party models
03
Websites and e-commerce
A site that brings in enquiries while you do something else, and that gets found both by Google and by the AI assistants people now ask for advice.
- Designed around real demand, not around anyone's taste
- Speed and accessibility as requirements, not extras
- Technical and semantic SEO from day one
- Optimised to be cited by ChatGPT, Claude, Perplexity and AI Overview
The method
What happens, exactly, and in what order
The path is always the same and no phase starts before the previous one has closed. You know in advance what happens, how long it takes, and when you can stop without having lost anything.
-
Listening
One call. You tell me where your day gets stuck. At the end I tell you honestly whether this is a problem worth tackling now, later, or never. Plenty of calls end with "you don't need this".
-
Mapping
I come and see how you actually work, not how the manual says you do. I talk to the people doing the job, not only to the people running it. You receive a map of the current process with the points where time is lost, quantified in hours. That document is yours even if we stop here.
-
Proposal
I present three levels of intervention: the minimum that solves the biggest problem, the recommended one, and the complete one. With timings, costs and what you get from each. You choose. No pressure, no invented deadlines.
-
Building
I do not disappear for six months and reappear with something. Every two weeks you see a working piece and you try it. Every Friday you get a thirty-second update on what was done. If something is heading the wrong way, we find out in week two, not in month six.
-
Autonomy
Handover, training your people, documentation, and the warranty on the software. The stated goal of this phase is that you no longer need me. If a supplier has an interest in making you dependent, you have the wrong supplier.
The risk
I am not asking you to trust me. I am giving you guarantees.
The three things below go into the contract, not into a presentation. They are verifiable, and they are how I take on part of a risk that would otherwise be entirely yours.
-
Up to 2 years of warranty
If the delivered software does not do what we agreed, I fix it. Without re-reading the quote looking for the line that proves me right.
-
The code and the data stay yours
Documented, in open formats, exportable whenever you want. I use no technical locks or contract clauses to make changing supplier expensive.
-
You can stop after two weeks
At the end of the mapping phase you hold a document that has value even without me: your process, with the points where time is lost quantified in hours. If you decide not to continue, that document is still yours.
Honesty
Who this is for, and who it is not for
I do not work with everyone, and saying so upfront serves us both. A project that starts with the wrong expectations ends badly even when the software is perfect.
It makes sense if
- You have between 10 and 250 staff and your way of working outgrew your tools.
- At least one person in the company can give the project a few hours a week.
- You want to understand what you are buying, not just delegate it.
- You care more about the result in two years than about the cheapest quote today.
It does not make sense if
- You are looking for the lowest quote: it will not be me, and I say so now.
- You want to "do AI" without knowing which problem it should solve.
- Nobody in the company has time for the project: without your knowledge it does not work.
- You expect to hand everything over and not be involved until the end.
Questions
The questions I always get
It depends how many processes it touches, and that is the only honest answer before seeing how you work. For an order of magnitude: a targeted intervention on a single process starts in the low thousands; software covering the full operations of an SME typically lands in the five-figure range.
What I can guarantee is how you get to the number: after the mapping phase you receive three options with price, timing and expected result, and you decide. No quote arrives before the problem is understood.
The process map arrives within two weeks of starting. The first working, testable piece of software arrives within the first four to six weeks of development, and every two weeks after that.
I do not work with a single delivery at the end: it is the surest way to discover too late that something was misunderstood.
If your process is standard, buying off-the-shelf is the right call and I will tell you so myself. Packaged software costs less, installs faster and is maintained by an entire company.
Custom makes sense when the way you work differs from your competitors and that difference makes you money. In that case bending to standard software means giving up your advantage to save on a licence.
In the projects I do, no: AI takes the mechanical work, not the craft. Reading a PDF and retyping its contents is not a craft — it is an activity consuming the time of someone who could do better things.
The rule I always apply: AI prepares, proposes and flags, but decisions with financial or legal consequences are confirmed by a person. The signature stays human.
No. I use configurations where company content is not used to train third-party models, and when data is particularly sensitive I evaluate solutions running on your own infrastructure.
Worth knowing: 67% of executives believe their company has already suffered a data leak through AI tools used by employees without authorisation. Giving the team an official, safe tool is also the most effective security measure.
The code and the data are yours, documented, and you take them with you. I do not use closed formats or contractual locks to make leaving expensive.
A supplier who makes it hard to leave has stopped competing on quality. I would rather you stay because it suits you, not because you cannot do otherwise.
The office is in Florence and for clients in Tuscany and Emilia on-site work is the norm, particularly during analysis.
Elsewhere in Italy and in Europe I work remotely with one or two on-site visits at the key moments: initial analysis and training. Those are the two phases where being physically present makes a real difference.
I do. There is no handover to a support desk that does not know the project: you talk to the same person who built it.
Average response time is 12 working hours and the software warranty runs up to 2 years.
The first step
We start with a conversation, not with a quote.
Forty-five minutes in which you tell me where your day gets stuck. At the end you will have at least one useful thing: my honest opinion on what to tackle first — even if you then decide to do it with someone else, or not at all.
No commitment, no email sequence afterwards. If you are not the right client, I will be the one to say so.