A Greater London cleaning business
A public route for regular, deep, end-of-tenancy and commercial cleaning enquiries.
LIVE BUSINESS PROJECTCleaning services2026
Limpify
Cleaning.
A live cleaning website that moves customers from service discovery to a structured, personally reviewed request.
AT A GLANCE
The project in four answers.
Unstructured requests create extra back-and-forth
The service, location, timing and job context need to be understood before work can be confirmed.
A guided request with a human review boundary
Customers can choose a service and supply the useful details while Limpify retains control of the final quote and availability.
Live and accepting requests
The delivery is verified. Quantitative business impact has not yet been published.
THE BUSINESS PROBLEM
Make the first request useful for both sides.
A cleaning enquiry can arrive without the service type, postcode, preferred date or enough context to estimate the work. That leaves the customer waiting and the business asking basic questions before it can even assess the job.
The website needed to give customers a clear route to act without pretending that every clean could be priced or confirmed automatically.
CONSTRAINTS & SCOPE
Automation stops where judgement begins.
- The business confirms the date, service and final price personally.
- No payment is taken when the initial request begins.
- The service area and postcode need to be understood early.
- Optional job photos must be handled without exposing customer information.
- The public experience must remain usable on the phone customers are likely to have in hand.
RAFAEL'S ROLE
One connected public experience.
The scope shown here covers product direction, information architecture, UX/UI, responsive implementation and QA for the public customer journey.
APPROACH & KEY DECISIONS
Four decisions that shape the journey.
- 01
Start with the service
Problem: vague enquiries are difficult to assess. Decision: begin with a recognisable cleaning type. Effect: the business receives a more useful starting point.
- 02
Explain the review boundary
Problem: an instant promise may be wrong. Decision: state that Limpify reviews the request and confirms the date and final price. Effect: expectations are clear before submission.
- 03
Delay payment until agreement
Problem: taking money before availability is confirmed creates risk. Decision: explain that a 50% deposit is due only when the appointment is agreed. Effect: the customer knows when commitment begins.
- 04
Keep reviews tied to completed work
Problem: unverified review content weakens trust. Decision: use a completed-booking review route rather than filling the site with unsupported claims. Effect: proof can grow honestly.
WHAT WAS BUILT
Functionality grouped by customer value.
Find the right service
Clear service routes, London positioning, visible quote actions and a separate path for commercial cleaning.
Provide useful job context
Service choice, location, preferred timing and optional supporting details are collected in a guided sequence.
Know what happens next
The site explains personal review, confirmation and the later deposit boundary before the customer commits.
Use evidence carefully
Verified feedback and privacy-aware handling are treated as operating requirements, not decorative claims.
RESPONSIVE EXPERIENCE
The real interface.
Desktop and mobile.
These captures come from the live public site. No fixture, AI-generated interface or private customer state is shown.
TECHNICAL DELIVERY
Buyer-facing reliability, not a technology résumé.
The public delivery uses responsive layouts, progressively structured form steps, visible validation and explicit journey states. The important result for the buyer is that the service remains understandable across devices and that final commercial decisions stay reviewable.
OUTCOMES · UNMEASURED
What can be stated today.
- The website and quote-request route are live.
- The main cleaning services have a clear public entry point.
- The initial request is structured before personal confirmation.
- The deposit boundary is explained before submission.
- Outcome measurement is pending; no conversion or revenue uplift is claimed.
LEARNINGS & NEXT PHASE
Measure the handoff, not just page traffic.
The next useful baseline is request completion by device, followed by time-to-confirm and the proportion of requests that arrive with enough information for review. Those measures would show whether the journey is reducing friction without inventing a success story in advance.
A SIMILAR BUSINESS PROBLEM?
Need a booking and quote journey?
Start with what customers need to provide and what your business must confirm before work begins.