you write exactly when a company has just received budget or new work — not to “check in”
01 · RADAR
a new research grant — budget for exactly the work you do
02 · RADAR
the company has just raised money — the budget has just appeared
03 · RADAR
a new trial or a move to the next phase
04 · RADAR
a regulator's decision on a drug or an application
05 · RADAR
new science that shows where a program is heading
06 · RADAR
a team hiring for new work — a contractor is often needed before the hires arrive
Example
a biotech wins a grant to develop a compound. Soon after the award is published, the rep has a card with an email to that company's chief scientific officer
an email that is visibly for this person, not a mass mailing; the rep only edits or taps
Example
on a call you agreed to send a proposal — the email opens with exactly that, not with “just checking in”
call notes: what was discussed, what was agreed, what is still on you — the strongest reason to write
all previous email with the person, so the new email continues the conversation instead of restarting it
what we already wrote and how the person replied
what has already been said in the other channel — so the email does not repeat it and does not read like a stranger's
each new email is written to avoid the opener, angle and question of every earlier one in the sequence
figures and claims about your company come from a single list kept by a human; what is not on it is not written
the rep only sees what needs a human; pauses, do-not-contact entries and return dates happen on their own
names a time, books or gives a phone number → alert the rep immediately
“sounds good”, “I'll check my calendar” → the sequence pauses, the decision is the human's
“talk to X” → contact swap
→ a pause with a date; the lead comes back on its own
“not relevant for us”, “we're covered” → stop and do-not-contact
→ straight to the rep
→ a search for the successor in the same role
→ the reason for the loss is recorded
someone replied on LinkedIn — a deal is created in the CRM immediately, with an owner and a stage
a different person answers in the same thread — the system shows who actually runs the matter and stops emails to the silent address
the lead referred you to another company — later they return to the desk on their own, with that conversation as the opener
“later” and “left the company” each get their own return date · “I'll take it” — the machine steps back. No “forgotten for good”
every week — a list of people we no longer contact but whose deal is still open, with its value; the decision is the human's
no address was found — the system keeps retrying on its own, and if it still fails, hands the lead to a person
you can't see it in a demo, but it is what decides whether the system still works a year from now without manual supervision
1.3×
failure-handling steps for every working step
For every working step there are 1.3 steps that handle failure — more for failure than for the work itself
measured September 2026
every action carries a fingerprint, so a repeated signal, email or reply is recognized and skipped
an outside service went down — the lead keeps its chances; the system waits and resumes
every retry has a ceiling; once reached, the record moves to a named final state with a reason and an alert to a human
a pharma lead can be worth a large contract, and your domain's reputation even more
Example
the rep tapped “send” on an older card — the system re-read the deal: closed → the email does not go out
the gates require a signature, a title, the company's postal address and an unsubscribe line
anyone on your do-not-contact list — unsubscribed, declined or erased — gets no Catalyst email; one list for every engine
the system recognizes such an email on its own, logs it and raises the alarm well before the legal deadline
files are never attached automatically; the lead's text is given to the model as data, with an instruction never to follow commands inside it
sending is capped over a rolling week; one key pauses outgoing email within seconds
external deliverability verification: an address that fails the check gets no email, so far fewer bounces reach your domain
a public record tells us when to write; the person to write to is found and verified separately, and we do not use contact details published in the record
on the platform, everything specific to you — texts, signature, sources, limits, schedules — lives in settings, not in code; checking on the work needs no access to your mailbox or database
every lead has an owner; if a second rep reaches for a company already in work, they see a warning first — or you can make it a hard block; lead handover has a set path
channel limits are shared by the team — they protect the domain; daily card quotas are separate per engine
grants, trials and approvals are dated public events with a company behind each one
42,966
new clinical studies registered in 2025
ClinicalTrials.gov · by first-posted date · counted 13 Sep 2026
65,888
NIH-funded projects in fiscal year 2025
NIH RePORTER · sub-projects excluded · counted 13 Sep 2026
46
novel drugs approved by the FDA in 2025
FDA Center for Drug Evaluation and Research · Novel Drug Approvals for 2025 · checked 13 Sep 2026
Research outsourced to CROs — $69.6–85.4 billion in 2025. Development and manufacturing outsourced to CDMOs — $197.4–258.9 billion.
published estimates for 2025: Precedence Research (Feb–Mar 2026), MarketsandMarkets (Apr 2026), Mordor Intelligence (Sep 2026)
the platform, the four engines and the cost of running them come in one subscription — run it yourself, or have us run it for you
AI, mailbox and CRM run on your own accounts and keys, and you pay them directly — we resell no data and no model access
your own isolated workspace on the platform, hosted in the European Union
a dedicated environment for your company alone — owned and paid for by you
short answers about your data; the full terms go into the data processing agreement we sign with every client
Yours. Every lead, email, note and reply belongs to your workspace. On the platform, you can have a full export at any time in a standard database format — ask us and we deliver it.
On the platform, the database itself enforces the boundary, not only the app: every record is tied to your workspace, and isolation tests try exactly that — one client reading another’s data.
On the platform, your database is hosted in a European Union region, where the provider stores and primarily processes it. Providers that process your data are listed by category on the subprocessors page; clients receive the named list and advance notice of changes under the data processing agreement.
Your rep, from their own mailbox, in the same thread. Nothing goes out from a shared Kason address, and each client sends only from its own accounts.
You take a full export of your data. And when someone leaves your team, their leads are handed over along a documented path — nothing is lost in a chat.
The system recognizes the request on its own and raises an alarm well before the legal deadline. The erasure is completed within the legal deadline; only a minimal record of the refusal is kept, so the address is not written to again.
Yes — one key pauses Catalyst’s outgoing email within seconds, and sending is capped over a rolling week.
We work with a small number of CRO and CDMO teams at a time — each shapes the platform and runs it first. Run it yourself, or have us run it for you.
Security · how data is handled · subprocessors · privacy
Catalyst · four engines: reactivation + follow-ups · RADAR · cold outreach · auto mode
your CRM and your reps’ mailboxes stay yours · your data can be exported in full at any time