Reframing a CRM Selection into an Executive Operating Decision
Executive Decision Support · CRM Strategy · Operating Model · Change Management
B2B demand generation company
Executive decision support and CRM strategy
How a CRM platform debate was reframed around adoption, integration, management participation and the operating conditions required for successful implementation.
The co-founders of a B2B demand generation company were divided over which CRM should replace an internally developed system. Sales was not using the existing CRM consistently, Marketing operated through spreadsheets, Finance depended on information that was manually transferred between systems, and management did not trust the data available in the CRM. The organization needed more than a vendor recommendation. It needed clarity on the operating conditions required for a new platform to succeed.
Choosing a new CRM without fixing the operating model
The CRM disagreement was a symptom of a broader operating failure. Sales and Marketing maintained critical information outside the system, a dedicated team manually entered CRM data into the finance tool, and leadership did not use the CRM as a reliable source of truth. Selecting a different platform without resolving adoption, integration and accountability would have risked reproducing the same problems in a newer and more expensive system.
Executive decision support and CRM strategy
I diagnosed the operating conditions behind the founders' disagreement and reframed the decision around the requirements of the wider organization. I connected CRM selection to Sales adoption, Marketing participation, Finance integration, management usage, data trust and formal onboarding. This helped leadership move from a preference-based platform debate to a decision supported by clearer operating commitments.
Reframing platform selection around organizational requirements
I moved the conversation away from individual vendor preferences and back to how the organization actually operated. The evaluation focused on the processes the CRM needed to support, why Sales had rejected the existing system, how Marketing and Finance needed to participate, what information management required, and which adoption, integration, governance and training commitments would be necessary. This gave the founders a shared decision framework grounded in organizational requirements rather than product features alone.
Choosing a new CRM does not resolve the conditions that caused the old one to fail. Unless adoption, integration, ownership, management participation and onboarding are addressed, the organization risks recreating the same operating problems in a different platform.
A new CRM backed by adoption, integration and training
The company decided to replace the existing CRM, but the decision included commitments designed to prevent the new platform from repeating the failures of the old one. Sales would be required to use the CRM consistently instead of maintaining parallel spreadsheets, and the platform would be adopted across the organization, including by management. The new CRM would connect with the finance tool, removing the need for a dedicated team to transfer information manually, and users would receive structured onboarding and training before activation. The result was not simply a different technology choice, but a stronger implementation direction grounded in adoption, integration and accountability.
EXPLORE MORE WORK