I'm Pedro, a full stack developer. I build backends, interfaces and the systems in between — production software that keeps working long after launch.
Everything I have shipped, in production or freshly delivered. Filter by where the heavy lifting happened, then open a card for the full story.
01BackendLive siteFull backend design for Multipark — 33+ car parks, 5.000+ spaces and 100+ charging stations — plus the shared Multigroup auth and services layer.
02Full stackLive siteComplete frontend and backend for a collection of restored Lisbon apartments, with a full backoffice and a two-way Beds24 integration.
03Full stackLive siteThe whole country on one map: every district shows how much is happening, then opens into its own agenda. Events are fed in from municipal council sources.
04Full stackLive siteWebsite and backoffice for Luis Duarte Vinhos: wines, vineyards, wine tourism and the estate’s story, in Portuguese and English.
05BackendLive siteBackend and booking engine for Portugal Rent: fleet, availability, extras and reservations — with the frontend still being finished.
06FrontendLive siteMulti-page corporate website for a scaffolding company — services, portfolio, careers and quote requests.
Backend and frontend feature work for a startup restaurant management tool built with Django and Next.js.
A simulator that trains AI agents with evolutionary reinforcement learning to find optimal battle strategies.
A minimal Android launcher focused on privacy and battery efficiency.
No black boxes and no deadlines invented after the fact. The same four moves, in this order, on every project.
Before a line of code, I map how the business actually runs: who touches the data, where it gets lost today, and what a good week looks like. That conversation decides everything that follows — including what not to build.
Calls with the people who use it · Constraints, volumes, edge casesThe schema and the service boundaries decide how a product ages. I settle those first, so the interface is a consequence of a solid model instead of a patch over a shaky one.
Schemas · Service boundaries · API contractsEach slice runs from database to interface and lands in production early. Nothing waits for a big-bang launch, and nothing sits “almost done” for weeks on end.
Vertical slices · Deploy early · Iterate with the clientA backoffice the client can actually operate, documentation that makes sense, and a codebase the next developer can read. Handover is part of the build, not an afterthought.
Custom CMS · Docs & handover · No lock-inTell me what you’re building, who it’s for and what has to be true for it to work. I’ll come back with an honest read on scope, timeline and whether I’m the right person for it.
contacto@pedroinacio.com Currently taking new work for Q1