I Went to Denver Looking for a Dispatch Problem. I Found an Outlook Calendar.
What a fuel operator taught me about looking past the workflow that looks broken and finding the one that actually costs money.
In 2024 I flew to Denver to visit my friend Pete.
Pete runs a fueling company. He knows everyone in the industry and his opinion carries weight because he has been inside more fuel operations than most people will see in a career. When he offered to take me to see a friend who ran a bigger operation, I said yes immediately.
I went in thinking I knew what I was going to find.
Dispatch was the problem. I had been thinking about it for months. Mid-market fuel distributors running routes on whiteboards and phone calls. Drivers showing up to sites without clear instructions. Loads getting missed. Customers calling to find out where their fuel was.
I was going to see it in the field and it was going to confirm everything I had been thinking.
The Outlook calendar
We walked into the dispatch office and the owner pulled up his screen.
It was an Outlook calendar.
Every driver had the app on their phone. Recurring orders were scheduled in advance. The owner could see the day’s routes at a glance. Drivers knew their stops before they left the terminal.
I asked him about it.
“It works for us,” he said. “Every driver has it. Easy to maintain recurring orders. We have been doing it this way for years.”
He was not embarrassed. He was not describing a workaround he hoped to replace someday. He was describing a system that worked.
And he was right. Fuel was going out on time. Customers were getting their deliveries. Drivers knew where they were going.
The dispatch problem I flew to Denver to confirm did not exist.
I flew home with a lot to think about.
What I got wrong
I had made the mistake that is easy to make when you are building software for an industry you have not worked inside.
I looked at a tool and I saw a gap. I assumed that because Outlook was not designed for fuel dispatch, the people using it must be struggling.
They were not struggling. They had found something that worked and built their operation around it.
I was solving for the thing I could see. I had not yet spent enough time asking about the thing that was actually costing people money.
Two years later
In 2025 I decided to build Fueleo.
Before writing a line of code, I started having real conversations with fuel marketers. Operators, billing teams, controllers, owners. I asked them what was actually breaking in their operations. Not what looked broken from the outside. What they felt every day.
The same answer kept coming up.
The fuel always goes out on time. The invoice takes three to five days.
A driver delivers 5,000 gallons on a Tuesday morning. The customer has fuel in their tank by 10am. The invoice does not arrive until Friday. Sometimes the following Monday.
Not because anyone is being careless. Because the handoffs between delivery and invoice are long and nobody owns the gap between them.
The driver brings back the ticket. Dispatch closes the load. Billing checks the gallons. Pricing verifies the rack or contract rate. Someone checks freight, fuel surcharge, taxes, exemptions, fees. Then the invoice finally gets created and pushed into accounting.
Each step adds hours. The hours add up to days. And the cash sits unbilled the whole time.
The delivery was never the problem.
The invoice was.
What the Denver trip actually taught me
Looking back, the Outlook calendar was the most important thing I saw on that trip.
Not because it showed me a gap to fill. Because it showed me I was looking at the wrong gap.
The operator had solved dispatch in a way that worked for his operation. What he had not solved, what nobody had solved cleanly, was the three to five day window between a completed delivery and a sent invoice.
That window is where cash flow sits unbilled. Where pricing errors go undetected until the customer calls. Where customer trust quietly erodes one late invoice at a time.
I would not have understood any of that if I had walked into Denver and found the dispatch chaos I was expecting. I would have built a dispatch tool and moved on.
Instead I walked out of an Outlook calendar demo with the most important question I have asked in this industry.
If dispatch is working fine, what is actually broken?
Two years of conversations with fuel marketers gave me the answer.
What I am still figuring out
I do not think I have gotten everything right since Denver.
There are parts of the fuel distribution workflow that are more complex than I understood when I started building. The way common carrier operations handle carrier settlements. The way wet hosing billing differs from tank delivery billing. The way tax exemption compliance sits between systems that were never designed to talk to each other.
Every operator conversation surfaces something I did not account for. That is not comfortable to admit when you are building software that people are trusting with their operations.
But it is true.
The thing I am most certain about is the thing the Denver trip taught me. The best way to understand what is broken is to go see what is working and ask why.
The Outlook calendar was working. That question led me to the invoice.
I am still trying to earn the answer the same way: by walking into real operations, noticing what already works, and asking what still costs money.
About the author
I’m Dibyesh Giri., founder of Fueleo. I spend my time talking to fuel marketers about the messy handoffs between pricing, dispatch, delivery, BOLs, invoicing, inventory, and accounting. This newsletter is where I write about what I find.
Great read Dibyesh! I got a front row seat to your thesis building a national brokerage from the ground up, Thanks for sharing.