We build assets that compound
Every brief improves the discipline of source review. Better foundation models help the input layer; the durable work is the review standard and the evidence record around it.
Talent
NextConsensus builds AI systems that track how medical claims change over time and turn that movement into sourced briefs for high-stakes healthcare decisions. The work runs on temporal replay, claim identity tracking, language-change classifiers, provenance systems, and calibration that compounds with use.
Medical knowledge does not update all at once. A trial shifts the evidence base. Specialists begin changing practice. Payers respond unevenly. Guidelines lag. Labels lag. Public reference systems absorb change through argument, revision, and stabilization.
Institutions sit in the middle, trying to make decisions while every surface is moving on a different timeline. NextConsensus exists to make emerging knowledge change legible early enough for experts and institutions to review it before decisions harden.
Too early is reckless. Too late is expensive. The hard part is knowing when uncertainty has changed enough to require action.
Every brief improves the discipline of source review. Better foundation models help the input layer; the durable work is the review standard and the evidence record around it.
Medical knowledge changes before institutions can safely admit it has changed. The hard problem is recognizing that moment without pretending uncertainty has disappeared.
Begin with the disputed claim and decision context. The unit of work is a sourced brief, not a stream of undifferentiated updates.
Evidence movement is not the same as review obligation. The product governs the space between detection and action, without collapsing it.
Hindsight does not leak into the assessment. Each read is pinned to a review date — what was knowable then, not what we know now. If the evidence is thin, the brief says so.
What we choose to optimize — and what we leave to others.
Sourced through Refract, our open-source developer SDK. It turns raw public revision histories into structured timelines. Anyone can inspect it, run it, or build on it.
Buyers get the healthcare decision layer: sourced briefs with caveats, source references, and review context. Developers and researchers get the observation layer that demonstrates how public knowledge change can be structured from revision histories.
You might be a fit if:
If building decision infrastructure for that gap is more interesting to you than optimizing existing tooling, get in touch.