Skip to main content

A WordPress developer working since 2010

I have worked as a WordPress developer since version 3 and have built, repaired and taken over WordPress sites in a large share of my 400+ projects. You get custom themes without a page builder, fewer plugins and a site that is still fast in two years. And you talk directly to the person writing the code.

  • I usually reply the same day
  • Written estimate before work starts
Mikkel Tschentscher

star reviews

Read every review
  • Helpful and lightning fast to reply

    Mikkel is seriously good, helpful, lightning fast to reply, and on top of that he is a nice person. I can warmly recommend Mikkel to others..

    Trine Handskemager(translated from Danish)
  • A fast, trouble-free process

    Mikkel delivered competent, professional work setting up my website. Everything ran quickly and without a hitch.

    Sisse Find(translated from Danish)
  • My go-to guy

    That is why I can still give Mikkel my very best recommendations.

    Janni E Clausen (Janniclausen)(translated from Danish)

WordPress developer

A theme change, a plugin or custom code?

The choice depends on the actual problem. A plugin can suit a well-defined feature. Theme changes suit presentation and editing. An integration may need custom code when data and responsibilities cross systems. The table describes common choices rather than a rule that everything needs custom development.

Choosing an approach for a WordPress task
NeedPossible approachWhat to assess
A new product-page layoutA theme template changeEditing, mobile rendering and maintenance
A standard featureA well-documented pluginDependencies, updates and actual needs
Data between systemsA scoped integrationData ownership, failures, retry and responsibility

Custom themes over off-the-shelf

A purchased theme is cheap to start with and expensive to live with. You pay in speed, in code nobody can read, and in every customisation needing a child theme with thirty overrides.

I build themes from scratch with Advanced Custom Fields or blocks, depending on who is editing. The result is usually a fraction of the code and an admin interface where the fields are named something meaningful to the person using them.

Typical WordPress jobs

  • A new theme built from scratch to your design.
  • Cleanup of installations where 40 plugins do 12 different things.
  • Taking over a site after a previous developer or agency.
  • Speed optimisation when the site fails Core Web Vitals.
  • Updating PHP and the code that snaps along the way.
  • WooCommerce customisation in checkout, shipping and product display.

WooCommerce

WooCommerce can absolutely run a store, but it gets heavy as catalogues grow. I work on product data structure, caching strategy and the points in checkout where people typically drop off.

If you have several thousand SKUs and serious growth ahead, I will say out loud if Shopify would be a better fit. The decision is yours, but you should have the grounds for it.

What is a WordPress developer?

A WordPress developer is a programmer who works in the code behind a WordPress site: themes in PHP, custom blocks, plugins and the database. That is different from someone assembling pages in a page builder. A page builder changes how the site looks. A developer changes how it works.

You need a WordPress developer when the built-in editor and the installed plugins no longer suffice: the theme needs adapting, the site has grown slow, two plugins fight over the same thing, or functionality has to be built that does not exist as a ready-made package.

The difference between a specialist and a generalist shows in the solutions. A generalist installs yet another plugin. A specialist knows when thirty lines of code in the theme do the same without a subscription and without extra load time. I have followed WordPress since version 3 and seen what most choices cost over a three-year horizon.

In practice I work in your existing installation, take a backup before anything else and deliver changes you can review. I build themes from scratch with ACF or blocks, and everything is documented so the next developer can take over without an onboarding call with me.

Plugins and functionality: when to write your own code

The first question with any new feature is whether a plugin exists that does it well enough. Often one does. A well-maintained plugin with many active installations, regular updates and a developer who responds to bug reports is often a better choice than something coded from scratch. There is no reason to reinvent the wheel, and a professional WordPress developer should say so out loud, even when it means fewer hours for the developer.

The problem starts when plugins become the answer to everything. Every plugin loads its own code, some of them on every single page, and every plugin is a possible way in if it is not kept up to date. If a large plugin has to be installed to solve a small task, or it needs an annual subscription for something a few lines of code can handle, I write it myself. Fewer plugins mean fewer updates to keep track of and fewer security holes.

