Our Fall release closes a year of work on a conviction most medical AI ignores: nothing gets adopted until it recognizes whose job it is.
Earlier this year I wrote about a shift in when intelligence arrives: from the quarterly report you pull to the continuous signal that gets pushed to you. That was the Spring story, and it still holds. Our Fall story is something quieter that we cared about all year: who the intelligence recognizes.
Medical affairs is not one job. An MSL preparing for a call, a field medical leader who owes a director a monthly report, and a medical strategy lead accountable for whether the scientific narrative is landing across the field work in very different ways, on different deliverables, and answer for different things when someone pushes back. What they share is a scientific mission and the evidence underneath them. What they do with it, hour to hour, is not the same job.
Most medical AI ignores this, and it ignores it because the field has been optimizing the wrong variable. Accuracy matters enormously, but accuracy that goes unused is worth almost nothing. The graveyard of medical AI is full of accurate tools nobody adopted. A model can be perfectly right about a question no one in the workflow was asking, and the team will quietly stop reaching for it. The harder and more valuable problem is not making intelligence correct. It is making it recognizable: knowing which question matters before anyone asks it, and knowing what the person asking is on the hook for, so a team sees its own job in the tool and reaches for it. You cannot retrofit that onto a general assistant. You have to build to the job.
So we did. This release gives each team its own named solution, and each solution runs on one shared, governed platform: Sorcero Medical™. One platform underneath, but what each team meets is theirs. That structural point is the actual news, more than any single feature, so let me walk it the way our customers actually experience it: as the job each of them is accountable for.
The MSL: the pre-call plan
An MSL is rarely at a desk, and the work that matters is the scientific exchange itself, not the preparation and paperwork around it. The problem was never a shortage of information about a stakeholder. It was that assembling it, prior interactions, field notes, advisory board transcripts, publication and congress activity, meant digging across systems in the little time before a meeting, so most calls started with a fraction of what was knowable.
This release makes that preparation instant, and it is the standout of the release for the field. Minutes before a call, an MSL opens a stakeholder profile and gets a pre-call brief that has already pulled everything relevant to that person into one place in real time: what they care about, what they have asked before, where they stand on the clinical questions the team is tracking, and what has changed since last contact. What used to be an evening of digging, when it happened at all, is now assembled the moment it is needed. It is not another system to update. It is the ability to walk into a specific conversation already knowing what matters about the person across the table.
The brief is only as good as the data feeding it, which is why capture matters as much as retrieval. The Sorcero Capture App, launched in March and now on iPhone as well as iPad, lets an MSL log an interaction in the moment it happens rather than reconstructing it later, with offline capture and automatic enrichment as records sync. Every exchange captured makes the next brief sharper.
The accountability here is the call itself. Walking in prepared, with the last six months of context assembled in seconds, is the difference between a scientific conversation and a reintroduction.
The field medical leader: the report you have to defend
One level up, the artifact under scrutiny is the monthly report. A field medical lead does not get to say the intelligence is somewhere in the platform. They have to stand behind a document in front of a director, and the thing they quietly fear is not how long it took to build. It is being asked where a number came from and not having an answer. What they are really buying is time to defensible output: the report done fast, and done so it holds up.
That is why the reporting workflow is built the way it is. Medical Strategy Reports give each intelligence question a continuously refreshed summary and a clear view of what changed against the prior snapshot, every claim traceable to the evidence beneath it, and the output moves directly into a document, so the report starts from a draft rather than a blank page. Both things matter, and they matter together. The time savings are real: on earlier versions of this workflow customers cut weekly reporting time by over 72%. But speed only counts if the output holds up under questioning, and defensibility only counts if it does not cost two weeks to produce. What the field lead is really buying is time to defensible output, both at once: the hours saved, and a report they can defend line by line.
The medical strategy lead: keeping the narrative honest as the evidence moves
A medical affairs leader is accountable for a scientific narrative they cannot directly observe, and that narrative moves whether or not anyone is watching. Strategy in medical affairs rarely fails by being wrong on the day it is set. It fails by quietly ceasing to be true while everyone keeps executing against it, and the lag between the two is where launches and reputations are lost. Leading indicators are not a reporting nicety. They are the only defense against being confidently wrong for two quarters. In June we introduced the Therapy Resonance Profile and the Strategic Alignment Framework to move that accountability off quarter-old reporting and onto leading indicators drawn from the evidence as it changes. This release makes the underlying objects operational rather than illustrative.
Strategic Imperatives now function as working objects, not slideware: a leader encodes the objectives the medical organization is accountable for directly into the platform. The Therapy Resonance Profile then scores how each stakeholder in that leader's universe, KOLs, HCPs, and others, aligns to those imperatives, and tracks scientific sentiment alongside that alignment. Because the scores are continuous, longitudinal, and evidence-backed, a leader sees not just where a stakeholder stands but how the position is moving: alignment, recency, and trajectory, improving or declining. Which relationships are advancing the strategy and which are drifting becomes a question with an answer that traces to source rather than to a hunch.
Congress is one more example of the same pattern. It used to be handled in a separate, slow, manual process, a sixty-day wait for a post-congress debrief, which is exactly the kind of blind spot the platform is built to close. Congress Intelligence launched in March with centralized access to 3.5 million abstracts and posters from more than 4,300 conferences. This release makes congress data a first-class citizen: abstracts and late-breaking data now exist as a dedicated record type, unified with KOL publication profiles and analyzable alongside every other source. Planning assumptions, field captures, and abstract data sit in the same dataset, so a single question can span what the team expected before an event, what it heard during it, and what it means afterward.
One conversation across all of it
If each team meets its own solution, the risk is three good experiences that do not talk to each other. Sorcero Wizard, entering beta for current customers by the end of the month, is the connective tissue. It is a conversational layer with native awareness of platform objects, including Insights, Collections, and Stakeholder profiles, and it holds context across an exchange so a line of inquiry can be narrowed, redirected, and drilled into without being restated.
And because this is medical affairs, fluency is not the bar. Wizard is bounded by the same governance as everything else: prohibited-intent detection on the way in, source traceability on the way out, so a response is not just fluent but grounded, permitted, and auditable.
That reads differently depending on who is asking, which is the whole idea. An MSL keeps narrowing on a stakeholder without re-identifying the subject. A field lead interrogates a monthly report and then asks what changed since the last one. A strategy lead moves from a congress abstract to its presenting author to that author's prior engagement history in a single thread. It is one capability that recognizes three jobs, not three features wearing a trench coat.
What every team shares
The obvious worry about a solution per team is that you are just rebuilding the old silos with nicer names. It would be a fair worry if each solution were its own island. It is not. Underneath the team solutions is one backbone, and this is where a platform argument is either won or lost. Because every team draws on the same evidence layer, the field lead's capture becomes the strategy lead's signal without anyone exporting anything, and the silos never form. Every insight traces to the source. Governance, role-based access, and audit hold across every team, which is the only reason AI is usable in a regulated medical organization at all, backed by independently audited SOC 2 Type II, GxP, GPP, 21 CFR Part 11, GDPR, and Data Privacy Framework compliance.
This release also makes the backbone itself observable. A new executive-grade analytics layer gives medical operations and IT leaders a real-time view into the platform's own work: how evidence is ingested, transformed, enriched, and turned into intelligence across every connected source. The people accountable for the pipeline can finally see it running, and walk into a business review with an artifact instead of an anecdote.
Two things about that backbone matter more than any feature. First, everything in this release is in production on real enterprise data today, not a roadmap commitment or a services engagement dressed as software. New customers see working intelligence on licensed external evidence in their first weeks, before their own pipelines are even connected. Second, because every team runs on the same evidence layer, a medical organization can start with the team whose problem is most urgent and expand across teams, therapeutic areas, and data sources, each solution composing onto the same backbone rather than standing up a new one.
There is a longer game underneath this, and it is worth being explicit about. Most medical AI has no memory. Every question starts from zero, gets answered, and is forgotten, so nothing accumulates. When every team instead reasons on one evidence layer, the opposite happens: each decision, each captured interaction, each resolved question deepens a context specific to one organization's therapies, stakeholders, and history. The model underneath is something anyone can license. That accumulated context is not, and it is what a competitor cannot reconstruct by buying the same tools next year. The moat was never the intelligence. It is the memory.
Why this is the design, not the packaging
It would be easy to hear "a solution per team" as a repackaging exercise. It is the opposite. We did not take a suite and slice it into tiers. We learned what each of these people do, what they are measured on, and what they have to defend, and we built to it. Yes, this is how the product is now sold, a named solution a team can adopt on its own. But the packaging follows the point rather than making it: organizing around the team is how intelligence actually gets used, because adoption follows recognition. When a team opens the platform and sees their own work reflected back, they use the platform. When they open a general-purpose tool and have to translate their job into the tool's worldview first, they do not. It is the same reason this release puts an AI guide inside the Help Center itself, walking any user through advanced features the moment they need them, so a new capability does not sit behind a training backlog.
That is the conviction I opened with, that the hardest problem in medical AI is recognition, not accuracy, and it is what this year of work was really about. It is worth being clear that this is a beginning, not a finish line. I walked through three jobs in depth here, but the family is already larger than three. This same release brings named solutions for other teams too, among them Medical Information, Medical Communications, Medical Intelligence & Analytics, and Therapeutic Leadership & Launch. The work of the back quarter, and the quarters after it, is to go as deep for each of those jobs as we went for these three, one accountable role at a time. Every one of them lands on the same backbone, so the whole organization gets sharper as it grows, and the memory it accumulates keeps compounding into an advantage no competitor can shortcut.
This release is simply the moment the premise stopped being a thesis and started being how our customers open the platform on a Tuesday morning.
Medical affairs is not one job. It never was. This is the release where the product finally agrees, and where we start proving it, role by role, for everyone else in the family.
Onward.
This release is simply the moment the premise stopped being a thesis and started being how our customers open the platform on a Tuesday morning.
