Estimated reading time: 2 minutes
Every piece of your stack MUST have a reason why it is the best option for its primary users.
I once worked with a community bank that decided to go with 1 company for their full tech stack.
At first glance, it sounds like a good, convenient, and practical decision.
But let’s look closer:
One of the tools was a CRM.
A crucial piece for every bank.
But this particular CRM had a huge problem.
It didn’t integrate cleanly with everything else.
Odd right?
It’s all the same company, so shouldn’t everything be integrated?
I dug deeper and found that this company had just recently acquired this CRM and hadn’t been able to integrate it fully yet.
It was a small company they acquired.
A relatively new CRM.
And honestly…
It was pretty bad compared to other options.
Even aside from the fact that it wasn’t fully integrated.
But why did the bank go with this option?
Because it was convenient to deal with just 1 provider.
The end user played almost no role in the decision.
When you add new software to your tech stack,
MAKE SURE it’s the one that will best serve the END USER —
Not your accounting department when they go to pay your vendors…
