CRM data quality before forecasting (and before AI)

The fields the forecast actually uses

A forecast meeting stalls when someone has to ask what commit means, the amount on the slide does not match the opportunity, or a close date moved and nobody can say who moved it. A new forecast model carries that argument into the next meeting. An AI summary of the pipeline does the same, in smoother sentences.

You do not need every CRM field to be perfect. You need agreement on the fields the forecast and the revenue conversation use:

• What counts as an opportunity, and when it is created
• Stage names, including what commit, best case, and pipeline mean in your business
• Amount, and whether it is a booking, billable work, or a placeholder
• Close date, and who is allowed to change it
• Account and owner, so the customer on the opportunity is the customer finance recognizes

Write those definitions in words a new account executive and a finance partner would both accept. If the only copy is a slide from last year's kickoff, you do not have a definition yet.

A check you can run this week

Pick a few open opportunities and read them with sales and finance together. Ask each person for the stage, the amount, and whether the close date is a commitment or a hope.

If they disagree, do not add a model yet. The model has to pick one answer, and the meeting returns to the disagreement.

Any figure in an example should be labeled. This one is synthetic, not a client result. An opportunity called Northwind expansion sits in Commit, with an amount of 120,000 and a close date of the coming Friday. Sales uses Commit to mean a verbal yes. Finance uses Commit to mean a number they will send to the board. Those are two different decisions. No forecast and no assistant can repair the word until it means one thing.

Forecasting, then AI

After the fields are agreed and someone owns them, a forecast has a fair chance of being useful. The same bar applies to AI. An assistant can draft a note from the CRM, and it will sound sure of itself either way. It will not tell you that two teams are using commit differently. That is a management decision, and it comes before the assistant is turned on.

When the forecast and the revenue number need to use the same definitions, see revenue and customer analytics.