How to combine safety screening with spec-driven candidate discovery to triage leads faster and with fewer dead ends.
Most lead-optimization campaigns follow a linear path: design candidates for activity, synthesize them, then check whether they have acceptable ADMET profiles. The problem is that this sequence guarantees wasted effort. Candidates that fail safety screening after synthesis represent months of chemistry investment that could have been avoided.
A triage workflow reverses this. Instead of designing first and screening later, you screen first — and only design within the space that has already passed a safety filter. This article describes how to do this in practice using two FluxMateria capabilities: the ADMET module and the Inverse Search engine.
ADMET screening evaluates absorption, distribution, metabolism, excretion, and toxicity for a given molecule. The FluxMateria implementation runs a full panel — solubility, permeability, CYP inhibition, hERG liability, hepatotoxicity — at approximately 350 molecules per second, with confidence indicators on every prediction.
Inverse Search works in the opposite direction. Instead of "here is a molecule, what are its properties?", it answers "here are the properties I need — which molecules meet them?" You define a specification (target ranges for solubility, permeability, molecular weight, logP, etc.) and the engine searches a candidate library for matches.
Used separately, each is useful. Used together, they create a triage workflow that is fundamentally more efficient than the linear alternative.
In a linear workflow, the medicinal chemistry team designs 50 candidates, synthesizes 30, and discovers after assay that 12 have ADMET liabilities. Those 12 represent wasted synthesis cycles.
In a triage workflow, the team starts with thousands of candidates in a virtual library, screens all of them computationally (seconds, not months), and advances only the ones that pass both the property spec and the safety filter. The synthesis queue is shorter, but every compound in it has a higher probability of surviving downstream testing.
The economics are straightforward: if synthesis and assay costs are $5,000–$50,000 per compound, and computational triage costs effectively nothing, even a modest reduction in late-stage failure rate pays for itself many times over.
The Inverse Search module includes six built-in spec presets (oral drug, CNS drug, topical, inhaled, pediatric, geriatric) that encode common property ranges for each delivery route. These are starting points. In practice, most teams will customize them based on their specific program constraints: target tissue, patient population, co-medication risks, and existing SAR knowledge.
The spec DSL supports 20 searchable properties, including molecular weight, logP, TPSA, HBD/HBA counts, rotatable bonds, and all ADMET endpoints. Ranges can be set as hard cutoffs or soft preferences.
In a triage workflow, confidence indicators are not optional. They are the mechanism by which you separate "safe to advance" from "needs experimental verification."
A candidate with high-confidence ADMET passes across all endpoints is a strong advancement candidate. A candidate with high-confidence passes on four endpoints and a low-confidence pass on hepatotoxicity is a candidate where the hepatotoxicity assay should be prioritized in the experimental plan. A candidate with a high-confidence fail on hERG is a candidate to deprioritize or redesign.
Without confidence signals, every computational pass looks the same. With them, you can allocate experimental resources where they will be most informative.
Lead triage is not a new idea. What is new is the ability to run it at scale, at speed, with deterministic results and per-prediction confidence. When you can screen a full ADMET panel on thousands of candidates in seconds, and pair it with spec-driven candidate discovery, the triage workflow becomes the default — not a luxury.
Paste a SMILES string and get a full ADMET panel in milliseconds. No signup required.
Try the Demo