Blog
General

Reflections and Insights from JPM 2026

I walked 117,000 steps between Mission and Market Street in San Francisco last week. My feet are still recovering, but the conversations were worth it.

JPM is a peculiar thing. Thirty-plus meetings crammed into hotel lobbies, rooftop bars, and the occasional 50th-floor conference room with actual views. The sun came out again this year - two years running now. That felt symbolic somehow.

Here’s what I noticed:

The conversations have shifted

For the first time in years, policy wasn’t dominating every room. People were focused on fundamentals again - timelines, execution, getting drugs to patients. The tone felt productive rather than defensive.

What struck me most was the consistency. Across meetings with pharma, biotech, healthtech, and women’s health companies, the same themes kept surfacing: how do we actually scale AI, where are the real productivity gains, and who can we trust to deliver?

That last question came up more than I expected. In almost every conversation about CRO relationships, the language was the same: partnerships, not vendor check-ins. People are tired of being managed. They want to work with teams who own outcomes alongside them.

The AI question has evolved

Every AI conversation I had came back to one question: What does this actually do for my trial timeline?

No one cares about theoretical applications anymore. The interest is entirely in what’s already working. What’s operationalized. What’s moving the needle today, not in a pitch deck.

The timing of the regulatory news felt almost scripted. On January 14 - literally during JPM week - the FDA and EMA jointly released guidance on AI principles for drug development. Real regulatory clarity, finally. Two days earlier, FDA published draft guidance on Bayesian methodology for clinical trials - a signal that statistical modernization is actually happening.

When regulators and sponsors are asking the same questions in the same week, you pay attention.

The meeting culture is changing

Fierce Biotech nailed it: “All meetings, none of the mega deals.” JPM is evolving into something different. The big announcements are happening throughout the year now, not saved for the conference stage.

What filled the space? More substantive conversations. Less theater. People evaluating what you’ve actually delivered, not what you’re announcing. I found that refreshing.

What I’m watching

Women’s health momentum is real. The conversations have matured from “this space is underserved” to serious discussions about infrastructure and capital in the same breath. Companies in this space are looking for development partners who genuinely understand what they’re building.

Timeline pressure is acute for biotech, especially with early-stage funding so concentrated. Everyone seems to be racing toward Phase 3 data at the same time, which means capacity constraints keep surfacing. When the constraint is execution, people start asking harder questions about who can actually help them get there.

The Lindus perspective

I’ll be honest - I came away from the week feeling like the timing is right for what we do.

When every AI conversation is about timeline impact, and regulators are providing clarity the same week, the question becomes: who’s already operationalized the tools that compress those timelines? When biotechs say they want partnerships instead of vendors, they’re describing something specific - teams who own outcomes with them, not just complete tasks and move on.

And when the focus shifts from stage announcements to track record, you can’t paper over gaps in execution. People are paying attention to what you’ve actually delivered.

That’s the work. Quiet, consistent, accountable work. It’s not glamorous, but it’s what makes progress possible.

My feet are telling me to take it easy this week. But the conversations from JPM are still turning over in my head - and I suspect they will for a while.


If you're thinking about clinical trial delivery partners for your next study, then we'd love to chat.

This is some text inside of a div block.
This is some text inside of a div block.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Continue reading

More from Lindus

Lindus BG Image
03 Jun 2026
Articles

An AI pilot is only as good as the data pipeline underneath it: our response to the FDA on AI-enabled optimization of early-phase clinical trials

Lindus recently submitted a public comment to the FDA on the AI-Enabled Optimization of Early-Phase Clinical Trials Pilot Program (Docket No. FDA-2026-N-4390). We support the pilot and believe it can be designed to answer harder questions than the request for information currently sets up. 

Lindus BG Image
01 Jun 2026
Blog

Stop prototyping, start building: How AI is shaping product & design in 2026

At Lindus, we believe AI will empower our tech organization to build better products. LLMs are unlocking potential across product management, design, and engineering, in ways that would have seemed far-fetched even two years ago. But the way we work is changing fast, and we think it's worth sharing what that looks like in practice.

Lindus BG Image
20 May 2026
Blog

What James Lind would ask us on Clinical Trials Day

What James Lind would ask us on Clinical Trials Day is whether the systems we have built are worthy of the participants, sites, investigators, and teams who make clinical research possible.We do not think they are yet, but we know they can be.

Lindus BG Image
11 Mar 2026
Blog

Achieving FDA-Grade Data Quality in Large-Scale Liquid Biopsy Screening Trials

"The data pipeline, from medical record retrieval to structured EDC output, has to be designed for regulatory scrutiny from the start. Retrofitting data quality into an operational model that wasn't built for it creates avoidable risk at exactly the wrong stage of a program."