Convergence Radar Convergence Engine

← Feed

F

MinerCert: MSHA Part 46/48 training-record and 5000-23 certificate compliance SaaS

21/100

A records-first compliance tool that generates, stores, and audit-proofs MSHA Form 5000-23 training certificates for small mine operators and the state grantee trainers who teach them.

Kill. Β· created 2026-07-10 15:14 UTC

saaspublic recordsindustrialcompliancetoo complexrevisit later

Scorecard

newness 3/10
convergence 3/10
demand evidence 3/10
existing spend 4/10
solo feasibility 8/10
speed to mvp 8/10
speed to revenue 3/10
distribution 3/10
competitive gap 2/10
expansion 3/10
founder fit 5/10

Penalty flags
enterprise sales long trust cycle no clear buyer no urgent pain (βˆ’19 from raw 40)

Opportunity brief

What changed
FACT (from source text): DOL-MSHA has posted MINE HEALTH AND SAFETY STATE GRANTS, CFDA 17.600, opportunity MSHA-2026-1, closing 08/10/2026. This is an annual federal pass-through appropriation to state mine-safety agencies that deliver miner training.
Why now
HYPOTHESIS: the 08/10/2026 close date forces ~45 state grantees into an application-and-reporting cycle this summer, and each funded state must document training delivery back to MSHA. The grant posting is FACT; the reporting cadence, the quarterly performance/expenditure reports, and the number of participating states are INFERENCE β€” none of that is stated in the provided source.
Converging signals
Only ONE signal is actually present in the input: the grants.gov posting itself. The 'convergence' framing in the input description is largely self-generated inference. The genuine underlying convergence β€” and it is real but NOT evidenced by this input β€” is that (a) 30 CFR Part 46/48 compels every US mine operator to train miners and certify it, (b) MSHA Form 5000-23 is the certification artifact, and (c) federal money flows through states to deliver that training. I flag that (b) and (c) are asserted from background knowledge, not from the provided source, and must be verified before any build.
Customer pain
HYPOTHESIS (unevidenced by this input): small aggregate/sand-and-gravel operators must produce complete 5000-23 records on demand during an MSHA inspection, and missing or malformed records draw citations. The input contains ZERO pain evidence β€” no complaints, no forum threads, no hiring data. I will not manufacture it.
Who pays
Two candidate buyers, of very different quality. (1) State mine-safety grantees β€” reachable but few (~45 max), publicly procured, slow, and each is a bespoke sale. (2) Mine operators and independent Part 46/48 instructors β€” numerous, self-funding, and already buying training. Buyer (2) is the only one worth chasing; buyer (1) is a government procurement office and should be treated as a poison pill for a solo founder.
Solved today
INFERENCE: paper 5000-23 forms, Excel rosters, generic LMS platforms (Vector Solutions/Convergence Training, Predictive Solutions, KMI), and per-site safety consultants. That an incumbent training-LMS category already exists and already sells to exactly this buyer is the central problem with this idea.
Why current solutions are bad
HYPOTHESIS only: paper certificates are lossy and LMS platforms are priced for multi-site enterprises. I have no source establishing that operators are dissatisfied.
Proposed product
If pursued: a narrow, records-only tool β€” generate a compliant 5000-23 per miner, tie it to an annual-refresher clock, alert on lapse, and produce an inspector-ready packet in one click. Explicitly NOT a training LMS; it sits underneath whoever delivers the training.
MVP version
Certificate generator + miner roster + refresher-due calendar + PDF export packet. Two weeks of work. The hard part is not the software; it is proving the record format and finding the buyer.
30-day build
Do not build. Verify the three load-bearing assumptions: (1) confirm 5000-23 is still the operative artifact and read the current Part 46/48 text; (2) determine whether any record is SUBMITTED to a portal or merely RETAINED on-site β€” this single fact decides whether the business exists; (3) call 15 small operators and 5 independent Part 46 instructors and ask what they pay today.
60-day build
Only if step (2) shows a submission surface, or step (3) shows instructors paying >$50/mo for roster tooling: build the MVP and pilot it free with three instructors who each serve many small mines (instructors are the distribution multiplier, not the mines).
90-day revenue plan
$29-79/mo per instructor or per small operator, sold through the instructor channel. Realistic first revenue is a few hundred dollars per month, not a business, unless the instructor-as-reseller motion works.
Distribution path
Independent Part 46/48 instructors and state grantee training staff as referrers. State mine-safety agency training calendars are public. There is no efficient paid channel to 12,000 scattered mines and this founder avoids ad spend.
Pricing hypothesis
Per-seat subscription to instructors/operators. The input's proposed '$2-5 per-certificate filing fee' is NOT supportable: a filing fee presumes a filing, and I have no evidence a certificate is filed anywhere. Do not price against a submission that may not exist.
Technical difficulty
Low. This is a CRUD app with a PDF generator. Trivial for this founder.
Legal / regulatory risk
Low for the software itself. The founder would not need to become a certified instructor to sell record-keeping tooling, though he must be careful not to imply the tool confers compliance.
Platform dependency
None. No app store, no platform owner, no deplatforming risk.
Founder fit
Genuinely high on the mechanics β€” public records, compliance, industrial operations, mining/scrap adjacency, and a shipped precedent in FMCSA ELDT. But the ELDT analogy is where I must be hardest on this idea. ELDT worked because the Training Provider Registry is a PORTAL that legally requires a submission, which created a per-transaction toll booth. Part 46/48 records are, to my knowledge, RETAINED, not SUBMITTED. Remove the portal and you remove the toll booth, and what remains is an undifferentiated records app competing with established mining-LMS vendors. The founder's edge is portal integration; this opportunity may have no portal.
Breakout potential
Low as scoped. ~12,000 mines is a small, shrinking, consolidating market with entrenched safety vendors. The replication story (50 states) applies to the grantee sale, which is the sale not worth making.
Final recommendation
KILL as specified; salvage only one thing from it. The system's own heuristic β€” 'government-portal mandate opportunities fit this founder best' (confidence 0.80) β€” is being pattern-matched onto an opportunity that lacks the load-bearing element of that pattern: a mandatory submission to a portal. The prior is being applied where its precondition fails. That is the failure mode this lesson makes likely, not a reason to proceed. The one salvageable action is cheap: spend a few hours confirming whether ANY MSHA training artifact is electronically submitted rather than retained. If a submission surface exists, this becomes a genuine ELDT-shaped opportunity and deserves a fresh brief. If it does not β€” which I expect β€” close it and spend the reasoning budget on mandates where the portal is confirmed up front. More broadly: this brief is evidence the ingestion layer is emitting raw grants.gov postings as though a posting alone constitutes convergence. A grant posting establishes that money moves; it does not establish that anyone must file anything. The pipeline should require a named submission surface before promoting a grant into a FedMoney candidate, or briefs like this one will keep consuming reasoning spend.
Next action
Read 30 CFR Part 46.9 and Part 48 recordkeeping provisions and answer exactly one question: is any miner training record electronically submitted to MSHA, or only retained on-site? Do not write code before that answer exists.

Kill arguments (adversarial)

Competitors

β€’ Vector Solutions (Convergence Training) β€” Mining (link) β€” INFERENCE, not from source: established MSHA Part 46/48 training LMS with built-in recordkeeping; sells to the same operators. Verify before proceeding.
β€’ Predictive Solutions / mining safety recordkeeping vendors (link) β€” INFERENCE: incumbent safety-software category serving mine operators. Existence of this category is the primary competitive_gap problem.
β€’ State mine safety agency in-house systems (link) β€” HYPOTHESIS: grantee states funded by CFDA 17.600 may build or already run their own training-tracking systems with grant dollars, making them a competitor rather than a customer.

Source citations (facts)

β€’ MINE HEALTH AND SAFETY STATE GRANTS β€” Mine Safety and Health Administration β€” FACT: DOL-MSHA posted grant opportunity MSHA-2026-1, CFDA 17.600, closing 08/10/2026. This establishes that federal money flows to state mine-safety agencies. It does NOT establish a filer class, a submission portal, a form, a respondent count, or any willingness to pay for software β€” all of which the input's description asserts as inference.

Actions