Divemotor’s portal serves six vehicle brands across Peru. I kept it improving while it stayed live, and designed the sections it was missing.

Divemotor’s live home page, with tiles for its four vehicle lines (cars, trucks, vans and buses) and the dealerships section.

Divemotor sells and services Mercedes-Benz, Freightliner, FIAT, Jeep, Dodge and RAM vehicles across Peru, and divemotor.com is where a fleet buyer compares trucks and a family books a service. For a year and a half I owned its continuous improvement: a clearer way to find a dealer, new sections the brand needed, the UI kit I built behind every page, and specs developers could build from.

Outcome
Three new sections shipped, a dealer finder people can use, and specs for six breakpoints that developers built from.
Role
UX Analyst at Altimea, then UX/UI Designer at Vide Solutions, both for Divemotor. Continuous improvement, the UI kit (built from scratch) and new sections.
Team
A team of 4; I designed most of the portal’s work
Duration
1 year and 6 months
Tools
Figma

One portal, six brands, four vehicle lines

Divemotor is a large Peruvian automotive group. Its portal has to serve very different people at once: a fleet manager comparing sixteen truck models, a family looking for a Jeep, a driver booking a service at the nearest workshop. All of it inside one Divemotor shell, with each brand’s content in its own voice.

A portal like that is never finished. My job was to keep it improving without taking it offline: find where people got lost, design the fix, and hand it to development in a form they could ship.

Finding a dealer shouldn’t need a map-reading lesson

The Dealerships page was the clearest case. The filters floated over the hero photo, half of them hard to read, and the map took the whole left side before you had chosen anything.

Drag the red line, or focus it and use the arrow keys.

The proposal: a filter card below the hero with region, your location, services, brands and vehicles, then dealer cards next to the map. The previous Dealerships page: filters overlapping the hero photo, a map on the left and dealer cards on the right.
Dealerships, before and in my proposal. The filters moved into one card under the hero, in the order people decide: where, what service, which brand.

The filter card shipped: today the live page leads with it, including “use your location”, so the nearest dealer is one tap away.

The live Dealerships page on divemotor.com, with the filter card under the hero.
The same filter card, live on divemotor.com.

The sections the brand was missing

Divemotor had stories the portal couldn’t tell: drivers and clients on the road, vehicle deliveries, its sustainability work. I designed the sections for them, desktop and mobile, each with its own components: a video series called Juntos en la Ruta, a customer experiences section, and an article layout that became the sustainability page. All three are live.

The Juntos en la Ruta section designed for desktop and mobile.
Juntos en la Ruta, designed for desktop and mobile with its own carousel and video components.

Inside the trucks listing, I added banner sliders that offer a next step when a buyer hasn’t found the right model: used trucks, the video series, or what other clients say.

Three variants of the Banner slider component used in the trucks listing.
One Banner slider component, three variants, so the listing never ends in a dead end.

One kit behind every page

A portal this size only stays consistent if every page is built from the same parts. I built the UI kit as that source: colours, type, and components grouped in the same sections as the site, so a designer or developer finds the header, a filter or a brand tab where they expect it.

The UI kit foundations: Divemotor’s colour palette and heading type scale.
Foundations: one blue for actions, one orange as the accent, and a heading scale in Roboto Condensed.

Brands don’t get their own theme; they get their own content inside the same shell. A brand tab is one component with a variant per brand, so adding a brand never means designing a new page.

The brand tab component in several brand variants.
One component, one variant per brand.
The dealership filter component in several of its variants.
The dealership filter, with every variant it needs drawn before handoff.

Specs developers could build from

Most portal changes are small, and small changes get lost in handoff. So I kept a page in Figma just for the development team: the layout at every breakpoint from 1920 down to mobile, and next to it, in plain words, what changes and why.

The developer view in Figma: the tablet home layout with annotations for type sizes and spacing.
The developer view at 768 px: type sizes per breakpoint, written next to the layout they belong to.

That note is now the live home: four vehicle lines, no gap.

new sections designed and live
3
breakpoints specified for development
6
brands inside one portal shell
6
component sets in the UI kit I built
87

What I learned

On a live portal, improvement is a habit, not a launch. The changes that shipped were the ones I wrote down where developers already look, with the reason next to them.

Not everything shipped as drawn. The sidebar filter I proposed for buses went live as a simpler brand filter. That taught me to design the version that can ship this sprint next to the ideal one, and to let the team choose with both on the table.

This was the trailer.

I'd love to walk you through the full story, dead ends included.