Company

About Kairon

Who builds it, where it is registered, and the one idea behind it.

What Kairon is

Kairon is an outbound tool for B2B teams. It finds the people a company should be writing to, judges each one against the company’s ideal customer profile, and runs the LinkedIn or email sequence that reaches them, from the operator’s own account. It is built as an MCP server, so the operator drives it from an assistant they already use, such as Claude or ChatGPT, or from a terminal with the Kairon CLI. There is also a web app, for reviewing what the agent drafted and what came back.

The idea

The name comes from kairos, the Greek word for the right moment. Most outbound is noise because it is sent to the wrong person at a random time. Kairon starts from a signal instead: a company hiring a role, a person reacting to a post, a funding round, a search the operator ran. It writes to that person then, once, from a real seat, and it stops when they reply. Autopilot is the default; a campaign schedules each send ahead, with time to review or cancel it. The goal is an outbound motion a founder or a seller can trust enough to leave running.

Who builds it

Kairon is built by its two founders, Luciano Trujillo and Mario León Rojas, and run by a small remote team that does its own outbound on the same product, from the same LinkedIn seats, under the same limits. The numbers on this site come from those seats and from the sequences our customers ran through the product. When a number does not hold, we say so.

Customers contract with Kairon, a company registered in the State of Delaware, USA, under our terms of service.

How it is run

The product runs on our own infrastructure, with the providers listed in the privacy policy. Customers are companies that run outreach from their own LinkedIn accounts; we do not buy contact databases, and we do not sell the data of the people they write to. Security reports go to the address in security.txt, and everything else to admin@heykairon.com, which a person reads.

Where to go next

  • The MCP server: every tool, with arguments and examples.
  • The CLI: the same calls, from a script instead of a model.
  • Pricing: the plans, and what each one includes.
  • Contact: how to reach us, and what to expect back.