Fabrizio D'Urso · freelance full stack developer

I build apps, backends and AI automations. From the idea to when it's live.

I shipped my first app in 2010 and never stopped. Today I build apps, backends and automations for startups and companies, on my own, from start to finish.

Write to meBook 15 minutes

  • 16 years of development
  • 8 apps published
  • almost 11 years at Crisalix
  • mentor at Nana Bianca and Startup Geeks
Lumideo: a capsule openingLumideo: sent capsules, with the days left
Lumideo, my app. Designed, built and shipped by me.

Twenty seconds

Who's on the other side

Route through places lived and worked fromNaples, Barcelona, Chiang Mai, Athens, Malaga, Yogyakarta, Ho Chi Minh City, Kuala Lumpur, Tenerife, Seoul, Warsaw and Prague.NaplesBarcelonaChiang MaiAthensMalagaYogyakartaHo Chi Minh CityKuala LumpurTenerifeSeoulWarsawPrague

Before building

Does any of this sound familiar?

If so, I can probably help.

  • Manual processes steal hours from you every week.
  • You have an idea to turn into a real product, fast.
  • No one on the team knows exactly what to build first.
  • You have integrations and internal tools that slow everything down.
  • You have something that works, but nobody quite knows how any more.
  • You need it to keep working, not just to be finished.

We sort things out, decide what to build and put it live.

What clients say

What people say about me

“Fabrizio was instrumental in the growth of our company — from an early-stage startup with a small development team to becoming a global leader in our sector. Technical depth, product vision, and the ability to scale systems and people: everything we built carries his mark. A rare combination of engineering excellence and product vision.”

CEO

“When Fabrizio joined the company, we had almost no technical foundation. In a few months he designed and built the entire technology stack from scratch — with results so effective that we went from having nothing to being ahead of the sector. That level of ownership and execution is rare.”

Head of Engineering

Services

Shall we work together?

It starts with a free 15-minute call.

I work on one or two projects at a time, no more. On the call we see if it makes sense to work together and when I can start.

01

One specific thing, built and shipped

A site, an app, an automation. We decide first what goes in, it's done quickly, and at the end it's live, not a file to install.

  • For people who already know what they need and want someone to build it
  • Deploy, domain and infrastructure included
  • The code is yours: repository, credentials, access
Write to me

02

Your company's entire technology

App, backend, internal ops tool, integrations, infrastructure. From scratch and on my own, as I have done before, or together with your team.

  • For people who have to build everything and have no technical team, or already have one but need someone with my experience
  • Quoted per project, in writing, after understanding what's actually needed
  • One person following everything, from start to finish
Let's talk about it

03

Someone who looks after it, every month

Something built is not something finished: it needs updating, fixing and keeping alive. A fixed monthly fee, and we write down first what it covers.

  • For anyone with something already live and nobody looking after it
  • Updates, fixes, store releases, monitoring
  • I take over code written by other people, or by you
Let's see what you need

Projects

Selected projects

Some of the projects I've built, across client work and my own products.

Lumideo: record a video, it opens on the day you choose

Lumideo

Record a video today and watch it again in a year, or whenever you want. For you or for someone you love.

Ruralis

When I got there, all that existed was a rough draft of the mobile app. In one year I shipped it on the App Store and Google Play, built the backend, created the internal ops tool from scratch, and the platform where guests check in and manage their bookings.

Crisalix

Almost eleven years testing, automating and leading development of a medical platform used by surgeons in more than 80 countries.

Friday Coffee

Born from a problem of my own, as a nomad: finding real connections when you work alone. A Friday ritual for remote teams.

OutyPlay

An app to find people to play sports with near you. Built and launched on my own.

StringSwitch

A tool for converting localization files between iOS and Android without rewriting strings by hand. Built from a real problem I hit while working on multilingual apps.

Noon Happen

A dating app that started from two concrete things: when you are free and what you feel like eating. Less swiping, more meeting at a table.

About

You have the idea, I make it work.

I wrote my first line of code in 2010, when programming books weighed three kilos and Stack Overflow already felt like magic. My first app reached 150,000 downloads.

Then almost 11 years at Crisalix, a medical platform used by surgeons all over the world. Today I work remotely, from different places, for startups and companies.

My story

Questions

FAQ

A few things people usually ask before reaching out.

Is the call free?

Yes, fifteen minutes. It's there to work out whether it makes sense to work together, not to sell you anything.

How much does it cost?

It depends on what you need, and I'll tell you on the call once I understand the project, not before. I don't have prices on the site because a number without context helps neither of us.

How long does it take?

One defined thing is measured in days or weeks, an entire product in months. You get the estimate after the call, in writing, and if I'm about to overrun you'll know before I do.

Where do you work from? What about time zones?

Remotely, and from different places. I always reply quickly when we're inside a project.

Is the code mine?

Yes, all of it: repository, credentials, access. I don't hand over a zip file and I don't hold anything hostage.

Can't I just do it with AI?

To get to a first version, often yes, and I use it every day myself. The real work starts after that: connecting it to systems that don't behave the way they should, fixing it when it stops working on a Friday night, changing it without breaking what was already there. Two of my clients came to me exactly that way, with something they had built themselves that now needs somebody to keep it running.

What happens after the call?

If it makes sense to work together, I'll send you a written proposal with what we're building, what it costs and when we start. If it doesn't, I'll tell you, and I'll tell you why.

Interested? Write to me.

Tell me what you need and I tell you if I can help.

Write to me

Contact

Let's talk

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

Rather pick the time yourself?

Book 15 minutes

The questions you're asking yourself

  • I reply within 24 hours. When I start a project, I see it through. Whether I'm in Naples, Mexico or Japan, I work on European hours and I reply within 24 hours. 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.