Skip to main content

Introduction to the Databook Score

The Databook Score is Databook's proprietary outside-in propensity-to-buy score

Written by Hriday Vaid
Updated this week

What is the Databook Score?

The Databook Score provides a data-driven propensity-to-buy (P2B) score for every company in Databook.

It provides a simple score between 5.0 (high propensity to buy) and 0.0 (low propensity to buy)

How is the Databook Score calculated?

The Databook Score is a multi-factor score. Clicking on the hyperlink below the score provides a breakdown of some of the key components of the score.

  1. Financial case for change. Databook analyses performance across key financial metrics.

  2. Buying cycle. Databook looks at how a typical deal is aligned with the customer's annual budgeting cycle.

  3. Management intent. Databook calculates an intent score based on how frequently the customer is referring to keywords that are important to you.

  4. Investor sentiment. Databook searches for red flags that could be signs of financial distress at the customer, and a higher risk for your deal.

Can the Databook Score be customized to my solutions?

Enterprise customers can customize the Databook Score algorithm to align with your solutions, use cases and go-to-market strategy. Please contact the Databook team for more details about this.

Where can I find the Databook Score?

The Databook score is available for every company in the Overview section

You can find the score in the overview section for each company:

And you can also view competitors’ Databook scores here -

How accurate is the Databook Score?

We believe that it is the most sophisticated external P2B score available. However, the score relies entirely on publicly available data and information, so there are often additional factors that can affect a prospect's propensity to buy. Therefore, we recommend that you use the Databook Score as a starting point for prioritizing accounts or prospects but not as a substitute for further research and analysis.

Did this answer your question?