Our Team
Three founders who spent years on the dispatch floor before writing a line of code.
Marcus Lindberg
CEO & Co-Founder
Ran a mid-sized freight brokerage in the Chicago suburbs for 8 years before co-founding HaulCortex. Previously a regional manager at Echo Global Logistics, where he oversaw a 60-person dispatch team handling 300+ daily loads across the Midwest corridor. Marcus is the product's first power user — he ran the internal prototype for 6 months before the company was incorporated.
Rachel Okafor
CTO & Co-Founder
Machine learning engineer with 9 years in applied logistics and supply chain prediction systems. Spent four years at project44 building carrier ETA models that processed 14 million shipment events per day. Rachel designed the HaulCortex lane scoring model architecture from scratch, including the nightly retraining pipeline and the carrier risk scoring system using FMCSA SMS data.
David Reyes
VP Operations & Co-Founder
15 years in freight brokerage operations, including 6 years as Director of Carrier Relations at a national 3PL running $120M in annual freight spend. David built HaulCortex's carrier compliance framework and leads all customer onboarding. His FMCSA safety data expertise underpins the carrier risk scoring module that monitors 47,000+ authority records daily.
A small team that ships and stays close to customers
At seed stage, we operate the way we ran our brokerage — tight feedback loops, direct customer access, and no layers between engineering and the problems we're solving.
Customer calls, weekly
Every customer gets a standing 30-minute weekly check-in during their first 90 days. Our founding team is on those calls — not account managers. We need to hear what's working and what isn't from the dispatchers actually using the product.
No feature without a conversation
We don't ship features based on competitor feature matrices. Every item on our roadmap came from a customer describing a specific dispatch scenario they couldn't solve. If we can't trace a feature back to a real load failure, it doesn't ship.
Dispatchers first, dashboards second
We design for the person who has 12 loads open at 2:30 PM on a Friday, not for the executive who reviews weekly reports. Speed of information delivery to the dispatcher matters more to us than making the analytics dashboard look impressive.
Where we are today
We're hiring people who understand freight
We don't need generalists. We need people who've worked a dispatch board, built carrier networks, or built data pipelines for logistics at scale. If that's you, we want to talk.
Contact Us About Opportunities