Product How It Works Integrations Pricing Customers Blog
Sign In Request Demo
About

Built in Dallas, where every late load has a name on it

Freightglint was founded in 2023 after years watching 3PL operations teams pad delivery windows because the only ETA they had came from the carrier who set it too tight at booking. We built the alternative.

Our Story

The problem started with a morning call sheet

Andre Coleman spent the better part of a decade working in logistics technology roles in the Dallas–Fort Worth area — close enough to the I-35 corridor to understand that freight operations buyers are not impressed by dashboards. They're measured by whether loads arrive when they told someone they would.

The specific problem became clear watching 3PL dispatch teams start each morning the same way: a list of loads that picked up the evening before, and 45 minutes of carrier calls to establish ETAs that the carrier would promptly miss. The ETAs weren't lies — they were just aggregated network averages that had nothing to do with this carrier, on this lane, at this time of year.

Andre founded Freightglint in Dallas in 2023 to build the thing 3PL ops teams actually needed: a prediction model trained on lane-specific carrier history, not a tracking platform or another visibility layer. Freightglint doesn't replace your TMS or your dispatcher — it tells them what time to write on the BOL.

In March 2026, we closed $750K in angel funding to expand the engineering team and deepen the carrier × lane × season dataset beyond the US South-Central corridors we launched on.

We are not a freight broker. We are not a TMS. We are not a shipment tracking platform. We are the layer between your TMS data and a delivery window your customer can plan around.

Team

The people building Freightglint

Andre Coleman, CEO and Co-Founder of Freightglint

Andre Coleman

CEO & Co-Founder

Logistics technology background in the DFW area for nearly a decade before founding Freightglint in 2023. Saw the same morning carrier-call ritual at too many 3PL ops desks to ignore it.

Freightglint team member, Head of Data Science

David Park

Head of Data Science

ML engineer specializing in time-series prediction on sparse, irregular freight data. Built the lane-carrier-season OTP indexing pipeline and the confidence band methodology from the ground up.

Freightglint team member, Head of Integrations

Sofia Reyes

Head of Integrations

Software engineer with deep experience in TMS and ELD API integration work. Leads connector development for McLeod, TMW, and Samsara — the plumbing that gets carrier data into the model.

Freightglint team member, Head of Customer Success

Mark Thornton

Head of Customer Success

15 years running freight ops at 3PLs across the Midwest and South-Central corridors. Joined Freightglint to make sure the product solves what ops teams actually need — not what an engineer assumes they need.

Dallas, TX

Why Dallas is the right place to build a freight data product

DFW ranks among the top US inland freight hubs. The I-35 corridor through Dallas connects Mexico, the Southwest, and the Midwest — some of the heaviest FTL volume in the country moves through this metro daily. The 3PLs and shippers operating here are not early-technology adopters. They are ops-focused teams who will tell you exactly when a product isn't solving the real problem.

That proximity shaped the product. The lane data we indexed first, the carrier integrations we prioritized, the accuracy methodology we chose — all of it reflects direct access to how South-Central corridor freight actually runs. Not academic. Not general-purpose.

Freightglint
1722 Routh Street, Suite 1000
Dallas, TX 75201
[email protected]
+1 (214) 580-6617
Dallas Texas downtown skyline at dusk representing the city's role as a major US freight and logistics corridor hub

Want to talk to the team directly?

Every demo call is with the people who built the product. No SDR hand-off, no qualifying call first. Bring your top lanes and we'll run the numbers live.