The choices you can't undo
The decisions taken at the start of a web project determine for two years what a change costs. This guide walks through them one by one.
22 articles
How you build determines what you can still do with it in two years. Our developers write about WordPress, hosting, speed, integrations and the choices you cannot reverse later.
The decisions taken at the start of a web project determine for two years what a change costs. This guide walks through them one by one.
The cost of having a website built can feel like a voyage of discovery without a map.
Being present online is a necessity these days. Your potential customers search online, compare online and decide online.
You have felt it for a while now: your current website really is not good enough any more.
You have probably heard of it before: the phenomenon known as ‘cache’.
Imagine this: you visit a website, click a link, and suddenly land on a completely different page without noticing it.
Have you ever wondered what really goes into hosting a WordPress website?
Liever meteen sparren?
You can read later. Half an hour usually gets you further.

Niels Teunissen
Founder
No pitch. We look at where you stand and say honestly what we would do. Even if that is that you do not need us.
If you work with WordPress every day, you know how repetitive some tasks can be: updating plugins, creating users, importing posts...
Have you ever wondered how websites and apps are designed before they actually go live? The answer lies in wireframes.
If you run a recruitment agency or HR department, you know how important it is to manage applicants quickly and effectively.
Structured data saves you a lot of work in your SEO. If you want more visibility in search engines, there is no way around it.
With a website, the most expensive decisions are the first ones. Which system you choose, how you model the content, where you host and whether you build integrations in or bolt them on later. That determines for two years how much a change costs. A site that looks good but needs a developer for every adjustment is more expensive than a site that is a notch less exciting and can be managed by your own team.
Speed belongs to those first decisions. Google measures three things: how quickly the largest element is on screen (LCP, target below 2.5 seconds), how quickly the page responds to a click (INP, below 200 milliseconds) and how much the layout still shifts while loading (CLS, below 0.1). You meet those thresholds by not loading too much; a plugin added afterwards rarely saves it.
The same goes for integrations. A website that stands apart from your CRM, your stock or your quoting system produces work that someone has to retype by hand, and that work grinds to a halt as soon as it gets busy. We prefer to build that connection in from the start, even if it means the first delivery comes later.
This category holds the articles in which our developers explain those trade-offs: which plugins we do and do not use, when a rebuild is cheaper than further development, what caching really does, and how to use redirects without throwing away your rankings.
The questions we get asked most about this. Yours not among them? Ask our assistant or just give us a call.
That depends on who will manage the site. WordPress is strong if you have a lot of content maintained by your own team; there is an editor to be found who can work with it and you are not tied to one supplier. Custom is better if the site mainly has to do something, such as calculate, connect or handle a process, and the content is limited. You only notice the wrong choice at the third change.
As a guideline: the largest element on screen within 2.5 seconds, a response to a click within 200 milliseconds, and virtually no shifting layout while loading. Those are the thresholds Google uses for a 'good' rating. More important than the number is where it comes from: usually it is images that are too heavy, too many external scripts and fonts that arrive too late.
When you spend more time working around the existing setup than on the change itself. Concrete signs: every adjustment touches unexpected places, nobody dares to run an update any more, or the content structure no longer fits what you sell. As long as it is only about the design, a rebuild is almost never needed. Then you are talking about a restyling.
Yes. If there is an API we connect to that; if there is not, we look at an intermediate layer or an export-import route. The question we ask first is which way the data has to flow and who owns the truth. If two systems are allowed to change the same field, sooner or later you run into conflicting data.
Maintenance is running updates, checking backups, closing vulnerabilities and seeing whether the site still does what it should. You can skip it, until it goes wrong: outdated plugins are the most common entry point for a hack, and a site that has not been touched for a year can almost never be brought up to date in one afternoon. Count on overdue maintenance being more expensive than maintenance.
Questions about development?
Reading is one thing. Knowing what it means for you is another.
Tell us what you are running into. In half an hour you hear what we would do, and why we think so.
Free check·30 sec
How visible is your website?
Over twenty checks on SEO, technology and whether an AI model can quote you.