Aqua Glaze Exterior Cleaning
One tick now plans the route, texts the customer, records the clean and collects the money.
Response times measured over eight cold loads from a real browser. Layout and accessibility checked at a true 390 pixel phone width.
The problem.
Liam ran a real round on a template website that could not do anything. The old site was built on an off-the-shelf booking-system template with 19 pages, a shopping-cart widget that never loaded, and a main navigation link spelled “Presure Washing”, a misspelling that was baked into the page address itself so nobody searching for pressure washing could ever match it.
No screenshot of the old site is shown here. It was replaced before anyone captured it, and a reconstruction from archived code renders inaccurately, so publishing one would misrepresent what was actually there. Everything described above comes from the 19 pages captured verbatim at the time, which is checkable. From now on the previous site is photographed before any rebuild starts.
The website was the smaller problem. The business ran on a paper round list, a phone, and remembering. Deciding the driving order each morning, texting each customer the night before, invoicing after the clean, then chasing the payment. Every one of those was a separate manual job repeated dozens of times a week.
What was built.
The round manager, on his phone
An installable app that knows who is due, works out the shortest driving order for the day, opens turn-by-turn navigation, drafts each customer's heads-up message, and records the clean with one tap.
A route that plans itself
The system solves the driving order across the day's stops, estimates arrival time at each house, and reports total miles, finish time and the day's takings before he sets off. Because a navigation link caps at ten stops, it chains the day into legs automatically.
Payment on the same tick
When he marks a customer cleaned, the Direct Debit is collected. No invoice, no chasing, no bank reconciliation. There is an undo window in case of a mistap, and payments taken in cash or by transfer are recorded in the same place.
A customer portal
Customers see where he is today, the arrival window they were actually promised, their rewards balance, their invoices, and can set up their own Direct Debit or book an extra service without phoning.
A loyalty scheme that cannot drift
Points are recalculated from things that actually happened rather than added up over time, so undoing a clean removes its points automatically and the balance can never need repairing. Earned badges apply a permanent discount to every future collection.
A daily due-check that runs itself
Every morning the system works out who has come due and sends him one summary notification. It never nags twice about the same date.
The parts you do not see.
The engineering that decides whether a system like this is trustworthy.
- Every customer record is encrypted before storage, so the underlying files are unreadable even if a storage address leaked.
- Each charge carries a key unique to that customer and day, so a retry or a double-tap physically cannot take the money twice.
- The payment system derives its live-or-test setting from the credential itself, so a test key cannot reach the real money API by accident.
- Owner logins and customer logins are separate realms. A customer session can never reach the round dashboard.
- Incoming payment notifications are signature-checked against the raw message before they are trusted.
All of this sits inside the plan.
The site is built free first. You see it working before you pay a penny. Then it is £99 to own it outright, or £149 a month fully managed from day one with no £99 at all. Ongoing work like the systems above is part of the monthly plan, not a separate invoice.