California Pay Data Reporting Filing Engine

01 Thesis

California Government Code §12999 requires private employers with 100 or more payroll employees (and, separately, those with 100 or more labor contractor employees) who have at least one California employee to file annual pay data reports with the Civil Rights Department (CRD). Verified For Reporting Year 2025, the filing deadline is May 13, 2026 (second Wednesday of May). Verified

SB 464 (chaptered Oct 13, 2025) raised the stakes: upon CRD request, civil penalties are mandatory — up to $100 per employee for a first failure and up to $200 per employee for subsequent failures — and employers must store demographic data separately from personnel files. Beginning January 1, 2027, job categories expand to 23 SOC-based categories. Verified Meanwhile, federal EEO-1 Component 1 faces proposed rescission (EEOC OIRA May 2026), which makes durable state pay-data regimes the compliance center of gravity. Verified (Foley / Seyfarth commentary.)

We sell the outcome, not a DEI dashboard. PayBand Desk ingests payroll, HRIS, and establishment data; maps employees to CRD job categories, pay bands, hours, and race/ethnicity/sex fields; produces portal-ready Excel/CSV packages; runs deterministic completeness and cross-tab checks; and delivers an audit vault the CHRO can defend. A human reviewer clears low-confidence mappings; the employer’s certifying official — who must be employer-authorized — submits on the CRD portal. Verified (CRD User Guide: Excel/CSV upload; authorized certifier.)

This is not a co-pilot. A VP of Total Rewards at an 800-person manufacturer with three CA sites does not want another analytics UI; she wants the filing accepted, the labor-contractor report handled if required, and a vault that survives a CRD inquiry — without betting the company on a spreadsheet hero who leaves in April.

02 Discovery rationale

This run scanned deadline-driven, document-heavy employment-compliance workflows with clear statutory triggers, outsourced precedent, and decomposable data synthesis. Five candidates were scored (§3). California pay data won because: (a) verified statutory duty with a hard annual deadline and now-mandatory civil penalties under SB 464; (b) budget proof — OutSolve, Berkshire Associates, and Trusaic already sell CA/IL/MA pay-data filing support; (c) a clean AI-native shape — HRIS/payroll → normalize → map → validate → package → human review → employer certifies; (d) a durable state moat as federal EEO-1 faces rescission risk while CA intensifies; and (e) a measurable TAM floor from EDD Size of Business data (~25,614 CA establishments with 100+ employees in 2024 Q3). Verified

Rejected this run: Illinois EPRC (strong runner-up, narrower beachhead), VETS-4212 (federal contractor niche), Federal EEO-1 (disqualified on rescission risk), and State BEAD subgrantee reporting (telecom saturation). The decisive asymmetry: the work is rules-bound and spreadsheet-shaped, yet failure now carries per-employee mandatory penalties — exactly where an internal engine plus thin expert review can sell a fixed-price accepted package.

03 Candidate comparison

Five candidates generated this run. Scores are the author’s 1–5 rollup of the screen (§5).

04 Hard disqualifier check

No hard fail. Margin curve and commoditization are Unclear and carried into risks / kill criteria.

05 Rubric scorecard

Gate sum = 26.0 / 30 (avg ≈ 4.33 / 5). Strongest on no physical labor and low trust burden (pay-data filing is already outsourced to OutSolve/Berkshire/Trusaic). Weakest on intelligence threshold — much of the work is structured mapping — and Sam Altman (public templates invite copycats). Durability comes from SB 464 teeth, audit-vault accountability, and multi-establishment / labor-contractor complexity that SaaS leaves on the table.

06 Opportunity

Even a conservative capture of mid-market private employers (100–5,000 EE) at $3k–$6k blended ACV (core + establishment/labor-contractor add-ons) implies a multi-hundred-million serviceable opportunity if a few thousand employers outsource. Inferred The near-term wedge is employers who already buy EEO-1/OFCCP help and now need a CA-specific accepted package with SB 464-aware audit hygiene — especially multi-establishment and staffing-heavy employers who must also file the Labor Contractor Employee Report.

07 Evidence quality & source-claim matrix

Selection rested only on Verified statutory, deadline, penalty, portal, incumbent, and sizing claims. Economics and switching are labeled and routed to the pilot.

08 Why now

Verified shifts

• SB 464 (Oct 2025) converted soft enforcement into mandatory per-employee civil penalties and forced demographic-data segregation — compliance leaders can no longer treat CA pay data as a “nice spreadsheet.” Verified
• RY 2025 deadline May 13, 2026 is the immediate clock for the first commercial season. Verified
• Federal EEO-1 rescission risk (OIRA May 2026) pushes attention and budget toward durable state filings (CA, and later IL/MA). Verified
• 23 SOC categories (2027) create a known mapping rebuild that rewards vendors who own the employer’s prior-year vault. Verified

Inferred capability shifts

Frontier models now reliably normalize messy HRIS/payroll exports, propose job-category and pay-band mappings, and draft exception narratives — the historical bottleneck for mid-market HR teams. Inferred

Unverified hypotheses

That mid-market buyers will pay $2.5k–$4.5k for a DFY package rather than stretch an already-bought DEI SaaS seat; that labor-contractor report add-ons convert at ≥30% of multi-site staffing-heavy accounts. Unverified

09 Customer & PMF

10 The outcome we sell

11 Internal AI engine architecture

Ten layers. AI is internal tooling; the customer buys a service outcome (Dynasty: tooling → service).

12 AI-vs-human operations pipeline

What the human expert actually does

Humans concentrate at exception clearing and release; the employer alone certifies. AI never submits unattended.

13 Operations as product

