A site that turns a visitor into a booking request.

A mobile detailer's work is visual, so the site had to look premium and custom. It also had to turn visitors into quote requests quickly, and let the owner deal with those requests without touching a database or learning new software.

It also had to avoid promising time slots the owner cannot keep. A detail is not a fixed-length job: a heavily contaminated car simply takes longer.

Quote first, not a calendar widget

A customer sends a request: service, extras, car, address and the time they would like. It is a request, not a confirmed slot, and nothing is charged. The owner checks each one by hand and replies within 24 hours to confirm or suggest a closer time.

Because the owner confirms every job himself, a customer can never grab a slot he cannot keep, and there are no customer accounts to run.

Honest, live prices

Every price on the site is a starting price, and the page says so. Larger or dirtier cars are priced as extras the customer can add up front, so there is no surprise at the end. The prices on the services page come from the same data the owner edits, so what visitors see is what he charges.

Mobile first

The journey is built for a phone and kept short: start the request from the homepage, finish it on the booking page, and land on a clear thank-you page. The form checks UK postcodes, the server checks everything again, and the public form is rate limited.

The owner logs in to a private admin page, with no public route to it. There is no database to touch and no jargon.

• A new request arrives by email, with the customer's address as the reply address, so answering it reaches the customer directly.
• The request list shows each job with a plain status: New request, Reviewing, Proposed time, Confirmed, Completed, Cancelled or Declined. It can be filtered by status and sorted by date.
• The owner can propose a different time, add private notes, confirm the job and choose whether to email the customer.
• A ready-written WhatsApp message can be prepared for the customer from the request.
• Services, prices, extras, areas covered and photos are edited from a settings page, and the public site follows.

The admin always separates what the customer asked for from what the owner has planned, so a request is never mistaken for a booked job.

The groundwork for local search is part of the build, not an add-on. Pages carry structured data for the business, its services and its common questions. The list of areas covered is kept in one place and reused across the site, so Google and AI assistants get the same answer as a customer.

The site also publishes an llms.txt file, a plain summary for AI search tools, generated from the same live service data as the pages, so it cannot drift out of date. A health check watches the data connection, so a quiet outage does not leave the site showing prices the business does not charge.

Next.js, React, TypeScript and Tailwind, with Supabase for data, Resend for email and Vercel for hosting.

I stay the one person to call. Every Website and Platform build includes 30 days of aftercare from launch. After that, I offer monthly care plans that cover updates, fixes and small changes, so the site does not get left alone.

Details and prices are on the services page.

If customers need to ask for a quote, book a time or find you on their phone, the same approach can work for you. Tell me what you do and what the site needs to do.