Moving a commercial team from parallel trackers to CRM
A fictional adoption case: the CRM is live; the team’s real operating system is a set of spreadsheets.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01The outcome
The team plans, reviews, forecasts and quotes from the CRM; analysis continues on governed data; the old trackers are frozen and retired on agreed dates; bypass is visible and owned.
The team has a CRM, but daily management still depends on spreadsheet trackers, local customer files, offline forecasts and manual reporting.
What does each tracker do that the CRM does not—and what must move, change or stop before the team works from one system?
Treat every tracker as a signal first: find what it does, classify it, move its legitimate value into the operating model—then freeze and retire it on a date, with an approver for exceptions.
A regional commercial team of account managers, two sales managers and a sales operations analyst has had a CRM for a year. Opportunities are entered—mostly the day before the weekly review. The review itself runs from a spreadsheet the analyst rebuilds every Monday; the forecast is a separate file with the managers’ adjustments; account managers keep their own customer lists; a margin workbook checks prices before quoting. Leadership has twice announced that “only CRM data counts”.
02The reality · current state
How work actually happens today.
- The weekly review runs from a spreadsheet rebuilt every Monday
- Forecast adjustments live in a separate file with no history
- Account managers keep private customer lists
- Price checks happen in a workbook outside the quote flow
- CRM updates cluster the evening before each review
- Two announcements changed nothing
03Approach
Not the obvious response—the approach.
The trackers exist because they do something the CRM does not. A mandate removes the file, not the need—so the need finds a new file.
- 01Identify why the trackers exist
Inventory every file: purpose, users, the decision it feeds, how often it changes.
Adoption owner with sales operations - 02Classify missing capabilities
Separate missing views, missing data, missing routines and habit.
Process owner - 03Reproduce legitimate value
Build the review view, forecast overrides and price check where the work happens.
Platform owner - 04Move the management cadence
Run the weekly review and forecast call from the CRM—two cycles in parallel, then the CRM only.
Sales managers - 05Set a retirement date
Freeze each tracker read-only on a date; exceptions need the business owner’s approval.
Business owner - 06Monitor bypass behaviour
Watch for new files, offline requests for data and pre-meeting update spikes.
Adoption owner
04Role value
What each role gives, gets and decides.
| Role | Gives | Gets | Decides | Should not have to |
|---|---|---|---|---|
| Account manager | Stage, next step, customer context | Prioritized pipeline; price check inside the quote | The next commercial action | Keep a private customer list in sync by hand |
| Sales manager | Review decisions, forecast judgement with reasons | A review view that replaces Monday’s spreadsheet | Where the team focuses; which deals escalate | Ask the analyst for a rebuilt file |
| Sales operations | View design, data quality follow-up | Time back from weekly rebuilds | How the review view is built | Be the human integration between files |
| Executive | Visible use of the CRM forecast | A forecast with recorded judgement | Targets and escalations | Request a separate forecast file |
05Key dimension · Shadow-tool inventory & retirement
Every tracker classified—before anything is retired
The inventory records what each tool does, who relies on it, which decision depends on it, what its existence reveals—and what happens to it.
| Tool | Purpose | Used by | Decision it feeds | What it reveals | Verdict |
|---|---|---|---|---|---|
| Monday pipeline spreadsheet | Weekly review | Sales managers, analyst | Which deals need help | No CRM view fits the review | ReplacedFrozen after two parallel reviews |
| Forecast adjustments file | Monthly forecast | Managers, leadership | Committed forecast | Overrides have no place in the CRM | ReplacedRetired at the next quarter start |
| Margin workbook | Price check before quoting | Account managers | Whether a price needs approval | Cost data missing in the quote flow | Required temporarilyRead-only until cost data is integrated |
| Territory analysis workbook | Account prioritization | Sales operations | Territory focus | Legitimate analysis, not a process gap | IntegratedMoved to the analytics tool on CRM data |
| Private customer lists | Contacts and visit notes | Account managers | Who to visit next | Habit—plus one missing visit-type field | RetiredArchived after the field is added |
Two of the five trackers revealed missing capabilities. Banning them would have removed the files and kept the gaps.
06Adoption signals
How we know it is working—each signal with an owner.
| Signal | Level | Owner | Meaning | Action |
|---|---|---|---|---|
| Weekly review run from the CRM view | L3 · Management adoption | Sales manager | The review has moved | Retire the Monday spreadsheet after two parallel cycles |
| Updates clustered before the review | L1 · Usage | Adoption owner | The CRM is updated for the meeting, not for the work | Show each rep their own prioritized view daily |
| Forecast overrides recorded with a reason | L3 · Management adoption | Sales leadership | Judgement is in the system | Review override accuracy each quarter |
| New files requested or shared | L4 · Operating-model adoption | Adoption owner | A need is not met | Classify it like the original inventory |
07The trade-offs
Credible options, judged against these premises.
Mandate and deadline
Trackers that are pure habit
Cost: Legitimate needs move to new filesLeave the trackers; improve the CRM first
A CRM missing core capabilities
Cost: Two operating systems indefinitelyClassify, migrate, move the cadence, freeze on a date
A sound CRM the team does not manage from
Cost: An inventory, parallel cycles and an owner for bypass08The second layer
Questions that change the design.
Purpose
- What purpose does each spreadsheet serve?
- Which capability is missing?
- Who uses it, and how often?
Decision
- Which management decision depends on it?
- Can it be replaced—or should it be integrated?
- Which routine moves first?
Retirement
- When should it be frozen?
- Who approves exceptions?
- How will we see it coming back?
09Decisions & outputs
What the work produces.
- 01Shadow-tool inventory
- 02Classification and migration plan
- 03Management cadence run from the CRM
- 04Freeze and retirement plan
- 05Adoption signals with owners