Freelance Drupal developer in Limburg
A Drupal expert nearby, when that matters.
For workshops, kick-offs and complex conversations, I'd rather come by than call in.
Discuss your project
I work as a freelance Drupal architect from Herk-de-Stad, and for most of this work my address doesn't matter.
That's stated upfront, on the only page on this site that's about location.
What the work itself involves and how you bring me on board is covered at hiring a freelance Drupal developer.
I'm David Porschmann, more than fifteen years working with Drupal, working for clients in Belgium and the Netherlands, remote in CET, in Dutch or English.
Below is where I travel to, when sitting in the same room actually helps, and when it's mostly travel time.
Where I work: Limburg, Flanders, the Netherlands, remote in CET
Herk-de-Stad is the base, the working area is wider.
Hasselt, Diest and Sint-Truiden are a short drive away, Genk, Leuven and Antwerp are further but still doable.
- Limburg and surroundings: meeting on site is usually possible at short notice, even for a single meeting.
- Flanders and Brussels: reachable for a kick-off, workshop or delivery, planned as a full day.
- The Netherlands: mostly remote, with a day on site when that day actually decides something.
- Beyond that: remote in CET, in Dutch or English.
When proximity does matter
Proximity matters at the moments where decisions get made, not at the moments where code gets written.
Four situations where I'd rather show up than dial in:
- A workshop on the data model, where you and the content owners settle what's a page and what becomes a separate entity.
- Handover to an editorial team that needs to work with a new editor, because sitting next to someone is faster than a manual.
- An escalation involving multiple suppliers, where the first half hour goes into figuring out who manages what.
- An environment where access to systems or networks can only be arranged on site.
Then I show up.
It's a matter of days, not weeks: two structural days a week at your office isn't a requirement on my end.
When proximity doesn't matter, and that's most of the time
Most Drupal work happens in a repository, and a repository doesn't have an address.
Justifying architecture choices, writing migration scripts, taking part in code review, running a security release: that all runs through merge requests and written text, and it doesn't get any better with two hundred kilometres less in between.
What does count are four things that have nothing to do with distance: the same time zone, a shared language, a response time you can plan around, and work that can be found back in the repo instead of in someone's head.
A developer in Hasselt who doesn't respond is further away than a developer in Groningen who does.
What that work actually looks like is on Drupal architecture and development.
Why there's no list of towns here
There's no measurable search volume on Drupal terms combined with a town name, so a series of pages that only differ in the place name doesn't help anyone.
Anyone who needs a Drupal architect searches for the problem: a Drupal migration for the end of life of Drupal 10 on 9 December 2026, an accessibility audit against WCAG 2.2 level AA, a site that's slow.
So this page isn't here to rank for a search term with Hasselt or Genk in it, but because proximity matters to some clients, and it's only fair to say where that stops.
How a first conversation works
The first conversation is a half-hour video call, unless there's a reason to meet in person.
You send ahead which Drupal version you're on, the size of the team, and where it's stuck.
That lets me tell you within that half hour whether the work is a fit for me and what I'd approach differently.
If there's a project spanning months on the table, I'd rather come by, and then that's the first working day of the project, not a sales pitch.
How that kind of engagement runs afterwards is at hiring a freelance Drupal developer.
Rates and travel time
My rate is 75 to 95 euros per hour, or 650 to 800 euros per day, excluding VAT, and that amount doesn't change whether you're in Hasselt or in Rotterdam.
For long engagements and returning clients it's lower.
I don't charge for travel time within the region, days on site further away we agree beforehand, because travel costs belong in a budget, not in a surprise invoice.
How those amounts compare to the market is in what a freelance Drupal developer costs in 2026.
The full breakdown is on the rates page.
Proximity is one form of trust, public work is another
Someone living in your province says nothing about the quality of their code.
What you can check before letting someone into your codebase: my profile on drupal.org, my work on GitHub, and my LinkedIn.
The engagements for universities, government and industry are on the cases page along with the choices made, and who I am and how I work is on about David Porschmann.
Together that's more information than an address in the same postcode.
Frequently asked questions
Do you only work for clients in Limburg?
No.
Herk-de-Stad is the home base, the working area is Belgium and the Netherlands, and most work happens remotely on CET.
In Limburg and the surrounding region, a short-notice meeting is easier to schedule.
For the rest of Flanders and for the Netherlands, I plan full days on-site rather than separate hours, since half a day of travel for a one-hour meeting is well spent for no one.
Can you come work on-site?
Yes, for moments where it actually pays off: a workshop on the data model, handover to an editorial team, an escalation involving multiple suppliers, or an environment where system access can only be arranged on-site.
For day-to-day development work, remote is better in practice, since then I'm in the same environment as the code and the logs.
Do you also work for clients in the Netherlands?
Yes, alongside Belgium the Netherlands is my second market, and there's no timezone difference, so discussion and delivery happen within the same working day.
In practice that runs almost entirely remotely, with a day on-site when that day actually decides something, such as a workshop on the data model or a handover to the editorial team.
The language is Dutch or English.
Do you charge for travel time and travel costs?
I don't charge for travel time within the region.
Days on-site further away we agree on upfront, since travel costs belong in a budget, not in a surprise invoice.
My hourly and daily rate doesn't change with distance: whether you're in Hasselt or in Rotterdam, the amount stays the same.
How do we work together if we don't meet in person?
Remotely on CET, in Dutch or English, with the work in the repository.
Architecture decisions, merge requests, code review and releases run through written text, so what's been decided stays traceable instead of living in someone's head.
I respond to a request within 24 hours, and which days I'm available we agree on in advance instead of improvising week by week.
Does it matter where my developer is located for a Drupal migration?
Barely, since a migration is repo work, not on-site work.
What does matter is the timing: Drupal 10 reaches end of life on 9 December 2026.
Anyone still on Drupal 10 in November is competing for capacity, so availability weighs heavier than driving distance.
A question about this topic?
Briefly describe your situation, and I'll let you know what's going on and what it would cost. No sales pitch.
