What to Put in an OEM Inquiry

Why the First Message Sets the Pace

We reply to inquiries within two business days. Whether that first reply is worth anything, though, depends almost entirely on what arrived.

Some messages can go straight to an engineer. Others take four or five rounds just to establish what the product is, and a fair number of those go quiet somewhere around the third round. Not because anyone lost interest. Because answering “what would this cost” without knowing what “this” is turns into a guessing exercise, and everyone can feel it.

The difference is rarely the size of the project or the size of the company. It is whether the first message says what you are actually building.

The Five Things That Carry Most of the Weight

1. What the product is, the object rather than the category

“A medical device” narrows nothing. “A negative pressure wound vacuum pump” narrows almost everything: there is a pump, there is electronics, there is a housing that has to seal, and there is a regulatory path attached to all three.

You do not need a spec sheet. One sentence describing the object is enough to get an engineer reading instead of a salesperson filing.

2. What stage you are at

Concept, design in progress, ready for production, or moving from another supplier. These four open completely different conversations.

Concept stage is not a disadvantage, and it is worth saying plainly because a lot of people sit on an idea for months assuming they need finished drawings first. They do not. An early conversation is often cheaper than a late one, because the decisions that cost the most to reverse (how the housing splits, where the board sits, which certification path you are committing to) are made early whether or not anyone discusses them.

What actually stalls a project is not being early. It is nobody being able to say what the thing is.

3. Which processes you need

Injection molding, electronics assembly, both, or something you are not sure about yet. If you know the product needs a moulded enclosure and a populated board, saying so removes an entire round of questions.

If you are not sure which processes your product implies, that is itself a useful thing to say. It tells us the conversation should start at the design end rather than the quotation end.

4. Which markets you are selling into

This one gets skipped more than any other, and it changes more than most people expect. The target market decides the certification path, and the certification path decides both the timeline and a meaningful share of the cost. A product for the EU, a product for the US, and a product for both are three different projects wearing the same housing.

“Europe first, US later if it works” is a perfectly good answer. It is far better than silence, because silence gets read as “domestic only” and the quote comes back built on that.

5. Roughly what annual volume

A range is fine. An order of magnitude is fine. Volume is what turns a tooling discussion from theory into numbers: how many cavities, which grade of steel, whether the tool pays for itself or stays a fixed cost you carry.

If you genuinely do not know yet, say that. It is a normal answer at concept stage.

→ How volume becomes cavity count and piece price: Tooling Cost and MOQ Explained for OEM Projects

The Boxes You Cannot Fill In Yet

None of the above is an entrance exam, and treating it as one produces the worst possible version of a first message: a set of confident-sounding numbers that somebody invented to look prepared.

A named blank travels faster than a guessed number. “We have not settled on annual volume” costs one line. A guessed volume, on the other hand, quietly reshapes the entire quote around the wrong assumption, and the correction tends to surface after tooling has already been discussed. That is an expensive round trip for a number nobody actually had.

The same applies to markets, timelines, and target price. Say what you know, name what you do not, and the reply comes back scoped to reality rather than to a fiction both sides have to unwind later.

The one thing genuinely hard to work with is a message where the product itself is undefined. Being early is fine. Being vague on the numbers is fine. A message with no object in it at all is the hard case. If that is where you are, ask about feasibility rather than for a quotation, and asking directly gets you further than asking for a price that cannot exist yet.

Why We Ask for These Five

It is fair to want to know what the questions are for, so: our first stage is a positioning step, before anyone draws anything. What the product is, who it is for, which markets it ships to, what annual volume it is planned around. Those four answers are what every later decision leans on.

Cavity count comes from volume. Material selection comes from the product and its market. The certification path comes from the market. The tooling budget comes from all of it at once. A quote built without those inputs can only be a range wide enough to be useless, and a wide range is not a kindness to anyone. It defers the real conversation by a month.

→ Where these decisions go wrong when they are made in the wrong order: Where OEM Product Development Goes Wrong

What a Workable First Message Looks Like

Short is fine. This is roughly the shape:

We are developing a countertop UV-C appliance for home use, currently at concept stage. It needs an injection moulded enclosure and a populated board with a UV-C module. Selling into the EU first, likely the US later. Planning around 20,000 to 30,000 units a year, though that is an estimate. We do not have drawings yet, only industrial design sketches.

Five lines. Nothing confidential in it, no drawings attached, and one number openly flagged as an estimate. That is enough to route it to the right engineer, identify the certification questions worth raising in the first reply, and say something honest about tooling.

Note what it does not do: it does not ask for a catalogue, and it does not ask for a price list. Those requests are the ones hardest to answer usefully, because a catalogue answers a question about existing products and a price list answers a question about existing parts, while what is being described here is neither.

→ If you are still deciding whether you need OEM or ODM: OEM vs ODM: MOQ, Tooling, IP and Timeline

What Comes Back

An NDA before technical discussion, if the project warrants one. A reply from an engineer who will actually work on the project rather than a summary relayed through an account manager. And a first response within two business days.

What that reply contains depends on what arrived, which is the whole point of this page. With the five items above, it can address the real questions: whether the processes fit under one roof, which certification path the target markets imply, and where the tooling conversation should start.

Without them, the honest reply is a set of questions, which is also fine. It just takes two weeks longer than it needed to.