Leo
Quinteros
I build and keep alive web and mobile apps that already have real users, starting with the data model, so what we ship today still holds when the business grows.
Three things I do every time.
Data model first
I design the schema around the questions the business will ask later, not just today's screens. That is where reporting, scale and sanity come from.
End to end
Feasibility, scope, estimate, technical calls, build and production. One person with judgement across the whole thing, and docs for what I hand over.
Keep it running
Most of my work is on apps with real users. I keep them fast, safe and documented, and I tell you plainly when something is not worth doing.
Scoping, building, and keeping it alive.
Some projects are under NDA. Names and identifying details have been changed, and no confidential data or screens are shown. The engineering is described accurately.
Six years, mostly on live apps.
Scoping · Project management · Development · Testing
Lead Developer, Backend
Bubble & Xano Developer
Independent No-Code Developer
Product Lead
Data analysis & project management
Building with AI is normal now. What's rare is judgement about what to build.
I don't do rescue theatre and I don't sell fear. Vibecoding is a good tool. What's usually missing is someone with product judgement using it with a plan: a data model that holds, permissions that mean something, an architecture that survives real users. That's what I bring, with Bubble, Xano or code.
- ISchema before a single screen.
- III review AI output like a colleague's.
- IIII document what I hand over.
- IVI tell you when not to migrate.