Roadmap · Research software
From working tools
to connected research.
A staged development plan, grounded in what researchers need to do repeatedly. Each next step should earn its place through use and review.
Current stage Working prototype · Product discovery
Available now
Explore the foundations.
The prototype contains individual tools and reference resources that can be used today. Their purpose, assumptions and source material are described alongside each tool.
- Evidence library ↗
- Curated research and methods references with prepared notes and source links.
- Measurement methods ↗
- Context for comparing clinical age estimates, epigenetic clocks, pace measures and function.
- PhenoAge Explorer ↗
- A clinical biomarker model with unit selection, an example and downloadable output.
- Study Planner ↗
- Sample size and power exploration for a supported two-group design, with dropout planning and export.
- Evidence Copilot ↗
- AI-assisted questions over selected prepared source notes, with links back to the references.
Next product stage · Planned
Connect the decisions into one research package.
The next product goal is a continuous journey from a research question to sources, a method comparison, a study plan and an export that a reviewer can inspect. Today these tasks live in separate prototype views.
- Preserve the selected references and the assumptions behind a comparison.
- Save a bounded research package and return to it later.
- Export the package with method versions, source links and review notes.
- Evaluate the workflow with researchers before broadening the feature set.
Saved packages, cross-tool state and a unified export are planned capabilities. There is no published delivery date; discovery and review will determine the order of implementation.
Discovery · Planned
Learn from the work, then measure the improvement.
Our proposed first cycle is 10–15 interviews, followed by up to three design-partner pilots. We want to understand a recurring task, the current alternative, the person doing the work and the person reviewing it.
Pilots should measure time to a useful draft, reviewer effort, repeated use and corrections. A positive conversation is not proof of adoption; returning to a real research task and willingness to pay provide stronger signals.
These are targets for future discovery, not current partner or user counts. A useful introduction describes your research question, your existing workflow and the material a reviewer needs.
Longer-term direction
A shared workspace with a durable research record.
Subject to evidence from pilots, the longer-term direction includes collaborative review, broader curated collections, method versioning and integrations with research workflows. Team access and subscriptions are commercial possibilities to validate.
Expansion should follow a demonstrated need. The aim is to make research work easier to revisit and inspect while retaining the source, methodological context and human judgment behind a decision.
Read the product and investment thesisFrom idea to a working question
Explore it.
Help shape what follows.
Bring a research question, a method to compare or a workflow worth improving.
Discuss a product pilot