Migibio vs Alternatives: A Checklist Instead of a Scoreboard
Quick Answer — This page deliberately does not contain a table of competitor specifications. In this market those numbers are usually unverifiable, and a comparison built on unverifiable numbers is worse than no comparison: it looks authoritative, gets repeated, and collapses the first time a buyer checks it. What follows instead is the checklist we would want used on our own claims, and an honest account of where we are not the right fit.
Why no scoreboard
A feature table comparing named competitors implies that every cell was verified. In practice the cells come from brochures, distributor listings and conference slides, often written years apart and against different assay generations. The result is a document that is simultaneously persuasive and unfalsifiable — the worst combination in a technical purchase.
There is also a commercial reason to avoid it. A vendor that publishes an unverified comparison has implicitly invited one in return, and the reply will be written by whoever is less careful.
The checklist we would want used on us
| Question | Why it matters | Where our answer lives |
|---|---|---|
| LoD, with method and probability | Defines detection claim | Analytical performance |
| LoQ and its CV target | Defines the lowest usable number | Analytical performance |
| Precision at decision concentrations | Determines whether trends are real | Precision |
| Reference intervals with n and method | Makes the number interpretable | Reference intervals |
| Clinical sensitivity and specificity with CI | Separates detection from diagnosis | Clinical performance |
| Method comparison with bias and TEa | Shows what changes on a switch | Method comparison |
| Sample handling and interference thresholds | Predicts field failure modes | Sample handling · Interference |
| What is not yet validated | Defines the boundary of trust | Research and analytical performance |
If a vendor cannot answer the first four, the comparison is not worth having. If it cannot answer the last, it is asking for trust instead of evidence.
What we claim, and how we qualify it
| Claim | Qualification |
|---|---|
| Quantitative results in minutes | Manufacturer-reported platform timing; assay-specific variation applies |
| Menu covering canine and feline infectious, inflammatory, endocrine, cardiac and renal markers | Menu boundary is published; some agents require send-out |
| ISO 13485 / ISO 9001 quality management | Certificate scope should be checked, not assumed to cover every product |
| Independent third-party validation | Not yet published; we say so rather than implying otherwise |
Where we are not the right choice
- You need a full chemistry or haematology panel. A single-analyte immunoassay platform is the wrong instrument for that job.
- You require independently published validation before adoption. Our position is honest but incomplete on that axis; a laboratory with that requirement should wait or choose differently.
- Your volume supports a central laboratory platform. Batch economics win at scale, and pretending otherwise would be a disservice.
- You need agents outside the current menu — heartworm, vector-borne serology, some endocrine analytes. We state the boundary; we do not imply coverage.
How to run a real comparison
- Ask each shortlisted vendor for the same eight items above, in writing.
- Run the same three patient samples on each platform, including one low value, one mid and one high.
- Compare against your existing method with bias and limits of agreement, not correlation.
- Ask for the reference interval on the demo unit, not from a brochure.
- Check what happens when a lot changes, and whether QC is documented.
- Score the workflow, not only the instrument: placement, owner, training, downtime.
The Author’s Take
Position. Refusing to publish a competitor scoreboard is a stronger competitive move than publishing one, provided the refusal is replaced with something more useful than silence.
Reasoning. Buyers in technical categories are surrounded by comparison tables that all flatter their author, and they have learned to discount them to near zero. A vendor that says “we are not going to give you unverifiable numbers, here is the checklist instead, and here is where we are weak” is doing something the category does not do — and it gains the one thing a comparison table cannot buy: the assumption that the vendor is not exaggerating. That assumption is worth more than any single row of a feature matrix, because every subsequent claim inherits it.
Disclosure. This page contains no competitor specifications. Claims about Migibio products are manufacturer-reported and qualified in the table above. markers elsewhere in this section indicate values requiring verification.
Sources
- Analytical performance — LoD/LoQ definitions and buyer questions
- Reference intervals — platform-specific interval rationale
- Clinical performance — sensitivity, specificity and prevalence
- Research and analytical performance — current validation status statement
Frequently asked questions
- Why is there no feature-by-feature table against named competitors?
- Because most competitor specifications circulating in this market are unverifiable: taken from brochures, reseller listings or outdated datasheets, and rarely confirmed with the manufacturer. A comparison built on those numbers is marketing rather than evidence, and it fails the first time a buyer checks one.
- What should I ask every vendor, including Migibio?
- Ask for LoD with method and probability, LoQ with its CV target, precision at the concentrations you will use, reference intervals with sample size and statistical method, clinical sensitivity and specificity with confidence intervals, and a statement of what is not yet validated. A vendor that answers all six is comparable; one that answers three is not.
- When is Migibio not the right choice?
- When you need a broad chemistry or haematology menu, when you require independently published third-party validation before adoption, or when your volume justifies a central laboratory platform. Those are legitimate constraints, and recognising them early saves both parties time.