What Kaiju is and who it's for

Most outbound teams already know which companies they want to sell to. What they don't know is which of those companies is worth contacting this week. Kaiju is built to answer that question for every account on your list, and to keep answering it as things change.

Today we’ll cover what the Kaiju platform is, who it's for and how it works. If you're comparing tools, it should tell you whether Kaiju fits. If you've just signed up, we’ll tell you what to do first.

What Kaiju does

Kaiju watches a list of accounts you give it. It researches each company, notes what has changed, and tells you when enough has changed that an account looks ready to buy. For each of those accounts, Kaiju also tells you who to contact and which angle to take.

The key idea is that Kaiju Platform works from live research instead of a stored database. The data is gathered from the accounts themselves, and Kaiju regularly reviews and updates them as new observations become available. 

Who it's for

Kaiju is for B2B teams that run outbound against a list of target accounts. In practice that means SDRs, BDRs, account executives, GTM engineers and the RevOps people who support them, along with founders who still do their own selling.

You need two things for it to work. You need a list of accounts worth researching, and someone willing to act when an account is ready. Without both, Kaiju has nothing to say and nobody to say it to.

How it works

You bring a list. Kaiju works from your ideal customer profile. You import a CSV of accounts that fit it and choose where the list should live in your workspace. That's the whole setup.

Kaiju researches the accounts. In the background it reads each company and records observations. An observation is a change on an account: a new tool in their stack, a funding announcement, a hire. On its own, an observation is not a signal. It tells you something moved, not whether anyone is ready to buy. A funding round doesn't mean the budget is open for your category, and a new head of sales may have nothing to do with what you sell.

Observations add up to a buying window. A buying window is a group of observations that together suggest the right time for an account to consider buying. Here's a made-up example. A company replaces part of its tech stack, announces funding a few weeks later, and brings in a new leader in the department that would own your product. Any one of those could be a coincidence. Together they describe a company that is changing how it works and has money to do it. That's the account you contact first.

Accounts that haven't reached a window stay on your list. Kaiju keeps reviewing them, and that can change when a new observation arrives.

Each window comes with a contact and an angle. The observations behind a buying window also point to the right person at that company and the approach to take. Your first message can open with what actually changed, instead of a generic line about your product.

Getting accounts out of Kaiju

Accounts in a buying window are available through webhooks and integrations, so they don't have to stay inside Kaiju. You can send them to the tools your team already uses, such as your CRM or a sequencer, and let your existing process take over.

Each account carries its metadata and contextual information. An SDR can see why an account is in a window before writing a word, and an AE preparing for a first call can see the same history. Nobody has to research the account again.

How it differs from what you use now

Teams that do this work today usually combine a few things, so it helps to be clear about where Kaiju sits.

BuiltWith and Wappalyzer tell you which technology a company uses, and they serve that from stored data. That's useful for a lookup, but a snapshot can be out of date by the time you act on it, and it covers one kind of information. Kaiju follows several kinds of change on the same account (technology, funding, hiring) and treats the combination as the signal.

Clay lets you build your own enrichment and automation. If you have the time and skill, you can assemble something close to this, and many teams do. The cost is that you build it, maintain it and trust it yourself. Homegrown scrapers and scripts have the same trade-off. Kaiju is the version you don't have to build or keep running.

Happy hunting!