From Training to Competence: What Food Founders Miss at $10–20mm

Over the years, Liz and I have worked with a lot of founder led food manufacturing businesses. Different products, different personalities, different stages of growth. But there is a very consistent moment that shows up as companies approach roughly $10 to $20 million in revenue.

The systems that got them here start to feel shaky.

Not because people are lazy. Not because they do not care. And usually not because food safety or operations were ignored. It is because the business has quietly outgrown the way competence is defined and verified.

Most food companies at this stage have training. They have SOPs. They have videos, sign off sheets, maybe even an LMS. On paper, things look solid.

But founders start asking themselves uncomfortable questions.

Can this line really run without me here?
Who actually knows how to make the right call when something goes wrong?
If an auditor walked in tomorrow and I was not on site, who would I trust to explain what is happening?

That gap between training and real confidence is what this post is about.

The Checklist Trap

Training systems are very good at proving exposure.

Someone watched the video.
Someone read the SOP.
Someone signed the form.

What they are not good at proving is competence.

Food manufacturing does not break down when people forget steps they memorized. It breaks down at decision points.

A deviation that is not quite in spec.
An ingredient that shows up a little off.
A line that is technically running but clearly unstable.
A new operator who does not know when to speak up.

Checklists tell you whether rules were followed. They do not tell you whether someone can think clearly when the rules collide with reality.

As companies scale, these moments happen more often and with higher stakes. Throughput matters. Margins are tighter. One bad decision can cascade quickly.

This is where founders start to feel uneasy, even if they cannot yet articulate why.

What Competence Really Means in a Food Plant

Competence is not knowing what to do when everything goes right.

Competence is knowing what to do when it does not.

For every role in a plant, there are a small number of decisions that really matter. Decisions that involve safety, quality, people, or stopping and starting expensive equipment.

A competency based approach asks very different questions than traditional training.

What decisions does this role own under pressure?
When should this person act independently and when should they escalate?
What does good judgment look like here, not just technical compliance?

This is especially important in food safety. Real food safety is not blind adherence to a checklist. It is understanding intent, risk, and consequences well enough to make the conservative call even when it costs time or money.

When someone can explain why a step matters, not just how to do it, you are much closer to real competence.

Observable Proof Beats Assumptions

One of the most dangerous phrases in a growing food business is, “They are trained.”

Trained does not mean ready.

Observable proof of competence looks different.

Can this person run the line without supervision?
Can they catch a problem before QA points it out?
Can they explain a deviation clearly and calmly?
Can they train someone else correctly?

If competence cannot be seen, tested, or demonstrated, it is being assumed. And assumptions are expensive at scale.

This is where many founders feel trapped. They are carrying too much in their own heads because they do not yet trust the system to hold without them.

How We Approached It Differently

This week, Liz and I built a competency based personnel playbook for a food manufacturing operation scaling toward about $15 million in revenue.

The goal was not to add more training content. It was to give the owner clarity.

For each critical role, we focused on:

What decisions this role must make when things go sideways.
What good judgment looks like in real situations.
What observable proof would tell us this person is ready.

To help structure this work efficiently, I used Claude Cowork as a thinking partner. Not to replace experience, but to help organize it. Claude was particularly useful in pressure testing role definitions, decision ownership, and edge cases that founders often handle instinctively.

The result was a playbook the owner could use immediately, not after another long rollout or system implementation.

Why This Matters at $10-20mm

At this stage, the business starts to rely on trust rather than proximity.

The owner cannot be everywhere.
Decisions are happening without direct oversight.
Small gaps turn into real risk.

Growth is rarely blocked by equipment at this point. It is blocked by unclear ownership, uneven judgment, and invisible skill gaps.

When competence is defined clearly, something important happens. The business calms down. People know what is expected. Owners stop being the bottleneck for every decision.

A Final Thought for Founders

If you are feeling the quiet tension of asking yourself whether your team is actually ready for the next stage, you are not behind. You are right on time.

This is a normal inflection point in food manufacturing. And it is solvable.

The shift from training to competence is not about being harder on people. It is about being clearer. Clear about decisions. Clear about judgment. Clear about what readiness really looks like.

That clarity is often the difference between scaling with confidence and scaling with anxiety.

If this resonates, Liz and I spend our time helping founder led food brands strengthen operations, food safety systems, and teams before things feel broken. We are always happy to compare notes.