ReclassRush
Upload a 1099 contractor roster, score every worker against the DOL two-core-factor test, and walk out with a defensible documentation package and a retroactive-tax-exposure number per worker.
An HR or finance lead at a company with a large contractor pool is about to be told that a federal rule changed and a chunk of their 1099 workforce may now be employees. The honest way to answer is a worker-by-worker legal review — which means an employment-law firm billing by the hour against hundreds of names, on a clock set by a regulator. There is no tool that does this in bulk, so the choice today is a five- or six-figure legal engagement or hoping the rule slips.
The HR, payroll, or finance lead at a company carrying a large 1099 contractor pool — the person who owns worker classification and personally absorbs the cost and risk when the rule changes. The budget line already exists: it is the employment-law spend that a manual reclassification would otherwise consume.
A named, dated forcing function: DOL NPRM published in the Federal Register Feb 27 2026, comment period closed April 28 2026, final rule expected Fall 2026 (Ogletree-confirmed) — about as crisp as a temporal window gets.
The two-core-factor test did not exist until the Feb 2026 NPRM, and the signal confirms no bulk-reclassification product at any tier — the window is opening exactly now.
Six connections spanning four runs plus two cross-references — the strongest multi-run echo in this batch — but lower than the marquee ideas, hence a mid score.
The standout is timing: a named, dated, imminent federal forcing function (DOL NPRM in the Federal Register, comment period closed, final rule expected Fall 2026) paired with a confirmed-vacant category — no competing bulk-workflow product was found at any tier. The tension is real and productive: the rule demands mass reclassification while case-by-case legal review structurally cannot scale, and bulk scoring with defensible documentation is the resolution.
Two things pull the score down. The buyer persona is the softest part of the entry — the origin angle names a 'developer / technical team' while the actual buyer is HR, payroll, or finance, and no company size or budget figure is given to anchor willingness-to-pay. And the core promise — 'defensible documentation' produced by an LLM — is legally untested, which puts a malpractice-adjacent liability surface right at the center of the product.
Genesis doesn't invent in isolation — ReclassRush shares architecture with, or powers, these ideas.
Discussion
No comments yet — be the first to weigh in.