Development Agency
Contact Sign in Get a project quote

Service

Car wash software development

For owners of hand car washes, valeting centres and mobile valeting businesses who need a service menu by vehicle size, bay and team capacity, travel zones, wash subscriptions and fleet accounts designed around how their site and their vans actually fill the day.

Get a project quote See the software package

The problem

What goes wrong today

Where it usually starts

A valeting centre with three bays and a mobile van takes bookings by phone and through a social media inbox.

  • A full valet on a large estate takes the whole afternoon in one bay, but the price list and the booking form only know "car" and "van", so the team quotes small-car prices to large-car customers and the bay runs late.
  • Walk-ins pull in behind the booked cars and nobody can tell them how long they will wait.
  • The mobile van is booked for a flat in a tower block at nine and a farmhouse twenty miles away at ten, because the diary has no idea where anything is.

Where it gets harder

Monthly wash customers pay in cash at the start of the month and the owner keeps a list in a notebook of who has paid; by week three the team cannot tell a paid-up subscriber from someone who stopped in May.

  • A taxi firm sends six cars a week and is invoiced from memory at month end.
  • Add-ons such as a wax or an interior protect are sold at the bay if the valeter remembers to offer them and recorded nowhere.
  • The owner sees the bays busy and the takings thin, and cannot say which services make money, how many subscribers are active, or how much the fleet account actually owes.

Scope of the service

What the build covers

A custom car wash build normally covers:

  • A service menu priced by vehicle size With the size recorded against the customer's vehicle so the second booking is priced right automatically
  • Bay or team capacity per time slot So a full valet occupies a bay for the right length of time and the slot picker only offers what fits
  • A walk-in queue That the team adds cars to and that shows on a screen in the waiting area with an estimated turn
  • Mobile valeting with travel zones A van's diary built around journey time between jobs and the service time at each
  • Subscriptions for monthly or unlimited washes Paid by recurring card, with the subscriber recognised by registration at the bay
  • Fleet accounts That send vehicles on an arrangement and are invoiced monthly with a line per visit
  • Add-ons and upsells offered at booking and at the bay Recorded against the visit

How discovery works

Discovery follows one busy Saturday and one mobile day with you: how a vehicle's size is decided, how long each service really takes per bay, how walk-ins and bookings share the bays, how far the van will travel and what it charges for distance, who manages subscribers and how the taxi firm is billed. Each becomes a named stage in the scope document: choose service and size, slot, wash, pay or subscription.

Deliberately out of scope

  • Automatic wash machinery and its controllers, payment terminals beyond connecting a provider, water and chemical stock, and accounting

When the scope grows

Scoping scenario

A group with four sites, two mobile vans, a subscription scheme valid at any site and three fleet accounts with different arrangements needs site capacity per bay, subscriber recognition across sites, van diaries with travel zones and a fleet invoicing run that can split by depot. That is a different build from a single-site hand wash with a walk-in queue, and the scope document says so.

Deliverables

What you receive

  • Discovery notes from a walk-through of a busy site day and a mobile valeting day
  • A written scope document naming each stage, the capacity model, the subscription rules and what is out of scope
  • Design of the online booking flow, the bay board, the queue display, the mobile van diary and the fleet account view on phone and desktop
  • The build, deployed to your hosting or ours
  • Migration of customer and vehicle records, active subscribers and future bookings from your current list or app, where practical
  • Training for the site manager, valeters and the owner, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, the current price list, booking channels, subscriber list and how fleet customers are invoiced today.

    Project stage: Onboarding

  2. Planning

    Discovery with the owner, the site manager and a mobile valeter; the capacity model, service menu and scope document are agreed with a milestone plan.

    Project stage: Planning

  3. Design

    Clickable designs of the booking flow, the bay board, the queue screen and the van diary, checked on the phones valeters use with wet hands.

    Project stage: Design

  4. Development

    Built in stages: service menu and capacity first, then booking and the queue, then mobile zones, then subscriptions, fleet accounts and add-ons.

    Project stage: Development

  5. Client review

    The site runs a Saturday on the new bay board with real walk-ins and bookings, the van runs a mobile day, and the team tells us where it does not match the forecourt.

    Project stage: Client review

  6. Revisions

    Service durations, zone rules, queue display and subscription recognition are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions

  7. Ready for launch

    Subscribers and bookings migrated, recurring payments tested with the provider, the queue screen installed, checklist signed off.

    Project stage: Ready for launch

  8. Delivered

    The business runs on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Card payment providers for bookings, recurring subscriptions and terminal payments at the bay
  • SMS and email providers for booking confirmations, ready messages and subscription renewals
  • Mapping and journey-time services for mobile travel zones and van routing
  • Vehicle-data providers for registration lookup of body type and size
  • Number plate recognition cameras the site already has, for subscriber recognition at the entrance
  • Accounting software for fleet invoices and daily takings
  • Review and social platforms the business already uses, for post-visit requests

