15 Cleaning Software Demo Questions Before You Buy

Written by: LPSA
Evidence level: research_based
Product information checked: 2026-07-02
Pricing checked: 2026-07-02
Last meaningfully updated: 2026-07-02

Evidence status

Quick answer

A residential cleaning business should not use a software demo to ask, “Do you have scheduling, reminders, payments, and QuickBooks?” It should ask the vendor to prove the exact workflow: recurring cleaning setup, skipped visits, one-time reschedules, cleaner mobile view, seat or provider math, SMS costs, payment fees, accounting sync, export files, and cancellation or data-access rules.

This is a research_based demo framework, not a hands-on software test. FieldOpsLab did not verify any vendor’s live demo quality or live recurring-cleaning workflow. Use the questions below to force written confirmation before buying.

If the demo centers on estimates, quote approvals, deposits, or quote-to-job conversion, bring FieldOpsLab’s estimating and quote software guide for residential cleaners into the same vendor call.

Quick verdict

In this article

Key facts

Takeaway: The safest demo is not the one with the smoothest sales presentation. It is the one that exposes workflow risk, cost risk, migration risk, and exit risk before you buy.

Best for

• Cleaning business owners preparing for a software demo or free-trial review.
• Teams replacing spreadsheets, Google Calendar, texting, manual invoices, paper notes, and disconnected tools.
• Buyers comparing broad FSM tools, cleaning-specific tools, and booking-first tools.
• Owners who want a practical checklist before buying or committing annually.
• Teams using FieldOpsLab planning scenarios such as 2 field workers + 1 office user, 5 field workers + 1 office user, or 15 field workers + 2 office users.

Avoid if

• You want a final vendor recommendation instead of a buying framework.
• You want a hands-on software review or live workflow test.
• You need a final quote instead of a demo script.
• You want a generic SaaS demo checklist that ignores residential cleaning specifics.
• You have not defined your team size, recurring workflow, payment path, or export needs yet.
• You expect this page to prove any vendor’s live workflow quality by itself.

Buyer scenario

The target buyer is a US residential cleaning business with 2–20 field workers and 1–2 office users. The current workflow may still rely on spreadsheets, Google Calendar, texting, paper job notes, manual invoices, separate payment tools, and disconnected website forms. The owner is comparing software categories, not just one product name.

FieldOpsLab uses three planning scenarios in this guide. These are planning models, not real customer cases and not vendor quotes:

The same headcount can price very differently across platforms because vendors may count named users, licensed users, providers, technicians, office users, field users, team leads, or even inactive provider records. That is why a demo should always include written team-size math. See Jobber pricing, Housecall Pro pricing, ZenMaid pricing, and BookingKoala pricing.

Takeaway: Before the demo starts, know your real team count, who needs a login, who needs cleaner mobile access, and who only needs office access.

The 15 demo questions

You do not need to ask every question in the same order. But you should make sure the vendor proves every theme below before you buy.

Can you show our full recurring residential cleaning workflow from lead to payment?

Why it matters: A cleaning company is not buying isolated features. It is buying a connected workflow: lead, quote or booking, recurring setup, assignment, reminder, completion, invoice, payment, and follow-up.
What a strong answer should show: A single end-to-end walk-through using a recurring residential customer, not separate feature screens.
Caution answer or red flag: The rep says “yes, we do all of that” but jumps between unrelated screens or skips payment and accounting.
Proof to request: A recorded demo or post-demo summary listing the exact features and plan required to run your workflow.

How do weekly, biweekly, monthly, and custom recurring schedules work?

Why it matters: Recurring cleaning is the core workflow for many residential teams, and recurrence rules vary by platform. Jobber, Housecall Pro, and BookingKoala all document recurring work, but not in the same way.
What a strong answer should show: Weekly, biweekly, monthly, and a custom recurring example that actually matches how you sell cleanings.
Caution answer or red flag: The rep only shows one recurrence type or says custom rules are “possible” without showing them.
Proof to request: A written note confirming which recurrence rules are supported on your plan.

How do skipped visits, holidays, lockouts, cancellations, and one-off reschedules work?

Why it matters: Residential cleaning has normal exceptions. Customers travel, homes are unavailable, and schedules shift. Jobber documents rescheduling notifications, BookingKoala documents holiday skipping, and BookingKoala also documents cancellation and postponement options for customers.
What a strong answer should show: One live example for each: skip, holiday adjustment, lockout or late cancel, and a one-off reschedule.
Caution answer or red flag: The rep talks about “editing the appointment” but never shows what happens to reminders, billing, or the future series.
Proof to request: A written explanation of how the platform handles skips, holidays, one-off moves, and canceled visits.

