01
A web application, from nothing
The full path: working out what it actually has to do, modelling the domain properly, building it, and putting it on a server that stays up. Laravel and Livewire, because a small team maintaining one codebase beats a large one maintaining three.
02
Rescuing what already exists
An application nobody dares deploy, a developer who has moved on, a framework four versions behind. I take it over, get a test suite and a deployment under it, and make the next change boring again.
03
E-invoicing and Peppol
Structured invoicing that passes the official rule set — UBL 2.1, EN 16931, validated against the same artefacts the receiving Access Point runs. Either as an application of its own, or fitted into the one you have.
04
Payments and subscriptions
Stripe done properly: webhooks as the source of truth, idempotent handling, refunds thought through before launch rather than after the first one. Marketplaces and payouts with Connect where money passes between parties.
05
Integrations and automation
The work that removes an afternoon from somebody's week: a CRM that fills itself, provider PDFs generated and signed, documents filed where they belong, mail that goes out on time and can be resent.
06
Webshops, on the platform that fits
Next to Laravel there is Magento, Shopify, WordPress and WooCommerce — standard work here, not a favour on the side. Building a shop, taking a neglected one over, or wiring the one you have into the stock, invoicing and shipping systems it should have been talking to all along.
07
Hosting and staying alive
Docker for development, a scripted release for production, backups that have actually been restored at least once. Plus somebody to call when the thing you depend on stops behaving.