Operations automation · For company teams in Malta

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

Rekeying, report rebuilds, inbox sorting, approval chasing. I automate one process at a time, inside your own accounts, with your IT team holding the keys.

Email me the process See it in your department →
  • Written scope, fixed price
  • Built in your own accounts
  • GDPR agreement with every build

One person, one process at a time, and everything I build sits in your accounts from day one. Based in Mellieħa, and I'll come to your office.

P
Purchase approvalsTeam chat

Example messages, not a real company.

Sound familiar?

Where the week goes.

None of these need your systems replaced. Each is a step between two you've already got.

Works with what you already run

It connects the accounts you already have, using the access your IT team gives me. The one new piece of software runs in your organisation's name, on your own servers or its maker's, and any licence it needs is named in the quote before you agree to anything.

  • Outlook
  • Teams
  • SharePoint
  • OneDrive
  • Excel
  • Microsoft SQL
  • Dynamics 365 CRM
  • Gmail
  • Google Sheets
  • Google Drive
  • Slack
  • Jira
  • ServiceNow
  • Zendesk
  • Freshdesk
  • Salesforce
  • HubSpot
  • Xero
  • QuickBooks
  • Odoo
  • BambooHR
  • Oracle Database
  • Snowflake
  • SFTP
  • Stripe
  • Not listed? Ask, and I'll look first.

Pick the handover

What this looks like between your teams

Common examples, not a list of limits. If a step between two systems repeats, tell me yours.

The usual processes

Pick the ones your team repeats.

Start with whichever one costs your team the most 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.

1
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.

2
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.

3
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.

4
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.

Scope · Example

Yours is written after the first call.

Process
Purchase approvals
Trigger
A request has waited three working days
Steps
  1. Request read from the purchase systemautomatic
  2. Summary sent to the manager in team chatautomatic
  3. Manager taps Approvea person
  4. Answer saved on the requestautomatic
  5. Finance raises ita person
Systems and access
  • Purchase systemreadopen requests
  • Team chatcreateone message per request
Test
Sample data, pass before go live
Price
One fixed figure, written here before anything starts
Handover
A named owner, a written guide
youme

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.

Riccardo Tedesco

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

To
your IT team
From
Riccardo Tedesco, Neurocraft
Re
an outside automation you've been asked about
  1. 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.
  2. I never run it on my own server.
  3. It connects through service accounts your team owns, never a person's own login.
  4. 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.
Clauses five to eight
  1. Nothing goes live until you've seen that list, and I test it on sample data first.
  2. Every run's logged in your account, and anything that approves, pays or decides waits for a named person.
  3. 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.
  4. 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.

What I'd ask of you
01A service accountin your organisation's name, never a person's login
02Read on the named systemsthe narrowest permissions each system offers
03A named ownerwho takes it over, with a written guide
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 riccardotedesco9@gmail.com Call +356 9951 1425 I reply the same working day, in English or Maltese.

Opens your email with the message written, to send from your own address. Nothing's stored on this website.