The steps between your systems, done the same way every time.

What the research says

The numbers

Every number below is sourced, dated and says who was asked. None of these surveys covered Malta.

29%

of applications are connected to each other, out of 897 on average, at the large organisations surveyed.

MuleSoft Connectivity Benchmark 2025, a vendor survey run with Vanson Bourne and Deloitte Digital: 1,050 IT leaders at organisations of 1,000 or more staff in nine countries, October to November 2024.

8.2 hours

a week that knowledge workers estimate they spend looking for, recreating and duplicating information.

APQC survey of 982 full time knowledge workers, published November 2021.

18%

of the controllership staff surveyed make a financial error at least daily.

Gartner, February 2024: survey of 497 people in the controllership function, run in July 2023.

3.6 hours

a week that knowledge workers estimate they spend managing internal workplace communication.

APQC survey of 982 full time knowledge workers, published November 2021.

How it works

What happens after you email.

Free · a call or a visit

You and I scope one process.

You walk me through the steps, the systems and who signs off, and I write it down.

Within two working days

You get a written scope.

What it'll do, how it's tested, and one fixed price. Nothing starts until you sign.

Dates agreed in the scope

I build it where IT can see it.

In your own accounts, with the access IT gives me, and tested on sample data first.

Every day after

It runs, and your team owns it.

A named person on your team takes it over, with a written guide and a handover.

Start with step one Free, and the scope's yours to keep whether or not we go ahead.

Your data stays yours, in writing.

A signed agreement before any access. We sign a data processing agreement, the contract GDPR Article 28 requires, before I see anything. If your legal team has its own, I'll work from that.
One new tool, in your organisation's name. The automations run on one piece of software, set up in your organisation's name, on your own servers or its maker's servers in Frankfurt. Your IT team chooses, and the agreement lists every service involved.
Your data, used for your job only. It stays in your accounts rather than mine, it never goes in a demo, and no AI step runs without your written approval.
Breaches reported without undue delay. If I find or suspect one, you hear from me without undue delay, exactly as GDPR Article 33 requires, so your DPO has time to act.
A clean exit. When the work ends, I hand back or delete anything I hold, remove my access, and your team keeps the guide.

Security questions, a processing agreement or your own contract terms: send them before the quote and I'll answer each one in writing.

About

The person you email is the person who builds it.

Riccardo Tedesco

I've lived in Malta all my life and I'm based in Mellieħa. Before this I spent five years training as a commercial pilot, which is where I picked up a systematic way of working.

I took that into every job since: restaurant floors as a waiter, a warehouse, a hospital IT desk, and an office that got through hundreds of documents a day. I kept noticing the same thing everywhere, people giving up their day to jobs a small setup could handle, and it drove me to build things that took the job off their hands. That's where this came from. I enjoy the puzzle of it, and I'm just as interested in the people it's for.

Working on a hospital IT desk showed me what IT teams need from anyone who builds on their systems: to be asked first, to see it all written down, and to be able to switch it off. It's just me, so everything I build runs in your accounts and comes with a written guide, and your team isn't stuck if I'm not around. You see the work before it goes live, and the price is fixed before anything starts.

If your problem doesn't need automation, I'll tell you. Talking you out of a bad idea is part of the job.

Fair questions

What your team will ask.

“What happens if you're not around?

It's just me, so I build as if I won't be. Everything runs in your organisation's accounts, under logins your IT team controls. If I stopped halfway through a build, you'd keep everything made so far: it's in your account from the first day, with notes on where it stands. Each process comes with a written guide and a handover to a named person on your team, who can pause it, change it or pass it to any developer who knows the tool.

“Will our IT team allow it?

I'd rather work through them than around them. IT creates my access, with the narrowest permissions each system offers, and can remove it at any time. Nothing goes live until they've seen the full list of what it connects to, and after go live, changes go through your own change process. There's a note for them, written to be forwarded.

“We already have Power Automate, or our own developers.

Then the tools aren't what's missing, the time is. Small processes rarely reach the top of a development backlog, and they're the work I take on. I build in n8n. If your IT team would rather it lived in Power Automate, tell me at the start and I'll say straight away whether I'm the right person for it.

“What will it cost, and what's ongoing?

You get one fixed price for the build, in writing, before anything starts, and the first chat is free. For the first week after it goes live, fixes cost nothing. After that you choose between two options: €80 a month cover, which covers the processes named in your quote and fixes anything I built that stops working, including when Microsoft, Google or another service changes something on their side, or €30 an hour, as you need it. New work gets its own quote. Outages at those services and changes someone else makes aren't included, and if a change on their side means rebuilding part of it, you get a quote first. Licences and running costs are named in the quote and paid straight to the provider, never through me. If your IT team needs single sign on, that licence can cost more than the build, and I'll say so before you spend anything. No VAT is added, because I'm registered under Article 11.

“What if it breaks?

Every build sends an alert when a run fails, always to a named person on your team, and to me as well on cover. On cover, I reply the same working day and start on the fix by the next. On n8n's cloud, n8n keeps the software up to date. On your own server, your IT team does, or I do on cover. Every run's logged in your own account, so your team can see what happened and when, and neither option ties you in.

“Where does our data go?

