We started building together.
We began taking our ideas seriously in 2024. We tried things, built what we could and learned where our skills might be useful. We were still figuring out whether any of it could become paid work.
About us
Meet the people behind LelevAi.
We're Levy and Daniele. At LelevAi, we run Aitreach and take on selected technical projects, working directly with our clients.
This was a friendship before it was a business.
We grew up in the same small town and knew each other long before we worked together. Our studies took us in different directions, but we kept coming back to the idea of building something together.
The projects changed. We kept working together.
How the work took shape.
What began as our own experiments became client work, then a service built from a problem we had faced ourselves.
Our work became useful to others.
We developed our software and automation skills, then started building for other people: chatbots, websites and connected workflows. Client work taught us how to fit what we built to a real need and follow through on delivery.
The opportunity behind Aitreach.
We had been using outbound to find clients for our own work. Over time, we realised the system itself could solve a valuable problem for other businesses. That became Aitreach.
In September 2026, we formalised LelevAi as our shared commercial identity. Aitreach is now our main offer, alongside selected technical projects.
Different starting points. Shared responsibility.
Levy Lisboa Pan
Co-founderMy background is in data science and statistics, with an earlier degree in economics. I use that mix in software and outbound work, from prospect research to the systems behind a campaign. The technical side matters, but so does understanding what a business is actually trying to achieve, how it makes decisions and where the commercial problem really sits. I also work directly with clients, so that context stays part of the work from the first conversation through delivery.
Daniele Giordano
Co-founderMy background is in management engineering, with a strong focus on modelling, processes and structured problem solving. I tend to start by understanding how a business or workflow actually works before thinking about the system that should support it. From there, I work across automation, system design and delivery, keeping the practical constraints of the business in view rather than treating the problem as purely technical.
We both work across delivery, operations and client communication. Who takes the lead depends on the project.
Working with us, in practice.
Understand the situation.
Before suggesting Aitreach or a custom build, we ask who you need to reach, how the work happens now and what constraints matter.
Carry the context through.
We shape and review the work ourselves, with the original goals and practical constraints still in view.
Review what we learn.
As the work progresses, we discuss what is working, what needs to change and what makes sense within the agreed scope.
Bring us the problem, not a finished brief.
You don't need to have the solution mapped out. Tell us what is happening, and we can decide together whether there is a fit.