For an operator in the Southeast with a fleet of 200+

Did the fuel go into your trucks?

No new software to learn. I connect what you already run and build on top of it. Then I tell theft apart from a keyed truck number and a bad sensor. Evidence, not accusations.

Fleet AI work now runs through AxleLens, my fleet fuel and loss audit practice. See the AxleLens AI systems page.

Book a 15-minute call See the Monday report

No new software to install.
Keys you can pull any time.
No long contract.

Your Fleet

Fuel review for this week

This week · Sent Monday

Week at a glance

Diesel fills: 0
Gallons: 0
Spend: $0.00
Engine MPG: 0.0

0.0%

in a fleet tank

Fuel verified in tank

88% we could check. Unclear fills are never clean or theft.

340 gal · $2,220 bought on the card, never showed up in a tank.

MEDIUMPull receipts and video

N. Vargas · unit 3704

GPS put the truck about 41 mi from a stop in Ocala late last Tuesday.

Proof: $2,000+ caught in week one
Proof: 200+ truck fleet, Southeast
Proof: Not a new tool. Built on what you already run.
Proof: Daily manager actions. Weekly CEO numbers.

The problem

The leak is already in your data.

Your fuel card, GPS, and TMS each hold a piece. They don't sit together, so a typo and a stolen fill look the same.

01
Did the fuel go into your trucks?
Card hits a pump. GPS says the unit was miles away. If nobody lines those up, you pay anyway.
02
A typo can look like theft
Wrong truck number at the pump. Erratic tank sensor. Those are not the same as gallons that never hit a fleet tank.
03
The data is there. The time is not.
TMS, Samsara, Relay, safety. Four logins. The leak lives in the gap.

The solution

Connect. Line it up. Act.

This is not another tool to install. I connect the software you already run and build on top of it. For an operator in the Southeast with a fleet of 200+, I built that layer. Dispatch, operations, and fuel payments sit in one read-only connector on Claude. You keep the keys.

Your tools. I connect them.

TMS
Samsara
Motive
Relay
WEX

Alerts
Reports
Answers

01
Connect
No new software. You grant read-only access to the tools you already run. I can't change a load, a card, or a driver record.
02
Line it up
Every swipe, GPS ping, load, and idle hour matches by truck, driver, and time. Unverifiable fills stay unverifiable.
03
Act
Suspects come with evidence to review. Typos go to dispatch. Sensors that cannot be trusted get flagged. Not accusations.

An initial setup and audit, then a small monthly fee to keep it running. The fuel it finds is meant to dwarf what you pay. Done in 2 weeks from the day I get access. Managers get a daily list. The CEO gets the Monday numbers. The named practice for this fuel work is AxleLens, same operator as the rest of this site.

The Monday inbox

What lands in your inbox every Monday

Week at a glance. Fuel verified in tank. Fills to review. Truck number mixups. Fuel economy. Sensor and data health. Theft stays apart from a typo and a bad sensor.

Your Fleet

Fuel review for this week

This week · Sent Monday

Week at a glance

Diesel fills: 0
Gallons: 0
Spend: $0.00
Engine MPG: 0.0
Cost / mile: $0.00

Fleet engine MPG uses 172,800 miles and 25,890 gallons burned. Cost per mile is on that same engine basis.

Daily manager actions

What ops already saw this morning

01N. Vargas, unit 3704. GPS about 41 mi from the pump late last Tuesday. Pull receipts and video.
02F. Adeyemi keyed unit 6120 and drove 6210. Ops: ask drivers to enter their own unit at the pump.
03Tank sensor on unit 4491 jumped around. Do not treat those fills as clean or as theft.

Names and figures changed.

Beyond fuel

I also wire the rest of the shop.

Fuel is the door. This is not a new system. I build on the tools you already run. No rip-and-replace. The same Southeast operator with 200+ trucks got dispatch, operations, and fuel payments on one layer, with AI across all of it. Managers get a daily action list. The CEO gets the weekly numbers. I can't name them here.

Ask your fleet

Type a question in plain English. Dispatch, safety, and finance get an answer from the live systems.

Ask your fleet

Reading GPS and card swipes…

Put the routine on a timer

Morning exception list. Off-hours swipe to the fleet manager. IFTA prep. Detention by shipper. Nothing writes back. A person decides.

A simple automation

01 Trigger
Off-hours swipe
02 Check
Match GPS
03 Action
Alert manager

Read-only. A person still decides.

Case study

An operator in the Southeast, fleet of 200+

I can't name them. I can tell you what I did.

$2,000+
caught in week one: $18,400
saved in the first 4 months: 11%
drop in idle hours: 6 hrs/week
reporting removed

Situation. Cash was walking out of a 200+ truck Southeast fleet. Some of it was theft. Some of it was a keyed truck number or a tank sensor that could not be trusted. The tools they already had knew pieces of the story. Nobody had lined them up.

What I built. A layer on the stack they already used. Not a new install. It ties in dispatch, operations, and fuel payments. AI reads those systems together. Managers get daily action items. The CEO gets a weekly report on the numbers.

What we found. In the first week it caught over $2,000 in theft and fuel card misuse. It also told theft apart from data entry and sensor issues. 14 later flags added $3,180 once receipts and video were pulled.

What changed. Managers act from a daily list. Dispatch gets the exact fix, like having drivers key their own truck number. The CEO sees the numbers every week. Longer-run total: $18,400 saved in the first 4 months.

“The Monday report is the first time I could see a stolen fill next to a typed truck number. Managers act from a list. We stopped paying for gallons that never hit a tank.”
Operations Director, Southeast fleet of 200+

Your data stays yours.

Read-only
I can read the data. I can't change a load or a card limit.
Your keys
You grant access one system at a time. Revoke any key from your side.
Your report
Findings stay yours, whether you keep working with me or not.

I use HIPAA and SOC 2-grade habits from healthcare work. This service does not hold a SOC 2 report or HIPAA cert. Keys stay in your accounts. I keep working copies only for the engagement and delete them within 30 days after we stop, unless you ask me to keep a finding pack. I do not write back to your systems. I do not use your fleet data to train public models. You can revoke access any time.

Built to cost less than it finds.

Start

Initial setup and audit

Two weeks from the day I get access. Monday report, daily action list, walkthrough. You keep the findings.

Then

A small monthly fee

Keeps the connection live. Fleets recover more than they spend. If the audit does not pay, we stop.

Short answers

What access do you need?
No new software. Read-only access to the fuel cards, telematics, TMS, and safety system you already run. You make the keys. You can kill them any time.
Do I have to install new software?
No. This is not another tool to learn. I connect to the systems you already run and build on top of them. Samsara and Motive. Relay, WEX, and Comdata. Your TMS and safety stack. If you run something else, ask.
How long does the audit take?
2 weeks from the day I get access. Setup on your side is usually under an hour.
Who does the work?
I do. For an operator in the Southeast with a fleet of 200+, I built the same kind of layer.

Let's look at your fleet.

15 minutes. Your trucks, your systems, whether an audit is worth it. For an operator in the Southeast with a fleet of 200+, I already built this.

Zack ShieldsZack Shields Consultingzack-shields.com LinkedIn

Did the fuel go into your trucks?

The leak is already in your data.