During a recent sales call, we were asked if instead of our predictive modeling app could they use “average days to call” as a metric? They were referring to our cfTIME app for Salesforce, which predicts time to next purchase and then determines the right time to contact the customer to increase the probability of a sale.
So, you could look at two definitions for average (didn’t you know, in statistics there are two of everything, that’s how we cover our bases!):
- Average buying cycle (ABC). This can be defined as 365 days divided by number of orders. If there are 8 orders in a year, then 365/8 = 47 days. Note that you can also choose a calendar year or trailing twelve months.
- Time to Next Order (TNO). This is the expected days to next order. One approach is to average out the previous few orders. So let’s say the last three orders were 25, 10 and 45 days apart. The average of this is (25+10+52)/3 = 29 days.
Now, the answer to this question has two parts:
- Technical feasibility
- Build vs. buy investment
Technically, our models predict at an accuracy of 80%. That means at any given point in time, 80% of the customers will buy within the window we predict for them.
But if you used an average, assuming a normal distribution, here is what you will find:

As you can see, only a small percentage of customers fit within an optimum time window for a sales contact. Customers whose buying cycle falls short of this window are often your most valuable customers. And customers who are above this average are less valuable customers who will take up a disproportionate share of your resources and will likely not yield a positive return.
Next is the question of ROI for an app such as cfTIME. What will it cost to build vs. buy? When you buy an application, the app price is a transparent cost. However when you build, there are a lot of hidden costs that cannot truly be accounted for. Employee time, hardware and software costs, efficiency (or lack thereof) are some of the costs you have to take into consideration. Further, there is an opportunity cost when your marketing vice president is spending a lot of time on something that is less effective at moving the needle in terms of sales.
A predictive model is, quite simply, an outcome-based exercise. We are either predicting more sales, more orders, higher average order sale or more categories. If a model does not deliver against those outcomes – which can be measured by applying rigorous methods – it can be modified to improve the outcomes. A simple “average” cannot deliver this.
We definitely support using simple metrics in many cases. Averages are directionally good, but if misused operationally they can have devastating consequences – ones that you may or may not be able to measure until it is too late.


