Revenue Engineering

Why Your Reps Still Forecast in a Spreadsheet

You bought the CRM and the conversation intelligence tool, and the forecast still gets built by hand. The reasons that is rational, and what actually fixes it.

Mauricio Esparza By ·Published ·2 min read
mithub.club
Short answer

Reps rebuild the forecast in a spreadsheet because the CRM number is produced from fields they do not trust and cannot adjust with judgment. Forecasting fails on inputs rather than on tooling: stage definitions that mean different things, close dates that are aspirational, and no place to record what a rep actually believes. Fix the inputs and most forecasting tools work. Do not, and none of them will.

Almost every company complaining about forecasting already owns tools that forecast. The number that reaches the board still gets built by hand.

That is rational, and understanding why is the whole fix.

Why the spreadsheet survives

1. Stage definitions are not shared. Two reps put the same deal in different stages and both are following the rules as they understand them. The pipeline then sums categories that are not comparable, and everyone senses it.

2. Close dates are aspirational. Reps set them to end of quarter because that is what the field seems to want. Everyone knows this, which is why nobody trusts a date based roll up.

3. There is nowhere to put judgment. A rep who knows a deal will slip has no field that says so. Moving the date triggers questions, so they keep it in their head and reflect it in the spreadsheet.

None of these is a tooling problem, which is why buying another tool has not fixed it.

The three fixes, in order

1. Write an exit criterion per stage. What has to be true to leave this stage. Not a description, a condition someone can verify.

This single change makes the pipeline comparable across reps, which is the precondition for any roll up meaning anything.

2. Separate the system's number from the rep's call. Two fields. What the roll up says, and what the rep believes will happen.

The gap between them is the most useful forecasting signal in the business, and most companies never capture it. Reps who see their own judgment recorded stop maintaining a private version.

3. Compare forecast to actual, by rep, monthly. Not to punish. To calibrate. After three months you will know who is consistently optimistic and by how much, and you can adjust rather than guess.

What to do about close dates

Two dates: the customer's expected decision date, and the rep's realistic date. They differ, and pretending otherwise is what makes the whole field unreliable.

If that is too much change, at least make it normal to move a date without an interrogation. The interrogation is why dates are wrong.

When a tool does help

Once the inputs are fixed. Then a forecasting product adds real value: pattern detection across deals, signals from conversations, and roll ups nobody has to assemble.

Bought before the inputs are fixed, it produces a confident number from unreliable data, which is worse than the spreadsheet because it looks authoritative.

The test

Ask three reps what has to be true for a deal to be in your second to last stage.

If you get three answers, no tool will fix your forecast, and that is where the work is.

Frequently asked questions

Which forecasting tool is best?

The question is usually premature. Every tool in this category produces a roll up from your stages, dates and amounts. If those three are unreliable, the output is unreliable regardless of the logo on it.

Why do reps keep a private spreadsheet?

Because it is the only place their judgment fits. A rep who knows a deal will slip has nowhere in the CRM to say so without moving a date and triggering questions, so they keep two views.

What is the single highest impact fix?

An exit criterion per stage, written down: what has to be true to leave this stage. It makes the pipeline comparable across reps, which is the precondition for any roll up meaning anything.

Should the rep's call be recorded separately from the system's?

Yes. Two fields: what the model or the roll up says, and what the rep believes. The gap between them is the most useful forecasting signal most companies do not capture.

Sources

  1. Why evaluate AI workflows · n8n Docs (accessed 2026-09-22)
  2. Building effective agents · Anthropic (accessed 2026-09-22)
  3. Handle errors gracefully · n8n Docs (accessed 2026-09-22)
Revenue EngineeringForecastingCRM
Mauricio Esparza
Mauricio EsparzaGTM Systems Lead · Revenue Engineer · Founder of MitHub. Designs and runs revenue systems for multi-location businesses: AI voice campaigns, enrichment, CRM automation and attribution. Founded MitHub to teach the method in the open.

Part of Revenue Engineering on MitHub.

Keep going