The Method Made Story
Prototype (Dec 2024)
Usability Testing (June-Sept 2025)
Build Azure Managed Application (Nov 2025-April 2026)
Develop Supporting Validation Documents(April 2026)
Product Roadmap Reconciliation & Release (May 2026)
Customer discovery (May 2024)
Product Roadmap Definition (May 2025)
Enterprise Security Requirement Definition (Oct 2025)
Business Mandate Definition (Feb 2025-April 2026)
Technical Test Definition and Execution (May 2026)
Continuous Improvement (June 2026)
View from the trenches
I didn't build Method Made as a commercial technology exercise. I built it because I spent 10 years in the synthetic biology trenches trying to innovate across diagnostics, microfluidics, metabolic engineering, and process development. I ran two quality laboratories. I built Quality Management Systems from Google Sheets.
Across every deep technical innovation I worked on, I noticed a universal, frustrating truth: I could easily replicate an intricate biological procedure if a scientist physically showed me their nuance: how they gently resuspended a pellet, treated a sensitive culture line, handled silicon wafers. But the moment I tried to execute that exact same procedure from a downloaded, written protocol, it failed.
I realized that narrative words are a catastrophic medium for describing physical, multi-dimensional biology.
Nicholas (Nico) Crudele MSc
Founder
Research to Reality
The entire foundational premise of science is built on a single promise: you are supposed to be able to write an execution pathway down on paper so that another scientist, anywhere in the world, can perfectly reproduce your results.
But in graduate school, when I looked around the lab and asked my peers if they had ever successfully reproduced a protocol from a published paper outside our immediate circle, the universal response was a cynical laugh. It always sucked. It never worked. Eventually, people just quit trying. This creates silos - where labs can only really build on their immediate physical neighbours’ work.
I came to a staggering realization: the text-based scientific paper is a broken technology. In fact, on a technical level, the only reason modern research university programs still require physical, on-site presence is so that you can watch an expert physically execute a task. If the written medium actually worked, presence wouldn't be mandatory, and biotechnology would be like software: code could be used as a product, without needing to be the inventor.
When deep tech moves out of academic labs, where budgets are built for pure research and crosses into commercial CDMOs where therapies must be manufactured at scale and under GMP requirements, this text-based platform defect becomes a multi-million dollar liability.
Validation: 100 Process Development Engineers
Talking to grad school peers was enough to come up with a hypothesis, but naturally I needed rigorous data to understand whether this was a problem at scale. Was this documentation friction an isolated user-error on my part and other grad students, or was it a systemic industry failure?
To find out, I interviewed 100 Process Development (PD) engineers across the biotechnology ecosystem. What I discovered was staggering. PD engineers are hired to conduct advanced process characterization, but in reality, they spend the vast majority of their lives operating as overqualified technical writers. They are trapped in a constant, manual dance: using texts, emails, calls, and frantic site visits just to uncover and patch the massive documentation gaps (technical debt) left behind by R&D labs.
I asked the engineers a simple question: 'What do the Standard Operating Procedures (SOPs) look like when they are handed over to you?'
The reality they disclosed was an operational nightmare.
They weren't receiving standardized SOPs. They were receiving an unpredictable mish mash of unstructured data: fragments of messy lab notes, massive binders filled with a graduate student's stream-of-consciousness thoughts, or worse yet a PowerPoint deck detailing the 'Founder’s Vision' of how the process ought to look (but doesn’t).
Highly trained engineers were being forced to spend months acting as overqualified technical writers, using a chaotic web of frantic calls, emails, texts, and emergency site visits just to fill the massive cracks left behind by narrative text. It became blindingly obvious: Word documents are a completely non-viable software platform for high-stakes biology.
The Automation Myth: The Human Bridge
The advanced therapies industry loves to talk about complete automation as the ultimate cure-all for manufacturing risk, and removing human execution error. We see brilliant individual tools: highly sophisticated automated bioreactors and automated analytical assay platforms.
But the industry has largely adopted a serial, 'widget-based' approach to scaling: using one specialized tool for one specific task, then moving the product to the next. This leaves a massive, unaddressed vulnerability: The Human Bridge. Even if you fully automate a bioreactor, a human operator still has to physically harvest the cells, interpret the fluid transfer script, and get them inside the machine. Even if you automate an ELISA assay, a human must manually pipet the sensitive reagents, balance environmental variables, and execute the run. Technical risk doesn't evaporate with automation; it concentrates at the human-widget interface.
Today, patients are actively dying on waitlists while critical therapeutic batches sit frozen in paperwork backlogs.
Why? Because human operators are forced to act as the literal, manual interpreters of ambiguous text-based instructions, triggering endless compliance deviations and grueling CAPA investigations.
The Solution: Transforming Narrative Prose into Navigable, Structured Data
To eliminate human interpretation risk, Method Made does something fundamentally different:
1) eliminating guess work:
We collateralize all SOP text against video instructions, demanding not just what to do, but also how to do it,
2) navigable data:
We engineered a domain-hardened data schema that completely replaces narrative prose with a structured data array.
To a non-software operator, an 'array' sounds like abstract mathematics. In reality, you can think of our schema like an intelligently engineered book. A standard text document is like a continuous roll of parchment paper. You have to read the whole thing linearly to find a single detail. Our structured array turns the protocol into an object with a deterministic, predictable telescoping structure: document level title which contains sections, which contain steps. GMP environments demand such structure for SOPs, Method Made ensures that the data going into the engineer at the CDMO is already structured correctly, saving months of rewriting.
Because the protocol is transformed into clean data architecture, it becomes instantly navigable by humans, enterprise software systems, and future AI models alike. A QA auditor or a cleanroom operator on the ground floor can instantly open the table of contents, isolate a single specific action step, and click a hyperlink that takes them directly to the video timestamp showing how that precise step must be executed in the physical world. A clinical study designer can take a bird’s eye view to see the title and sections only of many SOPs, without drowning in the details of each.
We didn't just build a software tool. We rebuilt the medium of technology transfer from scratch.
Mission
That is why I built Method Made: a domain-specific data schema that fundamentally replaces narrative text instructions with structured, deterministic, action-oriented execution pathways. It removes the human interpretation risk from the equation.
It's the tool that I needed, that 100 PD engineers demanded, and that the future of translational medicine requires to get innovative cell and gene therapy products into the hands of patients before it's too late.