DiscoverOperations Utopia: Striving for Practical Excellence in Life Sciences Operations
Operations Utopia: Striving for Practical Excellence in Life Sciences Operations
Claim Ownership

Operations Utopia: Striving for Practical Excellence in Life Sciences Operations

Author: Matt Neal

Subscribed: 0Played: 0
Share

Description

In what may be one of the most niche topics for a podcast, Operations Utopia is a podcast about the desperate need to streamline Life Sciences Operations to get treatments to patients faster and explores how life sciences organizations should operate—by examining why they usually don’t.

Disclaimer: The podcast content represents the opinion of the speakers, guests & host and does not reflect those of their organizations, system vendors, or service providers.
13 Episodes
Reverse
Why Start With the Chaos? (with Jake Doran)Guest BioJake Doran is SVP, Client Success & Transformation at MResult, where he helps healthcare and life sciences organizations turn data, AI, and technology ambition into operating impact. He has more than 25 years in life sciences technology. Most recently he was Vice President, Digital and Head of IT at Lykos Therapeutics (formerly MAPS PBC), leading technology as the company moved from clinical research startup toward commercial readiness. Before that he was Head of Global R&D IT at Bausch Health, and Chief Technology Officer for the Regulatory Affairs business at Genpact, where he launched one of the industry's first AI-powered intelligent automation platforms for Regulatory Affairs.Jake founded LiST Innovations, a consultancy focused on regulatory data standards, governance, and RIM transformation planning, and still takes select advisory work through it, including a fractional CIO role at an emerging biotech. Earlier he spent eight years at Janssen (Johnson & Johnson), where he led a regulatory platform implementation that consolidated 21 legacy systems, and seven years at Schering-Plough managing Regulatory CMC Publishing & Technology. He has served on the Board of Directors of the IRISS Forum and holds a bachelor's degree in Biology from Fairleigh Dickinson University.Key TopicsSmall companies, big advantage? Jake argues that early- and late-stage clinical companies can build an AI-forward organization in a way legacy enterprises can't. Legacy companies all have systems now, but they lack process discipline, standards adoption, and enforcement of people actually putting data into those systems. In his framing, AI doesn't fix garbage in, garbage out. It just lets you see the mess faster.Why start with the chaos? Matt calls change management the bigger issue. He floats a reference-modeled starting database, even a templated spreadsheet, where maybe 60% of data points are identical across every pharma company. His question for Jake: when you walk into a blank-slate startup with a small budget and one product, is information management even a priority?Pick your mess, and when to pay for it. Jake's answer is "yes and no." Manufacturing has to be buttoned up early, whether in-house or through a CDMO, because batch records and product release are coming. The shared drives, Gmail accounts, Box, and Dropbox sprawl from a company's early days? Some of that just gets pushed aside. Why does the industry let startups suffer first? His simple answer is budget and resources. At some point, maybe late Phase 2, a company becomes an acquisition target or a likely approval and has to clean house. Until then, why buy an eTMF when you can build a folder structure that mirrors the TMF Reference Model yourself?The shed with no floor. Matt's metaphor: nobody outside a regulated industry would throw up a plywood shed, forget the floor, then bolt on a kitchen and electrical. Jake's addition: you don't get to go back and add the floor. You buy the next parcel of land and build it again. He calls data remediation probably the most expensive activity the industry goes through.AI-assisted cleanup, with a human in the loop. Jake walks through migrating a home-built TMF into a real system. Train an LLM on the reference model, run your extract through it, have someone compare the output against your master data model to catch hallucination, then document and validate the whole process before loading it into a validated system. That's far easier now than it used to be.Standards take forever. Jake works closely with the IRISS Forum and talks standards constantly. He recalls a roughly 10-year standards initiative presented at the DIA RSIDM Forum in February, and can't see why it takes a decade to define standards for things the industry has done for 100 years. Matt argues the industry keeps letting perfect be the enemy of good. Ship a good-enough standard, update it annually, stop handing out five-year adoption windows. Jake names the root cause as bureaucracy and fiefdoms. Functions do things their own way, throw it over the fence, and let regulatory piece it together. The real "secret sauce," in his view, is CROs, sponsors, academia, and health authorities working in the same environment.The patient angle. Matt recalls a DIA panel 15 to 18 years ago declaring patient records would never be shared. Now we hand our data to banking apps, social media, and AI tools. Jake notes that de-identification isn't that hard, asks why large practices don't run closed-loop record sharing, and admits he uploads his ring, scale, and physical results to his AI companion anyway.Clever isn't enough. Jake is bullish on AI. He cites a recent article on clinical control towers that pulled data from disparate systems into one view, and argues dashboards give point-in-time visibility, not trends, analytics, or checks against protocol expectations. He describes an AI conference in New York where people claiming healthcare expertise couldn't explain what a protocol is. AI still has to be defensible, traceable, and backed by an audit trail. And just as the industry moved from data centers to cloud faster than anyone expected, he thinks the jump to predictive, connected analytics is coming sooner rather than later.Notable Quotes"AI just accelerates how much faster you can see the mess, right? But it... doesn't fix the mess." — Jake Doran"They'll deploy Copilot to 75,000 people, which may help you draft an email and schedule a meeting and whatnot." — Jake Doran"Why start with the chaos? I guess is my point." — Matt Neal"I can build a folder structure anywhere that replicates a TMF reference model. So why would I go buy?" — Jake Doran"You make bad decisions initially; they just get compounded over time." — Jake Doran"I don't understand why it takes 10 years to define standards for things that we've been doing for 100 years." — Jake Doran"I can remember vividly conversations that I had in previous career where we couldn't come to agreement internally on what we call the product." — Jake Doran"Everybody do what you need to do, throw it over the fence, and let regulatory piece it all together." — Jake Doran"We know as technologists that the limitation is not technology." — Matt Neal"It can't be just clever, right?... It still has to be defensible. It still has to be traceable." — Jake DoranQuotes are verbatim from the transcript; ellipses mark removed filler or repeated words.Who Should ListenHeads of regulatory operations and RIM, especially anyone building the function at an early-stage or single-asset biotech. Clinical operations and TMF leads weighing build vs. buy. IT and digital leaders in life sciences deciding where AI actually moves the needle. Standards people at IRISS, DIA, and CDISC who are tired of decade-long timelines. And founders and executives who will eventually pay for the cleanup they skip today.ReferencesGuestJake Doran on LinkedInOrganizations & StandardsIRISS Forum — non-profit for implementation of regulatory information and submission standardsCDISC TMF Reference Model — industry taxonomy for Trial Master File content, now under CDISCEventsDIA Regulatory Submissions, Information, and Document Management (RSIDM) Forum 2026 — February 2–4, 2026, North Bethesda, MD Operations Utopia - Where Regops, Innovation, Technology, and Execution Meet.Disclaimer: This podcast reflects only the opinion of the podcaster and guests and does not reflect those of their organizations, system vendors, or service providerOriginal show theme "Little Sammy" by Matt Neal
John Jones is the founder and creator of the Nidura platform. He is Chief Executive Officer of Entitech Solutions and SVP, Head of Life Sciences Consulting at Tandym Group. Earlier roles include Practice Lead for IT Strategy & Implementation at Quintiles, Vice President of Application & Integration Solutions at HighPoint Solutions, Solution Partner for Life Sciences at Business Edge Solutions, and IT Manager at Aventis Pharmaceuticals. He started out as a mechanical engineer at Ford Motor Company and holds a BS in Mechanical Engineering and an MBA from Rutgers. John spent a good five years working on the DIA RIM Reference Model alongside Bala Balasubramanian, Joel Finkle, and others. Find him on LinkedIn.Key TopicsThe model never changes. The plumbing always does. (1:49) John has built data platforms on SQL Server and Oracle, then Redshift and Azure, now Databricks and Snowflake. His observation: the technology keeps changing, but the data and the way the business transacts it do not. The time goes into mapping today's source system into the model, and governance, data quality, and compliance get dropped when that mapping gets hard. Nidura is his "easy button on the plumbing": standard data models at the core, a data mesh framework, and business-owned data products.The RIM Reference Model as the foundation (5:56) Following Bala's visit in OU-007, John describes the working group spending an entire night on a single field because the field needed it. That work gave Nidura a model to make physical. He uses CDISC's USDM the same way for the clinical model. He notes the RIM Reference Model documentation is now publicly available on the DIA website.Why canonical models get a bad name (8:06) John thinks people see the value. The problem is that the word "model" makes it sound like an IT-led initiative, the work gets stuck in technical analysis paralysis, and ambitious projects fizzle. His view is that it only works with business people driving.AI stumbles where people stumble (11:56) Matt argues there's a false perception that AI will do everything without the plumbing. John agrees: poorly defined, poorly annotated data confuses AI the same way it confuses a person. Companies pull off a few use cases and end up with tooling overfit to one situation, something he saw in the vendor booths at DIA Global this year. He favors a context layer available to every prompt over prompt engineering for one question at a time.Getting the human out of the loop (23:06) John compares it to trusting a new employee. Accuracy goes up when AI makes lots of little decisions on small, precise, well-annotated pieces of information. He suspects ever-larger context windows make people lazy, and points to structured content such as ePI-formatted labels and structured authoring as the path.Side quest: tokens, gyms, and pickleball (26:01) Matt compares token pricing to old cell phone calling areas and pitches a flat gym-membership model. John thinks tokens are here for a while, that compute gains are flattening, and that token efficiency is the next wave. With AI built into everything, he expects pickleball, not the gym. Matt notes that PDF versus text changes the token count, and that the "new" advice to build folder hierarchies with MD files is the folder structure we already walked away from.A second value prop, and the same old hurdles (38:10) Standard models used to be a reporting and analytics pitch. Now AI needs the same data, which opens up delegating work: generating documents from data, or checking documents against data so XEVMPD submissions match SmPCs. The hurdles haven't moved, though. People working on the data still need to understand it, and John says newer platforms let you house more data and get to it faster without solving that.18 months versus a button press (44:55) John's estimate for building a regulatory data hub from nothing: a couple of months on a physical RIM Reference Model, six to eight months of ETL from Veeva, a couple more of testing, then six months of edge cases. Nidura pre-built that, and he says it happens in the first hour of operation.What users get (46:36) Three things. Ask the data questions through an AI console, with your own model or one provided, and get answers in RIM Reference Model terms. Build reports and dashboards from data products the business controls, including who gets access, how (JDBC/ODBC, API, MCP, download), and row-level security. Feed other systems for integration. Consumers can raise issues back to the data owner, and owners can publish the quality criteria a data product is meeting.Notable Quotes"They're the first things to go out the window when the plumbing becomes difficult." (John, 1:49, on governance, quality, and compliance)"We would spend an entire night talking about a field, right? Because it needed to be talked about." (John, 5:56)"The model is just a way that the business transacts data... It's not a technical thing." (John, 8:06)"It's really a peanut butter and jelly type situation." (John, 13:55, on the RIM Reference Model and language models)"AI doesn't complain, but it complains in the form of wrong answers." (John, 17:16)"The plumbing has to be there first to guide AI." (Matt, 9:35)"I think it's going to create more of a pickleball style model than a gym membership." (John, 34:53)"We're not in the age yet where the report is dead or the dashboard is dead." (John, 47:10)"That's honestly what I've been building for the last 30 years. And I'm like, wow, I'm building the same thing over and over again." (John, 52:01)Who Should ListenRegulatory operations and RIM leaders who are tired of funding the same data hub twice. Regulatory data folks working with the RIM Reference Model. IT and data teams building regulatory data products on Databricks or Snowflake. Anyone being asked to "just put AI on it" before the data is defined.ReferencesGuest and platform: John Jones on LinkedIn. DIA RIM Reference Model: V2.0 User Guide. DIA Global Forum overview. RSIDM 2025 session on V2.0, where John presented the deep dive.Standards mentioned: CDISC USDM. EMA electronic product information (ePI). EMA XEVMPD.Technology mentioned: Veeva RIM. Databricks. Snowflake. Copilot. Operations Utopia - Where Regops, Innovation, Technology, and Execution Meet.Disclaimer: This podcast reflects only the opinion of the podcaster and guests and does not reflect those of their organizations, system vendors, or service providerOriginal show theme "Little Sammy" by Matt Neal
Guest BioMegha Sinha is the founder and CEO of Kolter AI, an autonomous regulatory planning platform for life sciences, and managing partner and CEO of Kamet Consulting Group, which she has run since 2023. She has spent 17 years inside major life sciences lifecycle-change programs — M&A integrations, divestitures, tech transfers, post-merger rebrandings, and CMC changes across global portfolios — across 125+ cross-functional engagements. Eight of those years were at PwC, where she built and led the firm's Life Sciences Regulatory Consulting practice (Health Industries Strategy and Transformation, Global Regulatory Consulting Solutions Leader), growing it from a single capability into a cross-platform business and supporting engagements including a $63B pharmaceutical acquisition, a $25B pharma integration, and a $2.7B divestiture. At Kamet, she has led regulatory strategy for a $14B global healthcare spin-off — rebranding across 100+ countries, 45,000 SKUs, and 10,000+ label redlines — and a $14.6B consumer health carve-out. That spin-off-scale problem, building a plan by hand across tens of thousands of SKUs, became the seed for Kolter AI. Earlier in her career she held regulatory affairs and quality roles at Stryker and MD Resource Corp. She holds an MS in Biomedical Engineering/Regulatory Affairs from the University of Southern California and a BE in Chemical Engineering from R.V. College of Engineering, Bangalore, and is RAC certified.Key TopicsFrom billing hours to giving it away. Megha built the first version of what became Kolter as an internal automation engine for her own consulting practice — the kind of tool that could have easily billed a client for a week of work but instead took a matter of hours. Rather than protect that as a competitive edge, she chose to build a product around it, calling it "cannibalizing my own consulting business."Why the intelligence layer was the hardest part to build. The early architecture put PDFs behind a retrieval-augmented generation (RAG) layer, but Megha found that LLMs don't read documents consistently or deterministically. The team moved to a structured database schema and roughly 38 small, purpose-built computation engines instead — keeping the deterministic math and rules out of the model's hands entirely so the same input reliably produces the same output.Modular by design. An early beta produced an entire cross-functional plan — regulatory, labeling, supply chain — in one shot. Client pushback ("I don't want to tell supply chain what to do") led Megha to split Kolter into four or five separate agents, so each function can pull only the modules it wants.Trust in increments. Megha's current framework: administrative decisions get automated outright, genuinely ambiguous regulatory judgment gets escalated to a human, and once a human has approved the same kind of mitigation enough times, the system starts presenting it as a precedent to accept rather than a question to answer from scratch. She frames this as a recursive self-improvement loop, with human-in-the-loop as today's checkpoint rather than a permanent one.Strategic advantage versus tribal knowledge. If most of the industry ends up running the same planning engine, what's left to compete on? Megha's answer: the mechanics of building a plan quickly stop being a differentiator once they're commoditized. What stays proprietary is company-specific tribal knowledge and negotiated precedent, which customers can feed back into the platform as custom computation logic without a code change.The cross-functional bottleneck hiding behind regulatory timelines. Megha points to the EMA's pilot on parallel post-approval-change submissions across reference and rest-of-world markets as an example of a shift the industry isn't operationally ready for: if health authorities start approving submissions in parallel, the burden shifts overnight from regulatory drafting to manufacturing and supply-chain readiness — and most organizations have no current line of sight into those downstream implications.What's next. Megha describes early interest in extending Kolter into clinical — protocol amendments, IRB changes — and eventually letting agentic systems handle regulatory data entry directly, freeing operations teams for higher-value, patient-facing work.Notable QuotesMegha Sinha, on why she thinks regulatory belongs at the strategy table: "I truly believe that the regulatory folks in our industry are the true strategists... we take a drug and asset and build strategy, right? So we are true problem solvers."Megha Sinha, on the design choice to keep LLMs out of the decision-making: "LLMs are pretty bad in math... I don't want them to make the decision, right? Because I wanted when I give the same input, I get the same output."Megha Sinha, on choosing to build a product instead of protecting a consulting revenue stream: "I'm cannibalizing my own consulting business in some respect, but the expertise that I've developed over the years that will stay with me... I want to democratize it."Megha Sinha, on where she draws the line for AI agents today: "If you are not sure, don't make the decision, right?"Megha Sinha, on the industry's biggest objection to a shared planning engine: "Why would people want to give me their tribal knowledge? You know, that's their secret sauce, right?"Matt, on why he named the podcast Operations Utopia: "If the patient is the point, and speed is the point, we should not have any excuse. We are obligated to not waste time if we don't have to."AudienceRegulatory operations leaders, RIM and submission-planning teams, life sciences data and technology leaders evaluating AI for compliance-critical workflows, and founders building vertical AI tools for regulated industries.ReferencesGuest & CompanyMegha Sinha — LinkedInKamet Consulting Group — LinkedInLife Science Success Podcast — Transforming Pharma Regulatory Operations with Megha SinhaRelatedEuropean Medicines Agency — Using EMA Assessments for Reliance in Post-Approval Changes: Insights from PAC Reliance Pilots Operations Utopia - Where Regops, Innovation, Technology, and Execution Meet.Disclaimer: This podcast reflects only the opinion of the podcaster and guests and does not reflect those of their organizations, system vendors, or service providerOriginal show theme "Little Sammy" by Matt Neal
Guest BioLeslie LaCosta is a fractional operations leader who embeds directly with client teams to fix broken processes and remove friction in customer experience, rather than handing over a deck and walking away. She spent 31 years in retail, working her way from a store-level associate to district manager to nearly 13 years at Bed Bath & Beyond corporate — where she organically built and ran the company's Project Management Office across roughly 1,500 stores — before spending over six years at Party City in store operations and customer experience. She holds a patent for point-of-sale coupon-recovery technology. She now runs her own consulting practice and posts short-form operations content that's built a following for calling out what most operators only say quietly in meetings.Connect with Leslie on LinkedIn.Note: Leslie mentioned her TikTok content directly in the episode, but we don't have a verified handle to link here — if you're listening, Leslie, send it our way and we'll get it added.Key TopicsFrom the sales floor to the boardroom. Leslie describes going from part-time retail work at 15 to store manager at 18 to nearly three decades of climbing every level of retail operations without ever leaving the industry — and why that ground-level experience never left her, even years into corporate strategy roles.Building the PMO — and seeing the cracks. When Bed Bath & Beyond hit a ceiling on store growth and started acquiring brands (Buy Buy Baby, Christmas Tree Shops, Harmon), leadership needed someone with enough internal credibility to run cross-functional initiatives and report straight to the C-suite. Leslie got the job organically — and the seat gave her an unfiltered view into leadership's thinking that eventually told her the company was headed for trouble.Why stacking a transformation on someone's day job doesn't work. Leslie's core operating belief: if you're calling something a transformation, you need to bring in dedicated (often temporary) resources for it — not ask an SVP to run their business unit, lead the initiative, and project manage the cross-functional team, all as one job.The fractional model, on purpose. Leslie built her post-corporate career around embedding temporarily, moving fast because she doesn't own the politics or the day-to-day, and leaving once the fix sticks — a deliberate contrast to being pulled into the org chart permanently.Point of sale, coupons, and designing from a distance. Leslie tells the story of a Bed Bath & Beyond coupon bug that was refunding customers more than they'd paid — and why sitting between IT, finance, and the register (rather than just taking a requirement and building it) was the only way to catch it before it hit stores.Standing behind the register. Every six to eight weeks, Leslie would pull the most disconnected corporate stakeholders out of their meetings and put them behind an actual register for an hour, working real customers. She'd found someone in charge of a process who'd never once seen it run. Her fix wasn't a training deck — it was making them stand there.The light bulb, not the lecture. Leslie doesn't tell frontline staff what to do — she asks questions until they arrive at it themselves. She walks through how she gets buy-in on something as small as scanning a coupon by tracing the chain all the way to the employee's own bonus, because "everybody wants to know what's in it for me."AI as a tool for separating the science from the art. Leslie frames operations as having both a black-and-white, executable "science" side and a harder-to-replicate "art" side — reading people, seeing the pattern, knowing what to say to whom. Her take: AI's value is taking the science off her plate so the art has more room to work, not replacing the art itself."We're too busy to get good." Both Matt and Leslie return to this as the excuse that quietly runs most operations teams — the two hours you don't have time to invest now costing five hours a week forever.Notable Quotes"I never forgot where I came from, because every single block built on the previous one." — Leslie LaCosta"If you're really willing to call it a transformation, you need to bring in temporary resources to support it for a distinct amount of time, and then let them leave." — Leslie LaCosta"I'm here for a good time, not a long time." — Leslie LaCosta"You can't pressure test anything until you're standing in front of a customer who's in a rush." — Leslie LaCosta"By the time they walked out of the store, they would usually go like, 'Holy shit, that's hard.'" — Leslie LaCosta"Everybody wants to know what's in it for me." — Leslie LaCosta"Everybody perceives operations as always science, because it's mostly black and white. But there is an art to it." — Leslie LaCosta"If AI can take some of the workload of the science off of my plate... that to me is all it does is make me better and lets me shine on what I bring to the table." — Leslie LaCosta"Miraculously, when it comes time for me to take PTO, somehow I was able to take five business days off, and it all still ran." — Leslie LaCostaWho Should ListenAnyone running or absorbing the fallout of a cross-functional transformation initiative; regulatory operations and RIM leaders who manage vendor relationships and system change control; operations and CX leaders trying to close the gap between headquarters intent and frontline reality; anyone deciding whether their next hire should be permanent or fractional; and anyone using AI to offload repeatable work so they can spend more time on judgment calls.ReferencesLeslie LaCosta — LinkedIn, TikTokThe Metamorphosis Studios Real Experience. Real Transformation. Really Different. Business Consulting and Services Operations Utopia - Where Regops, Innovation, Technology, and Execution Meet.Disclaimer: This podcast reflects only the opinion of the podcaster and guests and does not reflect those of their organizations, system vendors, or service providerOriginal show theme "Little Sammy" by Matt Neal
OU-009: Frank Nogueira — The Wait Is Optional   Guest Bio Francisco (Frank) Nogueira is CEO of Accumulus Technologies, where he leads the continued evolution and global adoption of the Accumulus Platform, helping transform regulatory collaboration to accelerate patient access to medicines. Prior to leading Accumulus Technologies, he served as Chief Executive Officer of the nonprofit Accumulus Synergy. He joined Accumulus in 2020 from Genentech, where he served as he served as Vice President of Regulatory Affairs at Roche. Accumulus Technologies is reimagining how life sciences organizations and national regulatory authorities work together to accelerate the drug development lifecycle, from drug discovery through global availability. Connecting industry to 75+ regulators around the globe, the Accumulus platform is a secure, purpose-built, SaaS platform that enables real-time collaboration and continuous data streaming - powering faster decisions, global alignment, and accelerated access to therapies for patients worldwide.  Key Topics The four connective tissues. Frank's frame for the last thirty years: the internet connected people, cloud connected enterprises, AI is connecting knowledge, and the next layer — the one still missing — is connected scientific evidence. That is what Accumulus is building. Frank says the community today is "data rich but information poor," and the volume of scientific evidence generated worldwide has become astonishing. Somebody has to move it, securely, in real time, without waiting three years per region. The collision course. Large pharma is betting hard on AI, generating more data than ever, presenting it more ways than ever, with fewer people. Meanwhile some regulators are still receiving paper dossiers. Frank thinks the gap between leading and lagging regions doesn't just persist — it accelerates unless the digital infrastructure catches up. Gene and cell therapies mean smaller trials with smaller patient populations but larger information volumes per submission. His prediction for the next decade: regulator workload goes logarithmic. Trust, reliance, and the manufacturing change problem. Frank spends real time on the reliance framework — one regulator leaning on another's review work. Manufacturing changes today can take three to five years to work through global regions, forcing companies to maintain parallel manufacturing lines or accept country-level shortages. What Accumulus is seeing on the platform: regulators watching those changes in real time, seeing the questions and answers as they happen, and concluding "they did everything we were going to do. They asked every question we were going to ask. In fact, they asked more. There's nothing for us to wait three years for." Sovereignty is not the same as isolation. Frank is clear he isn't arguing for one mega-regulator. Each regulator maintains sovereignty and independence. But sovereignty is compatible with reliance, work-sharing, and specialization. Five countries in a region don't need five reviewers doing the same work in parallel — they can carve up the modules. Low-to-middle income regulators increasingly tell Frank they're relieved to be getting the same scientific package the FDA and EMA got, which increases trust in the system rather than eroding it. The three camps. Frank divides industry into three groups. Camp one: the naysayers with a thousand reasons change won't work. Camp two: the curious middle, who Frank says used to be curious about whether it would work and are now curious about how to make it work in their own company. Camp three: the "let's go" people who see a thousand reasons this will be problematic and decide to figure it out anyway. Matt and Frank are both in camp three. Technology isn't the bottleneck anymore. Frank's closing thesis, and Matt's too: this is no longer a technology problem. It's change management, vision, and incentives. The infrastructure exists. What determines the speed of adoption is how many companies and regulators move from wait-and-see to "let's go." How Accumulus got here. The nonprofit Accumulus Synergy was formally formed on July 13, 2020 out of quarterly regulator-industry conversations that had been running since 2019. The original scope was small — a handful of people and a large cloud provider. They ran a full year-long RFI/RFP with the three main cloud providers. The winner worked with them for three months and pulled out, saying it was too complex and outside their core business. That refusal is what forced Accumulus to become a technology company itself. Nonprofit skepticism and the spinout. The nonprofit ran into skepticism from two directions. Inside the U.S., people said big pharma funds it, so how nonprofit is it really. Outside the U.S., the concept didn't translate. Regulators told Frank they didn't want to work one way for large pharma, another for mid-size, another for small biotech. Building a growth-hungry SaaS platform inside a nonprofit shell got harder every quarter. On August 4, 2025, Accumulus Synergy spun out Accumulus Technologies as a commercial entity — turning one year old as a commercial company right around the time this was recorded. Public benefit corporation: a side quest worth taking. Matt asks if Frank considered a PBC for the spinout. He did, but sees PBCs today as more branding than structural — many are still fully driven by revenue and shareholder value. Matt pushes back with his own PBC pharma experience: the incentive is real, but no publicly endorsed measurement standard exists for pharma-specific impact. B Corp doesn't quite fit. Matt's take: there's opportunity for existing PBCs to define and publicize the standard themselves as a differentiator. Notable Quotes Frank on the real barrier: "Technology is absolutely no longer a factor. It is mostly change management." Frank on the four-layer progression: "The internet connected people... cloud connected enterprises... AI is connecting knowledge... our next step is to connect scientific evidence." Frank on where the industry actually sits: "The community in general is data rich but information poor." Frank on reliance in the wild: "They did everything we were going to do. They asked every question we were going to ask. In fact, they asked more. There's nothing for us to wait three years for." Frank on the paper-dossier gap: "You have regulators who are still receiving paper dossiers, and you can see why those two are on a collision course." Frank on the wait-and-see camp: "Change is even more uncomfortable than the parts of my job I don't like." Frank on the closing frame: "We no longer believe that every country is an island." Audience Regulatory strategy and operations leaders inside pharma, health authority technologists thinking about digital submissions and reliance pathways, RIM teams, and anyone building or buying tech that has to interoperate across sovereign regulators. Also for anyone who has looked at a three-to-five-year approval tail and quietly wondered why the industry treats it as physics rather than a decision. References Accumulus Technologies (commercial spinout) Francisco Nogueira on LinkedIn Accumulus Synergy spins out Accumulus Technologies (Aug 4, 2025) Nogueira appointed CEO of Accumulus Synergy (May 13, 2021) Operations Utopia - Where Regops, Innovation, Technology, and Execution Meet.Disclaimer: This podcast reflects only the opinion of the podcaster and guests and does not reflect those of their organizations, system vendors, or service providerOriginal show theme "Little Sammy" by Matt Neal
loading
Comments