Can we edit one visit without changing the whole series, and can we change all future visits without damaging past history?

Why it matters: This is one of the easiest ways to uncover recurring-workflow risk. Jobber documents visit-only edits and “Save and update future visits.” Housecall Pro documents “Only this job” versus “This job and all future jobs.”
What a strong answer should show: One single-visit edit and one future-series edit, with past history left intact.
Caution answer or red flag: The system forces re-creation of the entire series, or the rep cannot explain how past jobs are preserved.
Proof to request: A short written confirmation describing one-occurrence edits versus future-series edits.

How are cleaners, pairs, crews, and crew leads assigned?

Why it matters: Residential cleaning often uses solos, pairs, rotating teams, or lead-cleaner models. Jobber documents assigning team members to one visit versus future visits. Housecall Pro documents separate roles for office staff and field techs. BookingKoala pricing states that each team member counts as a provider.
What a strong answer should show: One solo cleaner, one pair, and one future reassignment example.
Caution answer or red flag: The rep cannot explain whether pairs are just scheduling groups or actual billing units, or cannot explain how team leads differ from standard cleaners.
Proof to request: A written note on how people are assigned and counted in billing.

What does a cleaner see on mobile before, during, and after the job?

Why it matters: Owner-friendly software can still fail if the field experience is weak. Housecall Pro notes that field techs access their accounts through the mobile app. ZenMaid and BookingKoala both publish cleaner or provider mobile details.
What a strong answer should show: A real cleaner view on a phone, including the day’s schedule, job detail, completion actions, and communication options.
Caution answer or red flag: The rep only shows the office desktop or says the mobile app is “basically the same.”
Proof to request: A link to the mobile help doc, mobile app page, and a post-demo note confirming which mobile actions cleaners can take.

Can cleaners see notes, entry instructions, pets, supplies, photos, checklists, and customer preferences?

Why it matters: Residential cleaning quality depends on property detail. ZenMaid says cleaners can see entry instructions, pet notes, cleaning checklists, and special requests. BookingKoala documents job notes, job media, checklists, and clock in or out in the provider app. Jobber documents visit notes and checklists.
What a strong answer should show: One live job showing entry instructions, pet notes, checklist items, and a photo or notes field.
Caution answer or red flag: Important visit detail lives only in the office view or only in internal notes that cleaners cannot reliably access.
Proof to request: A written list of what job detail is visible to cleaners versus office staff.

What can cleaners do and not do, and does every cleaner need a paid login, named seat, provider slot, or technician account?

Why it matters: Permission design drives both cost and control. Jobber says a user is anyone who needs to log in. ZenMaid’s terms require each individual user to have unique login credentials. BookingKoala says each team member counts as a provider. Housecall Pro documents separate office-staff and field-tech permissions.
What a strong answer should show: A permission walk-through for owner, office user, crew lead, and cleaner, plus billing treatment for each.
Caution answer or red flag: “We’ll figure that out later” or “you can probably share a login.”
Proof to request: A written seat or provider count for your exact staffing model.

For our 2+1, 5+1, and 15+2 team sizes, exactly how many users or providers are included, and what does each extra person cost?

Why it matters: Team-size math changes the real monthly cost. Jobber publicly lists included users by plan and extra-user pricing. Housecall Pro publicly lists Basic for 1 user, Essentials up to 5, and MAX up to 8 with additional users on MAX. BookingKoala also warns that both active and deactivated providers count toward plan limits when downgrading.
What a strong answer should show: Three written scenarios: 2+1, 5+1, and 15+2, including who counts and which plan fits each one.
Caution answer or red flag: The vendor only talks about “starting at” pricing or refuses to map your team sizes in writing.
Proof to request: A written plan recommendation and team-size quote for all three scenarios.

Which reminders and customer messages are included, and what do SMS or email usage costs actually look like?

Why it matters: Reminder workflows reduce no-shows and lockouts, but messaging can add real cost. Jobber lists automated reminders on higher plans. ZenMaid pricing states that SMS charges are not included. BookingKoala lists SMS on Growing and Premium, while BookingKoala’s Twilio setup guide shows that SMS still requires Twilio setup.
What a strong answer should show: Reminder timing, confirmation workflow, on-my-way messaging, and the real cost path for your expected message volume.
Caution answer or red flag: “SMS is included” without clarifying whether usage, Twilio, or overage charges still apply.
Proof to request: A written messaging-cost summary, including any add-on or third-party setup needed.

How do quotes, invoices, card-on-file, ACH, Tap to Pay, failed payments, and refunds work for recurring residential clients?

