Twenty-two months of route data, one screen.

Route Balance didn’t start as a product. It started as a spreadsheet.

A real South Florida tool truck route. Every day: drive the stops, collect what you can, note who promised what, try to remember which account drifted past 30 days. At the end of the day, sit down and try to reconcile what happened. How much did you actually collect? Which stop is now at 45 days? Did the guy who promised Thursday actually pay?

The answer was always the same: a spreadsheet with manually entered balances, a separate text file of notes, and a lot of mental arithmetic.

That spreadsheet eventually broke. Not technically — it just stopped working as a tool. Too many accounts, too many aging buckets, too many things to track. The spreadsheet told you what was in it. It couldn’t tell you what was actually happening on the route.

From spreadsheet to database.

The first version wasn’t a product. It was a database query. Took the dealer’s business export, loaded it into a database table, and ran a nightly script that flagged anything past 30 days. That was it. But the signal was immediately useful — you could see, at 6 AM, which stops to prioritize before starting the truck.

That nightly script became the daily briefing.

What 22 months teaches you.

Twenty-two months of real route data tells you things no benchmark can. It tells you which customers make a promise on Thursday and pay it by Monday — and which customers make the same promise five months in a row. It tells you which aging bucket is where money actually goes to die (hint: 90+ days, rarely recoverable after 120). It tells you that warranty credits take an average of 23 days to clear after you submit, and that the variance between what your dealer records show and what actually came back is almost never zero.

Every feature in Route Balance came from observing one of these patterns. The broken-promise alert came from watching a $1,200 account drift to 90 days despite four verbal commitments. The warranty reconciliation came from finding $400 in credits the business export showed as pending that had actually been applied three weeks earlier. The cash forecast came from trying to answer one question before the month was over: am I going to have a bad week?

The cockpit.

By month 14, the database had grown into a dashboard. Stop list in order. Balance aging per account — current, 30-day, 60-day, 90+. Notes attached to each stop. The whole thing visible in one scroll.

We called it the cockpit. That’s still what it is today.

The insight that stuck: you don’t need a dozen screens. You need four things — where to go, what they owe, what they’ve promised, and what actually happened last time — and you need them in order, fast, before you start the truck.

What we built.

Today Route Balance is that cockpit, plus the intelligence layer that makes it actionable. The daily briefing. The risk surface that ranks every customer by composite exposure. The payment links so a phone call ends with money in your account. The warranty reconciliation so you know what credits are still sitting open. The provenance trail so every number traces back to the source file that produced it.

All of it came from 22 months of watching a real route generate real numbers and asking: what does a dealer actually need to see, right now, to make a better decision?

The roadmap is the same question, repeated. If you’re running a tool truck route, we’d like to hear what the answer looks like on your end.