How we would approach it

Worked example

Concept demo

A four-site valeting group with a shared subscription and two mobile vans

The situation

A valeting group with four sites, two mobile vans and a monthly subscription scheme had no way to recognise a subscriber from another site, booked its vans without regard to distance, and invoiced three fleet accounts from memory.

Why it is a custom build

This needs a custom build because the subscription, the capacity and the mobile routing all have to agree with one another across sites, which single-site booking apps do not attempt.

The scope we would propose

  • A service menu by vehicle size shared across sites with site-level capacity per bay
  • Subscriber recognition by registration at any site, with the plan's usage shown to the valeter
  • Van diaries built from travel zones and journey time so a booking is only offered where the van can get to it
  • Fleet accounts with an arrangement per depot and a monthly invoice run with a line per visit
  • An owner view of revenue by service, active subscribers and fleet balances across the group

Concept demo: a scoping scenario written to show how we would approach the work. It is not a delivered client project.

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of sites and whether a fixed site, mobile vans or both are in scope
  • Number of bays or teams and how service durations vary by vehicle size
  • Walk-in queue with a display screen in the waiting area
  • Mobile travel zones and journey-time routing
  • Subscriptions with recurring payment and the provider involved
  • Fleet accounts and the monthly invoicing arrangement per customer
  • Number plate recognition or vehicle-data lookup
  • Volume of customer, subscriber and booking data to migrate
  • Hosting choice: your own hosting or ours

Start from a package

Car wash booking package

Service menu by vehicle size, bay and team slots, walk-in queue display, mobile valeting zones, wash subscriptions, fleet accounts with monthly invoicing and bay-side upsells.

Custom build
View the package

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

A single site with a few bays, perhaps a mobile van and a straightforward subscription is usually well served by the car wash booking package configured around your menu. Custom work is the honest answer for several sites sharing subscribers, number plate recognition, complex fleet arrangements or routing across many vans. Discovery settles it before anything is quoted.

How does the system know a car's size?

The customer picks a size at first booking, or a vehicle-data lookup suggests one from the registration where that is in scope. The size is saved against the vehicle, so every later booking and every bay-side upsell is priced from it, and the manager can correct it once if it was wrong.

Can mobile bookings account for travel?

Yes. Each van has zones with a travel allowance and a surcharge where you want one, and the diary offers slots that leave journey time between jobs. The valeter sees the day in order with addresses and the service at each stop.

How are subscribers recognised at the bay?

The valeter enters or scans the registration on the bay board and sees the plan, the washes used this month and any add-ons included. Where the site has number plate recognition cameras, recognition at the entrance can be scoped as an integration.

Who owns the system afterwards?

You do. Source code, customer and vehicle records, subscriptions and booking history are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for car wash software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote Discuss a partnership
Get a project quote

Cookies on this site. Strictly necessary cookies keep the site working. Allow first-party analytics so we can see which pages lead to enquiries. No advertising, no third-party trackers, no personal data; you can change this at any time on the cookies page.

Manage preferences