Guglielmo Paesano AI engineer and founder of AIGROW

I build AI systems that do people's work, and I measure where they still need people.

contact@guglielmo.ioDiscord, 4K members

A freelance AI engineer, hired per project

Four defined offers from one engineer: an AI agent, an MCP server, retrieval over your own documents, or an evaluation of a system you already run. Each is scoped in writing, priced per milestone and handed over complete.

The four offers

How the work runs

Method
A written brief in, a working deliverable out
Cadence
Milestones, each one approved before the next starts
Meetings
None required
Clients
United States, United Kingdom, Canada, German-speaking Europe
Pricing
Per milestone against a written scope, quoted per project
Handover
Code, deploy path, tests and the record of every decision

Why the work runs in writing

An asynchronous engagement is one where every decision, constraint and trade-off is written down at the moment it is made. It is slower to start and faster to finish, and at the end you own a readable record of why the system is the way it is.

Nobody has to be interviewed to find out why a decision was made, because the reasoning sits in the repository next to the code that implements it. Time zones stop mattering too, which is why most of the work is for teams in the United States, the United Kingdom, Canada and German-speaking Europe.

How an engagement runs, step by step

What this is not

No staff augmentation, no joining your standups, no hourly billing and no open-ended maintenance retainers. If what you need is an engineer inside your team every morning, you need to hire one, and I will say so before taking the engagement.

Questions about hiring

Why are there no prices on this page?
Because the figure depends on the scope, and a number without one would be a guess you could not hold me to. Send a brief and you get a written scope with a price for each milestone. If the project is not a fit for me, you get that answer instead, with the reason.
What goes into a good brief?
What the system has to do, what already exists, who will use it, and when it has to be live. A sample of the data helps more than a long description. Rough is fine: the scope I write back is where it gets precise.
How long does a project take?
A system that does one job properly is usually weeks, not months. The first working version of the 1o1.org dialogue engine existed in ten days; the product around it took a sequence of milestones after that. The variable is scope, which is why it is agreed in writing first.
Can you work alongside our engineering team?
For a defined piece with a clear boundary, yes: an agent, a connector, a retrieval layer, an evaluation. For work that means sitting inside the team day to day, no. In that case you need to hire, and I will tell you so.
Who owns the code?
You do, on delivery of each milestone, along with the deploy path and the written record of the decisions behind it. Nothing is held back as leverage and nothing depends on me to keep running.

The systems built this wayWho builds them

Start with a brief.

Write what the system has to do, what exists already and when it has to be live. I read every brief myself and answer in writing, with a scope and a price for each milestone.

Or write to contact@guglielmo.io

The human check appears here.

No calls and no sales sequence. One written answer from me.