The approved vendor list: why being better is not enough

You won. And nothing happened.

I have watched this happen more times than I can count. A deeptech founder gets the call every founder dreams about. The engineering team at a large manufacturer has tested their material, their sensor, their coating, and the verdict is in: it performs. Better than the incumbent. The champion inside the company is excited. There is talk of a first order.

Then months pass. Emails get answered more slowly. The champion stops promising dates. Eventually the founder hears a sentence that sounds like a formality: we just need to get you on the approved vendor list.

Just. That word has killed more deeptech revenue than any competitor ever will.

Because the approved vendor list is not a formality. It is a second sale, to a different buyer, with different rules, that nobody told you about. And most founders only discover it exists after they have already lost a year to it.

The list is not about your product

Here is the mental model that helps. The technical evaluation asks: does this thing work? The approved vendor list asks a completely different question: can this company be trusted with our production?

Those questions live in different departments. The first one is asked by engineers, who are paid to find better technology. The second is asked by procurement and quality, who are paid to prevent disasters. An engineer gets credit for finding you. A procurement manager gets fired if you fail and it stops a line.

This is why being better is not enough. Your product won its evaluation. Your company has not won anything yet. Procurement is not evaluating your technology at all. They are evaluating your balance sheet, your quality system, your production capacity, your second source for raw materials, your plan for what happens when your one key engineer gets hit by a bus. They are, in a very real sense, pricing the risk of you.

Why the list exists at all

It is tempting to read the list as bureaucracy. It is not. It is scar tissue.

Every large manufacturer carries the memory of a supplier failure that stopped production. A line that runs 24/7 and produces a million euros of output a day does not care how innovative your part is. It cares that the part arrives, every time, to spec, forever. One bad batch of a two-euro component can idle a plant.

The automotive industry codified this decades ago into standards like IATF 16949, and similar logic runs through aerospace, chemicals, food, and pharma. The approved vendor list is the visible tip of a risk-management system that the company built over years of expensive mistakes. When procurement asks you for a process audit, a financial statement, and evidence of a documented quality management system, they are not being difficult. They are doing the job they were hired to do.

Founders who understand this stop fighting the list and start selling to it. That shift is the whole game.

The champion cannot carry you through

Your technical champion is essential and insufficient at the same time. They can open the door, arrange the test, and argue for you internally. What they usually cannot do is fill in a supplier onboarding questionnaire.

Watch what happens in practice. The champion sends your details to procurement. Procurement sends back a form with two hundred questions. About your ISO certification. Your liability insurance. Your export control compliance. Your business continuity plan. The champion looks at it, realizes they have no idea what half of it means, and forwards it to you with an apologetic note. Now the process is in your inbox, and every week it sits there unanswered, the internal momentum your champion built is quietly draining away.

Procurement people have a phrase for suppliers who take three weeks to return an onboarding form. They do not say it to your face. They say: not ready.

The evidence pack

So here is the move, and I am going to give it a name because it deserves one: the evidence pack.

Every approved vendor process in every large manufacturer asks for roughly the same things. A quality management certificate, or at minimum documented processes. Financial statements that show you will still exist in two years. Insurance. A description of your production process and capacity. References. Answers about business continuity and second sources. You know this list exists. You have answered versions of it.

Almost no founder builds it once, properly, and keeps it current. Instead they reconstruct it from scratch for every prospect, slowly, while the champion waits. That is the difference between a three-month approval and a nine-month approval. Not the quality of your technology. The speed of your paperwork.

Build the pack before you need it. Keep it in one folder. Update it every quarter. When procurement sends the form, you return it in three days, complete, professional, boring. Boring is the goal. Boring is what trustworthy looks like to the person who can put you on the list.

But what about startups without certifications?

This is the counter-argument, and it deserves to be taken seriously. You are two years old. You do not have ISO 9001. A full certification takes a year and money you would rather spend on engineering. Are you simply locked out?

No. But you have to pick a route, and there are really only four.

The first is the small door: ask for approval at a limited scope. One part, one plant, one non-critical application, a capped annual volume. Procurement departments do this more often than founders realize, because it caps their risk while letting the business test you. You get on the list as an approved supplier for a narrow use, you perform flawlessly for a year, and the scope widens. Most large companies have an informal version of this even if they never publish it.

The second is the borrowed reputation: sell through a partner who is already on the list. A distributor, an integrator, a larger manufacturer who buys from you and resells under their name. You give up margin and some direct customer contact. In exchange you skip the list entirely, because from the customer's perspective their existing approved supplier is delivering. For many deeptech companies this is the right first revenue, and there is no shame in it. The shame is in pretending you can skip the route choice.

The third is the co-signed risk: get your champion's business unit to sponsor a formal exception. Large companies have deviation processes for exactly this, where a senior executive accepts the risk of an unapproved supplier in writing. This works when the value of your technology is obvious and the application is contained. It works less often than champions promise, because it asks an executive to sign their name next to your risk.

The fourth is the long road: get certified anyway. If your customers are automotive, aerospace, medical, or food, this is not optional, it is the cost of being in the market, and every month you delay it is a month added to every future sales cycle. The founders who win here treat certification as a product feature, not as overhead.

The question to ask in the first meeting

Everything above compresses into one habit. In the very first serious conversation with a large manufacturer, before the pilot, before the technical deep-dive, ask: what does your supplier approval process look like, and who runs it?

Ask it cheerfully, as if you do this all the time. The answer tells you the real timeline, the real stakeholders, and the real gate. It also signals something to the person across the table: this supplier understands how we work. That signal alone moves you up the invisible ranking of startups they are talking to.

The founders who ask this question in week one close their first industrial order in year one. The ones who discover the list in month nine close in year three. Same technology. Different paperwork discipline.

Common questions

What is an approved vendor list?

A list maintained by a company's procurement and quality departments of suppliers that are formally permitted to deliver goods or services. Being on it is a precondition for receiving a purchase order, regardless of how well your product performed in technical evaluation.

How long does vendor approval take?

For a new supplier to a large manufacturer, typically three to twelve months depending on industry, criticality of the part, and how prepared the supplier's documentation is. Regulated industries sit at the long end.

Can a startup get on an approved vendor list without ISO certification?

Sometimes, through limited-scope approval, a sponsored exception, or by selling through an already-approved partner. In automotive, aerospace, medical, and food, certification is effectively mandatory and should be planned as part of the go-to-market, not after it.

If you are sitting on a technical win that has not turned into an order, the problem is almost never the technology. It is that nobody is running the second sale. Here is how we run the customer side, from first meeting to purchase order.