Why most CRMs fail their second year — and what the operators who don't are doing instead.
A field guide eighteen years in the making, from the editorial board of Claritas. Audited findings inside.
For eighteen years we have observed, instrumented, and on more than one occasion rebuilt the customer-relationship systems of institutions across Asia-Pacific. The pattern that recurs — across industries, across team sizes, across the reigning fashions in software — is the one we wish we had named earlier.
CRMs do not fail because they lack features. They fail because they were procured as software and operated as furniture. The systems that survive their second year are the ones treated as architecture: opinionated about the work, integrated into the pipe, defended by an operator who understands the building.
In this edition we publish the Customer Architecture Review for MMXXVI: 247 enterprise deployments, audited annually for five years, organised against the question every operator already knows the answer to — does the system give back more than it asks for?
The methodology is at the back. The data are at claritas.asia/data/MMXXVI. What follows is the editorial.