CarLane - Redesign for a Local Car Dealership

Redesigned CarLane’s shopping flow to help visitors browse inventory, compare vehicles, schedule test drives, and find financing without decision overload.

View live site

Before

After

Before → After: clarifying the primary next step and adding trust above the fold.

Project overview

Impact

USABILITY TESTING

18 → 7 minutes

Average task time with five operators

POST-LAUNCH

15% fewer support tickets

Tracked over three months after launch

Role: UX/UI Designer (end-to-end), information architecture, interaction design, conversion-focused layout, copy hierarchy Scope: Home, Inventory, Vehicle Details + design system consistency Tools: Figma, Base44 AI use: I gave Base44 my Figma designs. It built the site and its backend, and I used it for minor UI adjustments. The layout, flows and visual design are mine. Constraints: Dealership users need fast browsing + high trust; financing is high-friction; inventory content is variable (photos, trims, pricing, mileage) Note: Post-launch analytics were outside scope for this engagement. The validation plan below defines how success would be measured.

Impact

USABILITY TESTING

18 → 7 minutes

Average task time with five operators

POST-LAUNCH

15% fewer support tickets

Tracked over three months after launch

Patients needed clarity

Could the pharmacy help them get medication delivered, handle insurance, and start intake without confusion?

Messaging + intake CTAs

Providers needed trust

Could the pharmacy reliably support referrals, prior authorizations, coordination, and patient updates?

Provider path + referral messaging

Offline users needed a bridge

Flyers and business cards had to move people from a physical touchpoint into the digital intake flow.

QR handoff to intake

The main UX challenge was translating several pharmacy services into audience-specific paths that made the next action obvious.

Before the redesign

The original Station page provided a point-in-time snapshot.

Real-Time Logs became the fallback for deeper investigation.

It confirmed configuration and current connection status, but provided little history or operational context to explain why the station disconnected.

Every OCPP event appeared in one continuous stream. Operators had to scroll through unrelated entries and open raw payloads individually to trace what happened.

Operators learned about station issues through offline notifications, driver reports, support tickets, and unresolved work orders.

The Station page confirmed configuration and current connection status, but gave operators little information about how the station had been behaving over time.

Patients needed clarity

Understand medication delivery, insurance support, and how to start intake.

Service messaging + intake CTAs

Providers needed trust

Understand referral support, prior authorizations, insurance coordination, and patient updates.

Provider information + referral guidance

Connecting print to digital intake

Flyers and business cards needed to guide people into the online intake flow through QR codes.

Finding the station was only the first problem

The original Station page provided a point-in-time snapshot.

Real-Time Logs became the fallback for deeper investigation.

It confirmed configuration and current connection status, but provided little history or operational context to explain why the station disconnected.

Every OCPP event appeared in one continuous stream. Operators had to scroll through unrelated entries and open raw payloads individually to trace what happened.

Finding the station was only the first problem

Operators learned about station issues through offline notifications, driver reports, support tickets, and unresolved work orders.

The Station page confirmed configuration and current connection status, but gave operators little information about how the station had been behaving over time.

Operators learned about station issues through offline notifications, driver reports, support tickets, and unresolved work orders.

The Station page confirmed configuration and current connection status, but gave operators little information about how the station had been behaving over time.

The original Station page provided a point-in-time snapshot.
It confirmed configuration and current connection status, but provided little history or operational context to explain why the station disconnected.
Real-Time Logs became the fallback for deeper investigation.
Every OCPP event appeared in one continuous stream. Operators had to scroll through unrelated entries and open raw payloads individually to trace what happened.

The original Station page provided a point-in-time snapshot.
It confirmed configuration and current connection status, but provided little history or operational context to explain why the station disconnected.
Real-Time Logs became the fallback for deeper investigation.
Every OCPP event appeared in one continuous stream. Operators had to scroll through unrelated entries and open raw payloads individually to trace what happened.

Audit

I audited the original site page by page. The homepage gave visitors five actions with equal weight, so there was no clear first step. The inventory pages also made it hard to compare cars, which shoppers need to do before booking a test drive.

Audit callout: multiple equal-weight CTAs creates noise and indecision.

Strategy

I aligned the experience to the real dealership funnel:

Browse → Schedule a test drive → Finance (when ready)

To reduce decision fatigue, I set CTA rules across the site:

Home: Browse Inventory (primary), Schedule Test Drive (secondary), Financing in nav
Inventory: Browsing + View Details stays the focus; filters/sort support narrowing
VDP: Schedule Test Drive becomes the primary commitment action; financing is supportive, not the first push

The 3 decisions that drove the redesign

Decision 1: One primary action per page (CTA hierarchy)

Before: Pages asked users to do five things at once.

After: Each page has one clear primary action, with supporting actions secondary.

Example - Hero page

Home: Browse Inventory is primary; Test Drive is secondary; trust moved above the fold,

Decision 2: Trust at the moment of hesitation

Before: Warranty/guarantee/ratings were present but not doing enough work.

After: Trust is positioned near the points where users hesitate (first impression + commitment moments).

Trust: guarantee + coverage presented as a quick checklist (fast to scan).

Decision 3: Faster browsing + easier comparison (Inventory + VDP)

Before: Inventory was harder to scan; Vehicle Details felt cluttered.

After: Inventory is scan-first, and the VDP focuses on a single decision moment.

Inventory

Inventory: scan order improved (model + price first), consistent specs, faster comparison.

Vehicle Details (VDP)

VDP: one decision point. Schedule Test Drive is primary, and payment and financing support it.

The Build

Base44 turned my Figma designs into a working site, which let me test inventory filtering and the financing flow in a real browser. The live site at carlanedealership.com runs on this build.

Financing placement

I did not make financing the main homepage conversion because it’s a high-friction credit application. Most users need inventory context first.

What I did instead:

Kept Browse Inventory as the main path
Promoted Schedule Test Drive as the first meaningful commitment
Made Financing easy to find via nav + a dedicated section (for users who are ready)

Financing is accessible without being forced as the first step.

System + Consistency

To keep the pages consistent, I built a small component system in Figma.

Reusable components: inventory cards, buttons and trust blocks, so new listings fit the layout without breaking it.
States: loading, empty and error states for inventory search.
Spacing and type: one spacing and type scale across every page, which kept the build close to the Figma designs.