Fabrizio D'Urso

API Integrations and Automation

I build API integrations and automation: I connect the tools a company already uses, like payments, accounting, banking and management software, and remove the work someone does by hand today, copying data from one place to another.

What I can do for you

Connect two systems that don't talk to each other today, so the data moves on its own.
Automate repetitive work: documents, reports, emails, checks.
AI automation: reading documents and files, filling in data, drafting replies. With a human confirmation before anything important.
The backend that holds it all together, on AWS or Firebase, with an alert when something goes wrong.

How I approach an integration

First I find out where time is lost today and who does what by hand. Then I start with the piece that pays off most, not with everything at once.

Every integration has a test environment, a log of what goes through it and an alert when a call fails. So you see a problem right away, not a week later.

Where I've done it

Ruralis

When I joined there was little more than a draft. I built the foundations of the platform: the serverless backend on AWS, the internal management tool and the automations that handle the paperwork on their own. With integrations for payments, accounting and banking: Stripe, QuickBooks, Qonto.

Lumideo

In-app subscriptions on iOS and Android, notifications, and cloud functions that do their job on their own when the day comes to open a video.

App Store Google Play

Don Gaitano

OpenAI and ElevenLabs inside an app: text and voice generated for every request.

App Store Google Play

What I work with

Node.js and TypeScript, AWS (Lambda, API Gateway, DynamoDB, S3, queues and events), Firebase, Python. REST APIs, and SOAP when needed.

Is there a task that eats hours of your week?

Tell me where the time goes. In the first call we work out what can be automated.

Let's talk for 15 minutes

Contact

Let's talk

Tell me what you want to build. I'll reply within 24-48 hours.

The questions you're asking yourself

I reply within the hour. When I start a project, I see it through. Whether I'm in Naples, Mexico or Japan, I work on European hours: within my working day, I reply within the hour. You know this before we start, not after.
It's yours from day one. The code on GitHub, server access, every project document: shared with you from minute zero. Not on delivery — right away. Which means the work carries on without me.
The price doesn't move. Once agreed, the price stays. Even if I got the hours wrong: my mistake, my cost. It changes only if what needs building changes, and in that case you hear it from me first — not on the invoice.
You're buying a date, not a file. A delivery date and something running in production. Not a file, not a zip: on the day I told you, it's live and you're using it. And from then on it's yours, because you've had it since day one.