For paediatric and early-stage cohorts, low tumour burden in low blood volume, the sensitivity floor is what decides whether you can run the study at all. It is the difference between a usable signal and an empty result section.

This is the foundational claim under everything else. Without it, the rest does not matter.

Send samples to the Simsen lab when you want the turnaround and interpretation done for you. Bring SiMSen-Seq in-house with LabSuite when you have bench capacity, want full control of the workflow, or are running volumes that justify an internal pipeline. Many groups start with one and add the other.

The full comparison is below, so you can see exactly what changes between the two before you commit.

For translational work, that is the actual research question, what the tumour is doing and how it changes under pressure, not a flag in a database. The output is built for the people reading it: principal investigators and study teams, with a rationale behind each call.

If the question is yes or no, we answer it. If the question is what is happening biologically, the platform was built for that one.

For a translational group, this is non-negotiable. You need to reproduce the call, run a second pipeline against the same data, and publish without a vendor between you and the result. We work that way by default, and we collaborate directly with your bioinformaticians.

It also means we get told when our pipeline is wrong. We prefer that to the alternative.

Co-authorship on the resulting paper, where the science supports it. Protocol design help up front, when an early conversation can save a sample run later. Interpretation help when a result is unusual and you want a second set of eyes on it.

We are not the right partner for every project. We are an exceptionally good partner for the ones we are right for.