Service

Cleaning company software development

For owners and managers of domestic and commercial cleaning companies who need a system built around recurring visits, cleaner continuity, keys, checklists and the inspections that keep a contract.

The problem

What goes wrong today

Where it usually starts

A cleaning company does not sell jobs; it sells the same two hours every Tuesday with the same person.

  • The whole operation is a repeating pattern, and most software treats each visit as a fresh booking.
  • The manager keeps the pattern in a spreadsheet with a tab per cleaner, and every holiday, sickness or new customer means re-cutting that spreadsheet by hand.
  • When a customer texts on Monday night to skip this week, the message reaches the cleaner or the office but rarely both, and the cleaner either turns up to an empty house or the slot goes unfilled when another customer would have taken it.

Where it gets harder

Keys are a constant worry.

  • Who holds the key for the flat on the high street this week, and did it move when the regular cleaner went on leave?
  • Checklists are laminated cards that are never updated, so the office has no proof that the oven was done.
  • Commercial contracts require a visit log and a quality score the client can see, and the supervisor's inspection is a photo on a phone and a thumbs-up in a group chat.
  • Supplies disappear from the store cupboard with no record of which site they went to, and the manager finds out at the month end when the invoice from the supplier arrives.

Scope of the service

What the build covers

A custom cleaning company build covers the shared trade core where it applies:

  • A service area by postcode district or radius
  • A quote request with property details and photos
  • Job records that move through quoted Booked, in progress, complete and invoiced
  • Cleaner scheduling with travel buffers between properties
  • Quotes and invoices with line items and deposits approved online
  • A review request after a first clean. The remaining core Such as before and after photos, becomes part of the checklist rather than a separate step

The cleaning-specific layer is the recurring schedule. A customer has a pattern, weekly or fortnightly, a preferred window and a preferred cleaner; the schedule generates visits from that pattern and keeps the same cleaner unless the roster says otherwise. Rosters hold each cleaner's hours, skills such as end-of-tenancy or carpet work, and the keys they currently hold, with key handover recorded when a cover cleaner takes a property. Checklists are defined per property type and completed on site on a phone, with photos where the item needs one. Supervisors record quality inspections with scores against the checklist. Commercial contracts group sites under a client with a visit log and inspection history the client can see. Supplies are tracked from the store to the site. Customers reschedule or skip a visit within rules you set, such as notice periods and the number of skips allowed per month.

Deliberately out of scope

  • Payroll and timesheet export beyond recording visit hours, vehicle tracking, and employment compliance checks on cleaners, which the business handles through its own procedures

When the scope grows

Scoping scenario

A company with thirty-five cleaners serves two hundred domestic customers on weekly and fortnightly patterns and nine commercial contracts covering twenty sites with evening visits, and wants cover for sickness to be proposed by skill and area with key handover tracked. A two-person domestic cleaning business.

That needs

  • The pattern
  • The skip rules
  • A simple checklist
  • The scope document names which build is being made

Deliverables

What you receive

  • Discovery notes from a walk-through of a domestic week and a commercial contract month
  • A scope document naming each schedule, visit and inspection stage and what stays outside the system
  • Design of the recurring schedule view, the cleaner phone checklist, the inspection form and the client visit log
  • The build, deployed to your hosting or hosting we manage
  • Migration of customers, patterns, cleaner rosters and contract records from spreadsheets or an existing app where relevant
  • Training for the manager, supervisors and cleaners, with a written guide
  • Handover material and 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 to your scheduling spreadsheet, checklists, contract documents and the list of cleaners, keys and sites, with one named contact.

    Project stage: Onboarding
  2. Planning

    Discovery with the manager and a supervisor; the pattern model, cover rules, checklist types and skip rules are agreed in the scope document.

    Project stage: Planning
  3. Design

    Clickable designs of the week view by cleaner, the checklist on the phones your cleaners use and the client visit log.

    Project stage: Design
  4. Development

    Customers, patterns and visit generation first; then rosters, keys and cover; then checklists, inspections, contracts and supplies.

    Project stage: Development
  5. Client review

    Your team runs a test fortnight alongside the spreadsheet, including a sickness cover and a skipped visit, and reports where it does not match reality.

    Project stage: Client review
  6. Revisions

    Findings are corrected and re-checked against the scope document.

    Project stage: Revisions
  7. Ready for launch

    Patterns and rosters imported, visit messages tested against numbers you control, key register reconciled, launch list signed.

    Project stage: Ready for launch
  8. Delivered

    The schedule runs in the new system; hosting and maintenance continue under their own agreement if chosen.

    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 and direct debit providers for recurring domestic payments and contract invoices
  • SMS and email providers for visit reminders, cleaner-on-the-way messages and skip confirmations
  • Accounting software for invoices, contract billing and payments
  • Payroll or timesheet systems that take recorded visit hours
  • Mapping services for travel buffers and cover proposals by area
  • Calendar feeds so cleaners see their week on their own phone

How we would approach it

Worked example

Concept demo

A thirty-five-cleaner company mixing domestic patterns and evening commercial contracts

The situation

A cleaning company re-cut a spreadsheet by hand every time a cleaner was ill and had no record of where keys were.

Why it is a custom build

The cover proposal that respects key-holding is what makes this a custom build; general scheduling tools can move a visit but have no idea who can get through the door.

The scope we would propose

  • Customer patterns generating visits weeks ahead with the regular cleaner held unless the roster changes
  • A cover proposal when a cleaner is marked absent, ranked by skill, area and existing key access, with the key handover recorded when the cover accepts
  • A checklist per property type completed on the phone with photos for items the client cares about
  • Supervisor inspections scored against that checklist
  • A client login for each commercial contract showing the visit log and inspection scores for their sites

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 cleaners, supervisors and whether evening commercial shifts are run
  • Number of domestic patterns and commercial sites to import
  • Cover rules by skill, area and key-holding and how proposals are ranked
  • Checklist types, photo requirements and inspection scoring
  • Commercial client logins with visit logs and inspection history
  • Supplies tracking from store to site
  • Recurring payment or direct debit provider and invoicing cycles
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

How do you decide between a custom build and the package?

If your patterns, rosters, checklists and contracts fit the way the cleaning company package works with configuration, we quote for the package and say so. Custom work is the honest route when cover must follow particular rules, when a payroll or franchise system must be connected or when commercial clients need reporting beyond the visit log. Discovery is where we tell you which.

Can the system keep the same cleaner for each customer?

Yes. The pattern holds a regular cleaner and the schedule keeps them unless the roster marks them absent, in which case a cover is proposed and the customer can be told who is coming.

How is key-holding tracked?

Each property key is assigned to a cleaner or to the office, and every handover is recorded with who, when and why. A cover proposal shows whether the cover cleaner already has access or a handover is needed.

Can customers skip or move a visit themselves?

Within the rules you set: notice period, number of skips allowed in a period and whether a skipped visit is still charged. The customer does it from their login or a link in the reminder, and both the cleaner and the office see the change.

Who owns the system afterwards?

You do. Source code and data are handed over at delivery, and hosting and maintenance are optional and separately agreed.

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