• SOPs for intake, mapping, labor-contractor join, QA release, certifier briefing, and post-filing vault seal — versioned each handbook update.
• Structured intake checklist with automated completeness halt until required extracts arrive.
• Exception queues with confidence scores; only material items hit the reviewer.
• Demographic segregation controls (access, storage, retention) aligned to SB 464. Verified
• Gold-standard packages per employer size band and multi-establishment pattern.
• Deadline calendar with T-45 / T-21 / T-7 escalations into the May window.
• Root-cause postmortems on every portal rejection or late package — converted to a rule before the next cycle.

14 No-holes quality engine

15 Pricing, pricing legality & unit economics

Model

Primary: per-filing package $2,500–$4,500 for the core Payroll Employee Report (tiered by headcount and establishment count). Add-ons: multi-establishment complexity packs; Labor Contractor Employee Report; rush (<21 days); prior-year remediation. No hourly primary. No contingency on penalties avoided — that would look like penalty insurance and misalign incentives.

Pricing legality

Fixed package fees for compliance preparation are standard. We do not practice law, do not certify for the employer, and do not sell “penalty avoidance” percentages. Engagement letters state that CRD certification is the employer’s act and that we are not providing legal advice on discrimination exposure.

Illustrative COGS / package (steady state) Unverified

Targets: gross margin 55%+ at steady state; revenue/FTE $350k–$600k. Unverified — pilot kill-metrics.

16 Nonlinear scaling plan

Year-two filings reuse prior mappings and vault history — marginal cost collapses while price holds. The 2027 SOC remapping is a forced refresh that rewards incumbency. Inferred

17 Moat & Sam Altman test

Does model improvement strengthen us? Yes on cost: better mapping and exception detection cut reviewer minutes. Score: 4.0.

Commoditization threat: CRD templates are public; DEI SaaS and incumbents can generate files. If we only sold “AI fills the spreadsheet,” we lose.

Real defensibility: (1) accepted-package SLA + audit vault accountability; (2) multi-establishment and labor-contractor playbooks that DIY tools leave messy; (3) SB 464-aware demographic segregation ops; (4) prior-year vault switching cost into the 2027 SOC transition; (5) deadline factory that CHROs trust under mandatory penalties.

18 Go-to-market

Buyer is trust- and deadline-driven. Motion = founder-led outbound + counsel/PEO channel + content demand-trap into the May filing window — not pure PLG.

Distribution proof table

First 30 days content

• Week 1: “RY 2025 CA Pay Data Deadline (May 13, 2026) — Checklist for CHROs” (pillar page).
• Week 2: “SB 464 in plain English: $100/$200 per employee and demographic segregation.”
• Week 3: “Payroll vs Labor Contractor Employee Report — who must file both?”
• Week 4: “2027’s 23 SOC categories — what to fix in your HRIS now.”

Lead magnet / waitlist

Free “CA Pay Data Readiness Scorecard” — upload last year’s file (or a sample extract) → automated gap report (schema, missing fields, establishment coverage, labor-contractor flag) → waitlist for managed filing slots capped for the May cycle. Conversion path: Scorecard → 30-min review → fixed-fee package → optional multi-year retainer.

19 Pilot & early-demand-trap mitigation

20 Competitive landscape

Anti-duplication

Distinct from prior blueprints: not California climate disclosure (SB 253/261 emissions), not federal EEO-1 (disqualified), not generic HRIS analytics, not BEAD telecom reporting. Buyer job = CRD pay data acceptance; trigger = §12999 + May deadline + SB 464; data = payroll/HRIS/demographics; revenue = per-filing package. IL EPRC is an explicit expansion adjacency, not this SKU.

21 Regulation, compliance & licensing boundary

22 Founding team & expert map

23 Exhaustive risk register

24 Tech stack & build plan

25 Metrics & KPIs

26 What could kill this

• Margins never clear 50% because demographic/HRIS mess keeps reviewer minutes high.
• Incumbents productize the same DFY mid-market package faster with existing OFCCP relationships.
• Buyers refuse to pay above thin SaaS export pricing despite SB 464.
• A public filing failure early destroys trust in a reference-driven CHRO market.
• CRD process change (e.g., unexpected portal redesign) that we fail to absorb in-season.
• Legislative rollback of pay-data duties (low probability near-term given SB 464 direction) — monitor.

27 7 / 30 / 90-day plan

28 Sources

• California Civil Rights Department — Pay Data Reporting
• CRD — Pay Data Reporting Technical Guidance / Handbook (PDF; check site for latest)
• CRD — Pay Data Reporting FAQ (§12999 coverage)
• California Legislature — SB 464 bill page
• SB 464 — bill text
• EDD LMID — Size of Business Table 1, 2024 Q3 (xlsx)
• EDD — Size of Business Data landing
• OutSolve — pay data / EEO compliance services (incumbent)
• Berkshire Associates — affirmative action & pay data support (incumbent)
• Trusaic — pay equity & pay data reporting (incumbent)
• Foley & Lardner — EEO-1 / OFCCP commentary hub (rescission risk context)
• Seyfarth Shaw — EEO-1 / pay data client alerts (rescission risk context)
• EEOC — EEO data collections (federal Component 1 context)
• OIRA / Reginfo — federal rulemaking review portal (EEOC May 2026 context)

§12999 coverage, RY 2025 May 13 2026 deadline, SB 464 penalty/segregation/SOC23 provisions, CRD Excel/CSV portal + authorized certifier rules, EDD 25,614 establishments 100+, incumbent vendors, and federal EEO-1 rescission-risk commentary are labeled Verified from the sources above (research run 2026-07-09). Package pricing, COGS, margins, reviewer-minute compression, switching rates, and bottom-up unique-employer TAM are Inferred or Unverified and must be validated in pilots. This is a hard-to-fool blueprint, not a guarantee. Brand: PayBand Desk. Slug: california-pay-data-reporting-filing-engine.