Result story
A faster website the team runs itself
Bureau Brussels runs the website of a European trade association. What was slow and needed a developer for every change is now a fast site with an interactive decision tool the team keeps up to date itself.
- Visitors get a direct answer, without downloading a document.
- The team now manages members, publications, locations and frequently asked questions itself.
- Mobile performance went from 64 to 99.
The story
New European packaging rules (the PPWR) determine a company's role: producer, manufacturer or something in between. That guidance sat in a document visitors had to download and work through themselves. RUUB turned it into one interactive tool: answer a few questions and get your role with an explanation, without downloading a file. Behind the tool sit 128 decision rules; their content stays confidential.
The team now manages routine content itself. It describes a change in plain language; Claude and the Sanity MCP turn it into a structured draft; the user reviews and publishes it. Sanity only allows members, publications, locations and frequently asked questions. The structure of the website, the code and the decision logic of the tool stay with RUUB, so routine content no longer requires a web builder.
And the site got fast: mobile performance went from 64 to 99 and Largest Contentful Paint from 13.7 seconds to 1.8 seconds. Content, links and search structure moved across without loss.
How self-service updates work
The team describes a routine change in plain language to Claude or ChatGPT. The Sanity MCP turns it into a structured draft in the CMS, and the change appears live on the site, without a development round.
- AI chatAsk in plain languageTo Claude or ChatGPT, for example adding a new member.
- Sanity CMSStructured draftThe Sanity MCP maps it to the right fields: members, publications, locations and FAQ.
- WebsiteLive right awayThe change appears on the site, without a developer in the loop.
What got faster
- Mobile Lighthouse performance score
- 6499
- Largest Contentful Paint (mobile)
- 13.7s1.8s
Mobile performance, before and after the rebuild.
Questions
What can the team change itself, and what not?
Itself: routine content such as members, publications, locations and frequently asked questions. The structure, the code and the decision logic of the tool stay with RUUB.
Does a person stay in control of what goes live?
Yes. The AI only makes a draft; a person reviews it and publishes it. Nothing goes online automatically.
Can we do this without technical knowledge?
Yes, that is the point. You describe the change in plain language; a web builder or development round is no longer needed.
Does the site stay fast and easy to find after changes?
Yes. The changes you are allowed to make cannot break the site; we guarantee it. You only edit content, so speed and findability stay as delivered.
And if we later want to change something structural?
Then RUUB handles it, for example a new section or a change to the tool. Your day-to-day editing simply keeps running.
Does your system work, but struggle to absorb new needs?
Briefly describe what happens today, who works with it and where it gets stuck. RUUB will help identify a sensible first step.
info@ruub.eu