Skip to main content

Costs of Assays



I'm giving some talks over the summer, and am getting bored with some of the stuff I have, so I'm thinking of some new stuff to put in to add a bit of variety and interest. I'm getting interested in thinking about assay level attrition, and trying to put more of a taxonomy and inter-relationship mapping between assays used in drug discovery. As part of this, there is a cost component for each type of assay, going from very cheap to really really expensive. Here's a little picture from the presentation I've put together - I used educated guesses for the costs, so please, please critique them !


So, what do people think of the guesstimates of costs per compound per assay point on the picture above. I know it is really variable, there are startup costs to set something up, etc, etc. But what do you think about the orders of magnitude, are they about right? One of the key features of the numbers I've put there, are that there are big transitions at the switch between in silico and in vitro, and then on entering clinical trials.

The picture at the top of this post (about unicorns) is from the very funny http://www.depressedcopywriter.com/.

Comments

Bin said…
Hi, John, this picture is very interesting. Do you know how they got this data? It would be great to have another one illustrating the time line of each assay.
Lo Sauer said…
I applaud you for the daring attempt, but it is a difficult subject and biased (except for the unicorns which of course do exist ;) ). 'In silico' too requires scientist writing the software in the first place, and the models need to be verified and improved in co-existence with empirical experiments - thus raising costs.

One could easily envision 'selling' in-silico results based on obsolete software-models (I've seen such papers), yet performing an kinase assay past its expiration date is often unthinkable.

The cost of clinical trials are incredibly varied depending on the type of drug and drug target in question, whereas those of in-silico are typically not.

In-silico models are of course primarily optmized to computing only what is needed, and constrained by the underlying model, whereas empirical data generation is limited by other constraints, and often much more data is generated than ever published (especially when we are talking about corporate science)
jpo said…
Yes, of course, each problem is different, and the costs can be very low, or very high. Across each level of the assay hierarchy there will be cheaper assays and more expensive ones, but I made an estimate.

The costs of development are not factored in to my numbers either, since it is difficult to know when to stop..... A scientist writes the software, and they have a salary that pays them during this time, but do you count the cost of their education, etc.

It's a difficult problem!
Dear John,
I am interesting in the source of this prices. Does any reference exist supporting them?
Thank's!
jpo said…
Hi Vladmir.

The costs are just my personal estimates for this. So they are just that estimates. There could be some better ways of getting estimates - for example going to a CRO and asking for quotes for a series of defined and typical assays. The issue there is that there are many factors that would complicate things - they would have a profit margin to include, and also want to recoup cost of capital, etc. Secondly, they would not be interested in running a single biochemical assay for a few dollars, and then there would be a 'volume discount' to handle.

Another interesting number, alongside timeline as suggest by Bin, would be number of assays run per year, my guess it would be many billions for the virtual screening end of the spectrum through to maybe a few thousand at the clinical trials end.

Popular posts from this blog

ChEMBL 34 is out!

We are delighted to announce the release of ChEMBL 34, which includes a full update to drug and clinical candidate drug data. This version of the database, prepared on 28/03/2024 contains:         2,431,025 compounds (of which 2,409,270 have mol files)         3,106,257 compound records (non-unique compounds)         20,772,701 activities         1,644,390 assays         15,598 targets         89,892 documents Data can be downloaded from the ChEMBL FTP site:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/ Please see ChEMBL_34 release notes for full details of all changes in this release:  https://ftp.ebi.ac.uk/pub/databases/chembl/ChEMBLdb/releases/chembl_34/chembl_34_release_notes.txt New Data Sources European Medicines Agency (src_id = 66): European Medicines Agency's data correspond to EMA drugs prior to 20 January 2023 (excluding vaccines). 71 out of the 882 newly added EMA drugs are only authorised by EMA, rather than from other regulatory bodies e.g.

New SureChEMBL announcement

(Generated with DALL-E 3 ∙ 30 October 2023 at 1:48 pm) We have some very exciting news to report: the new SureChEMBL is now available! Hooray! What is SureChEMBL, you may ask. Good question! In our portfolio of chemical biology services, alongside our established database of bioactivity data for drug-like molecules ChEMBL , our dictionary of annotated small molecule entities ChEBI , and our compound cross-referencing system UniChem , we also deliver a database of annotated patents! Almost 10 years ago , EMBL-EBI acquired the SureChem system of chemically annotated patents and made this freely accessible in the public domain as SureChEMBL. Since then, our team has continued to maintain and deliver SureChEMBL. However, this has become increasingly challenging due to the complexities of the underlying codebase. We were awarded a Wellcome Trust grant in 2021 to completely overhaul SureChEMBL, with a new UI, backend infrastructure, and new f

Accessing SureChEMBL data in bulk

It is the peak of the summer (at least in this hemisphere) and many of our readers/users will be on holiday, perhaps on an island enjoying the sea. Luckily, for the rest of us there is still the 'sea' of SureChEMBL data that awaits to be enjoyed and explored for hidden 'treasures' (let me know if I pushed this analogy too far). See here and  here for a reminder of SureChEMBL is and what it does.  This wealth of (big) data can be accessed via the SureChEMBL interface , where users can submit quite sophisticated and granular queries by combining: i) Lucene fields against full-text and bibliographic metadata and ii) advanced structure query features against the annotated compound corpus. Examples of such queries will be the topic of a future post. Once the search results are back, users can browse through and export the chemistry from the patent(s) of interest. In addition to this functionality, we've been receiving user requests for  local (behind the

New Drug Approvals - Pt. XVII - Telavancin (Vibativ)

The latest new drug approval, on 11th September 2009 was Telavancin - which was approved for the treatment of adults with complicated skin and skin structure infections (cSSSI) caused by susceptible Gram-positive bacteria , including Staphylococcus aureus , both methicillin-resistant (MRSA) and methicillin-susceptible (MSSA) strains. Telavancin is also active against Streptococcus pyogenes , Streptococcus agalactiae , Streptococcus anginosus group (includes S. anginosus, S. intermedius and S. constellatus ) and Enterococcus faecalis (vancomycin susceptible isolates only). Telavancin is a semisynthetic derivative of Vancomycin. Vancomycin itself is a natural product drug, isolated originally from soil samples in Borneo, and is produced by controlled fermentation of Amycolatopsis orientalis - a member of the Actinobacteria . Telavancin has a dual mechanism of action, firstly it inhibits bacterial cell wall synthesis by interfering with the polymerization and cross-linking of peptid

A python client for accessing ChEMBL web services

Motivation The CheMBL Web Services provide simple reliable programmatic access to the data stored in ChEMBL database. RESTful API approaches are quite easy to master in most languages but still require writing a few lines of code. Additionally, it can be a challenging task to write a nontrivial application using REST without any examples. These factors were the motivation for us to write a small client library for accessing web services from Python. Why Python? We choose this language because Python has become extremely popular (and still growing in use) in scientific applications; there are several Open Source chemical toolkits available in this language, and so the wealth of ChEMBL resources and functionality of those toolkits can be easily combined. Moreover, Python is a very web-friendly language and we wanted to show how easy complex resource acquisition can be expressed in Python. Reinventing the wheel? There are already some libraries providing access to ChEMBL d