Salesforce's technical infrastructure is genuinely excellent. The object model, the automation engine, the formula layer, the integration architecture, these are serious tools built over twenty years. Nobody is replacing that with a weekend project. What is collapsing is the layer above it. The opinionated interpretation of how a business should work, encoded into a data model and sold as best practice. What a lead is. What an opportunity stage means. What belongs on a case v

CRM automation stacks do not collapse, they calcify. Workflows accumulate the way meeting invites do, each one added for a reason, none of them ever removed. A re-engagement trigger from a campaign no one runs. A task assignment firing to a user who left eight months ago. A cloned sequence carrying a stale exclusion list that nobody noticed. The problem is not automation. The problem is permanence. Workflows are treated as infrastructure when they should be treated as interve

The instinct to minimise CRM fields mistakes tidiness for health. Fields are not clutter. They are the mechanism by which a CRM reflects a living business, and a system that cannot grow new fields quickly is a system that cannot keep pace with reality. When field creation requires weeks of approvals, teams stop asking. They build parallel spreadsheets, repurpose existing fields for unintended concepts, and maintain private trackers that nobody else can see. The data does not

Field count is the wrong metric. A CRM with fifty well-governed fields is less reliable than one with three hundred fields that each have a clear purpose, a named owner, and defined update logic. The number is a distraction. The governance is the point. Consolidation projects that chase simplicity often strip away legitimate context. A field that captures adviser preference or onboarding exceptions may sit untouched for months, but when it is needed, it carries information th

Automation is the default setting in most CRM and marketing operations environments. If something can be automated, it is. The assumption, rarely examined, is that automation equals efficiency, and efficiency equals good. The maintenance cost alone gives that assumption pause. Triggers drift, integrations fail silently, fields freeze in states that nobody notices until something breaks badly. The workflow built to banish effort becomes the thing demanding the most of it, a sl

A CRM that nobody uses properly is not a technology problem. It is a habit problem, and habit problems do not respond to process rewrites or training sessions. They respond to friction reduction and visible feedback. Teams bypass CRM systems because using them feels like additional work rather than better work. Notes go into Outlook. Updates live in spreadsheets. The system drifts from reality, quietly, until pipeline reviews become fiction and marketing triggers fire on data

A CRM is only as useful as the people using it, and people stop using it the moment they stop trusting it. It usually starts with the small indignities. A contact who left the firm two years ago. Three records for the same person. An email address that bounces. A fund that no longer exists under that name. None of it is catastrophic on its own, but the relationship manager notices, loses a little confidence, and begins keeping their own records instead. Spreadsheets appear. C

Australian wealth management firms have spent years building genuine distribution intelligence. CRM platforms connected to marketing automation, contact-level engagement data, meeting history, campaign responses, fund-level activity patterns. The capability to understand a pipeline in real detail exists. The organisational function that would turn that capability into action, in most firms, does not. Analytics has not been embedded as a core discipline inside distribution and