Service

Cleaning booking platform development

For on-demand cleaning platforms, franchise networks and regional operators who price by property size and frequency, assign self-employed or employed cleaners from an availability calendar, and need bookings, recurring plans, check-in, cancellation rules, payment holding and payouts designed around their own service area and employment model.

The problem

What goes wrong today

Where it usually starts

A cleaning platform starts with a founder, a phone and a group chat of cleaners.

  • A customer messages for a two-bedroom flat every fortnight; the founder works out a price from a rate card in their head, asks which cleaner is free on Thursday mornings, and books it in a shared calendar.
  • The customer's key is with cleaner A, but cleaner A is ill one Thursday and cleaner B is sent without the key or the note about the alarm code.
  • Nobody knows what time cleaner B actually arrived or left, so when the customer says the clean was forty minutes short there is nothing to check.

Where it gets harder

Money is taken by bank transfer when the customer remembers, cleaners are paid from a spreadsheet at the end of the month, and a late cancellation is argued over by text because the policy was never written down.

  • A franchise network has the same problems multiplied: each franchisee runs their own calendar and rate card, head office cannot see utilisation or complaint rates by area, and a cleaner who was removed from one franchise for a complaint turns up working for another.
  • Growth stalls because every new booking adds to the founder's phone rather than to a system.

Scope of the service

What the build covers

A custom cleaning booking build normally covers:

  • Cleaner onboarding With identity and right-to-work documents recorded as supplied and any check-provider result recorded as returned
  • A service area by postcode district
  • An instant-price engine with rates you set by property size Bedrooms and bathrooms, frequency, extras and area
  • A cleaner availability calendar With booking that assigns a cleaner directly, with no quoting step
  • Recurring plans at weekly Fortnightly or four-weekly intervals with a same-cleaner preference and a substitution rule when the preferred cleaner is unavailable
  • Key handling and access notes held against the property and shown only to the assigned cleaner
  • Check-in and check-out on site From the cleaner's phone with location recorded
  • Cancellation and rescheduling windows with fees you set
  • Payment captured at booking and held until check-out
  • Cleaner earnings statements per period
  • Reviews after each visit
  • A dispute route for short visits Damage and missed cleans

How discovery works

Discovery follows one recurring customer through a month with you: how price is built, whether customers choose a cleaner or just a slot, how substitution works when the regular cleaner is away, who holds keys and how that is recorded, what the cancellation window is and who absorbs the fee, how cleaners are engaged and how that affects when and how they are paid, and whether franchisees need their own view. Each answer becomes a named stage in the scope document: onboard, price, book, assign, visit, check-out, pay out, review.

Deliberately out of scope

  • Payroll and employment contracts for cleaners, cleaning product stock, and insurance claims handling. The platform records engagements, visits and payouts and connects to payroll where cleaners are employed

When the scope grows

Scoping scenario

A franchise network with twelve territories wants one platform where each franchisee sets rates within head-office bands, manages their own cleaners and calendar, and head office sees utilisation, complaints and cleaner removals across the network with a block on a removed cleaner rejoining elsewhere. That is a different build from a single-city operator with thirty self-employed cleaners, and the scope document says which one is being built.

Deliverables

