Dynamics 365 vs the spreadsheet shadow-CRM inside your team

Every sales organization running a serious CRM also runs a spreadsheet. It lives on a shared drive or in someone’s OneDrive, it is updated more carefully than the CRM, and it is what the team actually opens before a customer call. Ask a rep which one is right and they will tell you without hesitating.

Sales leaders tend to treat this as a compliance failure. It is more useful to treat it as a free, unusually candid requirements document.

Read the columns

The spreadsheet is not a copy of the CRM. It is a copy of the parts that work, plus the parts that are missing. Those additions fall into three consistent groups.

Private confidence. A column — often just a color — that records what the rep actually believes, as distinct from the stage they are required to report. Its existence tells you the official stage field has become a compliance artifact rather than an estimate.

Commercial truth. The price actually promised on the call. The competitor in the deal. The discount the customer is expecting because of what happened last year. These are the facts that decide the outcome and they are frequently the ones with nowhere clean to go in the CRM.

Operational context. Stock position, lead time, credit status, the last invoice. None of this is CRM data at all; it lives in the ERP. The rep copies it in because the alternative is opening a second system, or asking a colleague, in the middle of a conversation with a customer.

That third group is the most telling. It is not a CRM adoption problem in any sense. It is an integration gap that the rep is closing manually, by hand, every week.

Why banning it does not work

Because the spreadsheet is a symptom with a cause, and enforcement addresses only the symptom. Remove the file and the need persists: the rep still cannot see stock during a call, still cannot record what they really think, still cannot get the whole territory on one screen. The workaround simply becomes less visible — a personal notebook, a phone note, a private message thread. You have not recovered the data; you have lost sight of it.

Closing the gap in the Microsoft stack

The good news for Dynamics 365 shops is that the operational half of the problem is a solved integration question rather than a product limitation. Dual-write keeps Dynamics 365 Sales in step with finance and operations data, and Business Central integrates directly with Sales for order and inventory context. Neither is trivial to stand up, but both are documented paths, and both remove the copy-paste that most spreadsheets exist to perform.

The judgement half is harder and cheaper. If reps need a private confidence rating, give them one — an explicitly non-reported field that never appears in a commit number. Teams that do this find the official stage field becomes more honest almost immediately, because it stops carrying a burden it was never suited to.

The test

Ask for the spreadsheet. Not to confiscate it — to read it.

Then, column by column, ask two questions: can the CRM answer this in under ten seconds, and if not, is that an integration gap or a missing field? Everything that survives both questions is a genuine requirement, discovered for free, from the people who know.