What changed
FACT (Jackson Lewis, cited): Colorado enacted a mandate requiring employers to file state EEO-1-style workforce demographic data reports with the state, explicitly decoupled from — and surviving — any wind-down of federal EEO-1 collection. INFERENCE (must verify in bill text): headcount threshold, first reporting cycle date, and the receiving agency/portal (likely CDLE) are not named in the captured text.
Why now
The federal EEO-1 apparatus is in flux; Colorado's rule creates a NEW state-level filer class with no established filing habit, no incumbent state-specific tooling, and a first-cycle scramble. First reporting cycles are when compliance vendors get bought — before habits and vendor relationships form.
Converging signals
Three signals meet at one point: (1) a new state rule compelling action, (2) a defined filer class (Colorado employers over the headcount threshold), (3) a required recurring submission assembled from HRIS/payroll data — workforce counts by job category, race/ethnicity, sex. This is the exact forced-filer convergence shape, and it matches the system's high-confidence lesson that government-portal mandate opportunities are this founder's best fit.
Customer pain
HR at a 100-800 person Colorado employer must map messy payroll/HRIS job titles into report categories, reconcile race/ethnicity/sex data with gaps, and file on a new state form on a new deadline. Companies that never filed federal EEO-1 (if the state threshold is lower) have never done this at all. The pain is classification, validation, and deadline certainty — not the upload click itself.
Who pays
(a) Colorado employers over the threshold — the compelled class; (b) higher-leverage: PEOs, payroll bureaus, and CPA/HR-consulting firms who must produce this report for dozens or hundreds of Colorado clients and will pay for multi-entity tooling; (c) employment-law firms white-labeling a prep tool for clients.
Solved today
For federal EEO-1: HR does it by hand from HRIS exports, or pays consultants (Trusaic, Berkshire, DCI Consulting bill for pay-data/EEO reporting, e.g., California SB 973 analog), or relies on partial HRIS report modules. For the new Colorado report specifically: nothing exists yet — HYPOTHESIS: the state will provide a bare portal or spreadsheet template, as California did, and the assembly work will land on employers.
Why current solutions are bad
HRIS 'EEO reports' are federal-format, frequently mis-mapped, and won't match a new state schema at launch; consultants charge $2k–10k+ per entity per cycle; manual assembly risks misclassification in a report filed with a regulator. Multi-client filers (PEOs/CPAs) have no batch tool at all for a brand-new state format.
Proposed product
A Colorado EEO-report engine: upload any Gusto/ADP/Paychex/CSV export → AI-assisted mapping of job titles to report job categories (human-confirmable) → validation against the state schema (counts reconcile, no missing cells, threshold logic) → output the exact state filing (file-ready format or direct portal submission if the portal permits automation, mirroring the founder's FMCSA ELDT per-upload model). Multi-entity workspace for PEOs/CPAs.
MVP version
Single-entity web app: CSV upload, column mapper, title→category classifier with review UI, validation report, and a state-format output file. No portal automation in v1 — verify the portal's mechanics first. Buildable solo in weeks with AI-assisted development; founder has shipped this exact pattern before.
30-day build
(1) Pull the actual bill + any CDLE rulemaking: confirm threshold, categories, first deadline, portal mechanics, penalties — this kills or confirms everything marked inference. (2) Build the classifier/validator core against the published schema. (3) Land 3 design partners via Colorado SHRM chapters and 2–3 Denver PEOs; offer free first filing for feedback.
60-day build
Ship the paid single-entity product ($249–499/entity/year). Publish the definitive 'Colorado EEO reporting: who must file, what, when' guide targeting the search demand every employment-law alert is creating. Open the multi-entity tier to PEOs/CPAs ($99–149/entity at volume).
90-day revenue plan
Convert design partners, run outreach to the ~50 largest Colorado-serving PEOs/payroll bureaus and CPA firms with HR practices. 20 direct entities + 2 PEO accounts at 25 entities each ≈ $12–20k ARR seeded; revenue timing ultimately keyed to the first filing deadline (unverified) — if the deadline is >180 days out, sell early-bird annual prep now.
Distribution path
Deadline-driven SEO (new mandates generate high-intent search with zero competition), Colorado SHRM chapters, direct outreach to PEOs/payroll bureaus/CPAs (one deal = many entities), and partnership/referral with employment-law firms already publishing alerts (Jackson Lewis-style firms advise but don't build tools).
Pricing hypothesis
$249–499 per entity per filing year direct; $99–149/entity/year at PEO/CPA volume; optional $150 'validated + reviewed' add-on. Undercuts consultant fees by 10x while charging enough to fund support.
Technical difficulty
Low-moderate: CSV normalization, a title→category classifier (LLM-assisted with human confirmation), rules-based validation, document/format generation. Portal automation is the only unknown and is optional for v1. Squarely inside founder's proven ELDT skill set.
Legal / regulatory risk
Low for the founder: he is a software vendor, not a filer, and needs no license. Standard care: accuracy disclaimers, customer attests to final submission, handle demographic data with proper security (sensitive PII — encrypt, retain minimally). Not legal advice — output is the customer's filing.
Platform dependency
None that can deplatform him. The state controls the format and could ship an unexpectedly good free portal that absorbs the assembly work (HYPOTHESIS, the real dependency risk); payroll CSV formats are stable and public.
Founder fit
Maximal and structural: this is the FMCSA ELDT playbook re-run — read a mandate, identify the compelled filer class, build the classification/validation/submission layer, charge per filing, with a multi-client tier. Matches the system's 0.79-confidence lesson on government-portal mandates and the founder's public-records/compliance strengths. No relationship selling; the deadline sells.
Breakout potential
High: the cited article itself frames Colorado as the template if federal EEO-1 ends — each adopting state is a near-identical replication (new schema, same engine), the California pay-data precedent shows states do this, and the multi-state version becomes the tool PEOs/CPAs standardize on. Also composts into a general 'state workforce-report engine.'
Final recommendation
PURSUE, gated on one day of verification. The forced-filer shape, founder fit, and replication path are all present; every load-bearing unknown (threshold, deadline, portal, schema complexity) lives in one bill text and one rulemaking docket. If the schema is nontrivial and the first deadline is within ~12 months, this is a top-decile fit — build immediately and own the first cycle.
Next action
Retrieve the actual Colorado bill text and any CDLE implementation guidance today: confirm (1) headcount threshold, (2) exact data schema, (3) first reporting deadline, (4) filing mechanism/portal, (5) penalties for non-filing. Simultaneously read the full Jackson Lewis alert (the RSS link) for the bill number.