Building Klau in the Open, Week 4: A Scorecard Tool

Week four of building Klau in the open.

I did two more demos this week. Both were with haulers larger than I expected to be talking to this early. They have capable teams and strong human dispatchers. They know where their inefficiencies are, but they haven't found software that fits.

The feedback has been very useful. It pushed me to simplify the pricing model. I'm still checking it with a few more people before I share the details publicly, but it's close.

It also pushed me to build something new: a scorecard tool.

You upload a day of dispatched jobs. Klau runs them through the same algorithm it uses for automated dispatching. It finds areas to improve and puts a number on each one: hours saved, fuel saved, yard returns eliminated, and extra job capacity.

The numbers matter. But what I care about is what's behind them: a dispatcher with less chaos in the day, drivers who aren't running in circles, and people getting home on time.

I've always believed software should sell itself. This feels like a way for Klau to do that. Show, don't tell.

Next week I'm sharing the scorecard with a few haulers to see if it helps the value make sense. If you want to run your own data through it, reach out.

It's a short week for me. I'm headed to King of the Hammers on Wednesday with my son. If you like horsepower and engineering, the live streams are worth watching. It's desert and rock racing at its most extreme.

Thank you to everyone who has connected, asked questions, and shared feedback. Klau is better because of you.

Originally posted on LinkedIn on January 31, 2026.