A good-fit account with a reason to look now
A qualified account becomes more timely when a relevant condition changes.
Evidence-backed sales signals
Research your accounts. Inspect the evidence.
Bring a List of companies. Kaiju researches supported sources and records evidence-backed Signals. Open the findings, dates and coverage before deciding where to focus.
Illustrative preview: Fit scores, Buying Windows and Priority views shown below are planned beyond V1.
The sales problem
Your account list keeps growing. Your team’s time doesn’t.
A hiring push, new leader, technology change, funding event, or other trigger can make an account worth another look. These signals are easy to miss across the web, CRM, and research tools.
- 01
Good accounts blend into the list.
Research gives your team evidence to decide which accounts deserve a closer look.
- 02
Important changes happen between CRM updates.
Leadership, hiring, technology, funding, and other changes can appear before anyone updates the CRM.
- 03
Research takes time, and useful proof gets lost.
Reps chase context across tabs. Research depth varies, and the source behind a useful signal gets lost.
What changes for sales
Open the list and know where to start.
Relevant changes stand out with enough context to decide whether the account deserves a closer look.
Know what happened and why it matters
See supported Signals with their dates and underlying evidence.
See the proof before outreach
Trace the conclusion back to its sources before outreach.
How Kaiju works
Add companies. Run Research. Review the results.
Start with a List of companies or a CSV. Research supplies evidence for the supported Signal definitions.
- 01
Choose the companies to research
Add companies to a List and provide the context your team uses to assess them.
- 02
Run Research
Kaiju checks supported sources. Supported Signal definitions evaluate the accepted evidence.
- 03
Inspect the findings
Filter your List using supported facts. Open Signals and their evidence before taking action.
Research coverage
Check the evidence behind relevant changes.
Coverage depends on the research unit and available sources. These are research topics; only supported definitions with sufficient evidence produce Signals.
01
Technology
A platform is installed, removed, or replaced
Spot migrations, modernization work, expansion, or a new competitive opening.
02
People
A relevant leader joins or a buying group changes
See changes in ownership, priorities, or the people your team should understand.
03
Hiring
A team starts growing
See where a company is investing and which teams are gaining weight.
04
Company activity
Funding, expansion, acquisitions, and other company events
Use dated funding, expansion, acquisition, and other company events when they affect the problem you solve.
The V1 workflow
From your List to the supporting evidence.
Add companies to an explicit List, run Research, and review supported Signals. Dynamic Lists, automated Fit and Priority scoring, Buying Windows and continuous market monitoring are planned beyond V1.
Lists
Which companies should Kaiju research?
Research
What can the supported sources establish?
Signals
Which supported changes have evidence?
Evidence
Which sources, dates and coverage support the result?
Proof behind the signal
Keep the evidence attached to the signal.
See the source, date, supporting observations, and what remains unknown before acting on a conclusion. The illustrative preview includes planned Fit and Buying Window views.
- Open the sources and observations behind a fact or signal
- See when the event happened and when Kaiju observed it
- Keep freshness, coverage, conflicts, and unknowns visible
CRM + Kaiju
Your CRM adds the signals the public web cannot see.
CRM activity can add first-party evidence the public web cannot see. Twenty is the first CRM integration in development.
Available now
AvailableStart with the accounts you already know
Keep the IDs and fields your team already uses while Kaiju adds research and evidence.
Priority integration
In developmentTwenty brings first-party sales activity into the picture
Opportunity changes, stakeholders, notes, and activity can support Intent, Mobilization, and Progression signals.
Target model
TargetSend the context back to the workflow
Send reviewed accounts and evidence to CRM, CSV Exports, or Webhooks.
Questions before you start
What teams usually want to know.
What is a signal in Kaiju?
A Signal is a dated, evidence-backed result produced when a supported definition is satisfied. Coverage and the underlying evidence determine which changes Kaiju can establish.
Can we define our own Signals in V1?
V1 uses the supported Signal catalog. Customer-defined Signals and continuous market monitoring are planned beyond V1.
Does a signal mean the company is ready to buy?
No. A signal can justify attention without proving budget, an active buying project, dissatisfaction, or vendor choice.
Are Dynamic Lists available in V1?
Dynamic Lists are planned beyond V1. V1 uses explicit Lists: you choose their members and filter the current results. Saved rules that automatically change membership are future work.
How do we know why an account was surfaced?
Open the account to inspect supported findings, Signals, dates, sources and coverage. Missing evidence can remain unknown.
Start with your market
Find the accounts worth your team’s time.
Bring the accounts you want to research. Inspect the findings and evidence before choosing the next step.