Why it matters: Payment path affects cash flow, admin work, and customer experience. Housecall Pro publicly lists separate fees for swiped or tapped cards, online cards, saved cards, ACH, and Tap to Pay. Jobber publishes online payment, Tap to Pay, ACH, and instant-payout pricing. ZenMaid says it works with Stripe and Square, stores cards through the processor after payment, supports batch charging from the calendar, and does not support deposits or pre-authorizations at this time.
What a strong answer should show: One recurring customer paying by saved card, one paying by ACH, one failed-payment example, and one refund example.
Caution answer or red flag: The vendor can talk about processing rates but cannot show the actual saved-card or failed-payment workflow.
Proof to request: A current payment-fee sheet and a written explanation of failed-payment handling.

What can customers do themselves online: book, request quotes, reschedule, cancel, or update payment details?

Why it matters: Customer self-service can reduce office workload, but the scope differs by product. Housecall Pro’s online booking FAQ says customers currently cannot cancel jobs booked through online booking and must contact the company directly. BookingKoala documents customer cancellation, postponement, resume, added cards, invoices, tips, and repeat booking through the dashboard. ZenMaid promotes embedded booking forms for quote and scheduling requests.
What a strong answer should show: A customer booking, a self-service change request, and a payment-update example.
Caution answer or red flag: The vendor promises self-service broadly but cannot show what customers can actually cancel, postpone, or update themselves.
Proof to request: A written list of customer self-service actions and any plan gates.

What exactly syncs with QuickBooks or accounting software, and what does not?

Why it matters: A QuickBooks logo is not enough. Housecall Pro says its QuickBooks Online integration typically functions one-way from Housecall Pro to QuickBooks Online and documents invoices, payments, customer info, and price-book item behavior. BookingKoala documents bulk syncing booking charges, refunds, and gift card purchases to QuickBooks. ZenMaid pricing still labels QuickBooks integration as “coming soon.” Jobber pricing lists QuickBooks Online on higher plans.
What a strong answer should show: Sync direction, what triggers the sync, which objects sync, how refunds and edited invoices behave, and what your bookkeeper should review.
Caution answer or red flag: “It integrates with QuickBooks” without object-level detail.
Proof to request: A written sync-scope summary and the relevant help-center article.

Which reports would an owner or office manager actually use every week?

Why it matters: Reporting is only useful if it helps you run the business. Owners typically need visibility into upcoming recurring work, cancellations, revenue, repeat clients, staff performance, and collection status. Public pricing pages and docs also show that reporting depth varies by plan, as seen on Jobber, Housecall Pro, ZenMaid, and BookingKoala.
What a strong answer should show: Weekly owner view, office follow-up view, and one report tied to recurring clients or cancellations.
Caution answer or red flag: The rep shows dashboards with no practical cleaning use case or hides meaningful reporting behind a higher plan after the workflow sale.
Proof to request: A list of included reports for your recommended plan.

What happens during import, onboarding, export, downgrade, cancellation, and post-cancellation data access?

Why it matters: Buying software without an exit plan creates lock-in risk. Jobber documents client export and recurring jobs report export. Housecall Pro documents import and export of customers and jobs, and its billing help page documents cancellation workflow and refund limits. ZenMaid pricing lists free transfer help on Pro and Pro Max and data export on Pro Max, while ZenMaid’s terms warn that downgrading can cause loss of content, features, or capacity. BookingKoala says canceled accounts are deleted and previously stored data cannot be retrieved.
What a strong answer should show: Import scope, onboarding support, sample exports, downgrade rules, cancellation steps, and post-cancellation access timing.
Caution answer or red flag: Export and cancellation are discussed only verbally, or the rep refuses to provide sample exports before you sign.
Proof to request: Sample export files, onboarding scope, cancellation steps, and data-access rules in writing.

Scenario-specific demo script

Takeaway: The bigger the team, the less useful “starting at” pricing becomes. Larger teams should expect to verify permissions, migration, reporting, and exit rules before signing.

Workflow proof checklist

FieldOpsLab did not verify vendor demos directly. Use this checklist to decide whether the demo actually proved your workflow or only described it.

Takeaway: If the vendor cannot show a skipped visit, a future-series edit, cleaner mobile detail, and a sample export, the demo is not finished.

Pricing and cost questions

Buyers often compare only the base plan. That is the wrong number to trust first. A better demo asks the vendor to confirm the full cost model: subscription, users or providers, office access, cleaner access, reminders, payment fees, onboarding, migration, taxes, and contract terms.

