Payments
8 min read

How long pool service companies wait to get paid in 2026

Pool service operators wait 30 to 45 days to get paid. What slow payment costs your business and how to cut days to cash with auto pay and embedded payments.

Clayton Shivers
April 11, 2026

A pool service business runs on cash flow. Routes go out, chemistry gets dosed, equipment gets installed, invoices go out, and then the operator waits. The wait is where most operators are quietly leaking money. This post breaks down what the average pool service business actually waits to get paid, what that wait costs in real dollars, and the three changes operators make to cut it.

TL;DR

  • Average pool service operator waits 30 to 45 days from invoice to bank deposit
  • A 50 stop route at $145/month with 30 day average days to cash carries about $7,250 in working capital tied up at any moment
  • Auto pay enrollment cuts days to cash to 1 to 3 days for the customers enrolled
  • Native embedded payments (Pooly model) cut deposit timeline from T+2 to T+1, removing another 24 hours of float

Why pool service has a days to cash problem

Most pool service businesses run on a billing model that the rest of the SaaS world abandoned a decade ago. Operator does the work, sends an invoice (often by email PDF, sometimes still by paper), and waits for the customer to mail a check or call in a card. The customer takes 10 to 20 days to act. The check, when it comes, takes 3 to 5 business days to clear. Card payments processed manually take 1 to 2 days to settle. Total: 14 to 30 days from invoice to deposited cash, before you account for the customers who simply forget for another two weeks.

For a single stop, that wait does not feel like much. For an entire route, the working capital tied up in receivables can equal a month of revenue or more. That is money you could be spending on chemistry, payroll, equipment, marketing, or pulling out of the business. Instead it is sitting in someone else mailbox.

The actual cost of slow payment, in dollars

Let us run the math on a 50 stop weekly route at $145 per month per stop:

  • Monthly recurring revenue: $7,250
  • Annual recurring revenue: $87,000
  • Average days to cash at 30 days: $7,250 in receivables outstanding at any given time
  • Average days to cash at 45 days: $10,875 outstanding
  • Average days to cash at 5 days (auto pay): $1,200 outstanding

Cutting days to cash from 30 to 5 is the same as freeing up about 7% of your annual revenue to use for everything else.

The three changes that cut days to cash

Operators who fix this generally make three moves, in this order. None of them require buying new trucks or hiring an office manager.

1. Auto pay enrollment as a default, not an option

Most pool service software lets customers opt in to auto pay. Most operators present it as an option during onboarding. Three operators out of ten enroll. Operators who shift to making auto pay the default (with an explicit opt out) hit 70%+ enrollment within 90 days.

Why this matters: every customer on auto pay drops days to cash for that account from 30+ to under 3. The math compounds. Sixty percent enrollment across a 100 stop route means $15,000+ in working capital recovered.

2. Card on file for upgrade jobs and add ons

Heaters, equipment, repairs, renovations: these used to require a phone call to collect a card number, a paper check, or a separate Square reader at the door. Card on file removes that friction. Customer agrees to the work, you charge the saved card, deposit clears in 1 to 2 days. No collection cycle.

The conversion rate on equipment upgrades when financing or card on file is in the same flow as the quote is materially higher than when it is not. Operators who run the math typically see ticket size lift by 20 to 40% in the first six months after enabling card on file plus tier pricing.

3. Native embedded payments instead of partner routed processing

This one is the wedge that pool service software companies fight over. Most pool service software (Skimmer, Jobber, Housecall Pro, Pool Office Manager) routes payments through a third party processor like Stripe. The processor takes a cut. The software takes a referral cut. Your funding timeline is set by their schedule, usually T+2.

Native embedded payments (the model Pooly uses through ClayPay) own the rails directly. No middleman, no referral cut. Funding timeline is T+1, sometimes same day for high volume operators. The economics show up on the P&L in two places: lower processing fees per transaction, and one extra day of working capital recovered every cycle.

Operator playbook: a 30 day plan

If you are sitting at 30 to 45 days to cash today, here is the order to fix it without disrupting routes.

  • Week 1: Pull a report of every active customer. Note who is on auto pay vs paper / manual card.
  • Week 2: Send an auto pay enrollment email or text to every non enrolled customer with a clear explanation of why (their convenience, your operating efficiency).
  • Week 3: For customers who do not enroll, follow up with a phone call or in person ask at the next service visit.
  • Week 4: Audit your processor statement. If you are on Stripe via your software, look at the cut your software vendor takes on top of Stripe. Compare against native rails options.

How Pooly handles this

Pooly is built around the assumption that days to cash is one of the most under managed numbers in pool service. Auto pay enrollment is in the default customer onboarding flow. Card on file is set up at the same time. Native embedded payments through ClayPay (our parent company) are on rails we own. No Stripe middleman. T+1 funding by default.

The pool route valuation guide breaks down how days to cash and card volume share feed directly into route value at sale. The cost of waiting on payment is one of the inputs.

Run this in your software

Pooly is built around the operator economics covered in this post. 30 day free trial.

Talk to founders