Nobody cancels. They skip twice — and then there’s no next visit on the board.
A bi-weekly client at ~$180 a visit is ~$4,700 a year and ~$14,000 over a three-year life. The sale that created her was one $180 event. Everything that decides whether the rest of it arrives happens after your pipeline is finished with her — in the recurring visit register, where no stage ever changes and no report ever runs.
Generic home-services software watches for things that happen: a form fill, a stage change, a payment. The most expensive event in this trade is a thing that doesn’t happen. Your build watches for the absence — and the first absence it watches for is a skipped visit with no next visit booked.
Her opportunity still reads Recurring Active. Nothing was cancelled, nothing was lost, no stage moved. The register simply stopped producing visits.
Three months, six scheduled visits, and the thing that cost you the client was a gap.
Every other trade’s churn has a moment you can point at. A declined quote. A lost bid. A job that got cancelled. Cleaning’s biggest loss has no moment at all.
A skip is not a rescheduling event — it is the first observable symptom of churn, which is why operators track skips as their own daily number rather than folding them into cancellations. The rung that matters is the second one: a skip where nobody put the next visit back on the board.
- Week 1Cleaned
Rated 5 out of 5. Same cleaner as always.
- Week 3Cleaned
Next visit already on the board when the crew left.
- Week 5Cleaned
Nothing to report. This is what a healthy register looks like.
- Week 7Skipped
She texted the office. The next visit is still scheduled, so this one is noise.
- Week 9Cleaned
Back on cycle.
- Week 11Skipped
Second skip inside 90 days — and this time nobody rebooked her.
- Week 13Nothing here
No visit. No cancellation. No stage change. No form fill. No webhook. The register just goes quiet.
Illustrative example. The dates and the rating are invented; the shape is not. A skipped visit with no next visit booked is the trade’s own leading indicator of attrition, and it is the one signal that leaves no record of itself. Without something watching for it, week thirteen looks identical to a quiet week.
The sale was $180. The client was ~$14,000.
In plumbing, roofing, paving, towing — revenue is opportunity flow. A won job is money in, and the pipeline is the business. Residential cleaning inverts that. A won client is an annuity you have not collected yet, and the great majority of her revenue arrives in a place a stage-shaped CRM never looks.
This is the number every stage report in a generic build is measuring, and it is roughly one percent of what she was worth.
None of which appears anywhere in the pipeline, because by then the opportunity has already been marked won and stopped moving.
The spread between a good month and a bad one is ~40% of the client
Published operator guidance puts the target below ~3% of recurring customers lost per month, with a sustained ~4–5% treated as the trigger for a retention plan; a parallel source publishes a ~1–4% band. At ~3% a month the average client life runs about ~33 months. At ~5% it runs about ~20. That difference is roughly ~40% of the lifetime revenue of every client on your book, and it does not appear in a single pipeline report ever run.
A downgrade is filed as a save and lands as a loss
Weekly to bi-weekly roughly halves a client’s annual value. It is recorded by the trade as a save, because she stayed — and it never appears as a loss anywhere. So the build records the previous frequency alongside the new one, stamps the change, logs the reason, and dates a re-upgrade touch 90 days out. The whole purpose of that workflow is to make an invisible revenue event visible.
Your cleaner is going to change, and that is a customer event
Technician turnover in this trade runs at roughly ~20–35% a year, which means a meaningful share of your clients will have their cleaner replaced in a normal year. Every operator frames same-cleaner as a preference and none of them guarantee it. So the answer is not to promise continuity — it is to make the handover invisible: the home’s preference notes live on the property, travel to whoever is assigned, and the client hears the substitute’s name from you before the visit, not from a stranger at the door.
A failed card reads to the client as the service ending
The quiet killer. A card expires, a charge fails, the visit stops, and nobody framed it as a billing problem — so she experiences it as the relationship ending. Dunning runs before the next visit for exactly that reason, with the pay link in the message.
Illustrative example. The ~$180 visit, ~$4,700 year and ~$14,000 three-year figures are one worked illustration of published pricing and retention ranges, not a projection for your business. Attrition, turnover and client-life figures are published industry benchmarks and vary by market, staffing and service mix.
What your build watches, once the pipeline has stopped watching.
Every active client is a standing arrangement — a property, a frequency, a day in the cycle, an assigned cleaner, an access method and a rate — generating dated visits forward. Nothing moves through stages. It is worked entirely off whether the visits actually happen.
Operators track skips as a daily number in their own right, at roughly ~0–2 per branch per day, and treat that number as the attrition figure arriving 30–90 days early. The named remedies — automated reminders, a communicated skip and lockout policy, waitlist backfill, rerouting, weekly trend review — are five automations wearing a trench coat. Here they are.
- 01 A visit is skippedNoise, until it isn’t Logs the reason, adds to the 90-day skip count on her file, and checks exactly one thing: is there still a next visit on the board. If there is, nothing else happens. One skip is not a churn event and treating it like one trains your office to ignore the alert that matters.
- 02 A skip with no next visit bookedThe real churn event Stamps the file, moves the opportunity from Recurring Active to At Risk, and tasks the owner the same day. She has silently exited the register. Nothing in a stage report will ever say so, which is precisely why this rung exists.
- 03 Two consecutive skipsPre-churn A human phone call, not a text, and the offer on that call is a frequency change — a save, deliberately, because a monthly client is worth far more than a former one. The build makes the call happen; it does not try to make it.
- 04 A lockout — the crew arrived and could not get inUsually a changed code, not a changed mind Charges per your policy, and — the part nobody builds — opens a review of the access method, the entry code and the alarm notes at the same time. Operators disclaim false-alarm charges arising from code changes they were not told about, which only works if the record holds the current code and knows when it changed.
- 05 A frequency downgradeThe loss that is filed as a win Fires when frequency moves down from the previous one. Records both, logs the reason, and dates a re-upgrade touch 90 days out. Weekly to bi-weekly roughly halves her annual value and shows up in no report as anything but a retained customer.
- 06 A cancelled visit not rebooked in 14 daysChurn in progress Starts the reactivation sequence. The 14-day window is a setting on your account, not a hard-coded number — it ships at 14 days because that is what the ladder was designed against, and you can move it once you have your own history to check it with.
- 07 A payment failure on the card on fileThe quiet killer Dunning runs before the next visit, carrying the pay link, because a failed card that stops a visit reads to the client as the service ending rather than as a billing problem. Chasing it after the missed visit is chasing a client who already thinks she left.
- 08 The register goes quiet entirelyLapse, then win-back Walks the opportunity Recurring Active to At Risk to Lapsed, opens the win-back sequence, and marks Won Back when it works. A lapse is also a key-return event — see the custody rail below, which is where the dangerous half of this lives.
Five of those eight fire on something that did not happen
No form was filled. No stage was moved. No webhook arrived. That is the whole design argument for this build, and it is the reason a snapshot assembled out of appointment reminders cannot be retrofitted into it. We looked at what the best cleaning packages on the market actually ship: the strongest of them offers customer-controlled skip, pause and reschedule — which is a button for the customer, not a watch on the absence.
- Skipped, with nothing rebooked
- Two skips in a row
- A frequency quietly stepped down
- A cancellation that never came back
- A register that simply stops
Deals in this lane almost never die at the quote. They die at visit one.
The first clean is priced differently on purpose — a ~20–30% premium over the recurring rate, or sold outright as a deep clean at ~1.5–2× standard. It is also where the home’s real condition is discovered, where your quote gets tested against actual hours, and where the client decides whether any of the next three years happens.
Visit two goes on the calendar before the crew leaves visit one
A booking that reaches First Clean Completed with no next service date is an exception queue item, not a normal state. The build refuses to advance it to Recurring Active until that date exists. This single gate is the boundary between a $180 sale and a multi-year client, and it is the strongest defensible default anywhere in the residential lane.
A first clean that ran long gets re-priced before visit two, not after visit twelve
Time-over-budget is a named mid-cycle adjustment trigger, and the moment to act on it is before the recurring rate is locked in. The build re-opens the quoted amount at that point rather than letting three years of visits run at a rate you set from a photo and a square-footage guess.
Satisfaction is asked after every visit, and it routes two ways
A one-to-five ask after every visit — not just the first. The same score is the client’s retention signal and the cleaner’s performance record, and that dual routing is the design point. A drifting score on one client is a save; the same drift across one cleaner’s route is a training conversation.
A re-clean opens a job, not a complaint ticket
The guarantee window in this trade is short — published practice is issues raised by the end of the next business day. Yours ships at 24 hours and is a setting. A request opens a re-clean job flagged against the original visit and the original cleaner, and it suppresses the review request and every upsell while it is open. Asking for five stars from someone waiting on a re-clean is how a fixable problem becomes a public one.
The review request is gated hard, and it waits two hours
It never fires while a re-clean or a complaint is open, never on an at-risk client, never on a do-not-contact, and never on a commercial account in a no-contact evaluation period. The two-hour delay after completion is a setting, and the link is yours.
The referral ask is weighted toward the route
Referral is the natural growth motion in a route business, because a referral from an existing client is usually already on the existing route — it costs less to serve and it densifies the day. So the ask fires at the point of a five-out-of-five rating and leans on neighbors. The reward wording is a setting; it ships reading “$100 for you, $100 off for them — paid when their job books.”
Your buyer is not being persuaded. She is filling in a form and getting a number.
Residential cleaning closes something like ~50–70% of quotes for recurring service. Compare that with the demand lane in plumbing at roughly ~35–45%. A close rate that high means the decision is a configuration decision, not a persuasion decision — so the job of the software at this stage is to remove friction, not to nurture.
Which is why your residential board opens Inquiry to Instant Quote Given to Booked — First Clean, with no estimate-visit calendar anywhere in it. A pack that ships an estimate-sent and estimate-follow-up stage pair as the residential default is modeling a painting contractor, not a maid service.
The quote is a formula, so it ships as one
Square footage, bedrooms, bathrooms, service type, frequency. Every published residential pricing model in this trade reduces to a base plus a bathroom add-on, times a clean-type multiplier, less a frequency discount, plus extras. That input set is not a wish list — it is the literal argument list of the price, so those fields are mandatory on the intake and they arrive on the file already filled in.
Card on file is taken at booking, before service
This is an intake requirement rather than a billing preference. It is what makes a lockout or late-cancel policy enforceable at all, and operators read hesitation about providing it upfront as a screening signal in its own right. No card, no confirmed booking.
Speed, then a short window, then stop
Published operator guidance is estimates out within ~2 hours, and the Harvard Business Review’s classic finding is that contacting a lead inside the first hour makes it roughly ~7× more likely to qualify. Your abandoned-quote sequence runs at the price, two hours later, day one, day three and day seven, then closes out at day ten. Anything past that in this lane is spend without return — the household either booked someone or gave up on the idea.
It recovers the configuration, not a PDF
A self-serve quote that did not book is a booking abandonment, not a proposal that needs nurturing. She priced the job and did not click book. So the asset the follow-up carries is her saved configuration and a one-click booking link, and it stops the moment she replies or books.
Frequency is shown as annual money, never as a percent off
Published spreads run around ~10–20% off one-time for weekly, ~5–15% for bi-weekly and ~0–10% for monthly — but presenting that as a discount undersells what it is. The quote shows weekly, bi-weekly and monthly side by side with the annual figure attached, because the frequency chosen at quote time is the single largest determinant of the client’s lifetime value.
Move-out is a separate lane because the date is not the buyer’s
The clean has to land after the home is empty and before the landlord walkthrough, the closing or the new tenant. The payer is frequently not the occupant — a tenant, a landlord, a property manager, a realtor — with a security deposit or a closing actually at stake. So it opens on its own board, books against its own calendar, and the recurring-conversion pitch is suppressed at that payer entirely.
A $180 bi-weekly booking and a 40,000 square-foot office are not the same business.
One closes in an online form in under three minutes. The other closes over four to ten weeks through a walkthrough, a workload calculation, a bid, a procurement scorecard and a signed contract. Same word on the truck. Different company. Forcing both through one stage vocabulary is the error that produces a cleaning snapshot in which “quote sent” means four minutes in one lane and four weeks in the other.
These are the actual stage names on the actual boards, in the order they appear.
Residential Recurring
Minutes to days · then it exits into the register- Inquiry
- Instant Quote Given
- Booked — First Clean
- First Clean Completed
- Recurring Active
- At Risk
- Lapsed
- Won Back
- Lost
One-Off / Move-Out / Deep
Days · a hard date somebody else set- Inquiry
- Quoted
- Scheduled
- Completed
- Invoiced
- Paid
- Converted to Recurring
Commercial Janitorial
Weeks to months · every stage produces an artifact- Target
- Walkthrough (10-section checklist)
- Workloaded
- Bid Submitted
- RFP Evaluation
- Awarded
- Contract Signed (COI + vendor packet)
- Active
- Quality Inspection
- Renewal Window
- Lost
Why At Risk and Lapsed are stages at all
Because the register needs somewhere to put a client who has not left and has not stayed. Most builds have a won column and a lost column and nothing in between, which forces the most valuable client on your book — the one who is quietly drifting — to be filed as a success right up until the day she is filed as a loss. These two stages are where the ladder above writes its findings, and Won Back is where it books the recovery.
Five calendars, because a first clean is not a maintenance visit
Cleaning schedules are routes. The constraint is drive time and crew day capacity, not the customer’s availability — the software is not finding a slot she likes, it is finding a slot near other work that she can accept. So confirmations carry an arrival window rather than an arrival time, and the durations are set to what the work actually takes.
Longer than a maintenance visit by design. This is the visit that sets the preference notes and the access record.
Generated from the frequency and the assigned cleaner. The client is usually not home, so the reminder’s job is access integrity, not attendance.
The hard-deadline lane, tied to closings and lease ends.
Runs the ten-section checklist that feeds the workload calculation.
A scored, per-site inspection with a trend — deliberately not a post-visit satisfaction text.
Sending a “how did we do?” text after a nightly janitorial visit is the tell.
It is the clearest possible evidence that a residential snapshot was relabeled and sold as a commercial one. Commercial quality is a scheduled inspection with a score and a trend, per site. So the residential post-visit machinery is structurally excluded from this lane — it cannot fire on a commercial account even by accident.
The bid is a calculation, and the proposal shows the math
Hours come from area divided by production rate, summed across zones, times visits per month — ~21.7 for five nights a week — times fully loaded labor, plus overhead and profit. The published trade-body rate tables run roughly ~3,500–5,000 square feet per cleaner-hour for general office and ~800–1,200 for restrooms, which is why restrooms are also commonly priced by fixture count. Your board will not open Bid Submitted until the production rate and the workloaded hours are on the record. In a lane where the buyer is comparing three bids on a spreadsheet, a measurable baseline is the competitive posture.
The walkthrough is a data-capture exercise with a published checklist
Ten sections: the account and estimator, the building profile, a zone-by-zone table with square footage, area type, soil level and requested frequency, restroom and kitchen fixture counts, floor types and conditions, the client’s own top three complaints, access and security and logistics, per-zone service-level options, exclusions and quoted-separately items, and your internal pricing notes. Ninety minutes on the calendar, and every field feeds the number.
During an evaluation period, everything goes silent
Requests for proposal come with hard procurement gates — a mandatory pre-bid walkthrough, a written-question deadline, a submission deadline with a specified delivery method, and a no-contact evaluation window. Responses that ignore the instructions can be ruled non-responsive and never scored at all. So marking an account RFP Evaluation suppresses all outbound — the bid cadence, the review ask, every broadcast. This is the one suppression in the build whose failure mode is losing the contract outright, with no error message anywhere.
Losing on price is a dated task, not a dead record
The published operator posture on losing to a lowball is explicitly not to match it. Underbid janitorial contracts fail on service, and the incumbent’s first quality complaint is your re-entry point — so every price loss sets a re-approach task six months out instead of disappearing into a closed-lost column. It is the highest-intent re-quote signal in the lane.
The periodic work is where the margin lives, and it gets scheduled
Strip and wax, carpet extraction, high dusting, interior glass — quoted separately, recurring monthly, quarterly or annually, and the highest-margin work on the contract. It belongs on the register as dated obligations that get proactively scheduled and re-quoted, not waited for. A scope change at an existing site is a mandatory re-price; the standard contract language requires written agreement on a revised fee before the change takes effect.
A downward inspection trend moves the account before the renewal does
Inspections are scored per site because standards drift as you add sites, and the scores are the contract’s own evidence — the audit trail behind a quarterly review. A falling trend pulls the account toward Renewal Window early and flags it at risk, which is the difference between arriving at a renewal conversation with a case and arriving at it with an apology.
And the clock that renews the contract whether or not anybody looked
Contract terms in this lane run 12 to 36 months with termination for convenience on ~30 to ~60 days’ written notice. That notice date is a computed date on the record, derived from the term and the notice window, with a reminder on it — because a contract that auto-renews for another year because nobody watched the window is a real outcome in both directions.
- Inspection-score reviewThe case you will argue withT-120
- Renewal and price-review conversationRoutine adjustments run ~3–8% a yearT-90
- Notice-window alertComputed, not rememberedT-60
- Last callBefore it renews itselfT-30
The four-rung ladder is our design; the two numbers it is pinned to — the ~30 to ~60 day notice window and the 12 to 36 month term — are the published contract conventions in this trade. The annual rate-review band is published for the commercial lane; residential has no published percentage, so the notice window there is a setting you fill in rather than a number we ship.
You are the only trade here whose crew lets itself into an empty house.
That makes the access record a custody and liability artifact rather than a scheduling note, and it is the part of this vertical where a stock CRM has nothing at all. These four rails ship switched on.
Keys tagged without the address on them, checked out per technician, never duplicated, a loss reported within hours. The build holds the tag identifier, who has it and whether it came back. The half nobody models: offboarding a client is a key-return event, and offboarding a cleaner is a key-return checklist. A lapsed client whose key is still in your safe is an open operational exposure with no contract behind it — so the flag persists and escalates until the key is marked returned. That is an operational characterization, not a legal one.
A snapshot that asks about pets but not cameras is asking the easy half of the same question. The client discloses whether there are indoor cameras and whether they record audio, and the assigned cleaner is told. Consent rules for audio recording vary from state to state and some states require all parties to consent — we ship the disclosure enabled because it costs nothing and it is good practice on its own terms. This is our configuration choice, not legal advice, and your own state’s rule is something to confirm with your own counsel.
No workflow, notification, transcript, review request or broadcast renders an access code or an alarm-disarm note. The on-my-way text names the cleaner who is coming; it never names the code. A unique code for your company, distinct from the family’s own, rotated periodically and revoked at service end — the method matters less than who holds it, and it should sit with your office rather than with an individual cleaner.
Do-not-contact, stop-nurture, an open re-clean or complaint, a bad-fit flag, and a commercial account inside a no-contact evaluation window — all honored in one place that every send has to clear. Rails built into individual workflows get forgotten when the fortieth workflow is added. This one is structural, which is the only way it survives.
The follow-up you keep meaning to build.
Written for this trade specifically, not renamed from a home-services template. Every interval below is a setting on your account rather than a number welded into a workflow.
Five intakes, because the first sentence differs
A web quote, a phone call or a maps listing, a referral by name, a move-out with a deadline, and a commercial walkthrough request. Same inbox, five different opening messages, and the commercial one never touches the residential quote configurator.
Missed-call text-back
Fires on a missed inbound and swaps to your after-hours wording outside office hours. Table stakes, and cheap, and the reason a two-truck operation stops losing calls it never knew it got.
The first-clean confirmation that is really an access reminder
The day-before message restates the access method, confirms the pets will be contained, and asks her to confirm nothing about entry has changed. That last question is the one that prevents a lockout.
Recurring visit reminders with an arrival window
Not an arrival time — a window, because the schedule is a route. She is usually not home, so the reminder’s real job is access integrity rather than attendance.
The on-my-way text that names the cleaner
Doubles as the lockout reducer and as how a client learns a substitute is coming. It names the person; it never names the code.
The cleaner-changed notice, sent before the visit
The workflow no stock system models. A change of assigned cleaner is a customer-lifecycle event, so it fires a client-facing notice naming the substitute and stating that the home’s preferences were handed over — which is true, because those notes live on the property rather than on the person.
Same-day cleaner absence, fanned across the route
A cleaner calling out at 6am on a six-stop route is the most common operational emergency in this trade. Every stop needs a decision and a notification. The decision stays yours; the notifications go out in one send, and each affected client is stamped so the continuity record stays honest.
The ten-day quote abandonment, with its stop conditions
At the price, two hours later, day one, day three, day seven, closed out at day ten — and it stops instantly on a reply or a booking. It carries her saved configuration and a one-click booking link, not a PDF.
The frequency comparison, priced annually
Weekly, bi-weekly and monthly side by side with the annual figure attached, presented as recurrence rather than as a discount. This is the single highest-leverage message in the residential lane.
The commercial bid follow-up on published day numbers
Four touches over roughly ten to twenty-one days: confirm receipt and invite questions, then add something of value, then surface the blocker, then a graceful close-out that asks for a yes, a no, or a pause. Each touch has to bring something new. Suppressed entirely inside an evaluation window.
Bid expiry, then a re-quote — never a quiet re-send
Bids age out at 30 days and re-quote rather than silently selling at last quarter’s labor rate. In this trade the honest driver is wage movement, not material volatility, and saying so is a better conversation than a price surprise.
A six-month re-approach on every price loss
You lost to a number, not to a company. The task is dated, it carries what you bid and what they took, and it lands about the time the incumbent’s first quality complaint does.
The visit-two gate and the over-hours re-price
No advance to recurring without a next visit on the calendar, and a first clean that ran materially over its quoted hours re-opens the price before the recurring rate locks. Two workflows, and between them they are the difference between a sale and an annuity.
One-off to recurring, suppressed where it should be
A paid deep clean is a conversion opportunity. A move-out paid for by a landlord and a short-term-rental turnover are not — so the conversion pitch is suppressed at those payers rather than fired at everyone and apologized for later.
The slow clocks
An annual rate-review notice with advance warning and a reason, suppressed while any quality issue is open. Client anniversaries and visit milestones at one, five, twenty-five and fifty. A ninety-day reactivation that treats a lapsed recurring client, an unconverted one-off and a closed-lost commercial prospect as three different conversations. And a deliberately thin seasonal calendar, because nobody has published cleaning seasonality with numbers and we would rather ship the shape than invent the figures.
Built against the trade, not against a template.
automations written for cleaning specifically — intake, visit lifecycle, quote follow-up, the register ladder, the commercial lane and the compliance rails.
named stages across three boards, because a bi-weekly booking, a move-out and a janitorial contract are three different businesses.
calendars with real durations — four hours for a first clean, two and a half for a maintenance visit, five for a deep or move-out.
rungs on the register ladder. Five of them fire on something that did not happen.
of a client’s lifetime revenue sits in the gap between a ~3% and a ~5% monthly attrition rate — and none of it shows up in a pipeline report.
Stage, calendar and automation counts are what ships in your account. The attrition, turnover, close-rate, production-rate and pricing figures on this page are published industry benchmarks and trade-body guidance collected in our own cleaning operations research (2026), presented as ranges because that is how they were published. They describe the trade, not a result we are offering you.
Your first thirty days.
- Days 1–3
Your boards exist before you log in
All three, all 27 stages, five calendars with the durations already set, and the fields the quote formula needs. You are not handed an empty pipeline and a video about how to build one.
- Days 3–7
Intake goes live, size and frequency first
The instant-quote form, the commercial walkthrough request and the move-out lane, each landing on the right board with the right first message. Missed-call text-back switched on the same day.
- Week 2
The things we need from you
Your service area and office hours, your review link, your rate card and frequency spreads, your skip and lockout policy, your re-clean window, and your key-and-code handling so the custody rail matches how you actually run. Half an hour of answers, and it is the half hour the whole build is calibrated on.
- Week 3
Payments connected
Square processing, dual-priced invoicing, card on file captured at booking, and the deposit line wired for the deep and move-out lane. The deposit product ships at zero cents on purpose — it is always computed from your deposit percentage against the quoted amount, so no literal price can ever be quietly wrong.
- Week 4
The register starts watching
Every active client on a frequency with a next visit date, the skip counter running, the ladder armed, and the commercial notice dates computed from each contract’s own term and notice window. From here the most valuable thing your software does is notice when nothing happened.
Every automation ends at a payment. So we own that part too.
Follow-up that ends in “I’ll send an invoice” is half a system. Your account runs on Square for processing, with dual-priced invoicing on top: the cash price is the price, and a customer paying by card sees the card price beside it and chooses.
Card on file is the entry gate, not a convenience
Taken at booking, before the first visit. It is what makes your skip and lockout policy enforceable at all, it is what lets the recurring charge run without a phone call, and it is the reason a payment failure can be caught before it turns into a missed visit.
The deposit ships at zero, deliberately
Deep cleans, move-outs and post-construction all take a deposit, and every operator takes a different one. So the deposit line carries no literal price — it is always computed from your deposit percentage against the quoted amount, with a payment schedule that overrides it when a job needs one.
Dunning that runs before the visit, not after it
A failed card is caught, texted with a pay link and resolved before the crew would have arrived. The alternative is a client who experiences a billing failure as the service ending and never tells you which one it was.
Dual pricing on volume you already run
Recurring charges, deposits and one-off invoices are steady card volume at roughly ~3%. Every invoice and pay link carries the cash price with the derived card price shown beside it, and the customer chooses every time. Nobody is surcharged in the dark.
Two plans. Month to month.
Everything above is included in both — all three boards, the register ladder, the custody and camera rails, the commercial lane, the payment rails. The difference is how much marketing and reporting surface you want on top.
- CRM and all three pipelines
- Unified inbox — text, email, chat
- Five calendars and online booking
- Website and funnels
- Forms and surveys — the instant-quote and walkthrough-request forms
- AI lead follow-up
- Payments and invoicing
- Everything in Starter
- Full marketing suite
- Reputation management — the review request with its suppression rules
- Social planner
- Memberships and recurring billing — the recurring plans
- Documents and contracts — e-signed commercial agreements
- Advanced reporting — skips, attrition and inspection trends
- Priority support
Fair questions.
Half my clients leave a check on the counter. Dual pricing will scare them off.
Dual pricing is built for exactly that base. The cash price is their price — nothing about a check or cash client’s experience changes. The card price is derived and shown beside it, and the customer chooses every time. In a trade where a large slice of the book already pays the cash price by habit, this is the easy case rather than the hard one.
I already schedule and route in software built for maid services. I’m not ripping it out.
Don’t. Your field software stays the operations source of truth for routing, dispatch and job costing — that split is the documented best practice in this industry. What moves is the marketing and follow-up layer, and who processes the cards. The register ladder reads the visit outcomes; it does not try to become your scheduler.
All my recurring clients are on stored cards with my current processor. Re-authorizing every one sounds brutal.
Honest answer: saved cards do not transfer between processors. Every recurring client will need to re-authorize, and in a card-on-file trade you should plan for that rather than discover it. Two things make it manageable. Payment links make re-capture a text and under a minute, and the annual rate-review notice gives you a natural window to fold it into — one touch that confirms the card and the new rate together, rather than a campaign about switching processors.
It’s me and one other cleaner and forty houses. This is built for a franchise.
It is built for exactly the opposite. A franchise has a branch manager whose job is to look at the skip report every morning. At forty houses you are cleaning, quoting and answering the phone, and the client who skipped twice is the one thing you have no spare attention for. The register is the part of this that does not scale down — which is why it is the part worth automating first.
Why not stay on the processor I’ve got?
Two concrete reasons. Dual pricing exists on the Square path — on most other processors the card cost simply leaves the building with no mechanism to hand any of it back. And Square adds things that matter in a trade with a truck and a counter: card-present hardware and next-day deposits, which is a real difference when your payroll runs weekly and your recurring charges land on a cycle.
Is this a generic CRM with a cleaning sticker on it?
Ask it three questions. Does it have a stage for a client who has not left and has not stayed? Does anything in it fire when a visit simply did not happen? Does it know that a nightly janitorial account must never receive a “how did we do?” text? We reviewed what the strongest cleaning packages on the market publish: the best of them ships customer-controlled skip and pause, and none of them ships anything that watches for a non-event. That gap is why this build exists.
The client you lose next quarter has already skipped once.
Board now and the boards are built, the intake is live, and the register is watching every active client on your book — instead of starting to watch on the day you finally notice the revenue is down and cannot say who left.
Automate With Us provides software and configuration services. Figures shown are published industry research or illustrative examples — they are not projections, guarantees, or representations of the results you should expect. Individual results depend on your market, pricing, staffing and execution. Attrition, retention, technician-turnover, close-rate, production-rate and frequency-discount figures are published ranges that vary by market, service mix and season, and the client-value illustration is one worked example, not a forecast. Processing costs vary by card mix and volume; the ~3% figure is illustrative and your effective rate will differ. Payment processing is provided through Square and is subject to Square’s approval and terms. Text-message and email sending are subject to carrier and regulatory registration. The key-custody, entry-code and indoor-camera disclosure practices described here are our own conservative configuration choices drawn from published operator practice; they are not legal advice and not a statement of what any statute or jurisdiction requires. Consent rules for audio recording differ from state to state — confirm your own with your own counsel. Insurance, bonding and vendor-packet requirements referenced here are contract terms set by your commercial clients, not statutory minimums. Nothing here is a representation by us about your employees, their screening, or their insurance — those are yours to make and yours to stand behind. Terms · Privacy