Case Study

Smart Water Window Cleaning

Doncaster-based window cleaning business. 4.5 years trading, 350+ regular customers. No online presence beyond a Facebook page. We built the website and are building the operational tooling behind it. This page covers both, honestly.

// 01 — STARTING POINT

Where Ash started

Smart Water Window Cleaning Services is Ash's business — water-fed pole work on windows, gutter clearing, fascia and soffit, conservatory roof cleaning. Operates across Doncaster and the surrounding postcodes (DN4, DN5, DN11, DN12). Four-and-a-half years trading, 350+ regular customers on a route-based model, sole trader, no staff.

What he had: a strong word-of-mouth reputation, a Facebook page he used for customer comms, and a head full of routes, prices, and customer preferences.

What he didn't have: a website, a way for new customers to find him online, a structured customer database, or a system for chasing late payments or confirming jobs.

// 02 — THE PROBLEM

What was in the way

Three things, ranked by how much time they were costing:

  1. No front door online. When a potential customer Googled the business, there was nothing to land on. Facebook reviews helped — but a website closes the loop and signals that the business exists properly.
  2. Admin load on top of the day job. Quotes, confirmations, route memory, payment chasing — all manual, all in Ash's head or on paper. Between rounds and rounds of messaging, the admin was eating evenings.
  3. No system he could own. Ash didn't want another SaaS subscription he'd have to re-learn every time a price or service area changed. The solution had to be editable by him, not by us.

// 03 — WHAT WE CHANGED

What we built

Two workstreams, phased so the quick win landed first.

// PHASE 1 — LIVE

The website

  • Built and deployed smartwaterwcs.co.uk on Cloudflare Pages
  • Mobile-first, custom components, copy written in Ash's voice
  • Service-area coverage for DN4 / DN5 / DN11 / DN12 postcodes
  • Floating WhatsApp button to the live business number
  • SEO light: structured data, Google Business Profile, analytics
  • Single-file config — Ash edits prices, services, testimonials without touching code
  • Handover doc: one page of instructions, edits deploy in about a minute

// PHASE 2 — IN BUILD

The operational tooling

  • Customer database holding the round — addresses, frequency, price, access notes
  • Web quote form on the site with price-estimate from lookup table
  • WhatsApp-first comms: daily check-in to Ash, reminders to customers
  • Payment reconciliation — standing order via open banking + GoCardless Direct Debit
  • Exception handling: Ash flags skips and cancellations via WhatsApp
  • Weekly summary roll-up — jobs done, revenue, outstanding, new leads

Payment reconciliation is code-complete; WhatsApp BSP and open-banking credentials in flight.

Deliberately not built

Part of the discipline is saying what's out of scope. Discussed, priced, parked.

  • ×Route optimisation — v2 if volume justifies
  • ×Customer-facing dashboard — WhatsApp is the v1 interface, deliberately
  • ×Invoicing — not needed in the standing-order + DD model
  • ×Blog / newsletter — possible later, not today

// 04 — WHAT HAPPENED NEXT

After the site went live

The website launched on a custom domain with a 1-minute deploy cycle. Ash now has a front door that loads fast, reflects what the business actually does, shows pricing clearly, and lets new customers reach him via WhatsApp or the enquiry form.

The operational tooling is landing in stages. Payment reconciliation is code-complete and waiting on credentials. Customer comms templates are built and tested on a mock WhatsApp adapter. The customer database is seeded with tenant zero's round. Scheduling and weekly reporting are in scoping.

We publish the in-flight parts as in-flight, not shipped. When they're live, this page is updated.

// 05 — ASH'S TAKE

Client feedback

"I had no online presence beyond my Facebook page. Now people can find me, see what I offer, understand my pricing, and get in touch easily. New enquiries have picked up, and I'm looking forward to what the next stage brings."

// 06 — WHAT WE'D DO NEXT

Where this goes next

Once the operational tooling stabilises with Ash, the same pattern — customer DB + comms + payment + scheduling + reporting — becomes available as a multi-tenant product for other small service businesses with the same shape of problem. That's an adjacent offer; not the Smart Water case study.

For Smart Water specifically, the next thing worth doing is route-aware scheduling plus a lighter-weight lead-qualification loop on the quote form — answer the "is this a real enquiry" question before it hits Ash's WhatsApp.

What we wouldn't rush: automating customer comms further. Messages that go out at the wrong time break trust. Getting that right is worth another month.

What made this fit

Ash had a working business before he had a website. That changed what we had to build. No campaigning to drive traffic to a placeholder. No case where the technology was trying to rescue a failing operation. The system had to reflect what already worked and remove admin friction around it.

The constraint that mattered most: Ash edits everything himself. Price changes, new service areas, new testimonials — he opens one file and the site redeploys in about a minute. No hidden CMS subscription. No dependency on us for trivial changes. That shape made handover short: one page of instructions, one live demo, done.

For the operational tooling, we're building carefully. Payment reconciliation is not something you ship and pray. The slower parts are slow on purpose.

Got a business that works and a system that doesn't?

That's usually the best starting point. Tell us where the admin drag lives — we'll tell you honestly whether it's a website job, a tooling job, or nothing we should be involved in.