Glossary

The words behind Catalyst in plain language — one sentence each, the way a salesperson would understand it, not an engineer.

Market and client

Pharma and biotech
companies that develop drugs: large pharmaceutical corporations and small biotechnology startups.
CRO
contract research organization: a contractor that does part of the scientific work for pharma (chemistry, biology, testing).
CDMO
contract development and manufacturing organization: a contractor that develops and makes a substance or drug product to order.
Big Pharma
the largest pharma corporations with many subsidiaries; every email to them is approved by a person, never sent in auto mode.
Subsidiary / parent group
a subsidiary is recognized by its email domain and leads to the parent corporation, which may have its own arrangements with you.
Service profile
the list of what exactly you can do for a client; the system filters out events outside it.
Medicinal chemistry
designing and improving molecules that could become drugs.
Screening
testing thousands of compounds to find the ones that act on the intended target.
DMPK
studies of how the body absorbs, distributes and clears a substance; a mandatory stage before the clinic.
Target
the protein or mechanism in the body that a future drug must act on.

Sales and CRM

CRM
the software where reps manage deals and contacts; Catalyst reads it but never overwrites your fields.
Deal
a CRM record of a possible contract with a specific company; it has a value, a stage and an owner.
Pipeline
the sequence of deal stages from first contact to payment.
Stalled stage
a deal that has sat at one stage for a long time with no movement; this is the deal the system proposes to revive.
Lead
a person at a client company with whom a conversation is or could be under way.
Rep
your business development manager, in whose name the emails go out and who approves them.
Champion
the person on the client's side who handled your business; when they leave the company, the system looks for a successor.
Lead owner
the specific rep a person is assigned to; if a second rep reaches for the same company, they see a warning first.
Book
all the people and deals you already have; “money from the existing book” means bringing back those who know you.

Emails and touches

Touch
one approach to a person: an email or a LinkedIn message.
Sequence
several touches in a row with pauses, each adding something new.
Follow-up
the next email after silence, which reminds without repeating the previous one.
Reactivation
returning to a conversation with a client where things stalled.
Cold email
the first email to a person you have never spoken to; by law it must not invent a “previous interaction”.
Card
the ready email put in front of the rep, with the trigger, the warnings and the decision buttons.
Tap
pressing a button on a card: send, skip, bad text, take the contact.
Thread
a chain of emails on one subject; a reply goes into the same thread, not as a new email.
Trigger
a concrete reason to write right now: a grant, a funding round, a job change, a stalled deal.
Email footer
signature, title, the company's postal address, unsubscribe line; without them the email does not go out.
Unsubscribe
a request to stop writing; after it, the person goes onto the do-not-contact list that every engine checks.
Do-not-contact list
the shared list of people who must not be written to: unsubscribed, declined, asked for their data to be erased.
Bounce
an email that was not delivered. Hard — the address is dead; soft — a temporary problem, pause and retry.
“Not now”
a soft decline with a date: the lead returns to the queue on its own when the pause ends.
Contact swap
the lead says “my colleague handles this”: the conversation moves to the colleague together with its history.
Personalization
the email is built from this person's history and this company's science, not from a template.

RADAR and data

Engine
one of the system's four separate jobs: RADAR, reactivation, cold outreach, auto mode; each has its own cap.
RADAR
the part of the system that looks for triggers in public sources and turns an event into a new lead.
Signal (event)
a fact from a registry that means a company has just received budget or new work.
Registry
a public database kept by a government body or regulator, such as funding, clinical or patent records.
Source
one feed of public signals — funding, clinical and regulatory records, new science, company activity.
Research grant
public funding for a research program; the award is a public record.
Clinical trials
testing a drug in humans; a new phase means new work for contractors.
Company → person bridge
the step that gets from a company name to a specific person in the right role.
Domain
the part of an email address after “@”.
Role
the title that decides on outsourcing: chief scientific, executive or business officer, not “the first contact we found”.
Enrichment
filling in a person's business email and title from an outside provider.
Vendor (provider)
an external service the system calls for a fee: address verification, people search, the model for text.
Lead source
a tag showing where a person came from.

Rules and safeguards

Gate
a check before an action; if it fails, the action does not happen and the reason is written to the log.
Cap (quota)
a daily or weekly limit: how many cards or emails may go out; anything beyond queues for tomorrow.
Weekly budget
how many emails are allowed over a set period for the whole company; it protects the domain's reputation.
Domain reputation
how mail providers rate your address; too many bounces and everyone's email goes to spam.
Address check
an external service confirms that the address exists before an email is sent.
Pause key
one key that pauses outgoing email within seconds.
Pause with a date
the lead is set aside until a specific day and returns on its own; “forgotten for good” doesn't happen.
Auto mode
sending without a tap; switched on only where it has proven accurate on your own live data.
Banned direction
sanctioned countries and domains, and your own company's addresses: blocked at the gates.
GDPR
the European data-protection law; for a person whose data was not obtained from them, the first email must name the source and the right to object.
Right to erasure
a person may demand that their data be deleted; the system recognizes such an email and tracks the deadline.
CAN-SPAM
the US law on commercial email: a genuine sender address and a way to unsubscribe in every email.
Legal credentials
signature, title, company address, unsubscribe line; the gates don't let an email through without them.

The technology you don't see

Workflow
one automated process of Catalyst: read the deals, classify a reply, build the report.
Step
one action inside a workflow: read a record, call a service, send an email.
System memory
where Catalyst keeps pauses, counters and a record of what it has already done, so repeats are recognized and skipped.
Model
the AI language model that writes the draft and classifies replies according to rules set by people.
Prompt (model instructions)
the instructions for the model: what to write, what not to write, which facts are allowed.
Approved facts
the single list of figures and claims about your company, kept by a human; what isn't on the list isn't written.
Protection from hidden instructions
the lead's text is given to the model as data, with instructions never to follow commands inside it; outside auto mode, a person approves every email.
Action fingerprint
a unique mark on every event, so a repeated email or signal is recognized and skipped.
Lock
a marker meaning “this record is already being worked on”, so two processes don't write to the same person at once.
Failure queue
a separate list of everything that failed, with the full request; it can be reviewed and retried.
Touch log
the table recording every email, reply, pause and the reason for every skip.
Meeting notes
the automatic transcript of a call: what was discussed, what was agreed, what is still on you.
Report
a page with the system's own counters for a period: how many events, leads, emails, replies, and why the rest didn't go out.