Every software company has an origin story. Ours starts with a spreadsheet — a massive, error-prone, soul-crushing spreadsheet that took 15 hours a week to maintain.
The Problem We Saw
We spent years working with FedEx Ground ISP contractors. The same story came up over and over: smart, hardworking business owners spending their evenings and weekends hunched over Excel, manually calculating per-stop pay for every driver, cross-referencing fuel card transactions, and triple-checking bonus calculations.
These weren't small operations. Many had 20, 30, or 50+ drivers across multiple CSAs. And every single one was doing payroll the same way — manually.
The math wasn't simple either:
- Per-stop pay varies by route, day of week, and stop volume
- Fuel deductions require matching individual fuel card transactions to specific drivers
- Bonuses differ by performance tier, attendance, and safety metrics
- Overtime calculations depend on state laws that vary wildly
- Multi-CSA operations mean different pay rates for different service areas
A single payroll run meant pulling data from FedEx settlement reports, fuel card portals, time tracking apps, and bonus spreadsheets — then manually combining them into one coherent paycheck per driver.
What Existing Solutions Got Wrong
We looked at every payroll tool on the market. ADP, Gusto, Paychex — they're all excellent at what they do. But none of them understood FedEx ISP payroll.
Generic payroll tools assume hourly or salaried pay. They can handle "40 hours × $20/hour" all day long. But they can't handle "237 stops × $1.35/stop + 6th day bonus + fuel deduction from WEX card ending in 4521 minus the $14.67 in-store purchase that needs to be flagged."
That's not a criticism of those tools. They're designed for a different world. FedEx ISP payroll is a fundamentally different calculation model that requires purpose-built software.
We also saw ISP owners trying to build their own solutions — custom Google Sheets with dozens of tabs, macros that broke every other week, and Access databases from 2008 that everyone was afraid to touch. These homegrown solutions worked, barely, until they didn't. And when they broke, payroll was late, drivers were upset, and the ISP owner was up until 2 AM fixing formulas.
What We Set Out to Build
FleetWage was designed from day one around a simple idea: payroll for FedEx ISPs should take minutes, not hours.
We started with the core calculation engine — the part that takes FedEx settlement data, fuel card transactions, and time records, and turns them into accurate per-driver paychecks. Getting this right was the hardest part. The edge cases are endless:
- What happens when a driver works two different CSAs in the same week?
- How do you handle a fuel card transaction that was declined but shows as pending?
- What's the overtime calculation when a driver works in both a daily and weekly overtime state?
- How do you split a bonus between two pay periods when a driver switches routes mid-week?
We spent months talking to ISP owners, learning their edge cases, and building a system that handles them automatically.
The Features That Matter Most
Automatic Per-Stop Pay Calculation
Import your FedEx settlement report, and FleetWage calculates per-stop pay for every driver on every route. No spreadsheet. No manual data entry. No formulas to maintain.
Fuel Card Integration
Connect your WEX, Coast Pay, Sunoco, or other fuel card account, and transactions are automatically imported, matched to drivers, and applied as deductions. Suspicious transactions are flagged for review.
Bonus Management
Set up your bonus rules once — 6th day bonuses, safety bonuses, attendance bonuses, performance tiers — and FleetWage applies them automatically every pay period.
Multi-CSA Support
Running multiple CSAs with different pay rates? FleetWage handles it. Each CSA can have its own rate structure, and drivers who work across CSAs are paid correctly for each.
Payroll Provider Export
FleetWage isn't replacing ADP or Gusto — it's filling the gap they can't. Calculate wages in FleetWage, then export to your existing payroll provider for tax withholding and direct deposit.
What We've Learned
Since launching FleetWage, the feedback from ISP owners has reinforced what we believed from the start: the pain is real, and it's universal.
ISP owners tell us they've gone from 10-15 hours per week on payroll to under an hour. Drivers tell us they finally understand their pay stubs. And the most common feedback we get? "I wish I had this years ago."
We've also learned that payroll is just the starting point. When you have accurate, real-time payroll data, you can answer questions that used to require a forensic accounting exercise:
- Which routes are actually profitable after labor costs?
- Which drivers are costing you money in fuel overages?
- What's your true cost per stop, including bonuses and deductions?
These insights help ISP owners make better business decisions — not just faster paychecks.
What's Next
We're continuing to build the tools that FedEx ISP owners actually need. That means deeper integrations, better reporting, and more automation. Every feature we add starts with the same question: "Will this save an ISP owner time or money?"
If the answer is yes, we build it. If the answer is "it would be cool but nobody asked for it," we don't.
FleetWage exists because FedEx ISP payroll is a unique problem that deserves a purpose-built solution. We're proud to be that solution, and we're just getting started.