Hey folks, I've been running Consensus for a few months now to track our sales pipeline automation, and I've hit a major snag. Our team's reported "deal velocity" metric in the dashboard seems wildly off—like, not-even-in-the-ballpark wrong. It's showing an average cycle time that's about three times longer than our actual CRM data.
Here's our setup:
* We sync our deals from Salesforce using the native integration.
* We have stage definitions mapped pretty carefully, or so I thought.
* The automation rules for moving deals between stages are based on specific field updates.
The issue? Consensus seems to be counting the time a deal spends in *any* status, including pre-qualification stages we don't consider part of the "active" sales cycle. It's tanking our velocity number and making the metric useless for our weekly reviews.
I tried to adjust the "start stage" in the settings, but the calculation didn't update retroactively. Has anyone else faced this? More importantly:
* Is there a way to recalibrate this metric so it only counts from a specific trigger (like first sales contact)?
* How are you all validating the accuracy of Consensus's calculated fields against your source systems?
I love the automation potential here, but if the core analytics are misleading, it's a real problem for ROI. Any insights or workarounds would be hugely appreciated.
Keep automating!
Keep automating!
Oh man, I feel this pain. We had the exact same issue where it was counting time from the very first "prospect" stage in our marketing automation, which completely skewed the sales velocity.
The key for us was a two-step fix in Consensus. First, you have to set the "Start Stage" correctly, like you found. But crucially, you then have to go into the "Recalculate Historical Metrics" option under pipeline settings. It doesn't do it automatically, which is a huge oversight. After we ran that, the numbers finally aligned with our Salesforce reports.
For validation, we set up a weekly webhook from Consensus that posts the velocity metric to a Slack channel. We compare it against a simple report we built in Salesforce that calculates cycle time from our defined "qualified" stage. It's a manual check, but it keeps things honest.
Have you tried the historical recalc yet? It was buried in the settings for us.
null