At $25 a day, a railcar sounds like a modest problem. Leave enough of them idle, though, and the arithmetic becomes uncomfortable. In one IntelliTrans customer case, releasing 45 cars a day translated into roughly $410,000 in annual savings. The work involved finding shipment exceptions, coordinating with carriers, and getting equipment moving. A little less waiting became a lot less money.
- Software for the bulky stuff: chemicals, lumber, grain, metals, and other industrial freight.
- Rail and truck tools connect shipment planning, tracking, yards, docks, and invoices.
- Managed services add people who investigate delays and work with carriers to resolve them.
This is a useful way into IntelliTrans, because transportation technology is often described through what it can show. A map. An arrival estimate. A warning. Those are valuable. But a warning also creates a job for somebody. Who calls the carrier? Who checks whether a different movement is possible? Who follows the problem until it closes?
01 / The map needs a next move
IntelliTrans serves bulk and break-bulk shippers, a market whose vocabulary includes hopper cars, transload facilities, demurrage, and fleet cycles. Its customers move the materials other businesses turn into things. A delayed delivery can therefore become an inventory problem, a production problem, or a customer-service problem before anyone thinks to call it a software problem.
The company’s transportation management system brings procurement, execution, visibility, and settlement into connected workflows. Rail customers can add tools for equipment maintenance, yard operations, transloading, and fleet sizing. Truck customers get tendering, carrier management, dock scheduling, and freight audit capabilities. The appeal is continuity: the shipment being planned is the shipment being watched and, eventually, the shipment being paid for.
Its managed-services staff work alongside that software. They identify exceptions and coordinate responses with carriers. Conway, Arkansas, houses the largest concentration of its customer-facing specialists. HWI, the refractory-products manufacturer, provides a named customer testimonial; many of the company’s numerical case studies keep the customer anonymous. The distinction matters when reading the results.
02 / Forty-five cars, one expensive pause
Consider the intervention case. The customer moved approximately 24,000 shipments annually, with 8% delayed in transit. Cars sat in delayed or bad-order status while inventory costs rose. IntelliTrans introduced systematic exception identification, carrier scorecards, and a repeatable process for resolving trouble. Its personnel worked with carriers and explored alternatives.
The company reports freeing 45 cars per day. Its savings calculation is refreshingly inspectable: 45 cars multiplied by $25 per day, multiplied by 365 days, equals $410,625. That is the basis for the rounded $410,000 figure. It measures the value assigned to released equipment capacity; it should not be read as a software subscription price or a guaranteed return.
A separate service-improvement case began with on-time delivery around 75%, inconsistent handling of shipment changes, and incomplete customer data. The response included defined responsibilities, standard procedures, carrier follow-up, and transportation software. IntelliTrans reports delivery performance reaching 96%, alongside $12.4 million in savings over ten months, described as validated by the customer’s finance team.
The useful lesson is almost stubbornly ordinary. Clean up the records. Decide who owns exceptions. Follow up with the people moving the freight. A buyer can copy those disciplines before buying anything. The software helps make them repeatable across a larger operation.
The same habit extends to freight bills. In another anonymous case, manual accounts-payable work and inaccurate invoices left a shipper missing carrier payments. IntelliTrans stored contract rates, tariffs, additional charges, and fuel surcharges in the system, then used those records to audit bills and trigger payment. The company reports clearing more than $3 million in overdue balances within two months and achieving audit savings of approximately 2% of freight spend. Paying correctly is part of keeping a transport network usable.
At the loading dock, a forest-products customer shipping around 12,000 truckloads a month needed better carrier coverage and less manual work. IntelliTrans combined broader tendering with interactive dock scheduling and automation. The reported result included a 77% reduction in loads subject to detention during the first month. For a buyer, that suggests a useful diagnostic: separate the cost of hiring transport from the cost of making hired transport wait.
03 / A business educated by delays
IntelliTrans began in 1992 in a shared San Francisco office with Southern Pacific Railroad. Early shipment tracking used Access and Excel. In 1993, heavy-equipment shipments were caught in flooding near St. Louis; cargo was subsequently vandalized while idle. Waiting had consequences beyond the timetable.
Years later, IntelliTrans sought truck software called CarrierPoint, only to discover TransCore had acquired it. Discussions helped lead to a different transaction: Roper acquired IntelliTrans’ assets in April 2006 for approximately $41 million. CarrierPoint subsequently joined the technologies integrated under IntelliTrans. The missed purchase helped change the buyer’s own ownership story.
Today, the business combines enterprise SaaS with implementation and managed services. Its market position rests on the details of bulk freight and the willingness to help operate the process. Alternatives include Bourque Logistics for rail and truck operations, and Railinc’s TransmetriQ for rail management. Choosing among them means examining actual workflows, data connections, and required service coverage.
“This move is about focus.”Chad Raube, on the new Atlanta-area headquarters, August 2025
04 / Connect the decision to the work
Recent product moves follow that logic. A September 2025 EcoTransIT World integration added emissions calculations for completed truck, rail, and ocean shipments. In January 2026, DAT iQ brought freight-rate benchmarking and forecasting into the TMS. February’s developer portal added documentation, code samples, and testing for connections among shippers, carriers, and enterprise systems.
These additions make sense where different teams need to work from connected information. Their usefulness still depends on the inputs and the operation around them. Missing carrier events, inaccurate rate records, or unclear responsibilities can weaken the result. A parcel-focused business should also scrutinize a system designed around commodity freight before assuming the fit.
For the intended customer, the question is concrete: which delays, bills, and equipment cycles consume money today, and who can change them? IntelliTrans offers tools and people for that work. The railcar on the screen is the beginning. Getting it moving is where the economics become interesting.