Project One Motors sells cars that cost more than most apartments in Dubai. The website took four seconds to load a photo of one.
That's the whole problem, and it isn't really a design problem. The old WordPress build was heavy, slow to browse, and painful to update. Adding a car meant touching the same information in three places. The team avoided doing it. Inventory drifted out of date, which meant the website was quietly lying to buyers about what was in the showroom.
I rebuilt it as a custom Next.js platform on Cloudflare's edge. It loads in four tenths of a second.
A dealership's organic search traffic is its foot traffic. The migration was the risky part, and it held.
The public side is what you'd expect: fast, clean, built around what someone actually looks at when they're considering a car this expensive - the images first, then the specifications, then a way to ask about it without filling in a form.
The part nobody sees is the part that mattered. I built the team a custom admin where publishing a car is one workflow instead of three. Images, specifications, availability, status - one place. The listing either exists or it doesn't. It can't half-exist across three systems anymore.
The migration was the risky part. A dealership's organic search traffic is its foot traffic. I mapped redirects, preserved the URL structure where it earned its rankings, and rebuilt the schema markup properly.