Start with the whole trip.
Account for loaded miles, the return journey, driver time, fuel, equipment, and overhead.
Pricing and profitability software for fuel haulers. Turn your operating costs, route details, and customer terms into a rate you can explain.
+ $116.00 fuel surcharge per load
A familiar spreadsheet can hide an old assumption. TankerIQ brings the inputs into view, so you can see what makes a lane worth running.
Account for loaded miles, the return journey, driver time, fuel, equipment, and overhead.
Separate billable mileage and surcharge revenue from the miles and diesel your truck actually uses.
Compare aggressive and higher-return pricing while keeping the underlying operating costs visible.
Try a simplified quote. Change the distance or target margin and see how the base freight rate responds.
Illustrative data only. This example uses 7,800 gallons, an assumed $250 fixed trip cost plus $3.40 per loaded mile for full-trip costs, and a sample $1.16 per loaded mile surcharge. It is not a live fuel index or a bid recommendation.
Trip cost = $250 + loaded miles × $3.40.
Required revenue = cost ÷ (1 − margin).
Base freight = (required revenue − surcharge) ÷ 7,800 gallons.
Profit = required revenue − trip cost.
The route calculator is the starting point. Pilot feedback will guide what we build next.
Editable cost assumptions, margin scenarios, surcharge inputs, and a clear breakdown of the calculation.
Import customer RFPs, review rates across lanes, preserve supplied mileage, and export a completed bid.
Compare completed trips with quote assumptions to understand where time, cost, and margin changed.
We’re looking for fuel-hauling operators who prepare quotes and RFPs today. Tell us where the work gets difficult and help test a more useful approach.
TankerIQ is in development. The route calculator is a working prototype; broader bid management and completed-trip analysis are planned. Pilot scope and any future pricing will be discussed before you commit.
The initial focus is pricing and bid preparation. The aim is to fit alongside your existing operation. No dispatch integrations are being promised at this stage.
No. Initial conversations focus on your process. Any prototype testing can use sample or anonymized lane information.