WhiteWhale helps teams monitor accounts for custom signals and turn them into Why Now summaries, scores, discovery, and CRM updates. Kaiju V1 provides account Research, explicit Lists, supported Signals and inspectable evidence. Dynamic Lists, automated Fit/Priority scoring and Buying Windows are planned beyond V1.
Choose Kaiju for source-backed account Research, explicit Lists, supported Signals and evidence your team can inspect. Dynamic Lists and automated prioritization are planned beyond V1.
WhiteWhale may fit when
Choose WhiteWhale when daily signal monitoring, Why Now summaries, scoring, live account discovery, and established CRM delivery are the main job.
Decision table
Compare the jobs that matter.
Signal model
Kaiju
A signal definition states what to watch. A signal is the dated occurrence or state produced when the definition matches evidence.
WhiteWhale
Users write 10–15 questions that WhiteWhale calls signals. WhiteWhale monitors accounts daily and produces Why Now summaries when those signals fire.
Account decision
Kaiju
V1 centers on account Research, supported Signals and evidence. Dynamic Lists and automated Fit/Priority scoring are planned beyond V1.
WhiteWhale
Signals feed a Why Now story and a 0–100 account score based on signal strength.
CRM today
Kaiju
CSV workflows are available. Twenty is the first bidirectional CRM integration Kaiju is prioritizing and remains in development.
WhiteWhale
WhiteWhale documents native HubSpot and Salesforce integrations. Its HubSpot integration pulls company and deal context and writes scores, signals, and Why Now summaries back to mapped fields.
Discovery and working sets
Kaiju
V1 Lists contain the companies you choose. Supported fact filters narrow the results. Dynamic Lists that automatically change membership are planned beyond V1.
WhiteWhale
Live Searches find net-new accounts that match configured signals, while monitored accounts feed the signal queue.
Scoring philosophy
Kaiju
Fit and time-aware signal families stay distinct. Kaiju avoids presenting one universal buying score as a calibrated purchase probability.
WhiteWhale
WhiteWhale publishes an account score from 0–100 based on signal strength and can use deal mapping to backtest signal correlation with closed-won outcomes.
What to inspect
Kaiju
Open the source observations, timestamps, freshness, coverage, and unresolved states behind important conclusions.
WhiteWhale
Inspect the signal question, monitored source coverage, Why Now summary, score behavior, and the CRM fields your team will actually use.
Kaiju and WhiteWhale capability comparison
Dimension
Kaiju
WhiteWhale
Signal model
A signal definition states what to watch. A signal is the dated occurrence or state produced when the definition matches evidence.
Users write 10–15 questions that WhiteWhale calls signals. WhiteWhale monitors accounts daily and produces Why Now summaries when those signals fire.
Account decision
V1 centers on account Research, supported Signals and evidence. Dynamic Lists and automated Fit/Priority scoring are planned beyond V1.
Signals feed a Why Now story and a 0–100 account score based on signal strength.
CRM today
CSV workflows are available. Twenty is the first bidirectional CRM integration Kaiju is prioritizing and remains in development.
WhiteWhale documents native HubSpot and Salesforce integrations. Its HubSpot integration pulls company and deal context and writes scores, signals, and Why Now summaries back to mapped fields.
Discovery and working sets
V1 Lists contain the companies you choose. Supported fact filters narrow the results. Dynamic Lists that automatically change membership are planned beyond V1.
Live Searches find net-new accounts that match configured signals, while monitored accounts feed the signal queue.
Scoring philosophy
Fit and time-aware signal families stay distinct. Kaiju avoids presenting one universal buying score as a calibrated purchase probability.
WhiteWhale publishes an account score from 0–100 based on signal strength and can use deal mapping to backtest signal correlation with closed-won outcomes.
What to inspect
Open the source observations, timestamps, freshness, coverage, and unresolved states behind important conclusions.
Inspect the signal question, monitored source coverage, Why Now summary, score behavior, and the CRM fields your team will actually use.
Same companies
Test the results.
1Choose the same familiar companies.
2Check the fields, evidence, misses, and unclear cases.
3Count the work required before the result is usable.
Analytics helps Kaiju understand which pages and actions are useful. Marketing tracking can identify business visitors for follow-up. Essential storage remains available either way.