Web development that holds up the day after.
Sites and web platforms built by hand when the problem deserves it, on top of WordPress when that's the reasonable choice, and custom plugins when what the market sells comes up short.
I've been writing PHP since 2008. That means two things. One, I've seen the trend of the day come and go four times and I've learned which were worth it and which were noise. Two, I know the real wrinkles of a project that has to stay alive in five years, not five weeks, and that changes how every decision is made: which framework to use, which dependency to avoid, what to document thoroughly.
Most of the work falls into three formats: WordPress with serious development on top (not retouched template, custom themes and plugins, no heavy Page Builders, auditable code), flat PHP applications or microframework-based ones when WordPress doesn't add anything and only gets in the way, and deep maintenance of legacy projects, the typical PHP 5.6 codebases nobody wants to touch and that, when you open them, contain fifteen years of mixed judgement.
The work doesn't end when the site is delivered. It ends when the site is delivered and there is clear documentation so that tomorrow someone else, or me, six months later, can step into the code, understand why each decision is made, and modify without breaking. That part is what costs and what makes the difference.
How we work
-
01
Real diagnosis
Before any quote, a 30–45 min call to understand what you're trying to solve. If the problem is marketing, not technology, I'll tell you. If what you need is better done with Webflow or Shopify, I'll tell you that too.
-
02
Proposal with scope
Concrete document: what gets delivered, what does not, in what order, with what milestones. No endless "discovery phase". If there are real uncertainties, we name them as such and decide how to close them.
-
03
Iterative build
We work in short sprints with real deliveries, not mockups. After 7–10 days there's already something running you or your team can touch. We iterate on that, not on PDFs.
-
04
Delivery + handoff
Deployment, technical documentation, walkthrough video if needed, and a support period included for the first production bugs that always appear.
What's included
- Free initial technical analysis, no commitment
- Site or application development with documented code
- Custom WordPress plugins when the problem calls for it
- Performance optimization (Core Web Vitals as measurable target)
- Hosting/Plesk configuration and deployment on your server
- Technical and user documentation
- Support period after deployment (1 month included)
- Optional ongoing maintenance plan afterwards
When we're not the right fit
- You want a website in 48 hours I don't work that way. If your deadline is that, you're better off with Webflow or Squarespace.
- You need a cheap, reused template My rate doesn't compete with a customised ThemeForest template. And it shouldn't: they're different products.
- You want to delegate everything and not weigh in I work better when there's someone on the other side making decisions. If you're going to be out of the conversation for three weeks straight, this won't flow.
Stack & tools
- PHP 8.x, still the most sensible choice for most web projects
- WordPress + WooCommerce, when it adds value
- WPML for multilingual
- Vanilla JavaScript, Alpine.js or React depending on the case (not React by default)
- MySQL/MariaDB
- Plesk + Linux (Ubuntu/CentOS), the whole hosting ecosystem I know in depth
- Git + staging → production workflow
If this sounds like what you have on the table, write to me and we'll look at how to tackle it together. The first conversation costs nothing and usually something useful comes out of it even if we don't end up working together.
Let's talk →