It's set up to hold as little as possible. Each step keeps only what its job needs, it all runs in accounts in your organisation's name, and we sign a GDPR processing agreement before I start, so what I can and can't do with your data is in writing. The engine runs on n8n's own cloud in Frankfurt or on your own servers, whichever your IT team prefers. The services it connects to, like Microsoft 365 or an AI provider, keep their own hosting terms, and the agreement lists each one and where it processes data. If it touches patient records or other health data, your DPO will likely want an impact assessment first, and I'll give them the details it needs.

“Does any of it use AI?

Only where it earns its place, and only with your written approval, on terms that keep your data out of anyone's model training. If AI drafts something a customer will read, a person on your team reads it and sends it. If customers ever chat with it directly, its first message says it's automatic, as the EU's AI Act has required since August 2026, and they can ask for a person at any point. It never decides anything about a customer or an employee, and it never touches patient records, other health data or hiring.

A note for your IT team

The automation runs on n8n, either on n8n's own cloud in Frankfurt or on a server you host, always under an account in your organisation's name. I never run it on my own server. It connects through service accounts your team owns, never a person's own login, and you create my access with the narrowest permissions each system offers. Where a connection asks for more than the job needs, I'll list it and say why. Nothing goes live until you've seen that list, and I test it on sample data first. Every run's logged in your account, and anything that approves, pays or decides waits for a named person. Single sign on, log streaming and separate environments are paid n8n features, billed to you by n8n directly. Single sign on starts on the Business plan and can cost more than a small build, so I'll say on the first call whether you need it. I don't hold ISO 27001 or SOC 2. I'll answer your security questionnaire in writing, sign a GDPR processing agreement before any access, and remove my access when the work ends. If your regulator expects set terms in an outsourcing contract, send them over and I'll say in writing which I can sign.

Forward this to IT

Get in touch

Tell me the process your team repeats every week.

A few lines is enough: the steps, the systems, and who signs off. A good first process is internal, with no customer data in it. If it isn't worth automating, I'll say so.

Email [email protected] Call +356 9951 1425 I reply the same working day, in English or Maltese.

How your details are handled

Last updated 26 September 2026

This is short, because this site collects almost nothing. There are no accounts, no payments, no analytics and no advertising trackers. The enquiry form is the only place anything is entered.

Who is responsible

Riccardo Tedesco, trading as Neurocraft, a self employed sole trader at Triq l-Għerien, Mellieħa, Malta. VAT registration 33090118, registered under Article 11 as a small undertaking, so invoices carry no VAT. Email [email protected] or phone +356 9951 1425.

What the form collects

Your name, a line about your business or your work, what you would like help with, and your email address if you choose to give it.

Nothing is stored on this website. Pressing the send button opens WhatsApp or your own email app, depending on the page, with your answers already written into a message, and nothing is sent until you press send there. A message sent through WhatsApp is also covered by Meta's privacy policy. Email and phone work just as well.

Why, and on what basis

To answer you, quote for the work and keep my own records for invoicing. The basis is legitimate interest, Article 6(1)(f) GDPR: you contacted a business asking about work, and replying is the ordinary consequence of that. Nothing is used for marketing, and nothing is sold or shared for advertising. You can object at any time and I will stop.

If you are a sole trader asking about work for yourself, the basis is also taking steps you asked for before a contract, Article 6(1)(b). Invoices and job records are kept because tax law requires it, Article 6(1)(c).

Who else sees it

WhatsApp (Meta) carries messages sent through WhatsApp, Google runs my email, and Cloudflare delivers this website and so handles your IP address when the page loads. Meta, Google and Cloudflare may process data in the United States under the EU and US Data Privacy Framework, Commission Decision (EU) 2023/1795.

How long it is kept

Enquiries are kept for up to a year after we last speak, then deleted. Where work goes ahead, invoices and job records are kept for as long as Maltese tax law requires.

Your customers' information, when I build for you

This is the part that matters if you hire me. An automation usually touches lists you already hold: customers, bookings, invoices, suppliers. That information stays yours. In data protection terms you remain the controller of it and I act as your processor, only on your instructions.

In practice: the work is set up inside accounts in your name, so your customers' details stay in systems you own and you can revoke my access at any time. I do not copy your customer lists out for my own use, I do not use them to train anything or in any demonstration, and I do not pass them to anyone else.

Every build comes with a written processing agreement under Article 28 GDPR, signed before I get access to anything. It sets out what I process and why, that I act only on your written instructions, which services are involved, how your data is kept secure, that I will help you answer requests from your customers, that I will tell you about any breach without undue delay, and that everything is returned or deleted when the work ends. It follows the European Commission's standard contractual clauses, Implementing Decision (EU) 2021/915.

Where a build uses an AI service, it is one you agree to in writing, on terms that keep your data out of model training, and any reply it writes tells your customer that it is automatic, as the EU AI Act requires. It never makes a decision about a customer or a member of staff.

This website itself

The page sets no cookies and runs no analytics. Its typefaces are stored on this site, so nothing is fetched from anyone else. The site is delivered by Cloudflare, which handles your IP address to serve the page and protect it from attacks, acting as my processor.

Your rights

You can ask for a copy of what is held about you, ask for it to be corrected, deleted or restricted, ask for it in a form you can take elsewhere, or object to it being held at all. Email [email protected] and it will be actioned. If you are not happy with how that goes, you can complain to the Maltese Information and Data Protection Commissioner at idpc.org.mt.