A self-serve tool for safety budget justification sounds obvious. The reasons it hasn't scaled yet are worth understanding.
There's a conversation that happens in manufacturing plants across the US, probably weekly. An EHS director walks into a budget meeting with a proposal to replace a PPE program with an engineering control. The CFO asks what the ROI is. The EHS director has a spreadsheet. The CFO has a golf trip. The proposal gets deferred.
This is not a niche problem. It's structural. And the fact that nobody has built a clean, self-serve tool to solve it is either a massive opportunity or a warning sign that people have tried and quietly given up.
I think it's both.
EHS professionals are trained to think in terms of hazard hierarchies, exposure limits, and compliance requirements. CFOs think in payback periods and risk-adjusted NPV. These are not naturally compatible languages, and nobody has built a good translation layer.
The existing options are ugly. OSHA publishes a free calculator. The NSC publishes injury cost tables. A motivated EHS director can manually pull numbers from the Liberty Mutual Workplace Safety Index, build a spreadsheet, format it, and pray the finance team doesn't challenge the assumptions. This takes days. Most EHS directors don't have days. And even when they do it, the output looks like a spreadsheet, not a business case.
The frustration is documented. G2 reviews of Intelex explicitly mention having no way to quantify incident costs for budget pitches. Cority users on Capterra say the same thing. There's a recurring thread in r/EHS where practitioners debate how to justify engineering controls to management who just want to buy more PPE. This isn't manufactured demand. It's a chronic, documented pain point with a clear villain (the persuasion gap) and a clear victim (the EHS director who knows the right answer but can't get funded).
The pitch for "why now" leans on rising insurance costs, supply chain transparency demands, and better cost-benchmark datasets. These are real forces. Commercial insurance lines have been hardening since the 2017 CAT losses, and workers comp carriers are increasingly scrutinizing safety programs during underwriting.
But here's the problem with this argument: insurance costs have been rising for seven years, and EHS ROI tools still haven't scaled. That's not nothing. It suggests the demand signal is chronic but the willingness-to-pay conversion is structurally low. Rising insurance costs make safety investments more justifiable, but they don't automatically create EHS directors with corporate credit cards and procurement authority.
The more honest "why now" is probably AI-assisted data retrieval. An LLM with RAG over the OSHA inspection citation database could let a user describe a hazard in plain English and get back relevant penalty ranges, applicable standards, and historical cost data automatically. That's a genuine improvement over manually cross-referencing three federal databases. It's not a revolution. It's a meaningful time savings that makes a $99/month price point defensible.
There are roughly 50,000 US manufacturing facilities with 100-500 employees, per BLS data. About 15% of those have a dedicated EHS role that actually needs budget justification tooling. That's around 7,500 addressable buyers. At $150-300 per year average, you're looking at a TAM of $1.1-2.2M for the narrow version of this product.
That's small. Bootstrappable-to-profitability small. Not venture-scale small, but potentially a very healthy indie hacker business if you can keep CAC low. The organic channel math is interesting: posting a free Google Sheets ROI template in r/EHS (35K members) costs nothing and could generate real validated demand in days. At 88% gross margins and a break-even of 17 customers at $99/month, the numbers work at a very modest scale.
Broader EHS analytics is a $200-500M SAM per Verdantix estimates, but you're not capturing that with a budget justification tool. You'd need to expand into incident tracking, compliance management, and reporting to access those dollars, which puts you in direct competition with Intelex and Cority.
No YC-funded company appears to directly address this gap. Intelex, Cority, and Enablon are all compliance and incident tracking platforms. They log what happened. They don't help you make the financial case for preventing it from happening.
There's a structural reason for this gap that I find compelling: EHS software incumbents are incentivized to sell PPE management modules. A tool that helps customers justify replacing PPE with engineering controls cannibalizes their own product line. They will not build this. That's a permanent wedge, not a temporary one.
Consultancies like DEKRA and NSC offer ROI frameworks, but they're project-based engagements at consulting rates. A self-serve tool at $99/month is a different category.
The genuine competition risk isn't the incumbents. It's free. OSHA could update their calculator. A large EHS content creator could publish a polished spreadsheet template. ASSP or AIHA could build a member benefit version. Any of these would compete at zero cost and destroy the value proposition for solo users.
There are two structural problems with this idea that I don't think can be fully engineered away.
The first is the attribution problem. The EHS director uses the tool. They build a beautiful one-page CFO-ready PDF. They present it. The CFO still says no. The EHS director blames the tool, cancels the subscription, and tells their colleagues it doesn't work. The tool may have been completely accurate. The analysis may have been correct. But if budget approval is the success metric users have in their heads, and the tool has no control over whether the CFO is actually persuadable, retention is structurally fragile. You're selling a persuasion tool to someone who isn't the person being persuaded.
The second problem is legal exposure. If a manufacturer uses your NPV output to defer an engineering control, an incident occurs, and plaintiff's counsel subpoenas the scenario report showing the company calculated the financial tradeoff and chose the cheaper option anyway, your tool's output becomes evidence of willful negligence. No disclaimer fully neutralizes this. It changes how lawyers frame the case. Before any commercial deployment, you need product liability insurance (budget $5K-15K/year) and actual legal review, not just a terms-of-service checkbox.
The tech stack is straightforward. Next.js, Supabase, Stripe, PDF generation via Puppeteer or react-pdf, deployed on Vercel. A solo developer with Cursor or Lovable could have an MVP in 5-7 weeks. The hard part isn't the code.
The hard part is the data. The value proposition depends entirely on the benchmarked incident cost library being credible. This means sourcing exclusively from publicly citable sources: the OSHA penalty database, NSC injury cost tables, Liberty Mutual Workplace Safety Index. Every number in every output needs an inline citation. Finance teams will challenge the assumptions, and the product has to survive that challenge or it's useless.
The AI layer is the most interesting build decision. Using a RAG system over the OSHA inspection citation database to let users describe a hazard in plain English and auto-populate cost parameters is genuinely useful and technically achievable. As users complete scenarios and (if you can get them to do it) tag whether the budget was approved or rejected, you accumulate a training dataset that makes the tool smarter over time. That's a real moat if the user base reaches meaningful scale.
The scenario builder core is simple: hazard category, workforce size, incident frequency estimate, proposed control cost. Output: risk-adjusted NPV, payback period, 3-year cost comparison chart. One-page PDF formatted for a slide deck. That's the aha moment. The user sees a chart they can drop into PowerPoint in under 5 minutes. That's what they're paying for.
Before writing a line of code, build the Google Sheets version and post it free in r/EHS. Watch what happens. DM 20 EHS directors on LinkedIn who have posted about budget frustrations and offer the template in exchange for a 20-minute call. If you can get 5 people to say they'd pay $99/month AND 2 of them actually put down a refundable Stripe deposit, you have enough signal to build.
If you can't get 2 Stripe deposits from a free template giveaway in the most targeted community imaginable, the structural willingness-to-pay problem is probably real and you should know that before spending 7 weeks building.
This idea makes most sense for someone with a background in EHS, manufacturing operations, or industrial insurance. The credibility gap is real. An EHS director who has actually sat in those budget meetings and lost them would build a very different product than a developer who read the OSHA documentation and built a form.
If you have that background and you've personally felt the frustration of watching a safety proposal die because you couldn't speak CFO, this might be the right problem for you. The market is small but real. The competition isn't trying to eat your lunch. The risks are manageable if you're careful about legal exposure from the start.
If you're just looking for an underserved niche with decent unit economics, be honest with yourself about whether you can get past the attribution problem. You're building a tool for someone who will blame you when their boss says no.