CELLS
Research consulting
Strategy and technical support for research teams, foundations, and ministries moving science into deployable systems.
The problem
There's a gulf between the lab and the deployed system. Most consultancies can only stand on one side of it.
MIBTY's research practice sits in the gulf — between principal investigators, ministries, and engineering teams — translating scientific output into actionable infrastructure.
Workflow
01
Map the science
Read the papers, talk to the PIs, write what's actually known vs. claimed.
02
Define translation paths
Which findings have a path to deployment, with which partners, under which constraints?
03
Prototype
Smallest deployable instance of the science — usually with a research partner co-author.
04
Publish & open
Open methodology, open code where possible, peer-reviewed where it sharpens the work.
Benefits
Translated, not summarized
Outputs are deployable artifacts — code, datasets, protocols — not 50-page reports.
Open by default
Where IP permits, we publish methodology and code. The compounding effect is real.
Multi-stakeholder fluency
We speak to PIs, ministries, foundations, and engineering teams in their own register.
Technologies
- LaTeX / Typst
- Quarto
- Jupyter
- Zenodo
- ORCID
- OSF
- GitHub research workflows
Industries served
- Universities
- Government agencies
- Foundations
- Research institutes
- Multilateral organizations
Frequent questions
Do you write grants?
We co-author technical sections and budgets. Strategy stays with your grants office.
What's a typical engagement length?
Three to twelve months. Research timelines don't compress well.