The rep decides — the system carries out
A draft waits in the rep’s workspace until a human taps “send” or “skip”; auto mode sends without a tap only where you have switched it on.
A deal dies not from a “no” but from silence, a forgotten address and a contact who moved on.
Catalyst finds new clients — and brings back old ones — for CRO, CDMO and CMO teams: it spots the reason to write, drafts the email in the rep’s voice and hands it over for approval.
The deck is written for CROs. A CDMO or CMO? Name your direction on the contact form and a founder replies with what fits it.
Who this is for
A CRO — medicinal chemistry, screening, biology, DMPK, preclinical or clinical services. A CDMO or CMO — development, manufacturing, packaging and supply, with buyers in CMC and supply chain, whose oldest deals still sit in a spreadsheet. Either way, your new business is a few high-value contracts with pharma and biotech, won through people rather than advertising. You own the pipeline. Your mailbox, CRM and LinkedIn stay yours.
42,966
new clinical studies registered in 2025
ClinicalTrials.gov · by first-posted date · counted 13 September 2026
62,804
NIH-funded projects in fiscal year 2025
NIH RePORTER · NIH only, sub-projects excluded · counted 13 September 2026
46
novel drugs approved by the FDA in 2025
FDA Center for Drug Evaluation and Research · Novel Drug Approvals for 2025 · checked 13 September 2026
$69.6–85.4B
research outsourced to CROs in 2025
$197.4–258.9B
development and manufacturing outsourced to CDMOs in 2025
published estimates for 2025: Precedence Research (Feb–Mar 2026), MarketsandMarkets (Apr 2026), Mordor Intelligence (Sep 2026)
What you get
A reason to write today, a draft in your rep’s voice, one tap.
A reply becomes a deal
What moves forward becomes a deal in your CRM — owner, stage and value.
Follow-ups continue without a reminder
Nobody disappears in silence — the next touch is drafted and ready when it is due.
Catalyst finds the pulse in deals that went quiet.
How it works — one loop
Examples are invented — the situations, people, companies and emails.
Catalyst in numbers
All-time totals for one CRO client, shown without its name with its permission — counted from the system’s own logs, updated weekly. Not a forecast.
2,853
public grant and hiring records read
86
kept as a real reason to write — the rest never reached a rep
38
named people found behind those reasons
174
emails drafted in the rep’s voice
201
replies read and given an action
92%
of quiet deals matched back to their contact automatically
Every reply gets an action
The rep only sees what needs a human; pauses, do-not-contact entries and return dates happen on their own.
01
Agreed to a meeting
names a time, books or gives a phone number
alert the rep immediately
02
Interested, nothing specific
“sounds good”, “I’ll check my calendar”
the sequence pauses, the decision is the human’s
03
To a colleague
“talk to X”
contact swap
04
“Not now” or budget frozen
a pause with a date; the lead comes back on its own
05
Decline
“not relevant for us”, “we’re covered”
stop and do-not-contact
06
Question about services or price
straight to the rep
07
Left the company
a search for the successor in the same role
08
Project closed or went elsewhere
the reason for the loss is recorded
What Catalyst never does
Enforced by the system itself — not a policy someone has to remember.
invent a fact
figures and claims about your company come from a single list kept by a human; what is not on it is not written.
invent a history
a first email never “reminds” anyone of a conversation that never happened.
obey a lead’s text
a reply is handed to the model as data, with an instruction not to follow commands in it.
email Big Pharma on its own
a corporation with subsidiaries gets a manual card for the rep, not an automated email.
touch a person twice at once
email, LinkedIn and — for key contacts, on an approved card — SMS take turns, and other people’s deals are never touched.
attach a file
files are never attached to an email to your leads.
write to someone who said no
one do-not-contact list, shared by every engine.
Your team, your data
Your accounts stay yours — the boundary is enforced by the database.
EU region · isolation · full export
hosted in an EU region; isolation enforced by the database itself; a full export at any time, in a standard database format
No footer, no email
the gates require a signature, a title, the company’s postal address and an unsubscribe line
Address check before every email
an address that fails the check gets no email — far fewer bounces reach your domain
56%
of all steps handle failure, not the work
More than half of the system exists for what goes wrong — 56% of all steps handle failure rather than the work itself
measured in September 2026 · how data is handled
Two ways to run it
Subscription pricing is discussed on the first call.
Format A
Your team runs it
Day to day, and the know-how stays with your team; we support the setup and the rules.
Format BRecommended
Turnkey — we run it for you
Our business development manager runs the engines and takes leads to the call — inside your accounts and in your rep’s voice.
The questions a buyer asks first
Short answers about your data; the full terms will go into the data processing agreement each client signs.
01Whose data is it?
Yours. Every lead, email, note and reply belongs to your workspace. You can have a full export at any time in a standard database format — ask us and we will deliver it.
02Can another client see our leads?
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.
03Where is the data stored?
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.
04Who sends the emails?
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.
05What happens when we leave?
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.
06Someone asked to be erased — then what?
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.
07Can we pause all outgoing email at once?
Yes — one key pauses Catalyst’s outgoing email within seconds, and sending is capped over a rolling week.
Stop losing deals to silence.
Catalyst finds the right moment to reach out and drafts in your rep’s voice.
Security · how data is handled · subprocessors · privacy