Multilingual done right
Translated URLs, hreflang, original copy per language - no machine translation that ruins your brand.
Websites · web apps · multilingual
Websites and apps
in steady hands.
Sites that load before you blink. No heavy themes, no plug-in stack that breaks after a year. I build what is needed - multilingual, fast, and set up so you can still extend it years later.
Speed is not a detail
See the difference.
A typical builder site versus what I deliver. Both bars start at the same time.
Heavy WordPress site≈ 6,2 s
What I build≈ 0,9 s
What you get
Everything a site needs in order to work.
Findable in Google and in AI
Structured data, sitemaps, llms.txt. More and more people ask an AI assistant first.
Forms that actually arrive
Delivery through automation, confirmation in the visitor’s language, the lead straight into your system.
Maintenance included
Updates, backups, monitoring and further development. You never have to work out what needs doing.
How it runs
You know in advance what happens.
No surprises halfway and no big reveal at the end. Four steps, the same every time.
- 01
We start with a conversation, not a quote
First I want to know what your business does and where it hurts. Only then do I know whether you need a new site, or whether the problem sits somewhere else. That conversation costs nothing and commits you to nothing.
- 02
You watch it grow, not only at the end
You get a link as soon as there is something to look at. You follow along, you say what is off, and we fix it while we build. No big reveal after eight weeks that then has to change anyway.
- 03
Delivery means handover
The domain is in your name, the hosting is in your name, and you get the access. Even if we part ways one day, all of it stays yours. That is not a favour, that is simply how it should be.
- 04
After that it keeps running
Updates, backups and monitoring keep running. If something breaks, we usually notice before you do. And if you want to extend something a year from now, you do not have to start by explaining who you are.
Straight up
What I do not do.
This is not here to sound tough. It saves us both a conversation that goes nowhere anyway.
I do not work with off-the-shelf themes
A bought theme does a hundred things, three of which you use. The other ninety-seven slow your site down and break at the next update. I build what is needed, and nothing more.
I do not hold your site hostage
Some agencies put the domain and hosting in their own name. Leaving then gets expensive, which is exactly the point. With me everything is in your name from day one - you could leave tomorrow and take all of it.
I do not promise a spot in Google
Nobody can, and anyone who promises it is selling you something else. What I do instead: build the site so it can technically compete, then work on findability month after month. That is ongoing work, not a one-off job.
Questions upfront
What people usually ask first.
What does a website cost?
It depends on the number of pages, the number of languages and whether anything has to calculate or connect to another system. I do not name a figure before I know what you need - that would be guessing. What you do get before we start: clear terms on what is included, what it costs and what falls outside.
How long does it take?
A straightforward site in two to four weeks; several languages or a calculator take longer. The timeline usually does not depend on me but on how quickly the copy and photos arrive - and if that stalls, I help move it.
Who owns the site if we stop working together?
Yours. Domain, hosting and code are in your name and you hold the access. You do not have to buy anything back or migrate something you already own.
Do you also work on a site that already exists?
Yes. D-Kozijnen was already there when I took it over; after that came a calculator, dozens of pages and several languages. Taking a site over is often wiser than starting again, certainly when it is already being found.
Which languages can you build in?
Dutch, Polish and English, with translated URLs and original copy per language instead of machine translation. This site itself runs on that setup, so you can see how it works out before you decide.