Who actually signs
At a hardware company between ten and two hundred people, the signer is the VP of engineering, the head of mechanical, or the CTO. There is a strong mechanical designer who lives in the CAD tool and has run its built in solver on a few parts. There is no simulation engineer, and the job post for one has been open since spring.
The champion is whoever is about to sign the tooling purchase order, because that is the irreversible decision and it is usually on the calendar. At larger companies with an analysis group, the buyer is the program manager whose project cannot get time on the internal queue.
The one sentence version
Your buyer is a mechanical lead with a design they trust, a tooling quote on their desk, and no way to know whether the enclosure will hold the heat.
The triggers, and where each one is visible
- Thermal, mechanical and simulation engineer job posts. A company advertising for a thermal engineer has a thermal problem now. A posting that names a simulation package is a company that wants a capability it has priced and cannot yet staff. Both are public and dated.
- Hardware funding rounds. Seed and Series A at companies building compute hardware, battery systems, power electronics, robotics, drones, medical devices and dense consumer products fund the design that needs analysis before tooling. Form D filings and the usual databases surface them.
- Recalls for overheating, fire or structural failure. Consumer product and vehicle recall databases are public and dated, and a recall in a category is a signal about every competitor's design in that category.
- Product launches at higher power density. AI accelerator boards, liquid cooled servers, fast charging, high output LED, compact power tools. A launch announcement that names a higher power figure than the previous generation is a thermal margin question.
- Design for manufacturing and tooling milestones. Companies announcing a contract manufacturer, a production partner or a factory build have a tooling date, and the simulation window closes before it.
- Patent publications for mechanical and thermal designs. A published application for a heat sink, an enclosure or a mounting system is a company that has invested in the design and is about to build it.
The thermal engineer job post is the one to build on. It is a company stating, in public, that it has the exact problem you solve and no one to solve it. Every day the req stays open is a day the design moves toward tooling without analysis.
Qualify in sixty seconds
- Is there power in a box? Anything that dissipates real wattage in an enclosure, or anything that gets dropped, vibrated or loaded, is in scope. A pure software company with a reference design from a chip vendor is not.
- Is there a simulation engineer on the team? Team page and job posts. A senior mechanical designer is not the same person, and they will say so.
- Where is the design relative to tooling? Before is the sale. After is a respin conversation, which is real but smaller and later.
- Is there funding or revenue to pay for it? A funded hardware startup or a product company with a shipping line. A pre seed team with a prototype is a future prospect.
The angle that gets replies
Lead with the tooling decision and the cost of getting it wrong. The reader knows what a tool costs and what a respin costs. They may not have connected either number to the analysis they are skipping.
Three openers you can adapt
- On a thermal engineer job post"Saw the thermal engineer posting. If the enclosure design is close to tooling, the analysis cannot wait for the hire, and the question that matters most before the tool is cut is whether the hot component has a path to the outside at the ambient you are specifying. That is a ten day study on your current CAD. Happy to scope it against the actual model."
- On a hardware Series A with a production partner announced"Congratulations on the round and the manufacturing partner. Between now and first tooling is the only window where a thermal or drop finding costs a design change rather than a respin. Most teams at this stage run the CAD tool's solver on a few parts and call it done. One page on what a full conjugate run catches that a part level run does not, attached."
- On a recall in their category"A competitor's product in your category was recalled last month for a thermal issue in the enclosure. Your design shares the form factor and the power class. A transient thermal run on the enclosure at the recall's stated conditions would show in about a week whether the same failure mode is present. No charge to scope it."
Each one names a physical question about their product, attaches a duration, and offers the smallest useful thing. It reads as an engineer writing to an engineer.
What not to send
- Software vendor language. "Multiphysics capabilities" and "advanced simulation solutions" describe a licence, not a finding. The reader does not want capabilities, they want to know if the box will hold the heat.
- A list of solvers and packages. Naming the tools you run is a resume. Naming what you found on a product like theirs is a credential.
- "We can simulate anything." So can the software. The value is knowing which run to do and which result to distrust, and that sentence says the opposite.
- Generic quality or reliability framing. If the email could be sent to any manufacturer, it does not know which product the reader is building.
The objection you will hit
Our CAD tool has simulation built in. It does, and it is good for a first pass on a single part. It is not the tool for a conjugate heat transfer run with real boundary conditions, radiation, and a mesh you have checked for independence, and its results on an assembly are the kind that look plausible and are wrong by a margin that matters. Do not argue with the tool. Offer to run the same geometry independently and compare. The comparison sells the engagement.
The second is we will test it physically. The test finds the failure. The simulation finds the fix, and it finds it before the prototype cycle time, which for a machined enclosure is weeks. Testing without analysis is a plan to discover the problem at the most expensive moment.
The third is we are hiring for this. The search takes four to six months. The tooling date is closer than that. The study is the bridge, and the hire will thank you for the report when they arrive.
Deal shape
- Scoped study on a single product, thermal or structural: commonly $8K to $30K, turned in ten to twenty business days.
- Design phase support through tooling, several studies plus iteration: $30K to $100K over two to four months.
- Retainer for a company with multiple products in flight: $5K to $15K a month.
- Failure investigation after a field issue or recall: $15K to $50K, closing in days.
- Signer: VP Engineering, head of mechanical or CTO. Cycle: two to six weeks, tied to design gates, and days after a failure.
The scoped study is the funnel. It is priced so a VP of engineering can approve it without a finance conversation, and it produces a report with a finding in it, which is what turns a skeptical mechanical lead into a repeat client.
A cadence you can actually run
- Weekly, pull thermal, mechanical and simulation engineer job posts, and note which name a simulation package.
- Weekly, pull hardware funding and manufacturing partner announcements, and check each company's product page for a power figure.
- Weekly, pull recall databases for thermal and structural failures in the product categories you serve.
- Qualify against the four checks, with the tooling position first. One message per account, naming the physical question. Fifteen to twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next product announcement or the next req is a fresh reason to write.
The company announces its production partner on its own blog. The consultants who grow are the ones who write that week, while the tooling quote is still a quote.
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 turnaround and prediction. A consultancy that can say it delivers a scoped thermal study in ten business days, and that its predicted junction temperature on the last dozen products landed within a stated margin of the measured value, has two numbers the large engineering firms will not put in an email.
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 25 person edge compute company, thermal study run in nine days before tooling, enclosure vent geometry changed, measured device temperature on the first production unit within a few degrees of the prediction, no respin. The day count and the prediction accuracy 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. Hardware funding clusters in a few months of the year, and those are the months to consider a second mailbox.
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 thermal engineer posting", "before first tooling", "the recall in your category". 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 10 to 200 in hardware, consumer electronics, robotics, energy storage, power electronics and medical devices, titles VP Engineering, Head of Mechanical Engineering, CTO and Program Manager, with the job change alert on for engineering leadership and a keyword alert on thermal engineer, simulation and the major simulation packages across job listings. Navigator confirms the person. The job boards and the recall databases 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 req, funding and recall pull, the qualification with the tooling question first, the angle per account naming the physical question, the sending across warmed mailboxes, and the reply reading. You take the conversations and run the analysis.
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 req or announcement, the contact, and the opening line for each.
Questions from people running this
Most hardware teams think they can run simulation themselves. Are they wrong?+
For a first pass in the CAD tool's built in solver, no. For the run that decides whether to cut tooling, usually yes. The difference is boundary conditions, mesh independence and knowing which answer to distrust, and that experience is what the client is buying. Do not argue that they cannot simulate. Argue that the tooling decision deserves a second, independent run.
Thermal or structural, which sells better?+
Thermal, by a distance, in the current market. Power density in everything from AI hardware to battery packs to compact consumer devices has gone up faster than the engineers designing enclosures have adjusted, and a thermal margin problem is invisible until the product throttles or fails in a customer's hands. Structural sells on drop and vibration, and it sells after a field failure more often than before one.
How do I compete with the big engineering services firms?+
Speed and specificity. They quote in weeks and staff in months. A boutique that can turn a scoped thermal study in ten days, on the client's actual CAD, before the tooling decision, is doing something the large firm cannot price. Say the turnaround time in the first email.
Is a recall a good trigger or a tasteless one?+
A recall for overheating or a structural failure is a company that has just learned, expensively, what simulation is for. Write to them the way you would want to be written to: a calm note that describes what the analysis would have shown and what it would show now, with no reference to the headline. Then write to their competitors, who have the same design and no recall yet.