No card asked for · nothing taken from a booking · your data exports
Base helps residential and commercial cleaning businesses qualify a site, agree the scope, obtain acceptance for a quote, create the job and schedule the right crew. A visit reserves all required team members and named resources together. Requests outside the service area stay requests, while an unavailable team leaves the visit unscheduled. Completion evidence and approved return work remain connected to the accepted scope.
The profile fits a small residential, villa, holiday-property, office or commercial cleaner that qualifies address and scope before committing a team. It supports service sites, versioned quotes, accepted jobs, one or repeated visits, finite visit plans, composite crew assignment, arrival and completion evidence, approved scope changes and return visits.
Quote, job and visit preserve the commercial decision and the field execution separately.
Staff record the customer site, check the service area and describe the approved rooms, area, frequency, extras and access needs. Restricted keys or access codes require appropriate protection and purpose-limited retention.
The estimator prepares labelled labour, area, room, extra, mandatory-fee and discount lines. The customer accepts a specific version. Until acceptance, the request cannot become authorised work, and a revised amount does not overwrite the earlier quote.
The accepted quote creates a job. One-off work receives its required visit; recurring work receives a versioned finite plan and generated future visits only through the configured horizon. Each occurrence remains individually reviewable.
Dispatch selects staff with the required skills and checks working hours, travel and turnover buffers plus any named vehicle or equipment. All required people and resources are reserved in one action. A collision leaves the visit unscheduled.
The assigned crew records arrival, the approved checklist and required completion evidence. A failed required upload cannot mark the visit complete. Approved scope changes or return work create linked records, so history is preserved instead of rewriting the original visit.
The workflow keeps the approved site and scope attached to every scheduled visit.
A postcode or map pin alone does not approve travel. Staff qualify the site against the business’s service zones and operating decision. An outside-area request remains visible for follow-up but cannot silently become a scheduled job.
Room, area, frequency, selected extras, access instructions and mandatory lines belong to a versioned quote. Acceptance fixes the working scope. A later change becomes an approved change order rather than an edited message that the assigned team never sees.
A repeated agreement produces a finite horizon of actual visits from a versioned plan. Each visit has its own crew, schedule and state. Conflicts are reported instead of being skipped inside an infinite recurrence.
The job owns the accepted scope; each visit owns a real field assignment.
Every required staff member and named vehicle or equipment must be available with working and travel buffers. Reservation happens in one transaction. If one member conflicts, nobody is partly assigned and the visit stays in the dispatch queue.
A repeated cleaning plan generates only a bounded horizon of visits. Changing frequency or scope creates a new version for future work without rewriting completed occurrences. Staff can see exceptions and unassigned dates explicitly.
A normal visit and two refusal paths show how the accepted scope remains protected.
Staff qualify the address, define the rooms and extras, issue a quote and record acceptance. The job generates a finite set of future visits. Dispatch assigns the complete crew, and each visit records arrival and evidence against the approved scope.
A customer submits an address beyond the company’s active zone. Base keeps the record as a request and refuses automatic job or visit creation. An authorised person may decline it or make a separate reviewed business decision.
The quote is accepted, but a required cleaner is already assigned during the travel buffer. Composite reservation fails and the visit remains unscheduled. Dispatch can choose a fully eligible team or another time without leaving a partial crew promise.
Field records support customer communication while keeping access data and staff decisions appropriately controlled.
Every quote version, acceptance, crew assignment, arrival, completion, change order and return visit keeps its actor and time. A later scope change does not alter what the original crew was asked to do or what evidence they supplied.
Addresses are collected for service delivery. Keys and access codes must be restricted, protected and deleted under purpose-based retention. Crew views should expose only their assigned visits and the operational minimum, not every customer record.
Define active service zones, cleaning services, scope templates, durations, price lines and reviewed access, cancellation, privacy and completion policies. Add staff skills, working hours, teams, vehicles or equipment only where they constrain delivery, plus realistic travel and turnover buffers. Configure quote approval, dispatch and crew permissions. Set a finite recurring generation horizon and required evidence rules, then validate imported sites, accepted quotes and future visits for missing scope or collisions.
The profile coordinates quoted field work without implying a marketplace or automatic dispatch intelligence.
Base is not a cleaning marketplace, payroll engine, route optimiser or chemical inventory. A site is the customer’s location, not a schedulable resource. The system does not accept out-of-area work automatically, and customer payment takes place outside Base.
Base does not generate leads, rank providers, pay crews, optimise routes or manage chemical inventory. Dispatch remains a staff decision based on released service zones, skills, schedules and buffers.
Immutable quote lines and external received, refund or deposit facts can be retained, but customer funds move outside Base. The product does not run checkout, payroll, bank reconciliation or settlement.
An out-of-area request stays a request, an unaccepted quote cannot create authorised work, and a crew conflict leaves the visit unscheduled. Required evidence failure also prevents completion. Each refusal preserves the last valid state.
A booking is not only a time — it is a person, a room and a machine, all of which can be busy. Booking the time and discovering the rest afterwards is how a day falls apart.
ExploreThe same person books four times and is typed in four times, each time slightly differently, and by the fourth nobody can tell whether they owe money.
Explore«Was last month better?» is answered from memory, and memory is generous.
Explore
Schedule intake, quotes, jobs and handback for Cyprus garages without claiming stock, accounting or payments. See the workflow and setup.
Run detailing requests as quote, job and handback work for shop or mobile vehicle care. See the workflow and setup.
Track device intake, diagnosis, quote, repair, parts evidence, warranty and handback. See the workflow and setup.
Base cleaning company software has a Free plan at €0 covering 2 staff accounts and 5 bookable items. Standard is €19 and Pro €39 a month per business, with no commission on jobs. As cleaning scheduling software it syncs both ways with Google and Microsoft calendars and sends notifications by email or Telegram, while customers pay you directly outside Base.
It keeps the enquiry visible but does not automatically create a job or visit outside the active service zone. Authorised staff decide whether to decline or review it separately.
Yes. A job is created from a specific accepted quote version. Revised scope or price requires a visible new version or change order rather than a silent edit.
Yes. All required eligible staff and named resources are reserved together. If any member conflicts, the complete visit remains unscheduled without a partial assignment.
A versioned plan generates a finite horizon of real visits. Each visit has its own schedule, crew and state, so exceptions remain visible and completed history is not rewritten.
No. Customer money and refunds remain outside Base. Accepted quote lines and factual external money events may be retained for operations.
Next step
Registration takes an email address. The operating model, services and resources are configured afterwards, in the console.