A fermentation R&D partner delivers a documented, reproducible process, not just experimental data. At the end of a well-structured project, you receive process parameters, analytical reports, and a validated protocol that your team or a production facility can work from directly. The exact deliverables depend on the project scope, but the goal is always the same: turning a concept into something technically proven and transferable. The sections below address the most common questions companies ask before engaging a contract fermentation partner.
What does a fermentation R&D partner actually do during a project?
A fermentation R&D partner designs, runs, and interprets microbial process experiments on your behalf, using infrastructure and expertise you do not have in-house. This includes selecting the right microbial system, setting up controlled fermentation runs, monitoring process parameters in real time, and adjusting conditions iteratively until the process performs reliably. The partner acts as an extension of your internal R&D team, not as a black-box service provider.
In practice, this means the partner takes responsibility for the technical execution while keeping you informed at every decision point. At Avecom’s fermentation services, for example, work spans aerobic and anaerobic systems, batch and continuous configurations, and mesophilic and thermophilic conditions, depending on what the target process requires. High-throughput molecular tools such as amplicon sequencing and qPCR are used to monitor and steer the microbial community, which is especially important when working with mixed cultures rather than single-strain systems.
Throughout the project, the partner documents every run, every deviation, and every process adjustment. This documentation is not administrative overhead, it is what makes the results transferable and defensible when you present them to investors, regulators, or a production partner.
What technical deliverables can you expect at the end of a project?
At the end of a fermentation R&D project, you can expect a set of technical deliverables that includes a validated process protocol, a comprehensive analytical report, and, depending on scope, physical samples of the fermentation product. These outputs are structured to be usable beyond the lab: by your engineering team, a licensing partner, or a contract manufacturer.
Typical deliverables include:
- Process protocol: A detailed description of operating conditions, inoculation procedures, feeding strategies, and critical control points
- Analytical data package: Yield data, product quality measurements, microbial composition profiles, and process stability indicators across multiple runs
- Scale-up recommendations: An assessment of which parameters are sensitive to scale and what risks to anticipate when moving to larger reactors
- Scientific report: A structured document suitable for use in subsidy applications, patent filings, or investor due diligence
- Product samples: Where applicable, small quantities of the fermented material for downstream testing or customer evaluation
The quality of these deliverables depends heavily on how well the project scope was defined at the outset. A partner who helps you frame the right questions at the start will produce outputs that are far more actionable than one who simply runs experiments and reports results.
Get in Touch
Let’s Talk Microbial Solutions
Book a conversation with Stijn, our CEO, or send us your request.
| Book an Appointment | Request Information |
How does a partner protect your IP during and after the project?
A reputable fermentation R&D partner protects your intellectual property through a combination of contractual agreements and operational practices. Before any technical work begins, a non-disclosure agreement should be in place. Ownership of results, including process data, protocols, and any inventions arising from the project, should be explicitly defined in the project contract, typically assigning those rights to you as the client.
Operationally, IP protection means working in a closed environment where your project is not discussed with other clients, your microbial strains or formulations are handled under strict confidentiality, and data is stored and accessed only by the team working on your project. A partner with a track record in contract R&D will have established procedures for this, it is part of the professional standard, not a special accommodation.
One practical consideration: if the partner contributes significant background knowledge or proprietary methods to the project, the contract should clarify what is licensed to you for the purpose of the project versus what remains the partner’s own IP. Getting this right at the start avoids disputes later, particularly if the project leads to a patent application.
What’s the difference between a feasibility study and a pilot-scale project?
A feasibility study answers whether a fermentation concept works at all; a pilot-scale project answers whether it works reliably and predictably at a larger volume. These are fundamentally different questions, and they require different resources, timelines, and risk tolerances.
Feasibility study
A lab-scale feasibility study typically runs in reactors of a few liters or less. The goal is to establish proof of concept: can the target microorganism or microbial community perform the desired conversion under controlled conditions? The study tests a range of parameters, temperature, pH, substrate concentration, aeration, to identify conditions where the process functions. Results are indicative, not definitive, and variability between runs is expected at this stage.
Feasibility studies are the right starting point when you are not yet certain your concept is technically viable, when you want to de-risk investment before committing to larger infrastructure, or when you need preliminary data to support a funding application.
Pilot-scale project
A pilot-scale project moves the process into reactors of tens to hundreds of liters, sometimes up to 2,000 liters in a well-equipped facility. The objective shifts from “does it work?” to “can we control it consistently?” Pilot runs expose process sensitivities that do not appear at lab scale: mixing gradients, oxygen transfer limitations, heat management, and the behavior of the microbial community under sustained operation. A pilot project produces the data needed to design a full production process.
Most companies benefit from completing a feasibility study before committing to pilot-scale work. The feasibility phase narrows the parameter space and reduces the risk of expensive pilot runs that fail for reasons that could have been identified earlier.
How do you know if the fermentation process is ready to scale up?
A fermentation process is ready to scale up when it meets three criteria: it performs consistently across multiple independent runs, the critical process parameters are understood and controllable, and the performance gap between lab and pilot scale has been characterized. Without all three, scaling up is a gamble rather than an engineering decision.
Consistency means the process delivers similar yield, product quality, and microbial stability run after run, not just in the best-case experiment. Understanding the critical parameters means you know which variables (pH, dissolved oxygen, temperature, feeding rate) have the largest impact on performance and can be actively controlled. Characterizing the scale-up gap means you have data or a credible model predicting how the process will behave in a larger reactor, where mixing and mass transfer dynamics are different.
Molecular monitoring tools play a significant role here. Tracking the composition and activity of the microbial community through techniques like amplicon sequencing gives you early warning of instability and helps distinguish between a process that is genuinely robust and one that happened to work well under ideal lab conditions. A process that looks stable at lab scale but shows community drift under pilot conditions is not ready for commercial production.
Who should consider working with a contract fermentation R&D partner?
Companies that have a fermentation concept but lack the infrastructure, expertise, or time to develop it internally are the primary candidates for contract fermentation R&D. This typically includes biotech scale-ups, agri-food ingredient producers, and industrial biotechnology companies that need to validate a process or generate scale-up data without building their own pilot facility.
The decision usually comes down to three practical factors. First, internal lab capacity: if your team can run small exploratory experiments but cannot operate controlled bioreactors or analyze microbial communities at the molecular level, a partner fills that gap directly. Second, timeline pressure: building fermentation infrastructure takes years; engaging a partner with existing capacity compresses that timeline to months. Third, technical risk: a partner who has run hundreds of fermentation projects can anticipate failure modes and design experiments that avoid them, which is difficult to replicate with a team doing fermentation development for the first time.
Companies working with complex mixed microbial cultures, rather than well-characterized single strains, benefit particularly from a partner with specific expertise in microbiome engineering. This is a technically demanding area where general bioprocessing experience is not sufficient. Avecom’s background, rooted in over 30 years of mixed-culture microbiology, reflects the kind of specialized depth that matters when the microbial system itself is part of what needs to be understood and controlled.
If your organization is evaluating whether contract fermentation R&D makes sense for your current project stage, the most useful first step is a technical intake conversation, not a commercial proposal. A credible partner will want to understand your process concept, your current data, and your timeline before recommending a project structure.