Skimmer’s mobile app already starts a timer the moment a technician taps into a route stop and stops it when they tap Finish — but that timer exists to show a customer how long a visit took, not to feed a reviewed payroll record. There is no manager approval step, no dispute trail, and no payroll workflow published for that data. Keito is the layer in between: AI-drafted time entries a technician confirms, a reviewer settles billable and payroll status, and the reviewed hours become the evidence behind labor cost and client invoices.
Illustrative review queue
Illustrative billing period
Hours reviewed
Entries confirmed
46
Stops billed
210
Technicians reviewed
6
Hours tied to each route
Technician, property, and stop count on every entry
Reviewed before payroll
A reviewer confirms hours before the period closes
Evidence behind labor cost
Approved hours back payroll and the client invoice
Skimmer’s app starts a per-stop timer the moment a technician taps into a route stop and stops it on Finish, recording the duration for the client to see. Skimmer’s own help documentation and feature pages do not describe a manager review step, a dispute or correction record, or a payroll workflow for that recorded time before it becomes part of a labor-cost or profit calculation — only a technician-initiated reset for an early start. Keito answers the question that leaves open: did a reviewer actually confirm each technician’s hours, not just record a stop duration, before those hours became a labor cost and a paycheck.
Set up technicians, routes, and reviewers in Keito in days — Skimmer keeps running route scheduling, technician stop timing, invoicing, and CRM exactly as it does today.
Keito drafts a time entry from the work that happened on a technician’s route, so a technician confirms hours for the day instead of relying on a customer-facing stop timer with no review step.
A reviewer approves billable and payroll status before the period closes, then hands the approved hours to payroll or whichever system bills the client.
A per-stop timer without a payroll review step
Skimmer is published as pool and spa service software: routing, scheduling, invoicing, customer communication, and a mobile app technicians use in the field. That app includes a genuine timer — tapping into a route stop starts the clock automatically, and tapping Finish stops it, with the duration recorded in the visit history. Skimmer’s own help center describes the purpose plainly: showing a customer how long a technician spent at their pool, if they ask for proof. What Skimmer’s published documentation does not describe, across its FAQ, feature pages, and Profit Report guidance, is a manager review or approval step for that recorded time, a dispute or correction record, or a payroll workflow that turns a stop duration into a reviewed hour. A technician who starts the timer early can reset it themselves through a “Restart Time” button, but nothing in Skimmer’s public material shows a manager confirming, disputing, or approving that time before it feeds into a Profit Report’s labor-cost line or a payroll run. Keito’s argument is not that pool service companies need a new routing, scheduling, or invoicing platform — Skimmer already publishes all three, priced per serviced location with unlimited technicians included. It is that the record behind a technician’s hours deserves a reviewed, payroll-ready confirmation, not just a customer-facing stop timer. Keito drafts a time entry for the work a technician did, the technician confirms it, and a reviewer settles billable and payroll status, with the reason for any change recorded, before the hours become evidence for labor cost or a paycheck. The boundary is deliberate: Keito has no routing, scheduling, chemical readings, or invoicing, and it claims no native Skimmer integration, automatic import, or synchronisation. Skimmer keeps running the route; Keito is where the hours behind it get reviewed.
Choose Skimmer when the business needs route optimization, scheduling, invoicing, and customer communication running from one pool-service platform
Choose Keito when the problem is that Skimmer’s stop timer has no manager review or payroll workflow behind it
Prove it in one pay period: Keito runs alongside Skimmer, reviewing technician hours without touching routing or invoicing
Workflow fit
Keito keeps Skimmer alternative connected to client, project, billable status, approval, and invoice context before the work reaches finance.
Choose Skimmer when the business needs route optimization, scheduling, invoicing, and customer communication running from one pool-service platform
Choose Keito when the problem is that Skimmer’s stop timer has no manager review or payroll workflow behind it
Prove it in one pay period: Keito runs alongside Skimmer, reviewing technician hours without touching routing or invoicing
Keito drafts a time entry from the work a technician did on their route; the technician confirms and corrects it instead of relying on a stop timer built for customer proof, not payroll.
Skimmer’s stop timer records duration with no documented manager approval, dispute, or payroll step; Keito’s reviewer settles billable and payroll status for each entry before the period closes.
Reviewers approve technician hours and hand the evidence to payroll or whichever system bills the client, through exports the team designs and tests itself.
The difference is not just recording time. It is whether the record can support billing, project decisions, and client conversations.
Product shape
A standalone workspace for reviewed, payroll-ready technician hours and billing evidence.
Skimmer publishes a pool-and-spa-service platform — routing, scheduling, invoicing, customer communication, and a technician mobile app.
How time is captured
AI drafts a route-specific entry from the work that happened; the technician confirms it, and a reviewer approves before it becomes a labor cost or paycheck.
Skimmer’s app auto-starts a timer when a technician taps into a route stop and stops it on Finish, recording duration mainly for customer-facing proof of visit.
Review before payroll
A reviewer settles billable and payroll status per entry, with any change reasoned and recorded, before the period closes.
Skimmer’s published material describes no manager review, dispute record, or payroll workflow for recorded stop time — only a technician-initiated reset for an early start.
Billing model fit
Built for confirming the specific hours behind a technician’s route before they become a labor cost or a paycheck.
Built around routing, scheduling, invoicing, and customer communication for a pool service business, with stop timing as a supporting feature, not a payroll gate.
Pricing and adoption
Published flat team pricing and a setup measured in days, run alongside Skimmer.
Skimmer prices per serviced location — $1 a month per location ($49 minimum) on Getting Started, $2 a month per location ($98 minimum) on Scaling Up, and custom Enterprise pricing above 1,000 locations — with unlimited technicians included at every tier.
Data movement
Team-designed, tested exports and API handoffs moved in deliberate stages.
No native Keito-Skimmer import or automatic synchronisation is assumed in either direction; Skimmer’s own QuickBooks Online sync covers paid invoices, not payroll.
It is software a pool or spa service business adopts instead of, or alongside, Skimmer, which runs route scheduling, invoicing, customer communication, and a technician mobile app. Because Skimmer covers that much of the operation, an alternative rarely replaces all of it at once. Keito is the alternative for the review gap Skimmer leaves behind its stop timer: AI-drafted entries confirmed by the technician who did the work, reviewed before those hours become a labor cost or a paycheck.
Skimmer does both, to a point. Its mobile app auto-starts a timer when a technician taps into a route stop and stops it when they tap Finish, recording the duration in the visit history — Skimmer’s own help center describes the purpose as showing a customer how long a visit took, if they ask for proof. What Skimmer’s published documentation does not describe is a manager review step, a dispute or correction record, or a payroll workflow for that recorded time before it factors into a Profit Report’s labor-cost line.
The gap is review, not capture. Skimmer already times each stop a technician visits, but nothing in its public material shows a manager confirming, disputing, or approving that time before it is used for labor cost or payroll. Keito adds the missing layer: AI drafts a time entry from a technician’s route, the technician confirms it, and a reviewer settles billable and payroll status, with a reason recorded for any change, before the hours become evidence for a paycheck or a client invoice. Skimmer still owns routing, scheduling, invoicing, and customer communication; Keito owns the reviewed hours record.
Choose Skimmer when the business needs route optimization, scheduling, invoicing, and customer communication running from one pool-service platform — it already publishes all of that, priced per serviced location with unlimited technicians included. Keito does not reproduce any of it: no routing, no scheduling, no chemical readings, no invoicing. It is the wrong choice if the immediate need is a pool-service operations platform rather than a reviewed record of technician hours.
Each reviewed record keeps the technician, route or property, duration, description, billable status, payroll status, rate context, reviewer, approval state, and pay period, tied to the specific work a technician did rather than a customer-facing stop timer. That package backs the paycheck or the invoice line Skimmer, or any other system, turns into a bill, and gives an office manager a reviewed answer when a technician’s hours are questioned.
No. Keito claims no native Skimmer integration, automatic import, or two-way synchronisation — Skimmer’s own routing, scheduling, stop timer, and QuickBooks Online sync belong to its platform, not Keito’s. Capture in Keito is its own workflow: AI-drafted, typed, timed, and manually entered records that pass review before becoming payroll or invoice evidence. A business can keep Skimmer for routing, scheduling, and invoicing and run Keito alongside it as the review layer for technician hours, with any transfer between them designed and tested by the team.
Solo includes 1 licensed user, unlimited AI agents, Mac desktop and iOS apps, Stripe payments, and standard CSV and Excel exports. Pro adds your team. Business adds integrations, planning, advanced reporting, and stronger controls.
1 licensed user
For independent consultants, freelancers, and small studios running work with AI agents.
Team collaboration
For teams that need shared workspaces, approvals, and team-level project visibility.
Advanced operations
For organizations that need integrations, planning, advanced reporting, and stronger controls.
AI agents do not require licenses on any plan.
Solo, Pro, and Business can use API keys for agent workflows.
Solo, Pro, and Business include standard CSV and Excel data export.
Start with Solo, add people on Pro when you need reviewers or collaborators, and see how Keito turns tracked effort into clearer reports.