Integrations are the other big part of WordPress development: forms that pass leads on to a CRM, sign-ups to a newsletter tool, orders from WooCommerce to an ERP or inventory system, and payment solutions in checkout. Some of them exist as ready-made plugins from the system's own vendor, and then I use those. Others need an integration through the system's API. There I write the code so errors get logged and noticed instead of disappearing without anyone seeing.

Speed and security start in the code

Speed is decided in the code, long before anyone installs a caching plugin. The theme should load only the scripts and CSS files the individual page actually uses, database queries should be few and targeted, and heavy lookups that rarely change can be stored temporarily so they are not recalculated on every visit. Images should use the sizes WordPress creates on upload, so a phone does not download an image meant for a large screen.

Caching is the last layer, not the first. Page caching on the server can make a slow site feel fast for visitors who are not logged in, but it hides the problem instead of solving it and helps neither in the admin nor in a WooCommerce cart. My aim is a site that passes Core Web Vitals on mobile with a good margin, even before caching is switched on. For LCP that means the largest content element on screen should appear within 2.5 seconds.

Security in the code comes down to the same few habits every time. Everything that comes in from a form or an address bar is validated, and everything shown on the page is processed so it cannot run as code. Actions in the admin are protected with security tokens (nonces) and a check of the user's permissions. Editors get the Editor role, not Administrator, and the option to edit theme and plugin files directly in the admin is switched off.

Ongoing maintenance after launch

A WordPress site is not finished when it launches. The core, the theme and the plugins keep getting updates, the PHP version on the server has to keep up, and a backup is only worth something if someone has tried restoring it. Skip that for a couple of years and it is no longer one update to run but a small project where several things break at once.

Ongoing maintenance therefore consists of a few fixed tasks: updates tested on a copy before they reach the live site, a regular check that the backup can be restored, a review of plugins whose developer has stopped maintaining them, and an eye on speed so it does not slowly slip. Much of it can be handled by a technically minded employee with a good guide.

For sites I have built myself, I can handle updates, security checks and backup verification. I do not take pure maintenance contracts on sites I do not know, because maintenance requires knowing how the code fits together. In return, what needs watching goes into the documentation, so you or another developer can take over the task without guessing.

WordPress developer for businesses across Denmark

WordPress work suits remote collaboration well, and that is how I handle it for clients across Denmark. I sit in Glostrup near Copenhagen, while the sites I work on belong everywhere from Aalborg and Aarhus to Odense and southern Jutland.

Access to WordPress and hosting is all it takes to get started. From there the dialogue runs on email and video, and you can follow the changes continuously instead of waiting for a monthly status.

Many of my clients come from an agency setup where every small fix had to pass through a project manager and be priced as a task. With a freelancer you write directly to the developer, get a fast answer and do not pay for a layer of coordination on top of the actual work.

On page builders

I do not start new projects in Elementor, Divi or WPBakery. They are the single factor that most often ruins performance on Danish WordPress sites, and they make content hard to move later.

It is worth knowing what you are committing to. Content built in Elementor sits as Elementor's own data structure in the database. Switch the plugin off and you are left with a page full of shortcodes. That is a real cost of switching, and it rarely comes up when the theme is sold.

I can happily maintain a site already running on a page builder, and I do not propose a rebuild just because I would have done it differently. But when we talk about something new, I build it without one.

What you get

Concrete deliverables, not a report of recommendations someone else has to find time for.

  • A custom theme

    Built with ACF or blocks depending on who edits, without the layers a purchased theme drags along.

  • Fewer plugins

    A map of what is actually used and what each plugin costs in load time. The rest gets solved in the theme.

  • Updated PHP and code

    Including fixes for the code that snaps under new PHP versions, before it becomes urgent.

  • A cleaned database

    Stale transients, revisions and leftover tables from plugins deleted long ago.

View all cases

How it works

