Playbook · July 27, 2026

A CRM rollout plan that survives first contact with sales

A phased CRM rollout: starting from the reports leadership needs, reducing required fields to the minimum, migrating in stages, and the training that only happens once the system is useful.

By Marsden Advisory· Updated September 17, 2026
Rollout timeline with four overlapping delivery phases
Rollout timeline with four overlapping delivery phases

We have joined three of these mid-flight. In each case the configuration was fine and nobody was entering anything.

## Start from the reports, not the fields

Agree the two or three reports leadership will run weekly. Every required field must be traceable to one of them. Fields that serve no report are the reason a team quietly stops updating records within a month.

## Migrate in stages and train on the real system

Bring open pipeline first, then recent history, then archive. Train on the migrated data with the team's own deals, after the system is genuinely useful. Training on a demo environment before migration is how a rollout gets remembered as a burden.

## Name an owner for the first ninety days

One person owns data quality, answers questions, and is allowed to remove requirements that are not working. Without that role, small friction accumulates and the rollout is judged a failure for reasons nobody records.

Where this applies

  • Implementation
  • Consulting

Work with Marsden Advisory

This playbook comes from the work Marsden Advisory does. See what they offer, the results they can evidence, and how to start a conversation.

More from Marsden Advisory