Pay your crew the way you actually pay your crew.
Lead and assistant splits, per-job rates, deductions, scorecards, and a QuickBooks-compatible CSV. The pay rules you've been hand-calculating, finally encoded.
Why this matters
Most field service software treats every tech the same. But pay splits are how distributed crew operations actually work - the lead gets X percent, the assistant gets Y, the per-job rate changes based on job type, and there's almost always a deduction or bonus to layer on top. Doing that math in a spreadsheet at the end of every pay period is how you end up paying techs wrong, missing trips, and slowly losing the trust of the people doing the work.
What it does
Lead and assistant splits
Per-job split rules: lead gets X, assistant gets Y. Splits can vary by job type, project, or trip.
Per-job rate tables
Different job types pay different rates - install vs service vs survey. Encode it once, applied automatically.
Deductions and bonuses
One-line deductions for tools, fuel, draws. One-line bonuses for completion, scorecard tier, or whatever you want.
Scorecard tier multipliers
Tie pay rate to scorecard performance. Higher-tier techs get a higher rate on the same job. Encoded, not negotiated.
QuickBooks CSV export
Final payout report exports as a QuickBooks-compatible CSV. Drop it into QBO or QBD and the payment run is ready.
Tech-visible pay
Each tech can see their own running pay. No more 'what's my paycheck this week' phone calls.
How it works
Set up the rules once
Pay split percentages, per-job rate table, scorecard tiers, standard deductions. One-time setup.
Jobs close, pay is calculated
As jobs are marked complete, payout entries are calculated against the rules - no end-of-pay-period batch math.
Review the period
Open the pay period report. See every tech, every job, every deduction. Adjust what you want.
Export and pay
Export QuickBooks CSV. Drop it into QBO or QBD. Payments go out. Techs see the breakdown in their own LeadRoute view.
What it replaces
A spreadsheet that one person at the office has to maintain. The calls from techs at the end of the pay period asking why their check is off. The reconciliation between 'what the job sheet says' and 'what the spreadsheet says'. The bonus you forgot to add. The deduction you forgot to take. The trust loss that follows every mistake.
Automated Payouts questions, answered
Does it handle contractors and W-2 employees?
Yes - the pay rules don't care about employment status. The CSV export is structured so contractor 1099 payments and employee paycheck batches can both flow into QuickBooks correctly.
Does it integrate with QuickBooks directly?
Today: CSV export compatible with QBO and QBD. A live two-way QuickBooks sync is planned but not live yet. The CSV is built so most teams can drop it into a QuickBooks payment batch with no manual rework.
Can I split pay differently per job?
Yes - split percentages can be set globally, per project, or per job. Most teams set a default and override on the rare jobs that need it.
What about per-diem and travel reimbursements on convoy trips?
Trip-level expenses (per-diem, hotel, fuel reimbursement) flow into the payout report separately from job-rate pay. The tech sees both line items, the CSV exports both.
Can techs see their own running pay?
Yes - each tech sees their own jobs, splits, deductions, and projected payout for the open period. Eliminates the 'what am I making this week' phone calls.
See Automated Payouts in your own org.
Start a 14-day free trial. No card required.