I Left My W-2 to Build a TMS From My Dispatch Desk

I did not set out to become a software founder in the Silicon Valley sense of the word. I left my W-2 because I wanted to build something of my own and because I was tired of depending on systems that never seemed designed for the people actually doing the work. Every TMS I touched had pieces I could use, but none of them felt like they were built from the perspective of someone covering freight, checking in on trucks, solving problems after hours, and trying to protect margin at the same time.

That frustration turned into 20-2 Dispatch. The name comes from Exodus 20:2, and that matters to me because the foundation behind this business is faith, obedience, and gratitude. I wanted the company name to mean something deeper than a software label. The platform grew the same way the brokerage work did: one real problem at a time, one workflow at a time, tested in live operations instead of inside a product-planning vacuum.

The difference between a broker who builds and a developer who guesses is that the broker feels the pain in real time. I know exactly what it feels like when a carrier packet is incomplete, when a tracking update goes stale, when a rate confirmation has to go out right now, or when a customer follow-up falls through because the CRM and TMS live in different worlds. I built this from the dispatch desk while still moving freight daily because I wanted every feature to survive contact with the real job.

That is also why the tone of the product is different. I am not trying to impress people with buzzwords. I am trying to give brokers a workbench that respects how they actually operate. If something in 20-2 Dispatch is there, it is because it helped me or someone like me do the work better. That is the standard. Not what looks good in a demo, but what holds up when the day gets messy.