Three hundred pools and up

Do not switch. Run one route.

You have hundreds of pools and years inside another system, with your billing running through it. Nobody sensible moves that on a weekend, and we are not going to ask you to. Bring the forty houses of one technician and leave everything else exactly where it is.

01

One route is $59 a month. Not $350.

We count the pools you service here — whichever is higher, the ones you visited here last month or the ones active on your routes here today. The three hundred houses that stayed behind count zero on both sides, because they are not in here. So one route of forty houses is forty pools: $59. The $350 starts the day you bring all of them.

Before you ask

And what happens when you import the rest.

If importing more pools moves you up a step, the difference is charged right then, not next month. Inside the same step the adjustment lands on your next invoice. Going down never happens mid-month: the count is redone on the 1st, and the new amount applies from the following invoice. We would rather you read that here than find it on a statement.

Stays where it is

The money does not move.

ZapRoute does not process payments and does not issue invoices — not in the app, not in the customer portal. Your AutoPay, your card on file and your monthly billing keep running exactly where they run today. What we do is prepare the lines: visits, salt, filters and repairs, ready for your QuickBooks. If billing inside one system is what decides this for you, then it decides it, and we would rather you know now.

Three things that route gets on day one.

01

The test strip, read from the photo.

Your technician photographs the strip and the readings fill themselves in, with a confidence score and anything uncertain marked for the office to confirm. Meters over Bluetooth exist elsewhere. Reading a strip from a picture, inside the route app, does not.

02

Suspicious photos, with the reason on the screen.

Not a score — the actual reason, next to the picture. The same photo sent twice, matched by fingerprint. Three different locations inside ten minutes, or six inside thirty. A timestamp more than thirty days old, or in the future. A photo taken more than a thousand feet from the house. And the AI saying the picture does not look like the service that was logged. Your office sees the queue; the technician on the route never sees an accusation.

03

Profit per pool.

Fuel, chemicals and labour against what each house pays, pool by pool. On forty houses it is interesting. On three hundred and fifty it is where the money is: finding the twenty that lose money every month is worth more than the subscription many times over. It needs your costs typed in once, and that is an hour of somebody's time.

Will it hold at my scale?

You have payroll depending on tomorrow's route, so this is the fair question — and our site did not have a line about it until now. Here is what is true, and what is not.

True

What actually protects you.

  • Today's route is already on the phone. It opens with no signal, and photos and readings taken offline go up by themselves when the signal comes back — the queue retries every fifteen seconds.
  • The photos have their own copy every night, in a separate bucket at Google Cloud, because the database backup does not cover photos. The job that makes that copy only knows how to create and read — it has no way to delete anything.
  • Adding pools never interrupts anything: the count is a number, not a migration, and there is no seat to buy or setup fee to pay.
Not true

What we do not have, said plainly.

  • No status page, no published uptime number and no service-level agreement. Our own terms say so in writing.
  • Tomorrow's route is not on the phone yet — only today's. If our server were down first thing in the morning, your technician would not have the day until it came back.
  • We have never rehearsed restoring a backup into a clean project. A backup nobody has restored is a promise, not a fact, and we are not going to print it as a fact.
  • And nobody has run an operation your size on this. Which is the whole reason this page asks for one route and not your book of business.

The price, said against whom.

At three hundred and fifty poolsSkimmerZapRoute
Scaling Up$700$350
Getting Started$350$350

Half of the plan you are most likely on, which is $4,200 a year — and exactly the same price as their entry plan, which caps photos at five per visit and has no route optimization. Two more things nobody writes about themselves: they bill per serviced location, one address however many bodies of water, while we bill per pool; and against competitors who charge per technician rather than per pool, a lean crew can make us the expensive one. Source: getskimmer.com/pricing, checked Sep 21, 2026.

That $350 against $700 only holds if you leave Skimmer completely — and while you are running one route here, you are not leaving: you pay us $59 and you keep paying them, the same as before. Leaving for real means your billing lands somewhere else, and here that somewhere is QuickBooks. If you would rather keep billing inside Skimmer, then keep it, and read this page as a $59 experiment rather than a saving.

One route. Thirty days. No card.

Start free · 30 days, no card