A compact website is a different job from a multilingual platform with a CMS, CRM integration, data migration and custom work. So we use clear starting prices and fixed scopes where we can. You know what it costs, and what you pay for. All prices excl. VAT.
For businesses that need a professional website without turning it into a needlessly big project.
We build a fast, responsive website on your brand identity or existing design. We look past what you see. The technical base has to be right too: structure, performance, technical SEO, forms, analytics and the checks before launch.
Who it's for. A practice, freelancer or business with a clear offer, an existing brand identity and a straightforward website.
Technical project setup, responsive development, reusable components, a CMS where needed, forms, analytics, metadata, sitemap, indexability, performance optimisation and checks before launch. We don't only build the pages. We make sure the website is technically sound.
A completely new brand identity, extensive UX work, dozens of unique templates, a lot of content production, complex animation, multiple languages, large migrations, custom software and integrations with external systems. We agree on those up front.
A small website can be technically quite simple. With a clear brand identity, a limited number of templates and little custom work, we keep the build compact. The price goes up once more unique parts need building, systems need connecting or there is a lot of content, migration and testing work. You don't pay per page. You pay for what needs to be built.
A website can look fine and still leave a lot on the table: technically, in measurement or commercially.
So we look further than an automated SEO scan or a single Lighthouse score. We find out what actually happens, which problems share a cause and which points need attention first.
Who it's for. Organisations with a website that delivers less than expected, teams that doubt their data or technical base, and anyone planning a migration or rebuild who wants to know first what they are taking over.
The exact scope differs per website. Among other things: technical SEO, crawlability, indexability, redirects, canonicals, structured data, performance, Core Web Vitals, responsive behaviour, accessibility, tracking, analytics, conversion paths and search data. Where we can, we combine sources. An error in a crawler isn't automatically a problem for Google, and a high bounce rate without context doesn't tell the whole story.
No export with hundreds of red dots. A reasoned overview of what we saw, how we established it, why it matters, how certain we are and what needs to happen. We turn that into a priority list that you, your current agency or blokwerk can work from.
The audit is the research. Implementing the improvements is not included by default. We can only draw conclusions from sources we have access to. If Search Console, analytics or the source code isn't available, we say so.
A twenty-page website is different from a multilingual platform with thousands of URLs, several templates, external scripts, ads and several data sources. The price depends on the size of the website, the number of research layers and how much data we need to analyse.
Want to know first whether a full audit makes sense? Then we start with a short check of the most important visible signals. Not a full investigation. Enough to decide whether something needs a closer look.
A form comes in. Someone copies it into the CRM. Then an email goes out. At the end of the month the same information goes into a spreadsheet again. Processes like that grow on their own.
In an automation sprint we take one concrete process and build a working solution that makes systems and steps fit together.
Who it's for. Teams that do the same manual work every week, retype information between systems, or run processes held together by loose spreadsheets, inboxes and tools.
First we map the process. What information comes in where? Which systems are involved? Which steps take time? And above all: which steps should not be automated at all? Then we build and test: an API integration, a workflow, a database, an internal tool or a mix. We only use AI where interpretation or language adds something. A plain software integration is often the better choice.
No slide deck about what might be automated. At the end there is something that works. Where needed with error handling, logging, human approval and documentation. It records what the system does when everything goes right, and when something fails.
A sprint solves one clearly bounded process. A new business platform, a large CRM migration or a system with dozens of integrations is scoped as a custom project first. Licence costs for third-party software are outside our development price.
Some automations are one clear integration. Others touch five systems, several user roles, sensitive data and processes that must not go down. The amount of logic, integrations, exceptions and checks sets the scope.
Browsers change. Dependencies get updates. External services change. A form can stop working without anyone noticing. Tracking can break. An old redirect can suddenly matter.
So we can keep looking after a website once it's live. Not to send a monthly report with twenty green ticks, but to catch problems before they sit there for months.
Who it's for. Organisations where the website is part of sales, lead generation or service, and nobody in-house is responsible for its technical health.
We keep the technical base working: dependency updates, security checks, hosting, deployment, backups and fixing technical problems, depending on the stack.
Uptime, forms, broken links, status codes, redirects, sitemap, analytics, tracking, technical SEO and performance. Automated checks flag a lot. A person then decides whether something is a real problem.
Depending on the plan, small changes and support fit within a monthly amount of time. Larger pages, features, integrations and redesigns count as further development and are agreed in advance.
You don't have to find out yourself that a form hasn't sent an enquiry in three weeks. You don't have to know which dependency causes a security issue. We watch what we agreed and tell you when something needs doing. In your own client portal you see your site's status, what we did, which agreements apply and how many hours are left.
A compact five-page website needs a different level of care than a multilingual site with CRM integrations, tracking, hundreds of URLs and several external systems. We base care on what actually has to be monitored and maintained.
Sometimes a website is a small part of the question. Information from several systems has to come together, a team works with manual processes that have grown too big, or the software you need doesn't exist yet.
Then we don't force the problem into an existing package. We first map what needs to happen.
Who it's for. Organisations where the challenge sits in the systems, data and processes behind the website, not only in the front end.
Client portals, internal tools, dashboards, data pipelines, CRM processes, API integrations, reporting systems, booking logic, automation, or software that runs an existing business process better.
Not with a tech stack. First: what does someone need to be able to do? What information does that take? Where does it come from? Which systems already exist? What must stay reliable at all costs? And what has become needlessly complicated? Only then do we decide what to build.
Because 'custom software' says little about size. An internal tool for three people can be smaller than one complex integration with an external platform. We make the scope clear first, then estimate development, integrations, data, testing and maintenance.
So we don't price a website per page. The size is in how many different things we need to build, and how much work it takes to make them run reliably.
What does a website cost? With us, from €2,000 excl. VAT. A compact site with 3 templates and 1 form costs €2,000 to €4,000. With bookings, two languages and a link to your till and CRM it becomes €15,000 or more.
External costs like hosting, domains, CMS licences or third-party software go on the quote as separate lines. If you can buy a tool directly, it doesn't need to go through blokwerk.
That keeps it clear which amount is for our work and which goes to external software.
You don't need a perfect brief up front. Send us your current website, design or idea. We look at what's needed, what fits your budget and what doesn't, and where it can be simpler. We'd rather say up front that something doesn't fit the scope than after we've started.