← Back to work

carwash.homeservice

Booking site that sends car-wash leads straight to WhatsApp.

Role
Design and development
Year
2026
Stack
  • Next.js
  • Tailwind CSS
  • GSAP
  • Sanity
  • Vercel

Features

  • Answers before anyone asks

    Prices per vehicle, the areas they cover and before and after photos, all on one page.

  • Four fields, then WhatsApp

    Name, vehicle, address and a time. Send opens WhatsApp with the whole booking written out.

  • Made for ad traffic

    Phone-first and fast on mobile data, because that's how nearly every customer arrives.

  • The owner edits it

    Prices, areas, the gallery, the FAQ and the reviews all change in Sanity without touching code, and the site updates shortly after.

  • Ads judged by bookings

    The Meta pixel records each booking as a lead, so the owner can see which ads bring in actual customers and not just clicks.

  • One colour for booking

    One blue is used for booking and for nothing else, so the next step is always obvious.

The problem

carwash.homeservice washes cars and motorbikes at the customer's home in Bandung. Nearly all of their customers find them through Meta ads, on a phone, usually on mobile data and in the few spare minutes they have.

Before the site, every ad led straight into a WhatsApp chat, and almost every chat opened with the same three questions: do you come to my area, how much is it for my car, and when can you come. The team spent a good part of each day answering those instead of washing cars. Replies took time, and many people left before they got one, which meant paying for ad clicks that never turned into a booking. The owner also had no way to tell which ads actually brought in customers.

What I built

A fast, phone-first website that answers those three questions before anyone has to ask, then hands the customer over to WhatsApp with a booking that's ready to go.

Thinking from the ad click

I planned the site around the moment someone taps an ad: a phone, a patchy connection and a few seconds of attention. So everything a customer needs to decide, the price for their vehicle, the areas covered and before and after photos, sits on one page, and that page has to load fast on mobile data. I kept WhatsApp as the place where bookings arrive, because that's where the team already works. The site's job is to make sure each chat starts with a complete booking instead of a question.

How a booking flows

Meta adMeta pixelWebsiteSanityWhatsAppThe teamtap the ad4 fieldsLeadbookingsend

Step 1 / 4

  1. Someone taps an ad and lands on the page, with prices, areas and photos right there.
  2. They tap the booking button and fill in four fields: name, vehicle, address and a time.
  3. Pressing send records the booking as a lead for the Meta pixel and opens WhatsApp with the whole booking already written out.
  4. The customer hits send, and the team receives a message with everything they need to confirm.
The home page on a phone, the way people arrive from an ad
The home page on a phone, the way people arrive from an ad
Booking: four fields, then straight to WhatsApp
Booking: four fields, then straight to WhatsApp

The owner changes prices, areas, the gallery, the FAQ and the reviews in Sanity without touching any code, and the site updates shortly after. Because each booking is counted as a lead, the owner can see which ads bring in real customers, not just clicks. One blue is used for booking and for nothing else on the page, so the next step is always obvious.

The same page on a laptop
The same page on a laptop

The result

The site went from an empty folder to live in three days. People who tap an ad now land on prices and a booking button, and the team gets bookings that already include the address and the time, instead of a "how much?" that takes five messages to turn into a job.

Next project →Lecturai
Download CV