A recurring window cleaning business runs on a chain that software either keeps intact or quietly drops: the frequency a customer agreed to, the property and the access it needs, the route day the stop sits on, the price for that visit, what happened last time, and the billing relationship the account sits under. This page is a requirements guide rather than a product ranking. It sets out the records that chain depends on, the exceptions that break it, and the behaviours to test in a demo or a trial. Evidence-backed product comparisons are linked here once they meet our publication requirements.
- Written for
- Window cleaning businesses from owner-operator to small crews: recurring residential routes, one-off residential work, recurring commercial accounts, and mixed models.
- Market
- United States and Canada. Payment methods, tax handling and product availability vary by country and by payment processor.
- Not covered here
- Product rankings, named recommendations and prices. Cleaning method, equipment, access safety and licensing.
Quick decision summary
The rest of this page turns each of those into checks you can run yourself.
Who this guide is for
Software requirements in this trade follow the operating model more closely than the size of the business. A solo operator working a dense residential cycle can need deeper recurrence and exception handling than a larger business selling one-off commercial work.
Recurring route operators. The schedule is built from stops that repeat: a four-week cycle, an eight-week cycle, a quarterly visit. Work is priced once and repeats at that price until something changes. The software questions are about grouping stops, recurrence rules, per-stop pricing, and what happens when a visit does not go to plan.
One-off residential operators. Work is sold job by job, often after a site visit or a photo. Repeat business is a reminder rather than a booked commitment. The software questions are about quote speed and consistency, scheduling, and converting a satisfied one-off customer into a booked repeat without rebuilding the customer record by hand.
Commercial account operators. The customer is an account rather than a household: a property management company, a retail group, a building owner. One account can hold several properties, each with its own stops, frequencies and prices, and the money sits at account level under agreed terms. The software questions are about account structure, consolidated documents, contract records, and whether stop-level history survives under a single payer.
Mixed models. Many window cleaning businesses carry two patterns at once: a recurring base and a stream of one-off work, sometimes for the same customer. The requirement is that the two coexist in one record without either overwriting the other. An out-of-cycle job added to a recurring account should reach the invoice without changing the recurring price or the next due date.
If your decision is about cleaning method, water-fed poles, ladders, access equipment or licensing, this is the wrong page. This one covers business software.
The recurring chain the software has to keep connected
Three words get used interchangeably in this trade and in software marketing. Separating them makes a demo much easier to run, because a product can be strong at one and weak at another.
Route is a group of stops worked together: by geography, by day of the week, by crew. It is a travel and capacity concept.
Recurrence is the rule that brings a stop back: a four-week cycle, a two-month cycle, twice a year. A stop can recur without belonging to a fixed route, and one route can hold stops on different cycles.
Billing cadence is when the money event happens: an invoice per visit, a monthly charge regardless of visit count, payment in advance, or a statement issued on account terms after a period closes. Billing cadence can be independent of both the route and the recurrence.
Tighter routes can reduce unpaid drive time and increase the service capacity available in a working day. Capacity is one input to revenue; job value, pricing and margin still decide what that capacity is worth.
- Account or customer
- Property and access
- Stop, price and frequency
- Route or service day
- Scheduled visit
- Completion and exceptions
- Billing event
- Next service date
Each arrow in that chain is a handoff, and a handoff is where a record either carries forward or gets retyped. Some businesses invoice at completion, some pre-bill, some batch bill monthly, some hold work for review before anything is charged. A product that hardcodes one of those patterns fits the businesses that already work that way and obstructs the rest, so the behaviour to test is configurability rather than automation on its own.
| Step | Record that must persist | Failure to test for |
|---|---|---|
| Account or customer | Billing relationship, agreed terms, statement preference, scheduling contact and payment contact. | A commercial account is stored as one customer per property, so nothing bills or reports at account level. |
| Property and access | Address, building or unit identity, access notes, gate codes, keys, parking, working constraints. | Access notes sit in a crew member's phone rather than the record, so a substitute crew arrives without them. |
| Stop, price and frequency | Service, price per visit, expected duration, recurrence rule, route assignment, crew or skill needed. | Price and frequency attach to the customer rather than the stop, so two properties under one account share one price. |
| Route or service day | Which stops are grouped, in what order, on which day, with which crew. | A stop moved for one week silently changes its permanent route day or its next due date. |
| Scheduled visit | Date, arrival window, assigned crew, expected duration, notification state. | Rescheduling does not update the customer notification, or fires a second one. |
| Completion and exceptions | What was done, what was skipped and why, photos or notes, access failures, extra work approved on site. | The exception is captured as free text, so it does not reach billing, reporting or the next visit. |
| Billing event | What is charged, against which stop and which account, on which cycle, in which document. | Completion forces an immediate per-visit invoice on an account that bills monthly in arrears. |
| Next service date | The date the recurrence rule produced, plus any manual override with its reason and author. | A skipped or moved visit shifts the whole future schedule, or leaves the stop with no next date at all. |
| One account, several stops | The link from one account to several properties, each with its own stops, prices, frequencies and history. | Statements and reports can be produced per property but not per account, or per account with no stop-level detail. |
Exceptions the record has to survive
Recurring work is stable until it is not. The nine exceptions below are ordinary in this trade, and they are where a route, a recurrence rule and a billing cadence pull against each other. This is the part of a demo worth the deepest attention, because a product can look correct for as long as nothing deviates from the plan.
| Exception | What the record must keep | What to test |
|---|---|---|
| Skipped visit | Which visit was skipped, the reason, who decided, whether it is billable, whether the next due date moves | Skip one stop for one cycle, then check the invoice, the following cycle’s route, and the next due date |
| Weather delay | Original date, new date, reason, and the message sent to the customer | Move a full day of stops to the next workable day and confirm the order, crew and notifications survive the move |
| Holiday shift | The shifted date, and whether the shift is one-time or permanent for that stop | Move a route day off a public holiday and confirm later cycles return to the normal day |
| Access failure | The attempt, the reason (locked gate, vehicle in the way, tenant absent), a photo or note, and whether a return visit or a charge applies | Report an access failure from a phone in the field and check whether the stop can be rebooked without duplicating the recurrence |
| Temporary pause | Pause start, expected resume date, whether billing pauses with it, and the stop’s place in the route while paused | Pause a stop for two cycles and confirm billing, notifications and route position rebuild correctly on resume |
| Price change | New price, effective date, who approved it, and the price that applied to earlier visits | Raise the price on one stop and confirm prior invoices are untouched while the next visit uses the new price |
| Route reassignment | Old route, new route, effective date, and whether history follows the stop | Move a stop between route days and confirm completion history, price and frequency stay attached to the stop |
| Extra work | The added service, its price, who approved it and when, and whether it repeats | Add an out-of-cycle service during a visit (screens, a post-construction clean, upper-floor glass) and check it reaches the invoice without changing the recurring price |
| Account-level billing | Which stops roll into which document, the billing period, and the account terms | Complete visits at three properties on one account, then produce a single statement that still shows each stop separately |
Two behaviours run across the whole table. First, whether an exception is stored as structured data or as free text: a note in a comment box is invisible to billing, to reporting and to the next crew. Second, whether a one-time change stays one-time. A single week’s move that permanently reassigns a route day does more damage than no automation would.
Software approaches for a window cleaning business
| Approach | Best fit | Main compromise | Verify in a demo | Integration or data risk |
|---|---|---|---|---|
| Broad field-service platform | Mixed service lines, or a business where quoting, invoicing, payments and accounting matter more than route mechanics. | Recurrence and route grouping are often configuration work rather than defaults, and exception handling may be shallower than a route-first product. | Build one account with three properties, give each stop its own price and frequency, then skip a visit and change a price. | Broad data models can flatten account-to-property-to-stop into a single customer record; check the export before committing history to it. |
| Route-focused field-service product | A schedule built from repeating stops on stable days, with high stop counts and frequent skips, pauses and moves. | Quoting, accounting depth, reporting and non-recurring job types may be thinner, and the product may assume one billing pattern. | Whether stops can be grouped by hand and re-sequenced automatically, and whether billing cadence can differ from the visit cycle. | A narrower product may integrate with fewer accounting systems; confirm the sync direction and how it maps accounts to customers. |
| Account or contract CRM beside an operations tool | Commercial account operators with agreed rates, contract dates, renewals, consolidated statements and a payer above the property level. | Field scheduling, crew mobile use and route sequencing usually live in the other tool, so two systems hold parts of one customer. | That a completed visit reaches the account record with enough detail to bill and to answer a stop-level query later. | Duplicate customer creation between the two systems, and history that splits across both after a switch. |
| Connected stack | A business with one settled component already (payments, accounting, or a customer database it trusts) and a single gap to fill. | Someone owns the joins. Exceptions have to be reflected in more than one place, and each vendor upgrade is a re-test. | Whether a skip, a pause or a price change made in one system appears correctly in the others without manual repair. | Integration coverage is usually partial; the parts that do not sync become the manual work the stack was meant to remove. |
Revenue mix is one factor in this choice, and on its own it settles little. Weigh it against the volume of exceptions in a normal month, the number of stops in a working day, how dense the route is, whether billing happens at account level, how often work is handed between crews, whether the business sells services beyond window cleaning, and what an existing accounting or CRM integration is worth to you.
Staying with a general platform is a legitimate outcome, and worth stating plainly because comparison content rarely offers it. Where route grouping is straightforward and exceptions are rare, the route controls a switch would buy can be worth less than the integration, the history and the retraining it would cost.
A product marketed to window cleaning is a hypothesis about depth, not evidence of it. Recurrence, route and exception handling vary product by product, and the checks on this page exist to find out which side of that line a given product falls on.
Capabilities to verify
Approaches are categories. Capabilities are behaviours, and several of the ones this trade depends on sit inside more than one category, or behind a paid add-on. Each item below is written so it can be checked in a trial rather than confirmed on a feature page.
One distinction to hold onto: route optimization and manual route grouping are different behaviours. Optimization sequences stops to cut travel. Manual grouping lets an operator keep a stable route day for customers who expect the same crew on the same day. A business can need both, and a product can offer one while its marketing implies the other.
Must have for this operating model
- Can one account hold several properties, and each property several stops, each with its own price, frequency and access notes?
- Can a stop carry a route assignment and a crew or skill requirement that a substitute crew sees on a phone?
- Can stops be grouped manually, and can an optimized sequence be reviewed before it is applied to the day?
- Can a skipped or paused visit be recorded with a reason without altering the underlying recurrence rule?
- Can completion trigger a billing event under a configurable rule, including a rule that produces no invoice at completion?
- Can the next service date come from the recurrence rule and still be overridden per stop, with the reason and author kept?
Important at the next stage of growth
- Can a price change, a pause or a route move be applied to a selected set of stops in one batch action?
- Can consolidated invoices or statements be produced per account while stop-level detail stays visible on them?
- Can card and bank payment methods be stored per account where the payment processor supports them in your market?
- Can customer notifications be configured per account, including accounts that want no automated messages?
- Can an audit history show who changed a price, a route or a schedule, and when?
- Can reporting break revenue, visit counts and skips down by route, by day and by account?
Useful only for certain services or contracts
- Structured quote inputs for window count, stories, access equipment, screens and glass condition, where quotes vary by more than frequency.
- Post-construction or first-clean job types that price separately and stay out of the recurring route.
- Contract records with start and end dates, agreed rates and renewal reminders, for tendered commercial work.
- Subcontractor or second-crew assignment with separate rates and their own completion records.
- Site-specific safety or induction documents attached to a property and surfaced before the visit.
Verify before switching
- Can customers, properties, stops, schedules, completion history, exceptions and invoices be exported in a readable format?
- Does the import accept an existing stop list with its frequencies and prices, or does it flatten stops into customers?
- Which route, recurrence, billing or payment capabilities sit behind a higher plan, an add-on, or a specific device?
- Does the accounting integration create one customer per account or one per property, and can that mapping be changed?
- What happens to scheduled recurrences and stored payment methods if the subscription lapses or is downgraded?
What changes when the season peaks
In many markets residential window cleaning demand concentrates in spring and fall, and the limit on revenue in those weeks shifts from lead volume to how many stops a crew can reach in a day. That pattern depends on climate and on the mix of work: a business weighted toward interior commercial glass, or working a mild climate, may see a flatter year. Treat seasonality as a question about your own booking history rather than a rule to design around.
Recurring commercial work can make demand more predictable for the businesses that carry it, on its own cycles, underneath whatever the residential season does. Holding both patterns at once is the real requirement: quoting fast enough to price a one-off job at the door, and billing that keeps charging a commercial account correctly through a slow month without anyone rebuilding the invoice.
A peak is also when exceptions stop being a detail. Weather moves a day of stops, a crew runs short, a customer pauses for a month, and a rescheduled route needs to settle back to its normal day afterwards. Rather than assuming that manual billing is where errors appear, reproduce the exceptions directly in a trial: skip a visit, move a day, pause a stop, change a price, then look at what the invoice, the route and the next due date became.
Questions to test in a demo or trial
Twelve checks, in roughly the order the chain above runs. They are written to be run in a trial account rather than asked and answered in a sales call.
- Can one customer or account hold multiple properties and recurring stops?
- Can each stop have its own frequency, price, access note, route, and crew assignment?
- What happens when a visit is skipped, paused, moved for weather, or completed late?
- Can the next due date and billing event follow different configurable rules?
- Can the operator group stops manually, optimize a route, and preserve a stable route day?
- Can a price change apply prospectively without rewriting prior invoices?
- Can commercial accounts receive consolidated invoices or statements while retaining stop-level history?
- Can crews complete, add notes, and report access failures from a phone with limited signal?
- Can the full customer, stop, schedule, completion, and billing history be exported?
- Can a price change, a pause or a route move be applied to a set of stops at once, with a record of who applied it?
- Which route, recurrence, billing or payment capabilities require a higher plan, a paid add-on, or a specific device?
- Does the accounting integration create one customer per account or one per property, and can that mapping be changed?
Where to go next
Use the part of this page that matches the bottleneck that brought you here.
- Quotes vary between estimators or take too long to build: the quoting items in the capability checklist, plus the stop-level price rows in the record model.
- Drive time eats the day, or a moved day breaks the following weeks: the exception matrix.
- Commercial accounts get billed late or need rebuilding each cycle: the billing cadence definition and the account-level rows in the record model.
- Nothing is broken in particular and the question is which category to buy: the quick decision summary and the approach matrix.
Research roadmap
Guides we plan to publish once they meet our evidence requirements. None of these is available yet.
- Planned Window cleaning software comparison: Which products fit defined window cleaning use cases, once comparable evidence exists for each of them.
- Planned CRM for window cleaning accounts: Account structure, contract terms and recurring billing for commercial work.
- Planned Window cleaning quoting software: Window count, stories, access and frequency as structured quote inputs.
How we evaluate this, and sources
The operational statements on this page are editorial assessment: reasoning from the shape of the work, labelled as such rather than presented as measured industry data. The one regional terminology claim is sourced below, with the date we checked it. No product is ranked on this page, and no product named anywhere on this site has yet been assessed for window cleaning fit.
Sources and scope notes
- What Should I Know Before Buying a Window Cleaning Round? Checked Reported. Supports the glossary note that "round" is used in the United Kingdom for a window cleaner's set of recurring customers and the schedule attached to them, including rounds bought and sold as a business asset. Cited for the term in that market; it supports no claim about usage elsewhere.