Currently taking on new projects
I take on your whole store - database, integrations and production.
PrestaShop 1.6 through 8.x, including versions nobody else wants to touch anymore. I work alone, remotely, and I'm accountable for the result - not just the code.
18 years
of documented client invoicing, 2008-2026
4
Client relationships of 9-10 years, all still active
92
PrestaShop modules I've written
1.6 → 8.x
PrestaShop versions supported
Technical responsibility
The problem doesn't end at the edge of my code
With seven regular clients (among them toys4boys.pl, dadum.pl, zmienolej.pl and sklep.dayspashe.pl) I also end up owning things that aren't programming at all: choosing a hosting provider, configuring Cloudflare, dealing directly with the ERP vendor and with BaseLinker (now rebranded Base.com, an order-management and sales-channel integration platform). Nobody else on the client's side handles these, so they stay with me.
The same responsibility looks different at efag.ie, an Irish store selling vaping products, whose technical side I've run since 2020. Ireland's E-Liquid Products Tax took effect in November 2025 and is charged per milliliter of liquid. For efag.ie I built the module that adds volume fields to products and includes the tax in the final price, with the rate as a setting (EUR 0.50 per milliliter by default, the rate set in Irish law).
Three kinds of clients
Who I work with
Each of these groups is buying something different. Pick yours, and we'll get specific from there.
You run a store
Store owners
Your store is losing money and nobody can tell you why.
- Production outages
- Performance and the database
- ERP and marketplace integrations
See details
You run an agency
Marketing agencies
The campaign is ready, but it stalls on the client's IT side.
- Technical support behind the agency
- Talking directly to the client's IT team
- Conversion tracking, GA4 and GTM
See details
You build software
Software houses
You took on a PrestaShop project, but your team's experience is in Symfony.
- Working inside your repo and your process
- Modules written to your coding standard
- Version migrations
See details
How I work
Before I touch production, I've already reproduced it on my machine
Three generations of PrestaShop (1.6, 1.7 and 8.x) run side by side on my machine, in containers. I check a change on the same version your store runs, before you see it and before your customers do.
This isn't a pledge about quality. It's a working routine: if you don't have a staging environment, I set one up at the start of the engagement. The exception is an outage - then I restore production first, keeping track of how each step affects the database and the integrations; staging comes once the store is back up.
Next step
Describe the problem, not the fix
Tell me what's happening and since when. We start with a short, free call with no obligation. A paid audit comes later, only if we both see a reason for it, and you know its price before it starts.