Four steps. You know what happens when, and you can stop after any of them.

  1. 01 / 04

    We walk through the job

    A 20-30 minute call where you describe what needs to be built or repaired. I ask about platform, access and deadline, and tell you honestly if the job sits outside what I am good at.

  2. 02 / 04

    Review of your code

    Small jobs get a price after a short clarification. If a larger existing project needs a technical review first, we agree the price and scope of that review before I open the code.

  3. 03 / 04

    Written quote with a clear scope

    You get a firm agreement on what is included, what is not, and when it will be ready. If the scope changes along the way, we deal with it openly instead of letting it drift.

  4. 04 / 04

    Delivery in your own setup

    I work in your own repository and your own hosting and deliver in pieces you can see and approve. When we are done, you have the code, the access and documentation that makes you independent of me.

Brands I've worked with

  • MT Højgaard Danmark
  • Egmont
  • NNIT
  • Visma
  • Lomax
  • Pascal
  • able.
  • OOONO
  • Novo Nordisk Fonden
  • Energii
  • Maersk Tankers
  • Nordkysten Entreprenørfirmaet

Frequently asked questions

What does a WordPress developer cost?

It depends on the job: a new theme costs more than a bug fix, and the price is driven by design complexity, the number of integrations and the state of the existing code. Write what you are facing, I will ask the necessary questions and give a concrete quote, with a same-day reply.

What does WordPress cost per month?

WordPress itself is free. What costs money each month is hosting and the domain, plus licences for any paid plugins or a theme. On top of that comes maintenance: updates to core and plugins, backups and monitoring, handled either by you or by a developer. Hosting is the line not worth saving on, because cheap shared hosting is one of the most common reasons a WordPress site is slow.

What does a WordPress developer do?

Builds and maintains the code behind WordPress sites: themes, blocks, plugins, integrations and the database. Everything beyond what the built-in editor can handle.

Can you develop a custom plugin?

Yes. When a feature does not exist as a ready-made plugin, or the ready-made one is too heavy or needs a subscription for something simple, I build it as a small plugin for your site. Functionality that has to survive a theme change goes in a plugin rather than in the theme, so it does not disappear the day the theme is replaced. The code is documented, and it is yours.

Do we need to meet in person, or can everything happen online?

Everything can happen online, and it does for most of my clients in Aarhus, Odense, Aalborg and the rest of the country. If you are in the Copenhagen area, I am also happy to meet in person for a kickoff.

Can you work on a theme someone else built?

Yes, it is a large part of my work. I read through the code first and tell you honestly whether building on it or starting over makes more sense. Sometimes the answer is to build on it even though the code is ugly.

Do you use Elementor or other page builders?

Not for new projects. I happily maintain sites already running on them, but new work I build with custom blocks or ACF, because it gives a faster site and content that can move.

Do you also do ongoing maintenance?

To a limited extent and only for clients I have built for: updates, security checks and backup verification. I do not take pure maintenance contracts off the street.

How long does a WordPress project take?

It depends on the type. A bug fix or a smaller change is typically a job of hours or a few days. A new WordPress site with ten to fifteen pages usually takes four to eight weeks from approved design. Integrations and custom plugins I estimate once I have seen the systems they need to talk to, and the timeline goes in the written quote.

What about multisite and multiple languages?

I have worked with both many times. Multiple languages is rarely technically hard, but it doubles the amount of content someone has to keep current, and that cost belongs in the decision.

How do we get started?

Write a few lines about what needs doing and send the site's address if it already exists. Then we have a short call about the job, access and deadline. For larger existing projects I read through the code before you get a written quote with a clear scope. When the work begins, I take a backup before touching anything.

Define the scope of your task

Send your website URL, what you need solved and your desired deadline. I will assess the next step and describe what the quote includes. Larger investigations are agreed separately before work begins.

Describe your task

Your next step

Get a quote for WordPress developer

Tell me about your project. I’ll get back to you with questions, options and a concrete next step.