Legacy System Replacement

Rescuing a sales team after a failed CRM rollout

How a technology solutions provider rebuilt its selling process after poor adoption of a previous CRM had left it with a large sales team and no pipeline visibility.

  • Multi-BUon one selling process
  • Mobile-firstfield adoption
  • Higherlead conversion rate

01

The dilemma

The client had already bought a CRM and already failed with it. That is a harder starting point than having nothing, because the sales team had learned that CRM means data entry with no return. Rebuilding required addressing the reason for the failure, not simply replacing the software.

What was breaking

  • No unified selling process. Multiple business units sold multiple product lines, each in its own way, with nothing common between them.
  • A large sales team with no shared structure. Managing scale without process means managing by individual relationship, which does not scale.
  • Poor adoption of the existing CRM. The Pipedrive deployment was not being used, so pipeline visibility was limited regardless of what the system could do.
  • No digital marketing capability. Lead generation depended entirely on the sales team's own effort.
  • No mobility. A field-based sales organization was being asked to update a desktop system after hours.

The cost of standing still

A failed CRM rollout costs more than the licenses. It teaches a sales team that management systems are overhead, and the next attempt starts from a position of earned scepticism. Meanwhile the pipeline stays invisible and forecasting stays fictional.

02

The idea

We started from the reason for the first failure. The previous rollout had asked salespeople to record data without giving them anything in return, and it had been deployed to a desktop for a team that works in the field. The redesign led with the two things that would give the sales team an immediate reason to use it: campaign-generated leads arriving in their pipeline, and a mobile interface that worked where they actually work.

The principles we worked to

  • Give before you take. Deliver leads through the system before asking the team to feed the system.
  • Mobility is not a feature for a field team. It is the difference between a system that is used and one that is not.
  • One process across business units. With unit-level variation configured, not improvised.
  • Governance built in. KYC and credit checks as part of account management rather than a separate approval chase.

What we ruled out, and why

Option consideredWhy we did not take it
Re-training the team on the existing CRMThe tool was not the primary problem, but re-launching something the team had already rejected would have inherited the scepticism.
Separate CRM instances per business unitSolves the adoption objection and destroys the cross-unit visibility that was half the point.
Deploying the CRM before building the marketing engineWould have repeated the original error, asking for data entry with nothing flowing back.

03

The build

Six components, sequenced so that value arrived before obligation.

01

Campaign management

Targeted outreach capability built first, so that digital campaigns began generating leads into the system the sales team was being asked to adopt.

02

Lead management

Customer acquisition optimized through structured lead capture, qualification and assignment across business units.

03

Account management with governance

KYC and credit check functionality embedded in account management, so commercial risk is assessed as part of the process rather than alongside it.

04

Opportunity and activity management

Integrated so that pipeline value and the work behind it are visible together, giving managers something more useful than stage counts.

05

Mobility solution

CRM on mobile for on-the-go management, addressing the single largest cause of the previous rollout's failure.

06

Unified selling process

One documented process across business units and product lines, with the variation that genuinely exists configured rather than left to individual practice.

04

The impact

MeasureBeforeAfter
Selling processDifferent in every business unitUnified, with configured variation
CRM adoptionPoor (Pipedrive)Adopted, supported by mobility
Pipeline visibilityLimitedOpportunity pipeline visible to management
Lead generationSales team effort onlyDigital campaigns generating qualified leads
Lead conversionBaselineHigher, with better lead quality
Credit and KYCSeparate manual checksEmbedded in account management
Field workingDesktop, after hoursMobile, at the point of the conversation

Beyond the numbers

  • Account insight and pipeline visibility restored. Management can see the opportunity pipeline rather than infer it.
  • Business units collaborate. A shared process makes cross-unit selling possible for the first time.
  • Sales representative satisfaction rose. The mobility solution made the system useful to the people entering the data, which is the only durable route to adoption.

05

What comes next

The engagement continues. These are the next moves on the table.

  • Territory and quota management across business units.
  • Campaign attribution linking marketing spend to closed revenue.
  • Partner and channel pipeline on the same platform.

Engagement delivered by the Ideentrix founding team. Technologies, scope and outcomes as recorded at project close, published with the client's consent.

Next step

Sitting on a CRM your team refuses to use?

Failed rollouts are usually process failures wearing a software costume. Tell us what your team says about the current system and we will tell you what it would take to fix.

Book a consultation Scope your project

First call: 30 minutes · A senior consultant, not a sales rep