Who actually signs
At a manufacturer between fifty and a thousand people, the signer is the plant manager or the VP of operations, and the person who champions it is the quality manager, because the escape is their name on the corrective action. The controls engineer is the person who has to live with the system and is either your ally or the reason it never gets installed.
In food and beverage, pharmaceutical packaging, automotive tier suppliers, electronics and medical device assembly, the buying reason is nearly always the same: something got out that should not have, or too many people are being paid to look at things a camera should be looking at.
The one sentence version
Your buyer is a plant manager who has either just had an escape reach a customer or is paying three shifts of inspectors to prevent one, and who was burned by a vision system once before.
The triggers, and where each one is visible
- Recalls. Food, drug, consumer product and vehicle recall databases are public, dated and name the defect: foreign material, mislabeling, missing components, cosmetic defects that were contractual. A recall is a failed inspection, and its competitors run the same line.
- Quality inspector hiring waves. Several open inspector or visual inspection roles at one site is one process that does not scale. Job boards surface it, and the number of open roles is the size of the problem.
- Vision engineer and controls engineer job posts. A plant advertising for a vision engineer has decided to automate inspection and cannot yet staff it. A posting that names a vision platform is a plant that has already bought a camera and needs someone to make it work.
- New line and expansion announcements. A new packaging line, a new plant, a new product introduction. Each has an inspection step that has not been specified, and the equipment purchase orders are being written now.
- Inspection observations citing labeling or foreign material. Regulator inspection findings at food and pharmaceutical sites are public with a lag, and a finding on labeling or contamination control is an inspection gap with a response date.
- Customer mandates in the supply chain. Automotive and medical customers push inspection requirements down to suppliers, and a supplier announcing a new customer program has just inherited that customer's inspection standard.
Recalls and inspector hiring waves are the two to build on. One names the defect, the other names the cost, and a plant manager reading a note that names both is reading about their own line.
Qualify in sixty seconds
- Is it high volume with a visual defect? Repeatable parts at rate, with a defect you could see on a photo. A job shop with a different part every week is a poor fit for fixed inspection and a good fit for nothing you sell.
- Is there manual inspection headcount? Team size, shift pattern, inspector roles. Headcount is the budget.
- Is there a controls or automation engineer in house? Someone has to own the system after handover, and if nobody can, the engagement includes a support contract or it fails.
- Is there a capital cycle open? A new line, an expansion, a recall response, or a budget year. Vision is capital, and the timing of the ask is half the sale.
The angle that gets replies
Lead with the defect and the escape rate. The plant manager knows what an escape costs. They may not have connected that number to the cost of a system that catches the specific defect class their inspectors are missing at the end of a second shift.
Three openers you can adapt
- On a recall in their category"A competitor's product in your category was recalled last month for a missing seal on a fraction of a percent of units, which is the escape rate human inspection settles at by the end of a shift. That defect class is a presence check a camera does at line speed with effectively no escapes. If your line has the same step, a feasibility run on fifty sample units settles whether it is catchable. No charge for the run."
- On an inspector hiring wave"Six open quality inspector roles at the plant is usually one inspection step that does not scale rather than six vacancies. If the defect is visual and the part is repeatable, one station typically replaces two to three inspectors per shift and does not tire at hour seven. Happy to look at a few sample parts and say whether that is true for yours."
- On a new line announcement"Congratulations on the new line. The inspection step is the cheapest thing to design in and the most expensive to retrofit, mostly because of lighting and fixturing that the machine builder will not think about. If the equipment spec is not yet final, an hour on the inspection points saves a retrofit. Two paragraphs on the questions to ask the builder, attached."
Each one names a defect class, a number and a small next step. That is an engineer writing to a plant, not a vendor writing to a list.
What not to send
- "AI powered vision solutions." The plant manager has a defect, not a technology preference, and the phrase marks you as a reseller.
- A camera brand list. "We work with all major vision platforms" is a catalog. Which defect on which part is a conversation.
- "Improve quality and reduce costs." Every vendor in the building says this. It contains nothing about their line.
- Promising zero defects. Anyone who has run a line knows the false reject rate is the number that decides whether the system survives, and a note that ignores it has not been on the floor.
The objection you will hit
We tried vision and the false rejects killed it. Almost always true, and almost always the lighting and the fixturing rather than the camera. A system tuned on a bench in fixed light and installed under a skylight next to a vibrating conveyor will reject good parts until the operators unplug it. Do not defend the last system. Ask what the false reject rate was and where the camera was mounted, and describe how the second attempt is designed for the line as it is.
The second is our machine builder includes vision. The builder's vision is tuned at acceptance and drifts with product changes, lamp aging and wear, and nobody owns it after handover. The integrator's job is the model, the retraining and the false reject rate over time, which the builder does not sell.
The third is the operators catch it. At an escape rate that settles at a fraction of a percent by hour seven of a shift, which is exactly the rate the recall in their category was at. Do the arithmetic on their volume, gently, and the objection answers itself.
Deal shape
- Feasibility study on sample parts, with a report on catchability and expected false reject rate: commonly $3K to $15K, and the engagement that opens most relationships.
- Single inspection station, including lighting, fixturing, integration and acceptance: $40K to $150K.
- Line wide inspection across several stations: $150K to $500K and up.
- Support and retraining contract: $1K to $5K a month, and the reason the system survives its first product change.
- Signer: plant manager or VP Operations. Champion: quality manager. Owner: controls engineer. Cycle: two to six months on a capital approval, and weeks after a recall.
The feasibility study is the funnel. It costs the plant nothing but fifty sample parts, it produces a written answer to the only question the plant manager has, and it sets the false reject expectation before anyone has spent capital.
A cadence you can actually run
- Weekly, pull recalls by category in the industries you serve, and note the defect class in each notice.
- Weekly, pull quality inspector, vision engineer and controls engineer job posts, and count open inspector roles per site.
- Weekly, pull new line, expansion and new product announcements at plants in your region.
- Monthly, pull inspection findings on labeling and foreign material at food and pharmaceutical sites.
- Qualify against the four checks, with the capital cycle question first. One message per account, naming the defect class. Fifteen to twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next recall in their category or the next expansion is a fresh reason to write.
The recall notice names the defect and the job board names the cost. The integrators who grow are the ones who write to the plant that week with fifty sample parts as the only ask.
The sending mechanics most people get wrong
Everything above is about who and what. This is about how, and it is where most outbound in this niche quietly dies. Seven rules. None of them are optional.
1.Three to five sentences. That is the whole email.
Your reader is on a phone between meetings. One observable fact about their company, one consequence they have not thought about, one specific thing you would do. Anything past five sentences is a memo, and memos get archived unread.
2.Lead with a technical differentiator that turns into a number.
The messages that work best name something concrete you do differently and translate it into time or money saved. In this niche the differentiator is the false reject rate. An integrator who can say what false reject rate its last dozen installations settled at after ninety days, and how many of those systems are still running, has the only two numbers a plant manager who has been burned before will believe. Say both.
Most services firms do not have a technical differentiator, and pretending to have one reads as exactly that. The substitute is a verticalized case study: a company like theirs, what you did, what happened, in one sentence. For this niche the line is: a beverage co packer with eight open inspector roles, feasibility on fifty sample cans in a week, one station on the seal check installed in six weeks, false rejects under a stated fraction of a percent after tuning, five inspector roles closed. The false reject figure and the roles closed are what the reader will check.
3.Ten to twenty emails a day per mailbox. Not a hundred.
Sender reputation is scored per mailbox and per sending domain. One inbox pushing a hundred cold emails a day looks like exactly what it is, and the penalty lands on the domain, which means it lands on your client correspondence too.
If the math says you need more volume, the answer is more mailboxes on more warmed sending domains, separate from the domain you invoice from. It is never more volume per mailbox. Fifteen to twenty accounts a week at three touches is nine to twelve emails a day, one warmed mailbox. A significant recall in a large category can justify writing to every plant in it that week, which is when the second mailbox is used.
4.Write ten versions of every step and test them.
Versions A through J, not A and B. Rotate subject lines and bodies. You learn which angle is actually working instead of guessing, and there is a second reason that matters more: identical bodies going out over and over is one of the patterns postmaster tools flag. Variation is a deliverability tool as much as a testing one.
Subject line seeds for this niche, each of which should become several variants: "the recall in your category", "the six inspector roles", "the new line's inspection points". Lower case, no punctuation tricks, and nothing that would look odd in a reply from a colleague.
5.Stop at three.
Most replies arrive on the first and second email. The third is already thin. Every touch past that raises the odds the whole thread gets classified as spam, and that classification follows the mailbox to the next person you write to. The long cadence is over. Three touches, each with something new in it, then leave them alone for ninety days.
6.Know what good looks like.
A one percent reply rate with a quarter of those replies positive is a healthy trigger based program. Anyone quoting you double digit reply rates is counting out of office messages or selling a course.
7.LinkedIn Sales Navigator is not optional.
Every other data source tells you who held a title at some point. Sales Navigator tells you who holds it today, because the person maintains it themselves. That is the difference between a three percent bounce rate and a fifteen percent one, and bounces are scored against the mailbox the same way spam complaints are. Verify the name there before anything goes out.
It is also the cheapest trigger detector you will own. The job change filter surfaces people who arrived in a role in the last ninety days, which is the moment they have budget and no incumbent. The posted recently filter surfaces companies talking about the exact problem you solve. Account lists with headcount growth alerts tell you who is scaling before the press release does. For this niche the saved search is headcount 50 to 1,000 in food and beverage, pharmaceutical manufacturing, automotive components, electronics and medical devices, titles Plant Manager, VP Operations, Quality Manager and Controls Engineer, with the job change alert on for plant leadership and a keyword alert on quality inspector, vision engineer and the names of the major vision platforms across job listings. Navigator confirms the person. The recall databases and the plant's own job board are the source.
Use it for the research and the verification, not for the message. InMail reply rates are a fraction of email, and the person who replies to a thoughtful email is the same person who ignores a connection request with a pitch attached. Pull the work email from a data provider once Navigator has confirmed the person is real and current.
None of this is specific to your niche. All of it is specific to whether anyone ever reads the angle you spent an hour getting right.
If you would rather not run it yourself
That is what we do. ExpertLayer runs this exact loop for expert led firms: the weekly recall and job post pull, the qualification with the capital question first, the angle per account naming the defect class, the sending across warmed mailboxes, and the reply reading. You take the conversations and run the feasibility.
The first step is free and it is the same research described above. Send us your website and we will come back with 10 companies that hit these triggers right now, with the recall or hiring wave, the contact, and the opening line for each.
Questions from people running this
Recalls are public, but is writing to a recalled company appropriate?+
A recall notice names a product category, a failure mode and a company that has just learned what an escape costs. A calm note that describes how an inspection system catches that specific defect class is the most useful thing in their inbox that month. The companies to write to with even more care are their competitors, who run the same line and have not had the recall yet.
Rule based or deep learning, which do I lead with?+
Neither by name. Lead with the defect. A cosmetic defect on a variable surface is where learned models earn their keep and where rule based systems produce the false rejects that got vision a bad name on that plant floor. A dimensional or presence check is a rule based problem and always will be. Say which their defect is and the technology follows.
The quality inspector job posts, are they really a signal?+
Six open inspector roles at one plant is not six hiring problems, it is one inspection process that does not scale. The plant manager knows this and has usually already been burned by a vision system that was sold on the camera and failed on the lighting. The job posts are the trigger; the previous failure is the objection.
How do I get past the machine builder that already supplies vision?+
By being about the line, not the machine. The machine builder's vision is tuned at acceptance and drifts with lighting, wear and product changes, and nobody owns it after handover. An integrator who owns the model, the retraining and the false reject rate over time is selling something the machine builder does not.