Case studies

Website // One product, two audiences

Garaje for Drivers

The front door to Garaje for car owners

The marketing site for car owners: the front door to Garaje for anyone looking for a shop, a part, a parking spot or the people who care about the same cars they do.

Year:
2026
Role:
Designer and engineer
Org:
Garaje LLC
The Garaje consumer homepage, Everything for car people, with the mobile app beside it

What it has to do

01

A marketplace is worth nothing to the first person who arrives. The consumer site exists to make the case before the supply side is visible: what Garaje is for, what you can find on it, and why it is worth opening the app to look.

It is a landing page rather than a product surface, which changes what matters. Nothing here is behind an account, so every claim has to land on a first read, on a phone, on Philippine mobile data.

Split from the business site on purpose

02

Car owners and shop owners want opposite things from the same platform. One is looking for somewhere to take a car; the other is looking for cars to take. A single site addressing both would have spent its first screen explaining which half the reader was in.

So there are two sites on one backend, each free to lead with its own audience's reason to care. This one never has to mention pricing, dashboards or onboarding.

At three widths

  • Desktop

    The Garaje consumer homepage, Everything for car people, with the mobile app beside it

Decisions

  1. 01Landing page, not product surface

    Nothing is behind an account, so every claim has to land on a first read.

  2. 02Phone first, on mobile data

    Built for a first read on a phone, on mobile data.

  3. 03Split from the business site

    Two sites on one backend, each free to lead with its own audience's reason to care.

  4. 04Content from Sanity

    Copy and imagery edited in Sanity, so the pitch changes without a deploy (unsourced).

How it ships

  1. Sanity contentCopy and imagery edited without a deploy (unsourced).
  2. Typed page dataSchema validation with TypeScript.
  3. Reusable sectionsShared with the business site.
  4. Static outputPrerendered HTML for a first read on mobile data (unsourced).

// A marketplace is worth nothing to the first person who arrives. The site's job is to make the case before the supply side is visible.

Checked for

Accessibility

  • Landmarks and heading order (unsourced)
  • Keyboard-visible focus (unsourced)
  • Alt text on product imagery (unsourced)

Performance

  • No account gate before the first read
  • Prerendered routes (unsourced)
  • Responsive images sized for a phone (unsourced)

Built with

  • TypeScript
  • Next.js
  • React
  • Tailwind CSS
  • Sanity

Elsewhere

More work