Writing
Feasibility, argued in the open.
Method notes on how a feasibility answer should be built, checked, and disagreed with. No invented statistics, no case studies we cannot name — if we cannot source a number, we make the argument without it.
Every claim traceable, here too
All posts
The archive
Bid defence
What a CRO bid defence needs
The bid defence is won or lost on one question asked five different ways: where did that number come from? Here is how to make every figure in a feasibility pack answerable.
Cohort
Eligibility criteria are a cohort tax
Every criterion is added for a good reason and priced as if it were free. The arithmetic is multiplicative, the cost is invisible at the point of decision, and nobody in the room owns it.
Operations
Site selection is a data problem
Track record, competition density and the enrolment arithmetic are all measurable from public records — and the most common site-selection mistake is a counting error, not a judgement error.
Evidence
Reading a trial’s failure: what “why stopped” actually means
A free-text field on a registry record is doing more work in the industry’s models than almost anything else. Most of what it says is not a failure — and “completed” is not the same as “worked”.
Method
What “probability of success” can and cannot tell you
Ours is directional, and we say so on the number. Here is why an honest directional read is more useful than a precise-looking one — and what a PoS structurally cannot see.
Method
Why most feasibility assessments are unfalsifiable
A feasibility pack that cannot be wrong is not a piece of analysis. It is a document. Here is the difference, and what a checkable one looks like line by line.
See a verdict you can actually check.
Send us a protocol — or just a molecule and an indication. We'll return a fully cited feasibility assessment you can trace, line by line, back to public data — yours to defend in a bid, take to your board or investment committee, or hand to a regulator.