Official vendor pricing pages show why. Jobber lists included users and extra-user pricing. Housecall Pro lists Basic, Essentials, and MAX team bands plus additional users on MAX. ZenMaid lists low starting prices but still asks how many cleaners and office managers are on the team and states that SMS is not included. BookingKoala prices by providers, storage, and, on Premium, campaign contacts.

Takeaway: Do not treat unknown costs as zero. If the vendor cannot explain a cost line clearly, treat it as unresolved until it is documented.

Accounting, payments, and QuickBooks questions

Public documentation is helpful here, but it still does not prove live accounting behavior. Treat this section as a diligence framework, not as proof that any vendor’s accounting setup will behave exactly the way your bookkeeper expects.

Card-on-file and recurring collections

Ask the vendor to show how a residential customer pays after the first visit and after later recurring visits. Housecall Pro publicly distinguishes customer-entered online cards, manually entered or saved cards, ACH, Tap to Pay, and instant payout. ZenMaid says that once a client pays, the card is stored via Stripe or Square for future use, supports batch charging completed appointments, and does not support deposits or pre-authorizations at this time. BookingKoala supports Stripe, Square, PayPal via Braintree, and Authorize.net for charging customers, but only one processor can be connected per account at a time.

Failed payments, refunds, tips, and deposits

Ask what happens when a recurring charge fails, whether retry logic exists, whether office staff are alerted, and what customers see. Also ask how refunds, tips, partial payments, and deposits are handled. Public docs vary: Housecall Pro and Housecall Pro ACH documentation are fairly detailed on fees and payout timing; BookingKoala QuickBooks documentation covers booking charges and refunds in sync; ZenMaid explicitly says deposits and pre-authorizations are not supported at this time.

ACH, card fees, and Tap to Pay

Do not ask only for “the card rate.” Ask for exact rates by payment path. Public examples show why: Housecall Pro lists 2.59% for swiped, tapped, or chipped cards, 2.99% for online customer-entered cards, 3.49% for staff-entered or saved cards on file, and 1% for ACH, with ACH fees varying by plan according to its ACH FAQ. Jobber publishes Tap to Pay, ACH, and instant-payout pricing on its pricing page.

QuickBooks sync direction and review

Ask which system is the source of truth, what syncs automatically, and what still needs a bookkeeper review. Housecall Pro says its QuickBooks Online integration typically functions one-way from Housecall Pro to QuickBooks Online and documents invoices, payments, new customer information, and new price-book items moving over. BookingKoala says it can bulk sync booking charges, refunds, and gift card purchases and create linked customer accounts when needed. Public docs do not prove how edited invoices, unusual tax setups, duplicate prevention, or reconciliation will feel in your own workflow.

Takeaway: A QuickBooks integration is not a yes-or-no question. It is a workflow question about sync direction, object coverage, edited invoices, refunds, and what your bookkeeper still has to review manually.

Migration, export, and cancellation questions

Import support and onboarding scope

Ask what the vendor can import from spreadsheets and what must be rebuilt manually. Housecall Pro says MAX customers can work with its data-import team for customers, job history, equipment, and price-book data, and that additional fees may apply for more complex work. ZenMaid pricing lists free transfer help on Pro and Pro Max. Public documentation helps you ask the right question, but it does not prove the real migration workload for your data.

Sample exports before signing

You should ask for sample exports before you commit. Public docs show that export support exists, but export depth still varies. Jobber documents client export and recurring jobs report export. Housecall Pro documents customer and job export, and price-book export. BookingKoala documents customer CSV export. ZenMaid pricing lists “Export of your data” on Pro Max, but public object-level export documentation remains limited.

Saved-card migration and recurring rebuild

Ask separately about recurring-schedule rebuild and saved-card migration. Those are often the hardest parts of switching. Public vendor materials may discuss payments or exports, but they rarely prove that an existing recurring route or stored-card setup will migrate cleanly. Treat these as high-priority written-confirmation items.

Downgrade, cancellation, and post-cancellation access

Ask what happens if you downgrade, cancel, or miss a payment. Ask when billing stops, when access ends, and how long exports remain available. Public docs show why this matters. Housecall Pro’s billing article says cancellation starts through support chat and notes that billing cannot be fully paused until a team member has spoken with the account owner by phone. BookingKoala’s cancellation article says canceled accounts are deleted and data cannot be retrieved, while recommending a downgrade to Starter if you want to retain data. ZenMaid’s terms say downgrading may cause loss of content, features, or capacity. Jobber’s terms are also part of the diligence review before purchase.

Ask for this after the demo

