Brett Murdock has been trying to solve field-tech pay since 2015 — he calls it "a stick in my craw." Not because it's complicated to him, but because it's easy to get wrong, and when it goes wrong, it's sand in the gears of the systems he's trying to build.
A stick in his craw since 2015
Brett likes to keep the main thing the main thing: serving customers and keeping them happy. Pay should just be running quietly in the background, doing its job — not something anyone has to think about. For years, that wasn't the reality. Overpayments, underpayments, and the manual work of getting them fixed kept pulling attention away from the business he was actually trying to run.
Deleting the steps instead of managing them
To make pay run quietly, Murdock connected its Skimmer field-service data straight into FieldPay. Brett's logic was simple:
All the data is sitting there in Skimmer anyways — we can delete a lot of steps in the process.
From there, FieldPay quietly generates a simple invoice/payout request on each tech's behalf, in their own business name, addressed to Murdock Pools — exactly the paperwork a real 1099 relationship calls for, without anyone having to sit down and produce it.
The team feels it first
Murdock's team of 14 techs feel it first. Brett's team describes the experience as "overdelivers" — getting paid fast, often, and with the critical reporting at their fingertips.
On the admin side, what used to be 2–3x the manual work has settled down since going live. One of Brett's ops folks put it plainly a few days in:
"We are good."
The only number that matters
And Brett's own bar for whether it's working is refreshingly simple:
The number I approved matches what the bank takes out. I never have to think about this again, and I can onboard and grow the business with confidence.