Building Klau in the Open, Week 14: The Dispatch Exchange

Week 14 of building Klau in the open.

Somehow it's Friday again.

This week was data pipes and customer data verification. Not glamorous, but it is the work that unlocks growth. Every active customer I'm working with at this stage is on the larger end of the hauler spectrum. That is not where I expected to be this early, and I'm not complaining. It's a gift.

The temptation with enterprise customers is to build one-off solutions: tape their unique requirements together and move on. I've been resisting that. Every problem gets solved as a product problem or it doesn't get solved. That discipline is what separates a SaaS from a services business, and I'm building a SaaS platform. The CLI from last week matured as I worked through new data formats and edge cases. And a new integration pattern came out of one customer's need and turned into something bigger.

File in, decisions out

One hauler needed Klau to pull jobs from their SFTP server, dispatch them to drivers, then write the results back. File in, decisions out. No API, no integration project, no unnecessary ceremony. Just automated dispatching through a folder.

That pattern is now the Dispatch Exchange, available to all Klau users. Point it at a file store hosted by Klau or connect your own SFTP. It's fully configurable in settings, with nothing hardcoded.

I also fit in some dozer time in the canyon, getting ready for some April rain this weekend. A good way to spend a week.

Still building.

Originally posted on LinkedIn on April 10, 2026.