• written plan recommendation
• user or provider math for 2+1, 5+1, and 15+2
• full add-on list
• SMS cost details
• payment-fee sheet
• QuickBooks or accounting sync scope
• onboarding and migration scope
• sample exports
• cancellation, downgrade, and data-access rules
• annual versus monthly terms
• total estimated monthly cost and first-90-day cost

Takeaway: If export, migration, and cancellation are only explained verbally, you still have material buying risk.

Product-category notes

This is not a comparison article. The goal is to help you change the demo by category.

Takeaway: The same 15 questions still apply, but the stress points change by software category.

Red flags during the demo

• The vendor cannot show skipped visits, holidays, or lockout handling.
• The vendor cannot show one-occurrence edits versus all-future edits for recurring work.
• Pricing depends on sales follow-up, but no written quote is provided.
• Every cleaner login cost is unclear.
• Provider, team, or inactive-provider counting is unclear.
• SMS pricing is vague or treated as zero.
• Payment fees are not documented by payment path.
• QuickBooks sync is described vaguely.
• No sample export is provided.
• Cancellation terms are only verbal.
• Migration scope is undefined.
• The rep says “yes, it can do that” without showing the workflow.
• An annual commitment is pushed before the workflow is proven.

Follow-up email template

What we could not verify

• live vendor demo quality
• live workflow fit
• whether a specific vendor can handle every skip, holiday, lockout, or reschedule pattern
• actual final quote
• actual support quality
• actual migration effort
• complete export quality across every object
• saved-card migration
• post-cancellation experience
• whether cleaners will adopt the mobile workflow well in practice
• whether every answer given verbally in a demo would hold up in the final contract or invoice

Final recommendation

The safest demo is not the one where the product looks polished. It is the one where the vendor proves the buyer’s real recurring-cleaning workflow, explains the exact cost model for the buyer’s team size, shows the cleaner mobile view, documents SMS and payment fees, explains QuickBooks or accounting behavior, provides sample exports, and confirms cancellation or data-access terms in writing.

Do not commit annually until the vendor has confirmed the key workflow, pricing, payment, accounting, export, migration, and cancellation assumptions in writing.

Methodology

This article uses a research_based evidence standard. FieldOpsLab reviewed public vendor pricing pages, official help-center articles, official terms and billing pages, official payment documentation, official import and export documentation, and official integration documentation, plus FieldOpsLab’s related public coverage of cleaning software categories.

FieldOpsLab did not use a controlled account, vendor demo, or live residential-cleaning workflow for this guide. The scenarios used here are FieldOpsLab planning scenarios for a typical US residential cleaning business with 2–20 field workers and 1–2 office users. Public documentation can support a practical diligence framework, but it cannot prove live workflow quality, migration quality, or support quality. Buyers should verify current pricing, packaging, and contract terms directly with vendors before purchase.

Sources

FieldOpsLab related reading

• Cleaning Business Software Buying Guide
• Jobber
• Housecall Pro
• ZenMaid
• BookingKoala
• Jobber vs Housecall Pro
• Jobber pricing
• Housecall Pro pricing

Official Jobber sources

• Jobber pricing
• Jobber Visits
• Export Client Information
• Recurring Jobs Report
• Jobber Terms of Service

Official Housecall Pro sources

• Housecall Pro pricing
• Manage Recurring Jobs
• Team Member Roles & Permissions
• Online Booking FAQs
• Housecall Pro Payment Processing Options
• ACH Payments FAQ
• QuickBooks Online: Syncing Information from Housecall Pro
• How to Import & Export Jobs and Customers
• Price Book: Import or Export Services and Materials
• Housecall Pro Billing and Account Management
• Housecall Pro Terms & Conditions

Official ZenMaid sources

• ZenMaid pricing
• ZenMaid cleaning business app
• ZenMaid cleaning service scheduling software
• ZenMaid cleaning booking software
• ZenMaid invoicing
• ZenMaid credit card processing
• ZenMaid Terms of Service

Official BookingKoala sources

• BookingKoala pricing
• Provider app overview
• Customer dashboard explained
• Payment processors overview
• Setting up frequencies for every form
• Setting up your store options “Scheduling” tab
• QuickBooks overview
• How to export customer data
• Upgrade or downgrade your subscription
• Close or cancel your account
• Set up Twilio

Next steps

Continue researching

Use these related FieldOpsLab resources to move from this article into the next pricing, comparison, demo, or migration check.

Estimating and quote workflowAdd quote, deposit, and approval questions to the same vendor demo.Migration checklistMove from demo answers into export, import, and launch planning.Buying guideUse the broader framework if your shortlist is still uncertain.Recurring schedulingTranslate demo answers into recurring-work workflow checks.