Neurova AI · Supporting work
Fast, accessible, search-visible websites and web applications, built as the delivery layer for the systems we ship, and on their own where that's what you need.
Almost every AI system needs somewhere to live. An assistant needs an interface, a booking system needs a flow patients can actually complete on a phone, a practice platform needs an admin view that staff will not fight. That is what this work is now: the delivery layer for the systems we build.
It is still real engineering, and we still do it properly. It just is not the headline any more.
We are based in Eindhoven and most of our clients are Dutch, which shapes the defaults. iDEAL and now Wero at checkout. Dutch-language content that reads as though a Dutch person wrote it, because machine-translated copy is obvious and it costs you trust. DigiD where citizen identity is involved. Hosting in EU regions by default. And Dutch accessibility expectations, which are stricter than most teams assume and are tightening as the European Accessibility Act widens.
We do not publish prices. What moves this one: how much of it is bespoke versus configured, whether there is an application behind the pages or just content, how many integrations are involved, and whether personal data is in scope. A brochure site and a patient portal are the same technology and completely different projects.
Tell us what you need and we will come back with a written scope, a fixed price and a date, including an honest view on whether a rebuild is warranted at all.
Do you still take on website projects on their own? Yes, though it is no longer what we lead with. Our focus has moved to AI systems and medical software, and web work is now mostly the layer those live inside: portals, dashboards, admin interfaces, booking flows. We continue to take standalone site work for existing clients and where it fits alongside something larger.
What stack do you build on? Whatever suits the project rather than whatever we happen to like. For content-led sites that often means a static or hybrid setup that is fast by default; for applications, something with a proper backend. We will happily talk you out of a framework you do not need.
Is SEO included? The technical foundations are, always: clean markup, correct structured data, fast Core Web Vitals, sensible URLs. Content strategy and ongoing optimisation are separate work; see SEO and search visibility.
Can you work with a site we already have? Usually. Adding a booking flow, a patient portal or an assistant to an existing site is a very common shape of project, and it is nearly always cheaper than a rebuild. We will tell you honestly if the existing site is the thing holding you back.
Tell us what you're building and we'll come back with a written scope, a fixed price and a date.