What you receive

  • Discovery notes from following one recurring customer and one cleaner through a month
  • A written scope document naming each stage from onboarding to payout, with what is out of scope
  • Design of the instant-price and booking flow, the cleaner day view with check-in, the customer plan page and the operator calendar, on mobile for customers and cleaners and desktop for the office
  • The build, deployed to your hosting or ours
  • Migration of customers, recurring plans, cleaner records and key notes from your current calendar or spreadsheet, where relevant
  • Training for the office, dispatch and franchisee roles, with a short written guide for substitutions and cancellations
  • 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, your rate card, service area, current calendar and the cancellation and substitution rules you apply today.

    Project stage: Onboarding
  2. Planning

    Discovery with the founder, whoever dispatches cleaners and a cleaner who has worked with you for a while; the scope document, the employment and payout model and the milestone plan are agreed.

    Project stage: Planning
  3. Design

    Clickable designs of the price-and-book flow, the cleaner day view with check-in, the recurring plan page and the dispatch calendar, reviewed with two cleaners on their own phones.

    Project stage: Design
  4. Development

    Built in stages: cleaner onboarding and availability first, then pricing and booking, then recurring plans, keys and check-in, then payments, payouts, reviews and disputes.

    Project stage: Development
  5. Client review

    Your team runs a fortnight of real bookings alongside the old calendar, with cleaners checking in on site and the office handling two test substitutions.

    Project stage: Client review
  6. Revisions

    Rate bands, substitution rules, check-in tolerances and fee wording are adjusted from the review and re-checked against the scope.

    Project stage: Revisions
  7. Ready for launch

    Customers and plans migrated, payment capture and payout runs tested on accounts you control, reminders tested, checklist signed off.

    Project stage: Ready for launch
  8. Delivered

    Bookings and visits run on the new platform; 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 with capture-and-hold and split payout to cleaners
  • Identity, right-to-work and background check providers, recorded as a result and date
  • Payroll providers where cleaners are employed rather than self-employed
  • SMS, email and push notification providers for confirmations, on-the-way messages and reminders
  • Mapping and postcode services for service areas and check-in location
  • Accounting software for customer charges, fees, payouts and franchise royalties
  • Calendar feeds so cleaners see their visits on their own phone

How we would approach it

Worked example

Concept demo

A franchise network with head-office rate bands

The situation

A cleaning franchise with twelve territories wanted one platform instead of twelve calendars.

Why it is a custom build

This needs a custom build because the three-level structure of head office, franchisee and cleaner, and the royalty on released payments, are not something a single-operator booking script can be configured into.

The scope we would propose

  • Territories as sets of postcode districts, each with a franchisee role that sets rates within bands head office defines
  • Cleaners belonging to a territory with a network-wide record so a cleaner removed after a complaint cannot be onboarded elsewhere without head-office approval
  • Recurring plans with a same-cleaner preference and a substitution rule that offers the customer a named alternative before the visit
  • Check-in and check-out with location, feeding a visit-length report per cleaner
  • Customer payment captured at booking and released after check-out, with the franchise royalty calculated on the released amount
  • A head-office dashboard of utilisation, cancellation and complaint rates by territory

Pricing

What affects the price

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

  • Instant-price rules: size, frequency, extras, area and any time-of-day loading
  • Single operator or franchise network with territory-level roles
  • Self-employed cleaners with payouts versus employed cleaners with payroll export
  • Check-provider integration for cleaner onboarding
  • Recurring plans, substitution rules and same-cleaner preference
  • Payment holding, cancellation fees and the payment provider involved
  • Check-in with location and visit-length reporting
  • Volume of customers, plans and cleaner records to migrate
  • Native cleaner app alongside the mobile web platform
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

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

A single operator pricing by size and frequency, assigning self-employed cleaners from a calendar and paying out per period is usually covered by the cleaning booking platform package through configuration. A custom build is the honest answer for franchise networks, employed cleaners with payroll rules, or pricing that depends on a survey rather than a form. Discovery is where we tell you which.

How does the platform handle the keys?

Key location and access notes are recorded against the property and shown only to the cleaner assigned to each visit, with a log of who saw them. Physical key handover between cleaners is recorded as a step the office confirms. The platform records; it does not hold keys.

Are cleaners vetted by the platform?

No. The platform records identity and right-to-work documents as supplied by the cleaner and any result returned by a connected check provider, with dates, and your office decides whether to activate them. The platform never states that it has confirmed the suitability of any cleaner.

How are cleaners paid?

For self-employed cleaners, the platform holds the customer payment until check-out and releases the cleaner share in a payout run on your schedule, with an earnings statement per period. For employed cleaners, visit hours are exported to your payroll provider. Either way, the money your platform collects and pays out is yours and separate from what you pay us.

Who owns the platform afterwards?

You do. Source code and your data, including customer records, plans, visit logs and payout history, are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for cleaning bookings 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