Who actually signs
At an e-mobility, energy storage, drone, power tool or consumer electronics company between ten and two hundred people, the signer is the VP of engineering, the CTO, or the head of quality. There is an electrical engineer who designed or selected the pack, a mechanical engineer who designed the enclosure, and a BMS the founder chose from a supplier's catalog. Nobody has read the test standard the retailer is about to ask for.
For stationary storage projects the buyer shifts to the project developer or the EPC, and the person with the deadline is whoever has to satisfy the fire marshal. That is a different conversation with the same laboratory behind it.
The one sentence version
Your buyer is an engineering lead with a pack that works on the bench, a certificate from the cell supplier that covers something else, and a retailer, a city or a fire marshal asking for a report they do not have.
The triggers, and where each one is visible
- Recalls for battery fires. The consumer product safety recall database is public, dated, and names the product category. A recall in a category is a certification failure and a signal about every competitor's pack in that category.
- City and state e-mobility ordinances. New York City has required certification for e-bikes and their batteries sold in the city since 2023, and other jurisdictions have followed. An ordinance is a deadline for every seller in that market, and the sellers are findable.
- Energy storage project announcements. Developers, utilities and commercial customers announce storage installations, and each one has to satisfy the fire code and the authority having jurisdiction, which means large scale fire testing and a listing. The announcement is public and the developer is named.
- Funding at e-mobility, storage, drone and power tool companies. The round funds the product that needs the report. Form D filings and the usual databases surface them, and the product page says whether the pack is in house or sourced.
- Battery and test engineer job posts. A company advertising for a battery test engineer has a testing program it cannot yet staff. A company naming a specific standard in the description has been asked for the report by a customer.
- Crowdfunded and pre order products with lithium packs. A campaign page with a delivery month is a company that has committed to a transport test and a market certification on a timeline nobody on the team has estimated.
The ordinances and the recalls are the two to build on. An ordinance names the market and the date. A recall names the category and the failure mode. Between them they describe the seller's problem in the seller's own words.
Qualify in sixty seconds
- Is there a lithium pack in the product, and is it theirs? A company that designs the pack or integrates cells with its own BMS owns the certification. A company that buys a finished, certified pack for its intended market has a smaller problem, if the certificate is real.
- Which markets and which channels? A city with an ordinance, a retailer with a requirement, a storage project with a fire code, or transport by air. Each one names a specific test.
- Is there in house test capability? Almost never below a few hundred people. A company with a cycler and a chamber is a different conversation about accreditation and correlation.
- Is the trigger inside ninety days? A funding round from two years ago is a company that has shipped or found a lab.
The angle that gets replies
Lead with the specific report the specific gatekeeper is going to ask for. The reader knows their product. They usually do not know that the city, the retailer and the freight forwarder each want a different document.
Three openers you can adapt
- On an e-bike launch into a city with an ordinance"Congratulations on the launch. Selling into New York requires the battery and the system to hold the specific certification the city names, and retailers there check the mark on the pack. If the cell supplier's certificate is what you have, it almost certainly covers a different configuration. The gap is usually a pack level test of about eight weeks. Happy to scope it against your BMS and enclosure."
- On a storage project announcement"Saw the storage project announced with the county. The authority having jurisdiction will want the large scale fire test results for that enclosure before permitting, and the current fire code sets the spacing and the suppression from those results. If the results are for a different cabinet than the one you are installing, that is the schedule risk. One page on what the fire marshal asks for first."
- On a recall in their category"A competitor's scooter battery was recalled last month for a thermal event during charging. The failure mode named in the notice is one the abuse test sequence is designed to catch, and your pack shares the cell format. A targeted run of that sequence on a sample pack is about two weeks. No charge to scope."
Each one names the gatekeeper, the document, and a duration. That is what makes it useful rather than alarming.
What not to send
- "Battery certification services" as the subject or the opener. Every lab has that page. The reader has a specific gatekeeper and a specific product, and the email should know which.
- Fire imagery or fear. The reader has seen the videos. A note from a stranger that leads with them is a note from a stranger.
- Confusing the standards. Naming the wrong standard for the product or the market is the fastest way to be dismissed by an engineer who has just spent a week reading the right one.
- "We test everything." The value is knowing which sequence the gatekeeper wants and running only that one, on time.
The objection you will hit
Our cell supplier has certifications. The cell certificate covers the cell. The pack, with its BMS, its interconnects, its enclosure and its charger, is a different device, and the retailer, the city and the transport regulation all ask about the pack. Offer to check whether the supplier's document covers the pack as built. It rarely does, and the check is short.
The second is we will certify at the end. A pack that fails an abuse test at the end is a redesign of the BMS, the enclosure or the cell selection, which is three to six months. The design review before the sample build is a fraction of that, and it predicts the result.
The third is the certification costs more than we will make on the first run.Sometimes true, and the honest answer is to say so and help them source a pack that already holds the mark for their market. A consultant who says that has a client for the second product.
Deal shape
- Design review of the pack, BMS and enclosure against the target standard: commonly $5K to $15K. The engagement that opens most relationships and predicts the test result.
- Transport testing: $3K to $10K, and required before the first unit ships by air or sea.
- Light electric vehicle pack and system certification: $30K to $80K, and the mark the city ordinances and the retailers look for.
- Electric vehicle pack certification: $100K and up.
- Large scale fire testing for stationary storage: $50K to $150K, and the document the fire marshal permits against.
- Cell characterization and cycle life studies for supplier qualification: $10K to $50K.
- Signer: VP Engineering, CTO or head of quality, and the project developer for storage. Cycle: three to eight weeks for products, longer for storage projects, and days after a recall.
The design review is the funnel. It is priced so an engineering lead approves it alone, and it produces a written list of what will fail the sequence, which is the redesign and the test program.
A cadence you can actually run
- Weekly, pull recalls in the battery powered categories you serve, and note the failure mode named in each notice.
- Weekly, pull funding and product launches at e-mobility, storage, drone and power tool companies, and check each product page for the pack source.
- Weekly, pull storage project announcements and note the developer and the jurisdiction.
- Monthly, review new and pending e-mobility ordinances and the sellers in each market.
- Qualify against the four checks, with the gatekeeper question first. One message per account, naming the document. Fifteen to twenty accounts a week is a full program.
- Three touches over two weeks, then stop. The next product, the next project or the next recall is a fresh reason to write.
The city has published the rule and the retailer has published the requirement. The labs that grow are the ones that write to the seller before the freight forwarder asks for the transport report.
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 first pass rate against a named standard. A lab or consultant that can say what fraction of the packs it reviewed before sample build passed the abuse sequence on the first attempt has the only number that moves an engineering lead. The second is turnaround: state the calendar weeks from sample receipt to report for the standard the reader's market requires.
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 20 person e-scooter company, design review before sample build, BMS overcurrent threshold changed, pack and system certification obtained on the first sequence in seven weeks, on shelves in New York the month the retailer required the mark. The week count and the single sequence 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 recall wave or a new ordinance can justify writing to every seller in a market in the same week, and that is when the second mailbox earns its keep.
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 New York requirement", "the fire marshal's first question", "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 e-mobility, energy storage, drones, power tools and consumer electronics, titles VP Engineering, CTO, Head of Quality, Battery Engineer and Project Developer, with the job change alert on for engineering leadership and a keyword alert on battery test engineer and the standard names across job listings. Navigator confirms the person. The recall database, the ordinances and the project announcements 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, funding and project pull, the qualification with the gatekeeper question first, the angle per account naming the document, the sending across warmed mailboxes, and the reply reading. You take the conversations and run the tests.
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, ordinance or project, the contact, and the opening line for each.
Questions from people running this
E-mobility or stationary storage?+
They are different practices with different buyers and it is worth choosing. E-mobility is many small companies, fast cycles, and a product safety regime driven by city ordinances and retailer requirements. Stationary storage is fewer, larger projects driven by fire codes, utility interconnection and the authority having jurisdiction. A lab can do both. A prospecting program should pick one to lead with.
Is the transport test really a trigger?+
It is the one obligation nobody escapes. Every lithium battery that ships by air or sea needs the transport test, it is required before the first unit moves, and a surprising number of startups discover it from a freight forwarder the week before launch. A note that names it to a company with a public ship date is both new and urgent.
How do I handle companies sourcing packs from overseas with certificates attached?+
Carefully and honestly. Some of those certificates are real, some are for a different configuration, and some are not what they claim. The offer is not to doubt their supplier. It is to verify that the certificate covers the pack as built, with their BMS and their enclosure, which it often does not.
The certification cost is more than some of my prospects' entire budget. What then?+
Then say so early and save everyone the time. For a small e-bike importer, a full pack certification may not clear against volume. The honest alternative is sourcing a pack that already holds the certification for the intended market, and a consultant who helps them find one has earned the next engagement.