Who actually buys a near-miss tracker first?

The idea behind Near-Miss & Chronic Exposure Tracker is genuinely interesting to me. Not because EHS software is sexy, but because the core insight is real: the stuff that almost goes wrong, and the slow-burn symptoms workers notice but never write down, almost never make it into any system. A fogged face shield. A brief glove breach. That weird headache you get every Tuesday when you're on the line with the solvent tanks. Nobody files a report for any of that. And then six years later someone has occupational asthma.

So the problem is real. The question is whether you can actually sell the solution to the first ten people who need it.

the customer isn't who you think they are

The idea names EHS managers, site supervisors, and occupational health nurses as the target. That's right, but it's incomplete in a way that will cost you deals. In a 100-person food processing plant, the EHS manager doesn't buy software. Operations does, or finance does, and they think of EHS as a cost center that generates paperwork. You can have the best 30-minute demo of your dashboard with an EHS manager, get genuine enthusiasm, and then watch the deal die when it goes to their boss who just bought a new conveyor belt and has no budget.

This isn't a knock on the idea. It's just the reality you have to build the go-to-market around from day one. The first ten customers need to come from EHS managers who either have budget autonomy or who have a recent incident on their record that has made their operations leadership scared. A near-miss tracker is a much easier sell the week after someone almost lost a hand.

the actual outreach strategy

The idea's first-customer plan is to find 30 food processing plants on Google Maps, look for mixed reviews mentioning safety, find the EHS manager on LinkedIn, and send a 3-sentence DM offering a free 60-day pilot. That's not bad. I'd tweak a few things.

Three-star reviews mentioning "safety" are a decent proxy for sites with recent problems, but the signal is noisy. A better filter is OSHA's inspection database, which is public. You can look up facilities that received a citation in the last 18 months, find the EHS manager on LinkedIn, and reference their actual situation in the outreach. "I saw you had a citation in March related to chemical PPE compliance. I'm running free pilots of a near-miss tracking tool for sites trying to get ahead of that pattern." That's not three sentences. It's more like five. But it converts at a completely different rate because it's specific.

For the Reddit play, r/EHS is real and the community there is surprisingly active. But don't post a Loom of a prototype. Post a question. Ask what happens to near-miss reports that don't meet the threshold for formal incident filing. Ask how many workers actually use the reporting system. Let them tell you the problem exists. Then show up in the comments with the prototype. The difference between those two approaches is whether you seem like a vendor or a person who did their homework.

the liability conversation you will have in every single sales call

Here's the thing I keep coming back to with this idea. The liability concern is not FUD. It is a real, rational objection that any EHS manager with a competent legal team will raise immediately. A database of documented near-miss clusters, especially ones linked to specific chemicals, tasks, and locations, is discoverable in litigation. If a worker later files a personal injury claim and their attorney subpoenas your customer's data, your customer is now worse off than if they had no system at all.

The idea has an answer to this, which is to position the tool under OSHA's Voluntary Protection Programs framework and prepare legal language templates for rollout. That's the right move. But you need to do that work before your second sales call, not your tenth. Get an EHS attorney to write a one-page brief on the legal posture of this kind of tool. It doesn't have to be expensive. Offer a mention in your case studies. But walk into every demo with that document ready to share, because the objection is coming and "we've thought about this" is not the same as "here's the attorney-reviewed framework we built around it."

who your actual first ten customers are

Realistically, the first ten paying customers look like this:

• 3 come from LinkedIn outbound to EHS managers at plants that had a recent OSHA citation or a safety incident that made the news locally. These are people with urgency.
• 2 come from referrals from those 3. EHS managers in food processing often know each other, especially in regional clusters like the Midwest. One good pilot with visible results turns into a warm intro.
• 2 come from Reddit or the ASSP community, probably people who are new to an EHS role at a smaller plant and don't have the budget for SafetyCulture. $99/month is approachable for them.
• 2 come from occupational health nurses, who are a wildly underutilized entry point. They actually want this data. They're often frustrated by how little signal they get before things escalate. They're also sometimes unionized or affiliated with a union structure, which matters for the worker trust problem.
• 1 is a wild card. Someone who finds the product through a food safety conference or FSPCA network and becomes an early evangelist because it solves something they've been complaining about for years.

the thing that could kill the whole pilot

Worker adoption is the actual product. Not the dashboard. The dashboard is useless if workers don't report anything, and workers won't report anything if they don't trust that the anonymization is real. This is not a UX problem. It's an organizational trust problem, and you cannot solve it with better onboarding copy.

The most honest version of the go-to-market is this: target unionized plants first. It sounds counterintuitive because sales cycles are longer and there's more stakeholder management. But union reps who co-endorse the tool before launch are the only credible trust signal that can move a workforce that has every rational reason to be skeptical of an app deployed by management. Get two or three union-backed pilot sites with real adoption numbers and you have a story. Without it, you're hoping workers trust a thing that management told them to trust, and that is a long shot in a 60% annual-turnover food processing plant.