ProValet
Mini Explainer · One route, start to finish

How the work moves

The route runs whether or not the phone ever rings.

Route-based businesses run two kinds of work at once: the visits that happen on schedule every week, and the repairs found during them. The recurring work covers the overhead. The repair work is the margin. Most software handles one and hands you a spreadsheet for the other. Below is the whole line, unbroken.

Pool · Lawn · Pest · Home watch · Window cleaning

The handoff map

Scroll sideways to follow the line →  ·  tap any step to jump to it

Homeowner Technician Company The route — default path Work moves Money moves Found work

The route, and everything hanging off it

Maintain → Repair → Bill → Collect → Settle
  1. R

    Company → Technician · standing

    The scheduled route

    Most of the work in a route-based business was never requested. It was sold once, as a service plan, and it regenerates on its own — every Tuesday, every other week, every month through season. ProValet builds those stops from the plan and its timing rules, then drops them on the right route with the right technician. Nobody types them in, and nobody has to remember them.

    This is the default path. Everything below is the exception, not the rule.
  2. 01

    Homeowner → Company · the second door

    Request

    Between visits, a customer notices something: heater won't fire, zone three is dry, the cage screen tore in the storm. They open the app and say so, with photos. It lands on the office board as a record with a number on it. For someone already on the route, this is an addition to an existing relationship, not the start of one.

  3. 02

    Company → Homeowner

    Estimate

    Parts, labor, trip. Most estimates don't actually originate here — they originate in the field, at step 5, when a technician standing at the equipment pad finds the failing part. Either way the customer receives a document they can read line by line, with the photos attached.

  4. 03

    Homeowner → Company

    Approval

    Approve or decline, in the app. That approval is a timestamped record attached to the job, which is exactly what you want on the day a customer says they never agreed to $1,840 of new plumbing. Declines don't vanish either — they sit on the customer record for follow-up.

  5. 04

    Company → Technician

    Service order

    This is where both paths merge. A recurring stop and an approved repair become the same object: scheduled work, on a route, on a day, with a technician's name and the parts attached. From here down, nothing cares which door the work came through.

    One object, one schedule, one billing stream — whether it was planned six months ago or approved this morning.
  6. 05

    Technician → performs the work

    Service visit

    The technician sees the stop on his phone, checks in, performs the maintenance, and records what actually happened — readings, chemicals, parts consumed, photos before and after. It runs with no signal in a screened lanai or a dead-zone lot, and syncs when there is one.

  7. BRANCH

    Technician → Company → Homeowner

    Found work

    The most valuable thing a technician does on a maintenance stop is notice. A weeping union, a motor drawing high amps, a cracked skimmer throat. He raises the estimate from the field, standing in front of it, photo already attached — and it re-enters the line at step 2 without anyone driving back out.

    This loop is the difference between a route that covers payroll and a route that grows. If raising an estimate from the field is hard, it doesn't happen.
  8. 06

    Technician → Homeowner

    Service report

    Closing the stop sends the customer a report: what was found, what was done, what to watch next visit. This is the step that ends the "was anyone even here?" phone call, and it is the single biggest reason customers stay on the route.

  9. 07

    Company → Homeowner

    Invoice

    Billing pulls straight from the closed job — same photos, same parts, same labor. Statement invoicing rolls the period's recurring visits and any repairs into one document, because the customer has one relationship with the company, not two.

    On a larger repair, the deposit is taken against that same invoice, and the final balance settles against it when the work is done. One document carries the job from deposit to paid in full, so nobody is maintaining a side ledger of who paid what up front.

    Nothing is re-keyed between the field app and the books, so nothing is typed twice and nothing is typed wrong.
  10. 08

    Homeowner → Company

    Payment

    The customer pays with a stored method, or AutoPay charges on the schedule they authorized in writing. No paper check on the counter, no card read over the phone, no chasing the same forty accounts every month.

  11. 09

    Company → Company bank

    Funds in the bank

    Funds land in the operator's own account on the standard settlement cycle — no batch to close out, no separate processor portal, no walk to the bank. The job closes on the books, and next week's stop is already sitting on the route. Nobody restarts the cycle, because nobody stopped it.

    Invoices and payments sync both directions with QuickBooks Online, so deposits reconcile themselves instead of being re-keyed at month end.

Why the route has to be the spine

The route is the asset

Recurring service is the base that carries the overhead and sets the valuation. Software that treats those stops as a series of one-off jobs makes you rebuild your own business every Monday morning.

Repair is the margin

The profit sits in the work discovered on the route. It only gets captured if a technician can raise a priced, photographed estimate in the two minutes he is standing in front of the problem.

One stream, one ledger

Maintenance and repair bill together, on one invoice, against one authorization the customer actually gave. The money lands in the operator's account and reconciles itself — the office never re-keys a deposit.