The rep decides — the system carries out
Every draft waits in the rep’s workspace until a human taps “send” or “skip”.
A deal dies not from a “no” but from silence, a forgotten address and a contact who moved on.
Who this is for
A CRO — medicinal chemistry, screening, biology, DMPK, preclinical or clinical services — whose new business is a few high-value contracts with pharma and biotech, won through people rather than advertising. You own the pipeline. You approve every email. Your mailbox, CRM and LinkedIn stay yours.
Design partners, not a waiting list.
We work with a small number of CRO and CDMO teams at a time — each shapes the platform and runs it first.
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
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)
What you get
A reason to write today, a draft in your rep’s voice, one tap.
A reply becomes a deal
The moment a lead answers, a deal opens in your CRM with 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.
66
replies classified as positive
from one client’s pipeline, not a forecast · measured 17 September 2026
Five engines — one system
Three channels — email, LinkedIn and SMS — never at once with one person; SMS only for key contacts, by an approved card.
01RADAR
reads public signals and turns an event into a lead.
02Reactivation
a short sequence that reopens quiet deals, no repeats.
03Cold outreach
first contact with people you have not met, under its own daily cap.
04Auto mode
sends without a tap only where accuracy is proven.
05Sprint
conferences and trips: the calendar fills before the rep packs. Two modes — conference or trip. People return to the usual engines afterwards.
One email, end to end
What the rep sees — and what happens after one tap.
A fictional example: the company, the people and the email are invented; the card is what the rep sees in the workspace.
TriggerYesterday: a grant announced for a lead-compound program at a biotech — public registry entry
ToDr. Lena Hart, Chief Scientific Officer, Arbor Therapeutics (fictional)
Checksaddress verifiedno live conversation at this companynot Big Pharmawithin this week’s sending cap
SubjectCongratulations on the grant — DMPK capacity when the program needs it
Dr. Hart — congratulations on the grant for your lead-compound program announced yesterday.
When a program moves from hit to lead, DMPK and in vivo PK studies usually become the bottleneck; we run exactly these studies for early-stage biotech teams.
If useful, I can send a one-page outline of what a first study looks like and typical timing.
Would a short call next week suit you?
Anna Lewis · Head of Business Development · Northline Research (fictional) · postal address · unsubscribe
Four buttonssendskipbad texttake the contact
After the tap
- sent from Anna’s own mailbox — a new thread, because there was none yet
- reply: “Timing is right — can we talk on Tuesday?”
- classified as interested → Anna is alerted
- meeting → a deal in the CRM: owner, stage, value
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
The rep stays in control
Approval card
carries the trigger and any warnings before you decide.
One tap
send, skip, mark bad text, or take the contact.
Caps and one list
sending is capped over a rolling week, and one do-not-contact list covers every engine.
One key
pauses outgoing email.
Your team, your data
Your accounts stay yours — the boundary is enforced by the database.
Your rep sends, 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
Isolation by the database itself
every record is tied to your workspace, and isolation tests try exactly that — one client reading another’s data — and must fail
Hosted in the European Union
your database is hosted in an EU region, where the provider stores and primarily processes it; providers are listed by category on the subprocessors page
A full export at any time
in a standard database format — ask us and we will deliver it; when someone leaves your team, their leads are handed over along a documented path
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
external deliverability verification: an address that fails the check gets no email, so far fewer bounces reach your domain
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 in September 2026 · how data is handled
Two ways to run it
Format A — our business development manager runs the engines and takes leads to the call, inside your accounts and in your rep’s voice. Format B — your team runs it day to day, and we support the setup and the rules. Both keep the same control: the rep approves every email, and your accounts stay yours.
Subscription pricing is discussed on the first call.
The questions a buyer asks first
Short answers about your data; the full terms will go into the data processing agreement each client signs with us.
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, and sending is capped over a rolling week.
Design partners, not a waiting list.
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 · five engines: RADAR · reactivation + follow-ups · cold outreach · auto mode · sprint
your CRM and your reps’ mailboxes stay yours · your data can be exported in full at any time