Picked for the newsletter Ran in “A mystery challenger at the AI frontier” on Aug 24(opens in a new tab)
Build a Multi-Channel Load Blast Platform for Freight Brokerage
Apps it uses
I work in the freight brokerage industry. When speaking with trucking companies, we usually want to send offers to multiple contacts at once. This is called a load blast. Clients prefer different communication channels, mostly email and Telegram, so freight brokers often have multiple screens open to manage all of those conversations.
Using Claude Code, I built a platform where I can save each client’s preferred communication method—email or Telegram—once. The platform then blasts the load information to the appropriate contacts through their chosen channels.
I also built a tooltip guide to help non-technical salespeople set up the system. It guides them through adding contacts, connecting Telegram, and sending load information to multiple contacts at once. This lets them manage the process from one screen instead of switching between multiple screens.
This process happens hundreds of times per day. Based on the demo, I convinced my company to start building the same platform internally.
Step-by-step
- I identified that freight brokers needed to send load offers to multiple trucking-company contacts at once, or create a load blast.
- I built a platform with Claude Code that lets me save each client’s preferred communication method, such as email or Telegram.
- I configured the platform to send load information to contacts through their selected communication channels.
- I added a tooltip guide explaining how non-technical salespeople can add contacts, connect Telegram, and send a load blast.
- I designed the process so salespeople could manage these communications from one screen instead of using multiple screens.
- I demonstrated the platform to my company and convinced them to start building it internally.
2 comments
Have a question about this workflow, or a way to improve it?
Log in to comment Create a free accountSweet - love that this got greenlit for an internal build off the demo alone. Thanks for sharing!
Storing each contact's preferred channel once, instead of leaving that decision to the rep on every send, is what will keep this alive when you're not in the room. One thing from hiring crew against a shoot date, which is the same shape of problem. The first yes is rarely the best one, it's usually the one with the emptiest week, and I've filled positions with whoever answered fastest and paid for it on set. The other half is that people can tell: someone who knows they got a blast negotiates differently from someone who thinks you came looking for them. Does the platform track who replies first versus who actually delivers well on the load, or only the sender?
Posting guidelines