PoolProof

Pool service software that cannot lose the service log.

PoolProof is a day route and a chemistry log for 1–20 truck pool operators. Readings, notes and photos are written to the phone first — the server can be down, the signal can vanish mid-pool, and nothing is lost.

Start — $49/mo flat Poke the live demo — no signup

What it looks like

Real screens, captured from the demo account — the route, the capture form with a record waiting to sync, and the customer report.

The day route: ordered stops, skip with a reason, reorder before you drive.
The day route: ordered stops, skip with a reason, reorder before you drive.
Capture a stop, saved on the device first: the badge reads Pending sync until the server has it.
Capture a stop, saved on the device first: the badge reads Pending sync until the server has it.
Pending vs synced, per record — including one deliberately failed sync in the demo.
Pending vs synced, per record — including one deliberately failed sync in the demo.
The customer report a link opens: readings, notes, photos, no login.
The customer report a link opens: readings, notes, photos, no login.

One flat price, because math on a truck shouldn't need a calculator

The incumbent ladder charges a base fee plus $1–2 per serviced pool per month. PoolProof is one number for the whole company: every pool, every truck, every report.

  • Unlimited pools and stops
  • Offline capture with an on-device replay log
  • Read-only customer report link per visit
  • Photo attach from the camera
  • Cancel anytime, no setup fee

PoolProof

$49/mo

Flat. Not per pool. Test mode checkout for now.

Start $49/mo

Prefer to look first? Open the live demo — a real company with 12 pools and a week of visits.

Built for the failure the reviews keep describing

Field software fails in three places: it crashes mid-service, it loses a photo, and it double-books the route. PoolProof answers with a durable local store, an atomic photo commit, and one idempotent replay log per device.

Saved before it is sent

A stop completes only when the readings are committed to the phone's own database. The submit path is a retry loop, never a one-shot POST.

Photos land whole or not at all

Photos are fsynced to a temp file and renamed into place on the server — an interrupted upload can never leave half an image.

Every record says what it is

Pending, synced, or refused-with-a-reason. The sync log is the receipt, and nothing is silently dropped.