Services

Work together

I build web and mobile apps, backends and AI automations, remotely: per project, or inside your team for a while. I work on one or two projects at a time, and it always starts with a free 15-minute call.

Write to me

  • 16 years of development
  • 8 apps published
  • almost 11 years at Crisalix
  • mentor at Nana Bianca and Startup Geeks

Three ways to work together

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
  • Per project at a fixed price, or on time if I work inside your team: agreed 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

How it works

From the first call to when it's live

  1. A 15-minute call

    You tell me what you need. We figure out whether it makes sense to work together and when we can start. It's free.

  2. A written proposal

    I send you in writing what I'll build, how long it takes and what it costs. Once agreed, the price doesn't move: if I underestimated the hours, that's on me.

  3. We build it, and you see everything

    The code on GitHub and the server access are yours from day one, not at delivery. I reply within 24 hours.

  4. Live, not a file

    At the end it's live and working, deploy, domain and stores included. And if you need it, I can look after it afterwards for a fixed monthly fee.

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

The questions that come before the call

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.

Do you also work by the hour?

Yes, when you need one more person inside your team for a while, for example a few months. Then we work on time, and hours and duration are agreed upfront. For a defined piece of work, I prefer a fixed price: you know what you spend before we start, and if I get the estimate wrong, that's on me.

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.

Referrals and agencies

Bring me a client? I give you 15%.

If you work with companies and startups, have you ever heard "we need an app"? Introduce me to the person, I do the rest. If the project closes, I give you 15% when the client pays.

If you run an agency and you don't do development, you can pass it to me, white label too: you stay in front of the client.

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.