Moving a commercial team from parallel trackers to CRM
The CRM is live; the organization’s real operating system is a set of spreadsheets, slides and one legacy tool.
The case in brief
Current reality
The team has a CRM, but daily management still depends on spreadsheet trackers, local customer files, offline forecasts, regional slide packs and manual reporting—and nobody owns the rules that would make the CRM the place the business is run from.
What must become true
The business plans, reviews, forecasts and quotes from the CRM: every management routine has a system view and an owner, every parallel tool has a replacement and a retirement date, data quality and stage definitions have owners, analysis continues on governed data—and bypass is visible and owned.
Design question
What does each tracker do that the CRM does not—and which routines, ownerships and decisions must move before the business operates through one system?
01The reality · current state
How work actually happens today.
A regional commercial organization of account managers, sales managers and a sales operations analyst has had a CRM for a year. The configuration is sound. 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; the monthly performance meeting uses slides per region; account managers keep their own customer lists; a margin workbook checks prices before quoting; one subsidiary still works in its legacy tool. Stage definitions are read differently by each team, and nobody has owned data quality or the CRM’s operating rules since the project closed. Leadership has twice announced that “only CRM data counts”.
- The weekly review runs from a spreadsheet rebuilt every Monday
- Forecast adjustments live in a separate file with no history
- Monthly performance reviews use regional slide packs
- Account managers keep private customer lists
- Price checks happen in a workbook outside the quote flow
- One subsidiary still works in its legacy tool
- Teams read the stages differently, so reports disagree
- CRM updates cluster the evening before each review
- Two announcements changed nothing
02Approach
Not the obvious response—the approach.
CRMSpreadsheets (retiring)Analytics toolCollaboration tools
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 and tool: 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 routines in
Weekly review, forecast call, monthly performance review and account planning run from the CRM—two cycles in parallel, then the CRM only.
Sales managers - 05Name the owners and rights
Owners for accounts, opportunities, data quality and stage definitions; who decides a retirement and on what evidence.
Business owner - 06Set a retirement date
Freeze each tracker read-only on a date; exceptions need the business owner’s approval.
Business owner - 07Monitor bypass behaviour
Watch for new files, offline requests for data and pre-meeting update spikes.
Adoption owner
What changes beyond the trackers
Retiring the trackers is the visible half. The CRM becomes the environment the business operates through only when these layers change with it.
- 01Outcome
Management decisions made from CRM evidence
- 03Process
One interpretation of stages, with exit criteria
- 04Ownership
Account, opportunity and data-quality owners named
- 05Systems
The CRM as the system of action for every commercial routine
- 06Data
Quality owned at the source by the people who can fix it
- 08Governance
A business owner and a change process for lifecycle definitions
- 09Measurement
Adoption measured by routines run from the system
03Role 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 |
Decision rights the move needs
Retirement is a decision with an owner and evidence—not something that happens by itself. Two further rights keep the moved routines trustworthy.
| Decision | Decides | Approves | Consulted | Evidence | Within |
|---|---|---|---|---|---|
| Retire a parallel tool | Sales leadership | — | Sales operations | The replacement view used for two cycles | By the agreed date |
| Change a stage definition | Commercial process owner | Global governance | Sales managers, platform owner | Stage ageing and conversion | Quarterly |
| Fix a data-quality issue | Data owner for the concept | — | Account owners | Quality measures by source | 5 working days |
04Key dimension · Shadow-tool inventory, routines & retirement
Every tracker classified—and every routine it carried moved in
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. Beside it, the routines that move into the CRM, each with a system view and an owner.
Tools that move out
| 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 |
| Regional slide packs | Monthly performance review | Sales managers, sales operations | Which accounts and plans need attention | No performance view per account and plan | ReplacedRetired after two monthly cycles in parallel |
| 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 |
| Legacy tool in one subsidiary | The subsidiary’s whole pipeline | Local sales team | Local pipeline and forecast | Local rules never registered as variations | ReplacedRetired at the subsidiary’s go-live, with registered variations |
Routines that move in
| Routine | Before | After | Owner |
|---|---|---|---|
| Weekly pipeline review | Exported spreadsheet, rebuilt every Monday | Team pipeline view with stage changes and stale deals | Sales manager |
| Monthly performance review | Slides per region | Performance view by account and recovery plan | Sales operations |
| Account planning | Slides per account | Account plan record linked to opportunities | Account owner |
| Forecast submission | Email with a total | Forecast view with recorded judgement | Sales leader |
Three of the seven trackers revealed missing capabilities; banning them would have removed the files and kept the gaps. A parallel tool without a retirement date is the real system of record—so retirement is a decision with an owner, taken when the routine it carried runs from the CRM.
05Adoption 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 |
| Parallel tools past their retirement date | L4 · Operating-model adoption | Business owner | A retirement decision was not carried out | Decide: retire now, or record an exception with a new date |
| New files requested or shared | L4 · Operating-model adoption | Adoption owner | A need is not met | Classify it like the original inventory |
06The trade-offs
Credible options, judged against these premises.
Mandate and deadline
Trackers that are pure habit
Cost: Legitimate needs move to new filesMore training and mandatory fields
Teams that already manage from the CRM
Cost: Compliance without useRebuild the CRM
A broken configuration
Cost: The same result if the routines do not moveLeave the trackers; improve the CRM first
A CRM missing core capabilities
Cost: Two operating systems indefinitelyClassify, move routines and owners in, retire on a date
A sound CRM the business does not operate through
Cost: An inventory, parallel cycles, named decision rights—and managers changing how they run meetingsDesign decision
Treat every tracker as a signal first and adoption as an operating-model change: find what each tracker does, move its legitimate value and the management routine it carried into the CRM with an owner, give retirement, definitions and data quality named decision rights—then freeze and retire each tracker on a date, with an approver for exceptions.
07The second layer
Questions that change the design.
Purpose
- What purpose does each spreadsheet serve?
- Which capability is missing?
- Who uses it, and how often?
Routines & owners
- Which management routine moves first—and who owns it?
- Which decision depends on each tracker?
- Who owns data quality and stage definitions once the routines have moved?
Retirement
- When should each tool be frozen?
- Who decides a retirement—and who approves exceptions?
- How will we see it coming back?
08Decisions & outputs
What the work produces.
- 01Shadow-tool inventory
- 02Classification and migration plan
- 03Routine migration plan with owners
- 04Ownership model and decision rights
- 05Freeze and retirement register
- 06Adoption signals with owners