Development
WordPress development and maintenance
WordPress runs a large share of Danish business websites, and a good many of them sit on a theme nobody has opened in two years. I build new WordPress sites, take over existing ones, write the plugin when a setting will not do, and keep the whole thing patched and fast.
When this makes sense
- The site works, but nobody left in the company can safely update it
- The agency or developer who built it has stopped answering
- A theme or a plugin is fighting you, and the workaround has quietly become the process
How it works
- 01
Access
Read access to the site, the hosting and the admin. I go through what is actually installed, which is rarely the same as what the handover document says.
- 02
Work
A new build, a takeover, or a specific fix. Changes go onto a staging copy first, so nothing reaches the live site untested.
- 03
Handover
You keep the logins, the hosting and the code. I write down what changed and how to do it again without me.
What the work covers
- Theme and plugin work, including custom plugins where configuration runs out
- Updates, security patches and PHP version upgrades
- Speed: caching, image handling, and cutting the weight the page actually ships
- Backups that get restore-tested rather than just switched on
Common questions
- What does WordPress work cost?
- Hourly work is DKK 600 an hour ex. VAT. A new site starts at DKK 15,000, which is 25 hours, and ongoing upkeep starts at DKK 2,400 a month. Freelance WordPress rates in Denmark are commonly quoted between DKK 650 and 850 an hour, so the rate here is deliberately below that while the studio builds out its portfolio.
- Will you take over a site somebody else built?
- Yes, and it is most of what comes in. It usually starts with a technical review at DKK 6,000 so we both know what is in there before I promise to keep it alive. If the review turns up nothing serious, that is a good result and I say so.
- Do you work with page builders like Elementor or Divi?
- Yes, when that is what the site is already built in — ripping out a builder a client knows how to use is rarely worth what it costs them. For a new build I would rather use blocks and a light custom theme, because builders add page weight you then pay me to remove later.
- Can you build a custom plugin?
- Yes. That is usually the honest answer when a client is about to buy their fourth plugin to approximate one thing they actually need. A small purpose-built plugin is less code on the site than three general-purpose ones.
- Is WordPress still the right choice?
- For a site whose content you want to edit yourself, often yes, and I say so more readily than most developers do. Where it stops being the right answer is when the site has to carry real application logic — a portal, a calculation, a workflow — and you end up bending a publishing system into a shape it does not want. That is the point to build it properly instead.
Other stacks I work in
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.