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.

First
Second
Before
After

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

Project overview

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 (demo build) 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.

My role: UI/UX + visual design (also created the brand + logo)
Scope: Home, Inventory, Vehicle Details (VDP) + basic navigation structure

Goal: Increase qualified leads by making next steps clear and low-friction

Tools: Figma, Base44 (rapid build/prototype), lightweight UX writing

Timeline: ~1 week (design + build)
Note: Analytics weren’t connected during this phase, so this is a hypothesis-driven redesign with a validation plan.

from

Service

complexity

organized as

Audience-

specific paths

to

Clear

next

steps

1

Patients needed clarity

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

Messaging + intake CTAs
2

Providers needed trust

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

Provider path + referral messaging
3

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.

from

from

Service complexity

Service complexity

Service complexity

organized as

organized as

Audience-specific paths

Audience-specific paths

Audience-specific paths

to

to

Clear next steps

Clear next steps

1

Patients needed clarity

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

Messaging + intake CTAs
2

Providers needed trust

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

Provider path + referral messaging
3

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
1

Patients needed clarity

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

Messaging + intake CTAs
2

Providers needed trust

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

Provider path + referral messaging
3

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
1

Patients needed clarity

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

Messaging + intake CTAs
2

Providers needed trust

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

Provider path + referral messaging
3

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.

Old workflow required navigating between 3-4 separate pages with no contextual links. Operators had to manually copy station IDs and search across different views to piece together diagnostic information.

Old workflow required navigating between 3-4 separate pages with no contextual links. Operators had to manually copy station IDs and search across different views to piece together diagnostic information.

Audit

The original CarLane interface was a conversion leak, not just a design failure. By auditing the site, I identified that users were being forced to navigate five competing primary actions simultaneously, leading to immediate choice paralysis. I identified that the inventory browsing did not support fast comparison, which is the primary friction point for automotive shoppers.

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: single moment of decision — Schedule Test Drive is primary; payment/financing supportive.


Technical Validation & The Build

I built a working demo in Base44 to validate that the design decisions were technically feasible, not just visually clean. This meant inventory filtering and financing flows were testable before any dev time was spent, reducing implementation risk.

To see how these architectural decisions translate into a real-world environment, you can interact with the live build here:

Explore the CarLane Published Site


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 experience consistent across pages, I created a lightweight component system:

  • Scalable Architecture: Built a lightweight component system in Figma to ensure future inventory scales without breaking the layout.

  • State-Aware Design: Defined explicit UI states (Loading/Empty/Error) to prevent user frustration during data-heavy inventory searches.

  • Feasibility-First: Spacing and type scales were mapped to code-friendly logic, ensuring a 1:1 match between design and the Base44 build.


Outcome

This was a design and strategy engagement — analytics tracking and post-launch measurement were outside scope. The validation plan below defines exactly how I'd measure success if given access.


Validation plan (how I'd prove it works)

Browse intent

  • Home → Inventory CTR (Browse clicks)

  • Search usage / filter interactions

  • Inventory views per session

Shopping intent

  • Inventory → VDP CTR

  • VDP views per session

Lead intent

  • Test Drive CTA clicks

  • Test Drive form completion rate

  • Click-to-call interactions (mobile)

Financing intent

  • Financing clicks (nav + section)

  • Credit app completion rate

Next test:

A/B test the homepage secondary CTA: Schedule Test Drive vs Get Prequalified and compare lead quality + conversion.

.say hello

Interested in working together?
Let's talk.

.say hello

Interested in working together?
Let's talk.