Automation and AI agents
The product is born already connected: leads that enter the CRM on their own, a chatbot that qualifies and books, alerts to the team when something gets stuck.
Software house · Remote, EU
The system you bought years ago covers the easy part and stops exactly where your way of working begins. I build the missing piece: internal tools, portals, web apps and prototypes cut to the process you already have. AI goes in where it frees up hours you can count. I work remotely with small companies across Europe, and from quote to release you talk to the person who writes the code.
I work with companies of two to twenty people: workshops, professional practices, distributors, labs, agencies. Companies where one person knows the process by heart, and when that person goes on holiday everything slows down at once. That is exactly where custom software earns its place. It takes the part that repeats itself out of the spreadsheets, and leaves people the part that needs judgement.
The question to ask is not build or buy. The question is which piece of your work deserves to be built. An off-the-shelf CRM holds contacts perfectly well and nobody has a reason to rewrite it. What it cannot hold is the logic with which you, and only you, price a job. Inside it there is a bill of materials, a price history and three exceptions that apply to the customer you have had for fifteen years. That piece gets built; the rest gets bought and connected.
It starts from a process, never from a technology. In the first forty-five minute call I look at how you work today: who touches what, with which tool, how many times a week. What comes out is a scope small enough to fit in two or three weeks and useful enough to change a working day.
That first piece goes live and gets measured in the field. The rest comes after, paid for by the hours the first piece freed up. It works the opposite way to the six-month project, the one you only see when the work is finished. On delivery, a project like that looks like what you had in mind in January, not like the work you do today.
Before the final code there is always a clickable prototype. It is there so you can say a step is missing while fixing it costs an afternoon, instead of after testing is over. You see the screens before they really exist, and we write the list of corrections while you are looking at them.
Artificial intelligence goes in where it frees up measurable hours. An attachment that reads itself and lands in the right fields. A product sheet written from the technical data. A natural-language search across the company archive. Where the model would cost more than it returns, I say so before it goes into the quote, and the reason stays written in the report.
The code, in the end, stays yours. Repository, credentials and documentation pass to you on delivery, with no exclusivity clauses. Almost nobody changes supplier halfway. But knowing the door is open changes the way we work together. I have to earn the next project, and you never have to defend yourself from something written in small print.
A development job rarely ends with the code. You need the page that presents it, the data to tell whether it is working, the content that keeps it alive. Here is everything I cover, with typical timings.
The product is born already connected: leads that enter the CRM on their own, a chatbot that qualifies and books, alerts to the team when something gets stuck.
The shop window the product deserves: landing pages with scroll animations, restyling of existing WordPress sites, forms wired to your back office. Copy included.
The core of the job: clickable prototype, then dashboards, logins, payments and apps on the stores. Two to ten weeks depending on scope.
A shop on WooCommerce, Shopify or headless with the real numbers beside it: margin per product, server-side GA4, recovery of abandoned carts.
A product nobody finds stays half a product: ranking on Google and presence in the answers of ChatGPT, Perplexity and AI Overviews.
Carousels, edited reels, product spots and talking avatars to tell people what you built. Storyboard approved first, generation after.
When the pieces add up: agents that orchestrate leads, content and reports, a company archive you can question, one dashboard for the owner.
A restaurant loses phone bookings while the room is full, hands a slice of every online order to the portals, and chases no-shows by hand. RistorantePRO closes those three holes in one place: bookings, a digital menu with allergens and food cost, orders on the kitchen screen, till and stock.
The AI part is not an accessory stuck on top. An assistant answers at any hour on WhatsApp, Instagram and Facebook and writes into the calendar by itself. A voice agent takes the calls, five at a time if needed, and passes on only the ones that deserve a person.
The product is mine and it pays for its own servers: you can open it right now at ristorantepro.it, and it is the most honest way I have to show you how I build.
Three families of work, one person to talk to. I build it, no subcontracting.
The price is fixed and you know it before we start. As an order of magnitude: a single automation costs less than one month of an employee's salary. A whole internal system gets sized after the Check-up, when we know what is really needed and, above all, what can be left out.
The Check-up report arrives four days after the call. The first useful piece goes live in two or three weeks; a complete product takes two to ten weeks depending on scope. Between one step and the next there is always something you can try with your hands.
In most cases yes. I read from and write to the systems you have, from the back office to the CRM to the shared spreadsheet, and where no clean hook exists I build a dedicated bridge. What already works stays where it is, even if I did not write it.
I do, from the first call to the release. No subcontracting and no handover to a team you have never heard of: you always talk to the same person. If at some point another specialist is needed, you know it before they touch the project.
You do, with no exclusivity clauses. Repository, credentials and documentation pass to you on delivery. Whoever comes after me finds readable, commented work, not a maze built to make replacing me painful.
Remotely, with companies across Europe. Calls booked in the calendar, progress visible at every step, everything put in writing: a site visit is reassuring, but it does not make the code better. Where a project genuinely needs it, a trip can be arranged.
Describe the work you keep standing by hand today, spreadsheet by spreadsheet. By the end of the call you know whether it is worth building and roughly what it costs.
Book a call