Why ingredient qualification doesn't fit a standard sales pipeline

Most B2B sales pipelines have five stages: Prospect, Qualified, Proposal, Negotiation, Closed. They were designed for deals that close in weeks or months, involve one or two decision-makers, and follow a roughly linear path. Ingredient qualification is structurally different from this in almost every dimension.

A single ingredient qualification project involves up to six customer departments with different evaluation criteria and timelines. The technical evaluation (formulation testing, stability, performance) runs in parallel with commercial evaluation (pricing, supply chain, regulatory). Either track can block progress independently of the other. And the whole process routinely runs 12-24 months, with plenty of projects taking longer.

Forcing this into five generic stages loses the context that determines whether a project is actually progressing or silently stalling. Here's a more useful framework.

Stage 1: Lead

A lead is a potential customer application identified as commercially interesting but not yet formally engaged. The supplier has either identified an opportunity through market intelligence, a trade show conversation, or a referral, but the customer has not yet made a formal request for samples or information.

Key activities: identifying the right entry contact, qualifying the application fit, making first contact. Key risk: leads that never convert because the right contact was never identified. Stall threshold: 30 days without contact activity.

Stage 2: Sampling

The customer has requested samples. This is the first formal commitment from the customer side. They've decided the ingredient is worth evaluating. The supplier prepares and ships samples, typically with accompanying technical documentation (TDS, SDS, CoA, efficacy data).

Key activities: sample preparation, documentation package, logistics, first technical briefing. Key risk: samples shipped but never tested because the customer's formulation team deprioritizes the evaluation. Stall threshold: 30 days without evaluation feedback. The average time from sample request to first evaluation result is 6-8 weeks in cosmetics, 8-12 weeks in food, and 12-16 weeks in pharma excipients.

The most common reason a Sampling stage project stalls isn't a rejection. It's silence. The customer's formulation team received the samples but got pulled onto a higher-priority project. A systematic follow-up 3 weeks after sample delivery recovers 40-60% of these evaluations.

Stage 3: Formulation Testing

The customer's formulation team is actively testing your ingredient in their product formulations. This is the core technical evaluation stage and the longest one in most qualification processes. The team is assessing performance, compatibility, stability, and process behavior.

Key activities: technical support (answering formulation questions, troubleshooting), providing additional sample quantities or variants, sharing application data. Key risk: formulation compatibility issues that slow or derail the evaluation. Stall threshold: 45 days without technical feedback.

This stage can cycle multiple times if initial formulations don't perform as expected. Each reformulation iteration adds 4-8 weeks. Technical suppliers who provide proactive application support during this stage win disproportionately. The formulation team develops a preference for suppliers who help them succeed.

Stage 4: Pilot

The formulation is approved. The customer moves to pilot-scale production to validate that the formulation works at commercial volumes. This stage involves the production team for the first time, introducing new stakeholders and a new evaluation lens: processability, batch-to-batch consistency, and scale-up behavior.

Key activities: supplying pilot quantities (typically 5-50kg for cosmetics, larger for food/pharma), supporting production trials, addressing scale-up issues. Key risk: production issues that were not visible at lab scale. Stall threshold: 30 days without production feedback.

Stage 5: Negotiation

The technical qualification is complete. Procurement takes over. Pricing, supply terms, minimum order quantities, lead times, and supply chain requirements are negotiated. Regulatory documentation for the target markets is finalized.

Key activities: commercial negotiation, supply agreement drafting, regulatory package completion, quality agreement review. Key risk: pricing negotiations that stall or collapse after years of technical investment. Stall threshold: 21 days without commercial progress.

Negotiation stage stalls are disproportionately caused by procurement cycle timing, not genuine price disagreement. A project that goes quiet in Negotiation in August is often just waiting for procurement's Q4 budget approval. Knowing the customer's budget cycle prevents premature escalation.

Stage 6: Commercial

The first commercial order has been placed. The supplier is supplying the ingredient for the customer's commercial production. This stage covers the launch period and initial commercial supply, from first order through to a stable, ongoing relationship.

Key activities: order fulfillment, quality management, commercial relationship maintenance. Key risk: supply issues in the first commercial batches that damage the relationship before it fully forms. Monitoring: order frequency, batch quality, relationship health.

Stage 7: Ongoing Supply

The qualification is complete and the commercial relationship is established. The customer reorders on their production schedule. This stage is often treated as 'done' by sales teams, but it requires ongoing relationship investment for two reasons: competitive threats from new suppliers, and new application opportunities within the same account.

Key activities: regular account reviews, monitoring for competitive threats, identifying new application opportunities, relationship maintenance with R&D for next-generation product evaluations. Key risk: complacency. The account that was hard-won over 18 months can be lost in 3 months if a competitor works the relationship more actively.

What good pipeline tracking looks like

Knowing which stage a project is in tells you what happened. Knowing how long a project has been in each stage, and which activities have occurred in that time, tells you what's likely to happen next.

A project that moves from Sampling to Formulation Testing in 4 weeks with five documented technical interactions is on a healthy trajectory. A project that has been in Formulation Testing for 60 days with no documented interactions since the initial sample dispatch is silently stalling, and the customer is probably evaluating an alternative.

This is why stage duration matters as much as stage position. A pipeline that shows '15 projects in Formulation Testing' is less useful than one that shows '8 projects actively progressing in Formulation Testing and 7 that have been there over 45 days with no recent contact.'