A few years ago, a broker would buy a tool because it might get them more loads. Today, that pitch doesn’t land. Even brokerages doing eight and nine figures in revenue are funding one thing right now: loss prevention.
It’s not hard to see why. Margins are still under pressure in the second half of the year, good reps are harder to keep than ever, and every brokerage I talk to has a story about a mispriced quote, a missed exception, or a carrier that should never have been booked. Those aren’t hypothetical risks. They’re line items. And when the CFO is in the room, the tool that gets funded is the one that can point to a specific loss and say, “This stops that.”
So when a brokerage sits down to decide where the next dollar of tech budget goes, it’s natural for them to target loss prevention. Whether it’s a TMS migration, a visibility platform, or an in-house AI build, every option gets justified the same way: what does this stop. That’s a rational response to the market. It’s also how a brokerage ends up with a tech stack that only knows how to play defense, and no budget line left for anything that actually grows the business.
TMS Migration: Real Loss Prevention, Slow Roll-Out
Ripping out your TMS and replacing it with something newer is the biggest change on this list, and it’s not wrong. There’s real loss prevention in clean data, a modern foundation, and a platform that isn’t held together with workarounds your team built in 2016.
But the cost isn’t just the invoice. It’s the six- to 12-month implementation window during which your team is retraining instead of quoting. It’s the disruption to the daily rhythm of booking loads while everyone learns a new system. The value is real, but the problem is that it shows up in quarters, not weeks. And most brokerages don’t have quarters to spare on margin they’re already losing today.
Visibility Tools: Useful But Narrow
Visibility tools for track-and-trace, better ETAs, and fewer “where’s my truck?” calls solve a real problem, and they’re usually an easy yes because the scope is contained. But that’s also their limitation.
Visibility doesn’t touch how a load gets priced. It doesn’t touch carrier vetting. It doesn’t stop margin leakage before it happens. It just helps you see the shipment once it’s already moving. While it’s easy to approve, it’s solving a smaller slice of the loss-prevention problem than brokerages actually have.
In-House AI: The Trap I’ve Watched Brokerages Fall Into
Building it yourself is appealing. You get full control, built around your exact workflow, no vendor telling you how it should work.
But here’s the hidden cost: your engineering team already has a full plate, and an internal AI project competes with everything else on their roadmap for attention. Plus, the ROI timeline depends on a team that has other priorities, which means the project stalls right around the point where it would have started paying off. I’ve seen this happen more than once. The intent was never the problem. The bandwidth was.
Where Drumkit Fits
Here’s the thing about all three: they’re defensive purchases, and defensive purchases have a ceiling. The best a TMS migration, a visibility tool, or an in-house build can do is stop a specific bleed. None of them hand anything back to your reps.
Drumkit is the one line item that does. We built Drumkit to work inside the TMS a brokerage already runs. That way, there’s no rip-and-replace, no six-month migration, and no asking your team to relearn how they do their job. That;s what makes it different in kind, not just in degree. When Drumkit closes a mispricing gap or catches a missed exception, that’s not just a loss avoided. It’s an hour a rep didn’t spend re-quoting or chasing down a mistake and instead goes straight back into selling and building relationships.
We keep rep judgment and override control intact, because adoption doesn’t work if the tool feels like it’s replacing your best people’s instincts. It works when it gives them leverage. Loss prevention and growth aren’t actually in tension. It’s just that most tools only ever deliver the first half.
Where the Budget Actually Lands
Every other tool on your list this cycle is going to answer the same question: what does this stop? That’s a fine question and for a TMS migration or a visibility platform, it’s the only one that matters. But it’s worth asking a second question of at least one line item: what does this start?
A migration doesn’t start anything for six to twelve months. Visibility tools don’t touch the top of the funnel at all. An in-house build starts things in theory, but has a roadmap that keeps getting bumped. Drumkit is the rare tool that answers both questions at once. It stops the same leaks everything else on this list is trying to stop. Plus, every hour that isn’t spent re-quoting or chasing an exception is an hour that starts something new: a call, a relationship, a load booked.
That’s the difference between a tool that plays defense and one that pays you back.
