My forecast numbers don't match my CRM

bont's forecast numbers and your CRM's pipeline number are almost never the same — and usually shouldn't be. The two systems measure slightly different things. Knowing which is which avoids weeks of pointless reconciliation.

Why they diverge

• Forecast categories — bont reads each deal's forecast category (Commit / Best Case / Pipeline / Omitted) and rolls up accordingly. Your CRM probably sums all open deals into one number regardless.
• Probability weighting — bont uses scoring-aware probability for some views; the CRM uses stage default.
• Active definition — bont excludes On-Hold deals from forecast by default. The CRM includes them.
• Currency normalisation — bont converts multi-currency deals to the workspace currency. The CRM may show native currency.
• Sync lag — small differences early in a sync cycle close up within minutes.

If you suspect a real bug

1. Pick a specific deal where the numbers disagree.
2. Open it in bont and in the CRM side-by-side.
3. Compare amount, stage, forecast category and any custom fields.
4. If they truly mismatch, that's a sync problem — see Troubleshooting CRM sync errors.

Reading guide

Detailed explanation: Understanding forecast vs. closed numbers.

Escalating

Email support@bont.ai with a sample deal ID and screenshots from both sides.