Are you ready for logistics automation? Take our readiness quiz to find out!
Tired of Not Hearing Back? Why Responsiveness Makes or Breaks a Technology Partnership
By Angie Sabourin, Partner
Updated: April 1, 2026 | 2 min read
In nearly every major warehouse technology project we take on at LIDD, one pattern stands out: we respond to customer requests and inquiries within 24 hours. It sounds simple, but in an industry where weeks can pass without a callback, it turns out to be one of the things clients value most.
That consistency got me thinking about what actually drives it — and why so many technology vendors struggle to maintain it as they grow.
Responsiveness Is a Choice, Not a Capability
Serving customers quickly is one of our greatest strengths, and honestly, it’s also what gives our team a real sense of accomplishment at the end of the day. As my colleague Jeff Hamilton put it during a recent WMS demo: our goal isn’t to sell licenses, it’s to make the journey to Go Live the best experience possible. That mindset shapes how we prioritize everything — including how fast we pick up the phone.
We are in the service business. As consultants, that is the job. Technical expertise matters, but it means very little if a client can’t reach you when they need you.
When Poor Responsiveness Drives Major Decisions
One of my top clients is currently preparing to replace their Transportation Management System. Not because it doesn’t work. Not because it lacks functionality. They are replacing it because they never hear back from their vendor.
They feel like they are constantly chasing answers — following up on tickets, waiting on callbacks, re-explaining the same issues to different contacts. The frustration has reached a point where they are willing to absorb the significant cost and disruption of a full system overhaul, simply to work with a partner who will actually respond. That is a remarkable thing when you stop to think about it. A functional system, replaced not for technical reasons, but because of a relationship failure.
The cost of poor responsiveness is rarely visible on a balance sheet — but it shows up in eroded trust, stalled projects, and eventually, decisions exactly like this one.
Understanding the Real Environment
At LIDD, we are real-world operators. We have spent time on warehouse floors. We understand what it means to find qualified personnel, to manage the fatigue of repetitive picking cycles, and to keep an operation running when things go wrong — because things always go wrong.
During one implementation, I heard a software provider tell an operations team they needed to “suck it up” after a picker made a mistake, because their system lacked the validation logic to handle it. I still think about that moment. What is an operations team supposed to do with that answer? Mistakes are an inherent part of any operation. A well-designed system should be built to accommodate them — with validation, exception handling, and workflows that support the people using them, not punish them for being human.
At LIDD, you will never hear us say that pickers need to adapt to the system’s limitations. The system should be built around the reality of how operations actually work.
The Agility Problem
There is a broader question underneath all of this that I have not fully resolved: as organizations grow, they almost inevitably lose agility. Response times slow. Escalation paths get longer. The urgency that defined them in their early years gets diluted by process and scale.
What I cannot figure out is why maintaining that responsiveness is not treated as a strategic priority — because the clients who leave are not leaving over features or pricing. They are leaving because no one called them back.
If you have experienced this with a technology partner, or if you have found ways to preserve responsiveness as your organization scales, I would genuinely love to hear your perspective.
Angie Sabourin is a Partner at LIDD, specializing in warehouse technology implementation and supply chain operations.
Related Posts
More Power Than You Think: Why Your Project Is Stalling (and How to Fix It)
Project launches are longer and more expensive than ever—but you have more power than you think to change that. Explore the key points LIDD partner Angie Sabourin has observed over the years and exactly how to handle them to get the results you actually want:
Preparing for a Successful Warehouse Management System (WMS) Go-Live
Can a supply chain be efficient & responsive? The answer to this is yes. Discover how LIDD designed a Salesforce-integrated solution that transformed the order entry process for a foodservice distributor, enabling the company to be both responsive and efficient when it came to supply chain management.
Generix Solochain’s Rémy Karmouche on the Future of WMS and Overcoming Key Challenges
Tune in as Rémy Karmouche, Director of R&D at Generix Solochain, shares his insights on the future of WMS, and why you should pay attention.