Condiment product development: how the process works

What to take away

• Development is a sequence of gates, not a long cooking session. Each gate kills ideas cheaply.
• Write the brief before the first bench batch. A product without a stated job cannot be judged.
• The process review sits in the middle of development, not at the end, because it can change the formula.
• Most projects fail at scale up, when a bench recipe meets real heat transfer and real equipment.

The six gates

Gate	Question it answers	Typical cost
Brief	What job does this do, and for whom	Time only
Bench	Can we make something that does it	Ingredients
Screening	Do people other than us prefer it	Small
Pilot	Does it survive the real equipment	Moderate
Process review	Is the process safe and documented	Real, and unavoidable
Launch	Can we make and sell it repeatedly	Largest

Skipping a gate does not save money, it moves the cost later. The most expensive version of this mistake is discovering at pilot that the formula cannot be made safely at scale, after the labels have been printed.

Writing a brief that constrains

A useful brief names the job, the user, the channel, the price ceiling, the format, and the constraints you refuse to break. Three sentences is enough. What is missing from the brief is what will be argued about in month four.

Set the exclusions explicitly. No refrigeration. No allergen X. No ingredient we cannot buy twice a year. Constraints written down early do more for a project than any amount of creative freedom.

Bench work, and knowing what has already been studied

Bench batches should be small, weighed, and recorded. Change one variable per batch. Keep the failures, because a failed batch with a good record is data.

It is also worth checking what is already known before you spend months finding it out. The USDA Food Safety Research Information Office collects and organises publicly funded food safety research, and its programme page explains that its purpose includes preventing unintended duplication of food safety research. For a small developer, the research projects database is a fast way to see whether your question already has an answer.

Where the outside help lives

Development touches areas most food founders have not done before: costing, packaging specification, regulatory route and channel strategy. The Small Business Administration funds a network of resource partners, including Small Business Development Centers, SCORE mentors, Veteran Business Outreach Centers and Women's Business Centers, which provide individual advising on planning, operations, financial management and marketing. It costs nothing and it shortens the learning curve.

The technical half is different. A process authority establishes the safe process for a shelf stable acidified product, and a laboratory can verify composition. Neither is optional, and neither is a business adviser's job.

Pilot and launch

At pilot you are testing the process, not the recipe. Heat transfer, fill temperature, closure performance and hold times all change with volume. Expect to adjust, and expect the process review to be revisited if you do. When you get to launch, the cost structure guide is the right place to check whether the finished product can be sold at a price anyone will pay, and the planning sequence covers the regulatory route in order.

Common questions

How long does development take? For a simple shelf stable condiment, months rather than weeks, mostly waiting on reviews and packaging.

Can I develop and launch at once? You can, and the usual outcome is a recall risk and a formula you cannot repeat.

Who signs off the formula? Name one person at the brief stage. Shared ownership stalls at every gate.

When should I involve a co-packer? Before the pilot, so their equipment shapes the formula rather than fighting it.