Adds to your score
ZoomInfo | Intent topics
Revenue Intelligence
211 of 446 wins
Only 99 of 554 losses had it.
Signal audit
Find out which of your ZoomInfo, Clay or 6sense signals actually came before your wins, free and read only, with nothing in your CRM changed.
No CRM connection? Use a spreadsheet instead.
Example report
Example data | 446 wins and 554 losses in HubSpot
Adds to your score
ZoomInfo | Intent topics
211 of 446 wins
Only 99 of 554 losses had it.
Predicts nothing
Your own lead score
101 of 446 wins
110 of 554 losses had it too.
Leans toward losses
ZoomInfo | Technologies they use
122 of 554 losses
16 of 446 wins had it.
Predicts nothing on deals of $149K and under
Predicts nothing on deals over $284K, on Expansion and Renewal deals and in Healthcare
How it is graded. Kaypo tried each value at creation and 30, 14 and 7 days before close, and 14 days before close predicted best on deals it was not fitted on. A field counts at a strength of at least 5 wins and 1.5 times as common in wins as in losses. 76 deals were left out of a field that was first set after that point. Example data.
Example data. Kaypo graded 6 vendor fields in HubSpot on 446 won and 554 lost deals, each value read 14 days before close. 2 of 6 fields add to our score, led by ZoomInfo Intent Topics: Revenue Intelligence, on 211 of 446 wins and 99 of 554 losses. 3 of 6 fields predict nothing, our own lead score among them: its highest quarter (76 to 100) was on 101 of 446 wins and 110 of 554 losses.
How it works
No tool can fairly grade itself, so Kaypo grades all of them against your own closed deals, with one rule and one cutoff for every field.
Connect HubSpot from the start page, or Salesforce from the free workspace it opens. The grade reads and writes nothing back.
Each vendor field is read as it stood before the deal closed. Kaypo tries creation and 30, 14 and 7 days before close, keeps the point that predicts best, and never reads the final 7 days.
Every field counted against your wins and your losses, with both counts, a verdict, and whether it adds anything beyond Kaypo's own score on deals the model was not fitted on.
Export your closed deals with the vendor columns, the outcome, the close date and the created date. Kaypo lists the tools it finds in your column names for you to confirm, then grades each column. A spreadsheet holds no history, so add a column named like "ZoomInfo Intent Topics set on" with the date each value was set, and Kaypo grades it as it stood before each close. A column with no set on date is marked Needs history.
Uploaded deals are kept in the free workspace the upload opens, so the report can be built. Its Import page clears the deals, their signals and the vendor columns at any time. Company names stay in the workspace as accounts, column names stay in its list of fields, and the list of uploads keeps each file name and row count.
What it reads
Questions
Grading starts at 30 closed deals, won and lost, and every closed deal you add makes each count harder to put down to chance. A field counts on a deal only when it was set before the cutoff. A field first written after a deal closed is left out of that deal, and a field with too few deals behind it is marked Needs history.
Kaypo grades any tool that writes fields into HubSpot or Salesforce, including ZoomInfo, Clay, 6sense, G2, Bombora, Demandbase and your own lead score. It tells them apart by who wrote each value, the Salesforce package a field came from, the field description and the field name. Anything it is unsure of goes into a short Fields Kaypo found list for an admin to confirm.
A field loaded into the CRM from a spreadsheet carries the import date in its history. Values imported before a deal reached its cutoff count like any other. Values imported after it cannot count for that deal, because Kaypo cannot tell what the field said before the close.
Nothing in your CRM changes. The grade only reads. A field that adds something can go into scoring with one click, and that changes Kaypo's own model, never a field in HubSpot or Salesforce.
Kaypo grades fields in both. HubSpot connects from the start page, and Salesforce from Connections in the free workspace the start page opens. HubSpot keeps the earlier values of a property with the date each was set. Salesforce keeps history only for fields with field history tracking turned on, up to 20 per object by default, so an untracked vendor field shows as Needs history until it has history to read.
Sources: HubSpot developer docs, reading a deal with propertiesWithHistory | Salesforce Ben, Salesforce field history tracking
Free, read only, and the report is yours to forward.
30 minutes with the founder
Bring your intent tool and your own deals. Pick a time and it is booked.