Web Development

I don't have a default framework that gets applied to every project. The choice is made case by case, based on the client's needs and three concrete variables: expected performance, the infrastructure cost that follows from it, and the load the system will actually carry.

That decision has financial consequences, not just technical ones. A framework that renders server-side on every request changes the size of the machines you pay for each month; a static generation approach cuts that cost but constrains how content gets updated. Discussing these trade-offs before writing code is what prevents rewrites halfway through.

The most representative project is the media management platform built from scratch for Stellantis. Work started from gathering the client's requirements on topics no off-the-shelf product covered: content embargo handling, publication rules, worldwide availability of materials, and server load limits.

The software was designed from those requirements, to satisfy them together rather than in isolation. Embargo in particular is not a checkbox: it is a constraint that has to hold on every path to the content, including previews and distribution to markets in different time zones.

Messagent turns WhatsApp into the direct channel between a retail brand and its customers: a single platform handles conversations, coupons, flyers and campaigns for several brands at once, currently running for Basko and Despar Nord Ovest. Each client has its own isolated configuration — numbers, credentials, keywords and permissions — without duplicating the underlying infrastructure.

Onboarding is conversational. The customer writes to the brand's WhatsApp number and is recognised automatically; new contacts get the privacy notice and registration in a single tap. From that point every interaction is profiled, with no app to install and no form to fill in.

For loyalty, the user photographs their card and the platform reads the barcode straight from the image, linking the card to the phone number — no manual entry. A keyword returns their wallet in chat, with coupons and point balance updated in real time, distributed and redeemed on the channel they already use.

Around this sit digital flyers, uploaded and scheduled with validity period and store, a store locator that ties the chosen shop to the profile, WhatsApp channels and newsletters with permanent media archiving, contests that run inside the conversation, and scheduled sends delivered at the set time even across service restarts.

A web panel manages brands, keywords, flyers and channels without touching code, with access governed by centralised authentication: each operator only sees their own brand's data.

I follow the project from architecture to deployment, with no handover in between. The code I write is covered by automated tests, and performance is a design constraint measured against Core Web Vitals, not a final cleanup pass.

What I deliver is an application your team can maintain: a tidy repository, upgradable dependencies, a working deployment pipeline and documentation of what it takes to run it.