It is evidence that your sales team stopped trusting Salesforce.
Most sales leaders treat a separate forecasting spreadsheet as evidence of poor CRM discipline.
Reps need to update Salesforce. Managers need to stop maintaining their own numbers. Everyone needs to use the system of record.
That sounds reasonable.
It also misses the point.
The spreadsheet is rarely where the problem began. It usually appeared after managers stopped trusting Salesforce to answer the questions they were being asked.
Which opportunities are genuinely likely to close? What changed since last week? Which deals are moving forward, and which ones have simply had their close dates pushed again? What evidence supports the number being presented to leadership?
When Salesforce cannot answer those questions clearly, somebody creates a spreadsheet that can.
The spreadsheet is not the problem. It is evidence that the sales organisation has built a second system because it no longer trusts the first.
The spreadsheet probably started as a workaround
Nobody wakes up one morning wanting another forecasting process.
The spreadsheet usually begins innocently. A sales manager needs a clearer view before the Monday forecast call, so they export the opportunities from Salesforce and add a few columns.
They include the information they cannot easily find in the CRM: the real next step, what happened in the last customer meeting, whether the decision-maker is engaged, what could prevent the deal from closing and how confident the rep actually feels.
The spreadsheet works.
It gives the manager a faster way to inspect the pipeline, question the forecast and prepare for the leadership meeting. Other managers begin using it. Finance asks for a copy. Before long, the spreadsheet becomes the forecast leadership relies on, while Salesforce becomes the place where the underlying records are stored.
Now the company has two versions of the pipeline.
Salesforce contains the official data. The spreadsheet contains the number people believe.
What the spreadsheet is telling you
A shadow forecasting process usually points to a deeper problem in one or more areas.
1. Salesforce no longer reflects how the company sells
Sales processes change. New products are launched, territories are reorganised, approval requirements evolve and managers begin asking different questions.
Salesforce does not automatically adapt when the commercial process changes. If the configured stages, fields and workflows still reflect an earlier version of the business, reps are forced to translate the way they actually sell into a system designed for something else.
That translation creates friction, incomplete records and inconsistent interpretation.
2. Opportunity stages do not mean the same thing to everyone
One rep moves an opportunity forward after a good meeting. Another waits for a confirmed commercial event. A third changes the stage because the opportunity has been sitting in the same place for too long.
The dashboard may look precise, but the underlying stage definitions are subjective.
When managers cannot rely on the stage to indicate what has actually happened with the customer, they need another way to judge the deal. That judgement often ends up in a spreadsheet or inside the manager’s head.
3. Salesforce asks for information without returning enough value
Reps will tolerate administration when it helps them sell, prepare for meetings, coordinate resources or move a deal forward.
They become resistant when fields appear to exist solely for reporting purposes, the same information must be entered in multiple places or the data disappears into dashboards that provide no value to the seller.
This is often described as an adoption problem. In reality, it can be a value problem.
The organisation is asking sellers to invest time in Salesforce without making the benefit of that investment visible to them.
4. Managers cannot see the evidence behind the forecast
A pipeline number is not useful simply because it appears inside Salesforce.
Managers need to understand what changed, what the customer has committed to, which risks remain and why a deal belongs in a particular forecast category.
If Salesforce provides the number but not the evidence supporting it, managers will create a separate process to capture the missing context.
Forcing everyone back into Salesforce will not restore trust
The usual response is to enforce adoption.
Leadership mandates that Salesforce is the only system of record. More fields become compulsory. Reports are circulated showing which reps have not updated their opportunities. Managers are told to stop using spreadsheets.
That may increase the amount of data entered into Salesforce.
It does not necessarily make the data more trustworthy.
If the sales process remains unclear, the stage definitions remain subjective and the CRM still fails to support the forecast conversation, the spreadsheet will return. It may have a different name or live somewhere leadership cannot see, but the workaround will survive because the need for it has not disappeared.
Compliance can make people use a system.
It cannot make them trust it.
Fix the reason the spreadsheet exists
The answer is not to rebuild Salesforce immediately. Nor is it to copy every spreadsheet column into a new custom field.
The first step is to understand what job the spreadsheet is performing that Salesforce is not.
Start by tracing how an opportunity moves through the business. Look at what the sales process says should happen, what Salesforce requires and what reps and managers actually do.
Then examine the gaps.
Are the opportunity stages based on observable customer evidence? Can managers see what has changed since the previous forecast? Are sellers entering information that helps them progress the deal? Does the forecast category reflect genuine confidence, or is it being used to balance the number? Which spreadsheets, messages and offline documents have become essential to running the pipeline?
Only then can you determine whether the problem sits in the sales process, Salesforce configuration, management cadence, seller behaviour or some combination of all four.
A simple test
Imagine switching off the forecasting spreadsheet tomorrow.
What would the business lose?
If the answer is visibility into deal risk, management judgement, next steps, forecast changes or the number Finance expects, then the spreadsheet is performing an important operational role.
Deleting it will not solve that problem.
You need to understand why Salesforce is not performing the same role and decide whether it should.
Salesforce should earn its position as the system of record
Your sales team should not need one system to record opportunities and another to run the business.
Salesforce should help reps manage their deals, help managers inspect the pipeline and give leadership a forecast they can defend. When it does, the separate spreadsheets become unnecessary because the official system is also the useful one.
Until then, the spreadsheet is telling you something important.
Your team did not abandon Salesforce for no reason.
They built a workaround because something they needed was missing.
The question is not how quickly you can eliminate the spreadsheet.
The question is where the trust broke.
Find where the trust broke
If Salesforce, your forecasting spreadsheet and your sales team are producing different versions of the quarter, Ravienta can help you identify where the process has stopped working.
Our Revenue Systems Assessment examines how your company sells, how Salesforce supports that process and where managers and reps have been forced to build workarounds.
Request a Revenue Systems Assessment to identify what is breaking trust and what to fix first.