A booking system that runs itself
A marketing site and viewing-booking system for a used-car dealership — edited by the people who sell the cars, and running without anyone administering it.
The constraint that shaped everything: nobody would maintain it.
A small dealership does not have a web team. It has people who sell cars, and any system that assumes otherwise stops being used within a month.
So the brief was less “build a website” and more “build something that runs without attention”. Content editing had to be obvious enough to do once a fortnight without a manual. The booking flow had to work without anyone administering it. And when something did break, we needed to know first.
We sell cars. We do not want to think about a website. Rabblepop built one we update ourselves in five minutes and a booking system that runs on its own — we have not needed to touch it since launch, which is exactly what we asked for.
Ali K. — BeyondCars · Used-car dealership, UK
Built to be left alone.
Next.js and TypeScript, with a structured content model so the dealership’s own staff change stock, pages and opening hours without touching a template. Bookings trigger email confirmations to the customer and the dealership. Error monitoring and separate staging and production environments from launch.
Nothing that needs a developer on a Tuesday afternoon. That was the point.
Most small-business software fails at maintenance, not at build.
What this means for youIf the people who have to live with a system were not considered while it was designed, it will be abandoned and replaced by a spreadsheet.
Designing for the least engaged user — the person who will touch this twice a month, in a hurry — is the difference between software that gets used and software that gets paid for and forgotten.
The results
OutcomesEditable
A structured content model rather than a page builder, so staff change stock and opening hours without being able to break the layout.
Unattended
A booking flow with sensible defaults, confirmations to both sides, and no admin queue to babysit.
Observed
Error monitoring from day one. If something breaks, we know before the customer does.