No theme or plugin updates
No maintenance window, no update list, no Tuesday morning where something looks different than it did on Monday.
We rebuild your site on current Next.js technology: your content comes along, the design gets a freshen-up, the copy is reworked for search engines and for AI answer engines, and the schema markup is put in place. On top of that an admin area for your editors, an AI chatbot that takes enquiries, and connections to whatever already runs in your company. Hosting and maintenance are ours.
At the start WordPress costs almost nothing. It gets expensive later: on the Tuesday when an update breaks the layout, and nobody can say which of the eighteen plugins did it.
| WordPress | AI Website | |
|---|---|---|
| Updates | Core, theme and every plugin want updating, and each one can be the one that breaks | There is no theme and there are no plugins that would need updating |
| Compatibility | One update can quietly disable another plugin, often unnoticed for weeks | One codebase, built and checked as a whole before anything goes live |
| Loading time | PHP, a database and a dozen scripts on every visit | Finished pages from the cache, page speed scores in the green |
| Mobile | The theme is responsive, the page builder is not always | Every page is built for the phone first and checked there |
| Security | Every plugin is someone else's code running inside your site | No third-party code in the path that serves your visitors |
| Extensions | Whatever exists as a plugin is possible. The rest becomes a project. | A connection to your CRM, ERP, shop or your own software gets built |
Six points that come up in every conversation before anyone decides to move. They are the actual reason people move.
No maintenance window, no update list, no Tuesday morning where something looks different than it did on Monday.
There is nothing that would have to get along with anything else. What the site needs is part of the same codebase.
Pages served ready-made, images in modern formats, and no script running purely because a plugin wants it. That counts for your visitors and for Google.
Built for the phone first rather than squeezed into it afterwards, and checked on real screen sizes before the site goes live.
You no longer depend on whether a plugin happens to exist for what you want. What you need gets built.
Forms, enquiries and orders land where you already work: HubSpot, Salesforce, Pipedrive, your ERP or your own database.
The move runs alongside your business. Your old site stays online until the new one is ready to take over.
one week
We pull every page, post, image and form out of your installation and put on the table what visitors actually open and what nobody has looked at in years.
one to two weeks
Your site is not reinvented, it is cleaned up: typography, spacing, colours and a layout that works on a phone first. You see the draft before anything is built.
in parallel
Titles, descriptions and headings are reworked for search, and written so AI answer engines can quote your statements correctly. The schema markup for each type of page comes with it.
two to three weeks
The site is built on Next.js, with the admin area for your editors, the lead paths, the AI chatbot and the connections to shop, CRM or ERP that you need.
one night
Every old address is redirected to its new one, so no ranking and no backlink is lost. Afterwards we watch indexing and error reports instead of leaving the site to itself.
For your editors little changes: there is still a screen to write in. What changes is the list of things that can break.
None of this is exotic. It is the set of things that decides whether a website earns its keep or just sits there looking current.
The technology behind modern sites: pages served ready-made, clean addresses, images in modern formats.
Your look, tidied: typography, grid, colours and spacing, kept close enough that your customers still recognise you.
Titles, descriptions, headings and internal links, reworked on the pages that actually bring visitors.
Content structured so answer engines find the statement, attribute it correctly and name your site as the source.
Organisation, services, products, FAQ and reviews marked up for machines, matched to each type of page.
Pages, posts and images maintained without touching HTML, in a screen that is separate from what is served to the public.
Answers from your own content, takes the name and the question, and files the enquiry where you will see it.
Forms, calculators, downloads and appointment booking, measured, so you can see which page brings enquiries.
An existing shop is connected or the selling is set up fresh: basket, payment and orders in a flow your customers know.
Calculators, configurators, customer areas and interfaces to CRM, ERP or inventory software, built rather than bolted on.
"There is no plugin for that." In a WordPress world that is where the answer ends. For us it is where the work starts: a configurator that calculates from your price list, a customer area behind a login, a form that writes the enquiry straight into your CRM as a record. That is not a special case, it is the normal case for this way of building.
So the project does not start with a plugin search. It starts with the question of what should actually happen when someone clicks send. Everything else follows from the answer.
Whatever does not exist as a ready-made connection gets built.
The packages differ in the size of the site and in how much gets connected to it. The technology underneath is the same in all three.
Hosting, maintenance and support carry on once the site is live. We agree that part according to the size of the site, before you say yes.
FitsA practice, a law firm, a trade business or a service company with a clear offer.
Have our site reviewedFitsCompanies that win enquiries through their site: chatbot, lead paths and a connection to the CRM.
Have our site reviewedFitsA shop, a portal or your own application, wired into ERP and inventory software.
Have our site reviewedThe price is a starting point, not an offer. What drives it is the number of pages and how much has to be connected, not how pretty it is allowed to be.
It moves with you. Pages, posts, images and documents are read out of your WordPress installation and taken over. What nobody has opened in years we show you first — deleting it is your call.
The switch-over is the moment where that can happen, which is why it is the most careful part of the job: every old address gets a permanent redirect to its new one. Add reworked titles and schema markup on top and it usually goes up after a few weeks rather than down. Nobody can honestly promise it.
Through an admin area where your team edits pages, posts and images. No HTML, and no waiting for us to approve anything. Structural changes are on us.
Then we look at what it does. Usually it does three things and you use one of them — and that one gets built, without the rest. Standard needs like forms, cookie banner, galleries or booking are part of the build anyway.
An existing shop is connected, WooCommerce or Shopify for instance, or we set the selling up fresh. Basket, payment and orders stay a flow your customers recognise.
Four to eight weeks, depending on size. The old site stays online until the switch. The long part is rarely the technology, it is deciding which content really comes along.
You do. It runs on your domain, on open technology, and the source code is yours. If you want to move operations elsewhere, you get everything you need for that.
It answers from your own content and says when it does not know something instead of guessing. Every conversation can be read back, and anything that looks like an enquiry reaches you as a lead rather than sitting in a log nobody opens. KI-Server
You get back what we see in its structure, its loading time and its content, where enquiries are being lost, and an honest estimate of what the move would cost. No meeting required.
No obligation, and no offer before the scope is clear.