FINAL DECISION: BLUEPRINT

AccrualTrue Clear — The Multi-State Paid Sick Leave Accrual Reconciliation & Remediation Desk

AI-Native Business Blueprint Factory · Run timestamp 2026-07-24-0613 UTC · Slug: accrualtrue-clear-multistate-sick-leave-accrual-desk

Executive Summary

AccrualTrue Clear is a done-for-you compliance desk that audits, corrects, and continuously monitors how a multi-state employer's payroll system actually accrues, caps, carries over, and pays out paid sick leave (PSL) against the specific rules of every state, city, and county where its employees legally work — including remote employees whose home jurisdiction is frequently missed entirely. The business does not sell HR software the buyer must configure and operate. It sells a quantified, audit-ready outcome: a Sick Leave Accrual Variance Report that tells a VP of People or Controller, in dollars, exactly which employees are under-accrued or over-accrued sick time relative to the law that actually governs their worksite, followed by a remediation ledger, corrected policy language reviewed by employment counsel, and an ongoing quarterly re-audit as headcount, locations, and statutes change.

The wedge is narrow and evidence-backed. Twenty-two states plus Washington, D.C. now mandate paid sick leave, and more than twenty cities and counties — concentrated in California but also New York City, Chicago, and others — layer distinct, more generous accrual formulas on top (TriNet, 2026). California's Paid Sick Leave Law is now enforceable under the Private Attorneys General Act following Wood v. Kaiser Foundation Hospitals (Feb. 24, 2023), which opened per-employee, per-pay-period penalty stacking (Workplace Legal PC, 2026). New York City's Earned Safe and Sick Time Act expanded again on February 22, 2026, simultaneously raising paid-leave tiers to 40/56 hours, stacking 32 hours of new unpaid leave on top, and — critically — handing the city's Department of Labor the power to place liens, issue bank-account warrants, and shut down non-compliant businesses, while the Department of Consumer and Worker Protection now mines CDC sick-leave-usage data to proactively flag employers whose employees appear to be under-using leave they are entitled to (HelpNewYork.com, 2026). A 2026 settlement against Alco Harvesting/Bonipak Produce for unpaid sick leave and related wage violations totaled $6.175 million across more than 10,000 workers (CSLEA, 2026). This is no longer a theoretical exposure; it is an active, growing enforcement environment with real settlement history.

Existing budget already flows toward adjacent problems: multi-state HR compliance platforms such as Mosey price flat-fee tiers from $399 to $1,999 per month scaled by the number of states covered, and SixFifty, GovDocs, and PEOs (TriNet, Justworks) all sell adjacent policy-template and registration services. None of them audit whether the payroll system's actual per-employee accrual math is correct against the applicable jurisdiction's formula, and none quantify historical shortfall dollars owed — which is exactly the gap between a compliance software subscription and an actual PAGA claim or DOL wage order. AccrualTrue Clear sells the gap-closing outcome, not another dashboard.

The final decision for this run is Blueprint. The candidate clears the evidence threshold on a specific and painful problem, verified active enforcement and settlement history, an identifiable and reachable buyer, existing adjacent budget, a credible narrow MVP wedge (a one-time Variance Report diagnostic), and a defensible path to 50%+ gross margin once the accrual rules engine and jurisdiction-classification logic are built once and reused across clients.

Thesis

Regulatory complexity that changes faster than any single company's internal HR/payroll team can track, combined with enforcement mechanisms that are becoming proactive rather than complaint-driven (NYC's CDC-data-triggered investigations being the clearest 2026 example), creates a permanent, recurring, dollar-quantifiable compliance gap at exactly the layer most payroll systems are worst at: per-jurisdiction accrual math applied consistently across every pay period, every employee, every location change, and every legislative update. This gap is small enough per employee (a few hours of sick time, a capped dollar payout) that no single violation looks like it justifies hiring a compliance attorney at $300–600/hour to check — and large enough in aggregate, once PAGA-style penalty stacking or a state DOL audit applies, to produce seven-figure exposure. That asymmetry is the business: continuously monitored, AI-accelerated, human-expert-reviewed accrual reconciliation is cheap to deliver at scale and expensive for the buyer to ignore.

Discovery Rationale

This run began by reading the full 789-entry run history in manifest.json and the repository's flat file listing of prior blueprints and no-go memos. The manifest confirms a very heavy prior concentration (200+ entries) in regulatory-filing "completeness/documentation" desks, and the most recent no-go memo in the manifest (adjacent-terrain-candidate-sweep-15, run 2026-07-24T04:16:00Z) explicitly flags that ten of twelve freshly-researched candidates that run were already duplicates on disk, and recommends several unexplored HR/benefits niches "beyond COBRA/ACA/FMLA/401(k)" as productive next terrain, specifically naming multi-state paid-sick-leave accrual-bank reconciliation as a candidate not yet built.

Following that lead, this run independently generated and keyword-checked five candidates against the manifest (freight cargo-claim recovery, franchisor FDD renewal compliance, staffing-agency I-9/E-Verify audit defense, solar/grid interconnection processing, and multi-state paid sick leave accrual reconciliation). The first four were confirmed duplicates by direct manifest and filename match (see Anti-Duplication Analysis and Candidate Comparison below); the fifth — paid sick leave accrual reconciliation — returned zero matches for "sick leave," "accrual," "PTO bank," or "leave bank" across all 789 prior run titles/slugs and zero matching filenames on disk, and is materially distinct from the two existing leave-of-absence case-administration engines already in the manifest (see Anti-Duplication Analysis). Fresh 2026 research then confirmed active enforcement, a real settlement, and existing adjacent budget, clearing the evidence threshold.

Candidate Comparison

Five candidates were generated from fresh research this run. Four were eliminated immediately on duplicate detection against the 789-entry manifest and the repository's existing blueprint/no-go files before any further research time was spent on them; the fifth was carried forward for full evidence development.

Candidate	Sector	Status this run	Reason
Freight cargo-claim recovery desk for SMB/mid-market shippers	Logistics	Rejected — duplicate	Manifest already contains Freight Cargo Claim Recovery Engine (no-go, 2026-07-10) and a later freight-claims-recovery-desk blueprint (2026-07-13), plus adjacent Carrier Detention & Accessorial Recovery Desk, Duty Drawback Recovery Engine, and two 2026-07-20/23 freight-broker/3PL desks.
Franchisor FDD annual renewal & multi-state registration compliance desk	Franchise	Rejected — duplicate	Manifest contains FDD Renewal & Multi-State Registration Engine (blueprint, 2026-07-02), matched twice under different slug variants.
Staffing-agency I-9/E-Verify worksite-audit defense desk	HR / Staffing	Rejected — duplicate	Manifest contains I-9 & E-Verify Compliance & Worksite-Audit Defense Engine (blueprint, 2026-06-30).
Community solar / grid interconnection application processing desk	Energy	Rejected — duplicate	Manifest contains at least five overlapping entries: Grid Interconnection Portfolio Compliance Engine, DER Interconnection Restudy Prevention Engine, Solar & Storage Beginning-of-Construction Evidence Desk, SunQueue Clear (interconnection/PTO desk), and CreditTrue Clear (community solar subscriber billing desk), the most recent dated hours before this run.
Multi-state paid sick leave accrual reconciliation & remediation desk	HR / Payroll compliance	Selected — cleared duplicate check and evidence threshold	Zero manifest or filename matches for "sick leave," "accrual," "PTO bank," or "leave bank"; distinct workflow and buyer motion from the manifest's existing FMLA/ADA/PFML leave-case-administration desks (which process individual leave requests, not ongoing accrual-balance math across payroll systems).

CODE Validation

Consumer/Buyer Trend

Paid sick leave law coverage keeps expanding and getting stricter rather than consolidating: 22 states plus D.C. now have statewide paid sick leave laws, more than 20 additional cities/counties (concentrated in California, plus New York City, Chicago, and others) layer distinct and often more generous rules on top, and in 2026 NYC's Earned Safe and Sick Time Act was expanded again — adding an entirely new 32-hour unpaid leave bank and materially strengthening the city's collection powers (TriNet 2026; HelpNewYork.com 2026). Eighteen states have separately passed laws preempting their own cities from creating new local paid-leave ordinances, meaning complexity is concentrating, not spreading evenly (Truthout, 2026) — which makes the handful of permissive, complex states (led by California and New York) the highest-value markets for a compliance desk rather than a diffuse fifty-state problem.

Opportunity

The specific underserved problem: payroll systems and PEOs configure paid-sick-leave accrual rules once, generally using the state-level default, and rarely revisit that configuration when a company opens a new location, hires a remote employee in a new city, or a jurisdiction updates its accrual formula, cap, or carryover rule. The result is silent, compounding accrual error that is invisible until an employee complains, a state agency audits, or (in California) a single aggrieved employee files a PAGA claim that can sweep in penalties for every other affected employee (Workplace Legal PC, 2026).

Demand

Demand evidence is not merely a rising trend line; it is active enforcement. The Alco Harvesting/Bonipak Produce settlement ($6.175 million, more than 10,000 workers, sick-leave-notice and related wage violations, resolved 2026) shows real dollar consequences (CSLEA, 2026). Wood v. Kaiser Foundation Hospitals (Feb. 24, 2023) is widely cited by employment counsel as having opened the door to PAGA claims specifically for California Paid Sick Leave Law violations, with per-employee-per-pay-period penalty stacking (Workplace Legal PC, 2026). NYC's DCWP now proactively mines CDC sick-leave-usage data to flag employers for investigation without waiting for a complaint (HelpNewYork.com, 2026) — a structural shift from reactive to proactive enforcement that materially raises the value of getting ahead of the problem. Existing multi-state HR compliance vendors (Mosey, SixFifty, GovDocs) sell adjacent policy-and-registration subscriptions priced from $399 to $1,999+/month, which is direct evidence that mid-market employers already allocate recurring budget to multi-state HR compliance — just not yet to accrual-math auditing specifically.

Economic Sizing

The U.S. Census Bureau and SBA Office of Advocacy do not publish a clean count of "multi-state employers," so this figure is Inferred, not Verified. The SBA's 2025 Small Business Profile counts more than 36 million U.S. small businesses in total (SBA Office of Advocacy, 2025), the overwhelming majority single-location. The relevant addressable segment here is narrower and higher-value: mid-market employers (roughly 75–1,000 W-2 employees) operating across three or more states or a mix of states and PSL-active cities, who run payroll through a PEO or mid-market HRIS. A conservative, explicitly uncertain estimate is tens of thousands of such employers nationally once remote-first companies (whose employees are geographically scattered by default) are included — a segment that has grown structurally since 2020 and is exactly the group most likely to have accrual-classification blind spots for remote hires. At a blended $9,000–$25,000 first-year contract value (initial audit/remediation project plus annual monitoring retainer, see Pricing below), even a low single-digit-percent share of a low-five-figure-count addressable segment supports a multi-million-dollar service business, well before any expansion into adjacent leave-of-absence, wage-statement, or multi-state new-hire classification services.

Six-Gate Rubric Scorecard

Gate	Score (1-5)	Rationale
1. Low Trust Burden	5	Payroll compliance audits are already routinely outsourced to PEOs, payroll vendors, and employment counsel; the buyer cares about the corrected balance and the audit-ready documentation, not the mechanics of how the reconciliation was computed. An employment-counsel-reviewed human interface preserves trust for anything employee-facing.
2. Low Task-Level Judgment	4	Jurisdiction classification, accrual-formula application, and variance calculation are highly decomposable, rule-based, and automatable; judgment is required only at defined exception points (ambiguous work-location data, conflicting local/state preemption, and any communication framed as "back pay owed").
3. High Intelligence Threshold	4	Correctly synthesizing a payroll export, a remote-employee roster, a written policy, and 40+ distinct and frequently-updated jurisdictional formulas into a single per-employee variance figure is exactly the kind of multi-document, multi-rule synthesis frontier models materially improve at handling faster and more consistently than a manual HR generalist.
4. Regulation as Moat	5	The entire service exists because of statutory complexity, PAGA exposure, and newly aggressive municipal enforcement (NYC lien/bank-warrant powers); this discourages casual entrants and increases willingness to pay for a defensible, documented process.
5. No Physical Labor	5	Entirely document-, data-, and workflow-based; fully deliverable remotely from payroll exports and policy documents.
6. Sam Altman Test	4	As frontier models improve at long-context multi-document reasoning and structured extraction, the accuracy and speed of jurisdiction classification and variance detection improve directly; the rules engine and jurisdiction database are the durable, compounding asset, not the underlying model.

Anti-commoditization note: if a future general-purpose model becomes capable enough that a buyer could plausibly ask it directly "does my sick leave policy comply," the defensible remainder is threefold: (1) the maintained, versioned jurisdiction rules database mapped to real payroll-export formats, which requires ongoing curation as ~40+ jurisdictions independently amend their laws; (2) the actual per-employee variance computation against a client's real, messy payroll data (not a hypothetical policy question); and (3) the employment-counsel review and audit-ready documentation trail that a generic chatbot answer cannot provide and that is precisely what a PAGA plaintiff's attorney or a state DOL investigator will ask to see.

Target Buyer

Primary buyer / champion: VP of People, Head of HR, or HR Director at a 75–1,000-employee company operating across three or more states (or two states plus a PSL-active city), typically without a dedicated in-house payroll-compliance or wage-and-hour specialist.

Economic approver: CFO or Controller, especially at companies without a standalone HR budget line, who ultimately signs off on new compliance spend and cares about quantified liability exposure.

Secondary/referral buyer: outside employment counsel and fractional HR consultants who identify the accrual-math gap during a broader wage-and-hour engagement but do not want to build and maintain a 40-jurisdiction rules engine themselves, and PEOs/HRIS vendors who want a specialist partner to refer accrual-audit findings to rather than own the liability of "fixing" a client's historical shortfall themselves.

Jobs-to-be-Done

"When we open an office in a new state or hire our first remote employee in a new city, help me know immediately whether our current sick-leave accrual setup is still compliant there, without me having to research the law myself."
"When our payroll vendor or PEO says a policy is 'handled,' give me independent, documented proof it is actually computing accrual correctly for every employee in every jurisdiction — not just a policy template."
"When I get an employee complaint, a state agency inquiry, or a renewal question from our EPLI insurance broker about sick-leave compliance, I need an audit-ready packet I can hand over immediately, not a scramble."
"When we've been getting it wrong, quantify exactly what we owe, help us fix it quietly and correctly before it becomes a claim, and make sure it doesn't happen again."

The Painful Problem

Multi-state employers configure paid-sick-leave accrual once inside a payroll system or PEO platform, generally at the state level, and then effectively never re-verify it. But the real governing rule is set at the most specific jurisdiction that applies to each individual employee's actual worksite (or remote home address), and that rule set includes accrual rate, annual/rolling cap, carryover-versus-front-load election, waiting periods, minimum increments of use, and rate-of-pay calculation for payout — each of which can differ from the state default in a city or county ordinance. HR teams do not have the bandwidth to manually re-derive this for every employee, every location change, and every year's legislative update across 40+ independently-amending jurisdictions, and payroll vendors are not liable for getting the underlying legal classification right — only for correctly executing whatever configuration the employer selected. The result is compounding, invisible accrual error that surfaces only when an employee complains, a state agency investigates, or — increasingly, per NYC's 2026 enforcement expansion — a regulator proactively flags the company using its own usage data (HelpNewYork.com, 2026).

The Outcome We Sell

A quantified, employment-counsel-reviewed, audit-ready statement of exactly where a client's paid-sick-leave accrual math is wrong today, what it is costing them in unpaid balances and enforcement exposure, a remediation plan and corrected policy language to fix it, and a standing quarterly re-audit so the same gap does not silently reopen as the company grows, moves, or the law changes. The client receives a decision-ready packet and a corrected number, not a dashboard, software seat, or generic policy template they must interpret themselves.

First One-Feature MVP Wedge

Element	Definition
ICP	75–300 employee multi-state employer with at least one California and one New York City work-location or remote employee (the two highest-complexity, highest-enforcement jurisdictions).
Trigger event	New office/location opens, first remote hire in a new city, an employee complaint, a state/city agency inquiry letter, or an EPLI/D&O insurance renewal requiring a compliance attestation.
Pain	HR has no reliable, current answer to "is our sick-leave accrual math actually correct for every employee, in every jurisdiction, right now" — only a policy document and a hope that payroll configured it right.
One-feature MVP	The Sick Leave Accrual Variance Report: a one-time diagnostic scan of the trailing 12 months of payroll accrual data against the applicable jurisdiction rules for every employee.
Input	Payroll accrual ledger export (CSV/Excel), employee roster with work location and remote-employee home address, and the company's current written PSL policy/handbook section.
Output	A PDF Variance Report ranking every employee/jurisdiction pair with a shortfall or overage, quantified in dollars and hours, flagged by PAGA/DOL exposure severity.
Human chokepoint	Licensed employment counsel reviews every finding before it is characterized to the client as "owed" or "at risk," and signs off on any remediation language before it reaches an employee.
Success metric	Client receives a defensible, counsel-reviewed dollar exposure number within 5 business days of submitting data, with zero employee-facing communication sent without counsel sign-off.
What they ask for next	"Fix it for us" (remediation execution + payroll/PEO reconfiguration support), then "keep it correct" (quarterly monitoring retainer), then multi-state new-hire jurisdiction classification as a standing intake service.

Evidence Summary

Twenty-four targeted searches and source fetches were performed this run across regulatory trackers, employment-law publications, enforcement news, and existing compliance-vendor pricing pages. Core findings: 22 states + D.C. have statewide paid sick leave laws and 20+ cities/counties layer distinct rules on top (Verified, TriNet 2026); California PSL violations are now PAGA-actionable with per-employee-per-pay-period penalty stacking following Wood v. Kaiser Foundation Hospitals (Verified, Workplace Legal PC 2026); NYC's ESSTA expanded again in Feb. 2026 with materially stronger, proactive enforcement powers including bank-account warrants and CDC-usage-data-triggered investigations (Verified, HelpNewYork.com 2026); a 2026 $6.175M settlement establishes real financial consequence for sick-leave and related wage-notice violations (Verified, CSLEA 2026); and existing multi-state HR compliance vendors already charge $399–$1,999+/month for adjacent (non-accrual-audit) compliance services, evidencing real, allocated budget in this buyer's stack (Verified, Mosey 2026 pricing page). The precise count of multi-state mid-market employers nationally is Inferred, not Verified, given no single published Census/SBA figure isolates this segment; the blueprint is explicit about that uncertainty rather than asserting a false-precision TAM.

Claim Table (Verified / Inferred / Unverified)

Claim	Label	Source	Type	Date	Confidence	Where Used
22 states + D.C. have statewide paid sick leave laws; 20+ cities/counties (mostly CA) layer distinct rules on top	Verified	TriNet — The Definitive List of States and Cities with Paid Sick Leave Laws (2026)	Industry publication	2026	High	CODE / Market evidence
California PSL violations are PAGA-actionable with per-employee-per-pay-period penalty stacking (Wood v. Kaiser Foundation Hospitals, Feb. 24, 2023)	Verified	Workplace Legal PC — PAGA Liability for Paid Sick Leave Violations	Law firm publication	2026	High	Regulatory / Demand evidence
NYC ESSTA expanded Feb. 22, 2026: new 40/56-hour paid tiers, +32 unpaid-hour bank, NYSDOL lien/bank-warrant/stop-work powers, DCWP uses CDC usage data to proactively flag employers	Verified	HelpNewYork.com — NYC ESSTA Expansion: The 32 New Hours, Stronger Wage-Theft Collection	News/legal explainer	2026	High	Demand / Regulatory evidence
2026 settlement: Alco Harvesting/Bonipak Produce, $6.175M, 10,000+ workers, sick-leave notice and wage violations	Verified	California Statewide Law Enforcement Association — Company to Pay $6 Million for Paid Sick Leave and Wage Violations	Trade association news	Feb 2026	High	Demand / Risk evidence
Mosey prices multi-state HR compliance software $399–$1,999+/month flat-fee, tiered by state coverage	Verified	Mosey — Pricing page	Vendor pricing page	2026	High	Competitor & budget validation
18 states have laws preempting their own cities from enacting new local paid-leave ordinances, concentrating complexity in a smaller set of permissive states	Verified	Truthout — 18 States Now Have Laws Blocking Cities From Enacting Paid Leave Standards	News	2026	Medium-High	CODE / market terrain
18 total distinct examples cited: SF (40-72 hrs), LA (48 hrs), Oakland (40-72 hrs), Chicago (1hr/40 worked, capped 40), NYC (40-56 hrs) all differ from state minimums	Verified	TriNet — Definitive List of States and Cities with Paid Sick Leave Laws	Industry publication	2026	High	Problem / workflow design
More than 36 million small businesses exist in the U.S. nationally (broad denominator, not multi-state-specific)	Verified	SBA Office of Advocacy — 2025 Small Business Profile	Federal agency report	2025	High	Economic sizing (background denominator)
Precise count of multi-state mid-market (75-1,000 employee) employers nationally	Inferred	No single published Census/SBA figure isolates this segment; estimate derived from firm-size distribution and structural rise of remote-first hiring since 2020	Analyst inference	2026	Medium	Economic sizing
Existing payroll-vendor/PEO accrual misconfiguration is the leading root cause of shortfalls (vs. willful non-compliance)	Inferred	Reasoned from PSL violation settlement patterns (notice/accrual errors, not outright refusal) and vendor liability structure (vendors execute configuration, not legal classification)	Analyst inference	2026	Medium	Problem framing / AI-native advantage

Source-Claim Matrix

Claim	Label	Source (linked)	Type	Date	Confidence	Section Used
22 states + D.C. have statewide PSL laws; 20+ cities/counties layer distinct rules	Verified	TriNet: Definitive List of States and Cities with Paid Sick Leave Laws	Industry publication	2026	High	CODE / Market evidence
Wood v. Kaiser Foundation Hospitals opened PAGA liability for CA PSL violations; per-employee/per-pay-period penalty stacking	Verified	Workplace Legal PC: PAGA Liability for Paid Sick Leave Violations	Law firm publication	2026	High	Regulatory / Demand evidence
NYC ESSTA expanded Feb 22 2026; NYSDOL lien/bank-warrant/stop-work powers; DCWP uses CDC data to flag employers proactively	Verified	HelpNewYork.com: NYC ESSTA Expansion	News/legal explainer	2026	High	Demand / Regulatory evidence
$6.175M settlement, 10,000+ workers, sick leave notice and wage violations (Alco Harvesting/Bonipak Produce)	Verified	CSLEA: Company to Pay $6 Million for Paid Sick Leave and Wage Violations	Trade association news	Feb 2026	High	Demand / Risk evidence
Mosey multi-state HR compliance pricing: $399-$1,999+/month, tiered by state coverage	Verified	Mosey: Pricing	Vendor pricing page	2026	High	Competitor & budget validation
18 states preempt their own cities from new local paid-leave ordinances	Verified	Truthout: 18 States Now Have Laws Blocking Cities From Enacting Paid Leave Standards	News	2026	Medium-High	CODE / market terrain
City examples with distinct accrual rules exceeding state minimums (SF, LA, Oakland, Chicago, NYC)	Verified	TriNet: Definitive List of States and Cities with Paid Sick Leave Laws	Industry publication	2026	High	Problem / workflow design
36M+ small businesses exist in the U.S. (background denominator)	Verified	SBA Office of Advocacy: 2025 Small Business Profile	Federal agency report	2025	High	Economic sizing (background)
US LTL freight market ~$118.68B 2026 (context/methodology cross-check on market-sizing discipline, not used as this candidate's TAM)	Verified	Mordor Intelligence: United States LTL Market	Market research	2026	High	Methodology cross-check only
Precise national count of multi-state 75-1,000-employee employers	Inferred	No single published Census/SBA source isolates this segment (analyst estimate)	Analyst inference	2026	Medium	Economic sizing

Market and Demand Evidence

22 + D.C.

states with statewide paid sick leave laws

20+

additional cities/counties with distinct, often stricter, rules

$6.175M

2026 settlement for sick-leave/wage violations, 10,000+ workers

$399–$1,999+/mo

existing multi-state HR compliance software budget (Mosey)

88 hrs

combined paid+unpaid NYC sick/safe leave for large employers post Feb. 2026 expansion

18 states

preempt local ordinances, concentrating complexity in fewer, higher-value jurisdictions

The demand signal here is structural rather than sentiment-based: statutes keep expanding (NYC Feb. 2026), enforcement keeps getting teeth (NYSDOL lien/bank-warrant powers, CA PAGA exposure), and enforcement is shifting from complaint-driven to proactive (NYC DCWP mining CDC usage data). Buyers are not being asked whether they want to solve this; increasingly they are being investigated whether they asked for it or not.

Active Buyer Conversations

Public evidence of buyer-side attention takes the form of a dense, continuously-updated 2026 explainer ecosystem published by payroll/HR vendors and law firms for HR buyers: Rippling, Paycor, Paylocity, ADP-affiliated SBS, GovDocs, and Inova Payroll all published dedicated "2026 paid sick leave laws by state" guides this year, and employment law firms (Ogletree, Workplace Legal PC, AMG Law) published dedicated 2026 explainers on PAGA exposure and state-specific noncompliance costs. This volume of vendor- and law-firm-authored guidance is itself demand evidence: HR buyers are searching for and consuming this content in volume, which is exactly the content-led wedge this business's GTM plan (below) is built to intercept.

Competitive Landscape

Multi-state HR compliance software (self-serve): Mosey ($399–$1,999+/month, tiered by state count, includes registration and handbook generation but not per-employee accrual-math auditing), SixFifty, GovDocs. These are software the buyer must operate; none reconcile actual payroll accrual balances against jurisdiction rules or quantify historical shortfall dollars.

PEOs: TriNet, Justworks, and similar bundle standard multi-state policy templates into their service fee but do not proactively audit whether a specific employee's accrual balance, given their specific work location and tenure, matches the applicable formula — their liability model covers execution of the client's chosen configuration, not verification of its legal correctness against every jurisdiction.

Payroll vendors: Gusto, Rippling, ADP Workforce Now, and Paylocity build generic multi-state PSL policy engines into their platforms, but correct configuration and location-data accuracy remain the employer's responsibility — and misconfiguration or stale location data is the most common root cause of the shortfalls this service is built to find.

Employment law firms: conduct wage-and-hour compliance audits, typically billed hourly at $300–$600/hour, which is expensive, slow, and not designed as a recurring monitoring service — a natural referral partner and escalation path for this desk rather than a direct competitor for the recurring audit product.

Competitor and Budget Validation

Buyers already allocate real, recurring budget to adjacent problems: Mosey's public pricing ($399–$1,999+/month) is direct evidence that mid-market HR teams pay meaningfully for multi-state compliance tooling, and PEO and payroll vendor fees already embed a compliance-template component buyers accept as a cost of doing business across state lines. This is not a "no competitors" market — it is a market with adjacent, well-funded incumbents whose products stop exactly at the point where AccrualTrue Clear's product starts: none of them independently verify that the actual, per-employee accrual balance in the payroll ledger matches what the specific governing jurisdiction's formula requires, and none of them quantify and remediate historical shortfalls. The service is not a clone of Mosey/SixFifty/GovDocs software, nor of a law firm's hourly audit; it occupies the gap between "we bought compliance software" and "we know our numbers are actually right," priced and delivered as an outcome rather than a seat license or an hourly retainer.

Pricing Evidence and Proposed Pricing

Pricing precedent from adjacent markets: Mosey's flat-fee, state-coverage-tiered software runs $399–$1,999+/month; employment law firm hourly audits run $300–$600/hour (Verified vendor pricing pages and industry norms; hourly comparator cited for contrast only — this business does not bill hourly). PAGA settlement/exposure figures in the low millions for mid-size workforces (Verified, CSLEA 2026) establish the scale of avoided-liability value the service can credibly price against.

Proposed pricing (outcome/unit-based, never hourly):

Initial Variance Report + Remediation Project (one-time): $4,500–$15,000, scaled by employee count and number of distinct jurisdictions covered — priced per audited employee-jurisdiction pair, not per hour of analyst time.
Quarterly Monitoring Retainer (recurring): $3–$6 per employee per month (minimum $750/quarter), covering re-audit after new hires, location changes, and jurisdiction rule updates.
New-Hire Jurisdiction Classification Add-On: flat per-new-hire fee ($15–$35) for companies that want every new remote hire automatically classified and accrual-checked at onboarding rather than caught in the next quarterly cycle.

This mirrors the audit-and-remediate-then-monitor pattern already accepted in adjacent recovery/compliance-audit service categories, while keeping the core unit non-hourly and tied to a quantifiable outcome (dollars of exposure found and corrected, or jurisdictions cleanly monitored).

Regulatory and Compliance Considerations

The governing legal landscape is genuinely fragmented and independently amending: 22 states plus D.C. have their own statewide paid sick leave statutes, more than 20 cities and counties (led by California) layer distinct accrual rate, cap, carryover, and front-load rules on top of (or instead of) the state default, and 18 states have separately enacted laws preempting their own cities from creating new local ordinances (TriNet 2026; Truthout 2026). California's Paid Sick Leave Law carries PAGA exposure following Wood v. Kaiser Foundation Hospitals (Workplace Legal PC 2026). New York City's Earned Safe and Sick Time Act was substantially expanded and its enforcement powers strengthened effective February 22, 2026, including NYSDOL authority to place liens, issue bank-account warrants, and issue stop-work orders, and DCWP's use of CDC sick-leave-usage data to proactively investigate suspected under-provision (HelpNewYork.com 2026). Because these rules amend independently and on different legislative calendars, the service's rules engine must be version-controlled and re-validated at least quarterly, and any output that could be read as legal advice, or any employee-facing remediation communication, must be reviewed and approved by licensed employment counsel before it leaves the building.

Licensing Boundary

What AI may draft/extract/classify/calculate: jurisdiction classification per employee (based on work location or remote-employee address), extraction of accrual/cap/carryover parameters from the applicable statute text into the rules engine, computation of expected accrual balance and variance against the payroll export, and first-draft remediation ledgers and policy-language redlines.

What trained (non-attorney) operators may review: data-quality checks on the payroll export and roster, exception-queue triage for ambiguous work-location data or conflicting local/state rules, and formatting/QA of the client-facing Variance Report before counsel review.

What licensed employment counsel must approve/sign before delivery: any characterization of a dollar amount as "owed" to an employee, any remediation plan, any amended policy or handbook language, and any communication that will reach an employee directly. This is a firm, non-negotiable chokepoint — the company never sends legal-conclusion-adjacent output to a client or an employee without counsel sign-off.

What the company must not claim: the company does not practice law, does not represent employees or employers in any dispute, administrative hearing, or litigation, and does not give legal advice; every deliverable carries an explicit disclaimer that it is a data-driven compliance diagnostic prepared for and reviewed with the client's own or contracted employment counsel, not a legal opinion. The service is not a debt-collection activity (it does not collect money from consumers) and does not require insurance-adjuster or third-party-collector licensure, since it audits and remediates an employer's own internal payroll obligations rather than adjusting an insurance claim or collecting a consumer debt — this framing is Inferred from the nature of the activity and the absence of any specific licensing regime found for "payroll accrual audit" services in research for this run, and should be confirmed with counsel in each state of operation before scaling, particularly if any success-fee/contingency pricing tied to recovered back-pay is introduced. Contingency pricing tied directly to "back pay recovered" is deliberately avoided in the proposed pricing model above in favor of flat project and per-employee monitoring fees, to avoid unresolved regulatory questions about fee-sharing on wage recoveries.

AI-Native Advantage

This is not "using ChatGPT to write an HR memo." The AI-native advantage is structural: (1) maintaining a continuously-updated, machine-readable rules database across 40+ independently-amending jurisdictions is a document- synthesis and change-detection problem frontier models are well suited to accelerating, at a cost and speed no manual research team can match; (2) mapping arbitrary, messily-formatted payroll accrual exports from dozens of different HRIS/PEO platforms into a standard schema is a document-extraction problem that improves directly as extraction models improve; (3) computing per-employee expected-vs-actual accrual variance across 12–24 months of pay periods, for every employee, in minutes rather than the days or weeks a manual audit would take, is what makes an outcome-priced, scalable service possible instead of a bespoke, hourly-billed law-firm engagement. Every layer that does not require a licensed professional's judgment is automated; the licensed chokepoint is reserved for exactly the moment output becomes legal-conclusion-adjacent.

Internal AI Engine Architecture

1. Intake
Secure upload of payroll accrual export, employee roster (work location/remote address), and current written PSL policy.

2. Normalization
Map arbitrary HRIS/PEO export formats into a standard employee-period-accrual schema; flag missing or ambiguous location data for the exception queue.

3. Retrieval / Knowledge
Pull the current, version-controlled rule set (accrual rate, cap, carryover/front-load, waiting period, increment, payout rate) for every jurisdiction represented in the roster.

4. AI Workbench
Classify each employee to the most specific governing jurisdiction; compute expected accrual balance per pay period; diff against actual balance.

5. Deterministic Rules
Hard-coded jurisdiction formulas (rate, cap, carryover) applied consistently — not left to model judgment — with the AI layer responsible for classification and extraction, not for inventing rule values.

6. Human Chokepoint
Licensed employment counsel reviews every finding framed as "owed," every remediation plan, and every piece of employee-facing language.

7. QA
Independent recompute of a sample of variance calculations against source data before delivery; confidence scoring on jurisdiction classification for ambiguous cases.

8. Delivery
Client-ready Variance Report, remediation ledger, and (if engaged) amended policy templates, delivered as a reviewed PDF/packet plus a plain-English walkthrough call.

9. Learning Loop
Exceptions and counsel corrections become updated rules, new QA checks, and refined extraction prompts/templates for the next client and the next quarterly cycle.

10. Model Portability
The rules database and workflow are model-agnostic; the underlying extraction/classification model can be swapped as frontier capability improves without rebuilding the jurisdiction rules layer.

AI-vs-Human Operations Pipeline

Task	Who/What	Notes
Payroll export parsing & schema normalization	AI	Deterministic mapping rules plus model-assisted parsing for non-standard exports
Employee-to-jurisdiction classification	AI, exception-reviewed by operator	Ambiguous addresses (e.g., hybrid, multi-location) routed to human review
Jurisdiction rule extraction & versioning	AI-assisted, operator-curated	New statutory text run through extraction pipeline, diffed against prior version, operator confirms before publishing to rules DB
Expected-vs-actual accrual computation	Deterministic rules engine	Not model judgment — formulas are hard-coded per jurisdiction version
Variance ranking & report drafting	AI drafts, operator QA's	Sample recompute check before send
Characterizing findings as "owed" / remediation plan / policy language	Licensed employment counsel	Non-delegable chokepoint
Client walkthrough & relationship	Human account lead	Trust interface; counsel joins for complex or high-exposure findings
Quarterly re-audit trigger & monitoring	AI (scheduled) + operator review	Automated re-run against updated roster and rules DB

Dynasty Translation Layer

Buyer translation: HR/People leader or Controller at a growing multi-state company, urgently wants to know if the company is exposed to a PAGA claim or a proactive state/city audit, and wants that risk quantified and fixed without hiring in-house payroll-compliance headcount.

Service translation: done-for-you accrual audit and remediation; the client receives a report, a fix, and ongoing monitoring — classification, extraction, and computation are automated, counsel review and client relationship are human.

Workflow translation: intake (payroll export + roster + policy) → research/classification (jurisdiction mapping) → production (variance computation, draft report) → review (counsel sign-off) → delivery (report + remediation plan) → follow-up (implementation support with payroll/PEO) → renewal (quarterly monitoring retainer).

Tooling translation: starts with spreadsheets/CSV parsing scripts and a shared jurisdiction-rules database (no custom software platform required to launch); a lightweight internal dashboard for tracking client exception queues and rule-version history is the first tool built, well after the first paying clients.

Sales translation: "We'll tell you, in dollars, exactly where your sick-leave accrual math is wrong across every state and city you operate in — and fix it — before it becomes a PAGA claim or a DOL investigation." Plain-language contrast: ignoring it risks six-to-seven-figure exposure (see the $6.175M 2026 settlement); DIY-ing it means an HR generalist trying to manually track 40+ independently-amending jurisdictions in a spreadsheet.

Delivery translation: first three clients delivered via manual spreadsheet-based rules lookup plus AI-assisted extraction scripts run by the founder/operator; automation of the rules database and variance engine is built incrementally as volume justifies it, never ahead of paying demand.

Expansion translation: the audited rules engine and workflow become the foundation for adjacent services — multi-state new-hire jurisdiction classification at onboarding, wage-statement compliance auditing, and eventually a broader multi-state payroll-compliance monitoring platform, sold first as service, only later as software-assisted self-serve tiers for the smallest clients.

Anti-Duplication Analysis

Similar existing services/tools: multi-state HR compliance software (Mosey, SixFifty, GovDocs) and employment-law-firm wage-and-hour audits. This is not a copy of either: Mosey/SixFifty/GovDocs sell self-serve registration and policy- template tooling the buyer operates themselves and do not audit actual per-employee payroll accrual math against jurisdiction formulas or quantify historical shortfalls in dollars; law firm audits are hourly-billed, one-off, and not built as a recurring, AI-accelerated monitoring service. The narrow wedge that differentiates this business is the combination of (a) a maintained, versioned, 40+-jurisdiction accrual-rules engine, (b) automated per-employee variance computation against a client's actual payroll data, and (c) counsel-reviewed remediation delivered as a recurring, outcome-priced service rather than a software seat or an hourly invoice. The underserved segment is mid-market multi-state employers too large to ignore the risk and too small to justify in-house payroll-compliance headcount or a standing law-firm audit engagement.

Duplicate check against this factory's own manifest: checked the freshly-cloned 789-entry manifest.json and the repository's full flat-file listing of prior *-blueprint.html / *-no-go.html files for "sick leave," "accrual," "PTO bank," and "leave bank" — zero matches on all four terms, and zero matching filenames. The manifest's two closest existing entries — Leave Of Absence PFML Administration Engine (2026-07-08) and LeaveDesk Clear: SMB Multi-State FMLA/ADA/PFML Leave Case Administration Desk (2026-07-16) — address a materially different workflow: they process individual employee leave-of-absence cases (intake, medical certification, return-to-work) for FMLA/ADA/PFML, not the ongoing, population-wide payroll accrual-balance mathematics and variance-detection problem this blueprint addresses. A buyer could reasonably need both services simultaneously without redundancy, in the same way a company might need both a tax-return preparer and a separate sales-tax-nexus auditor.

Anti-Commoditization Analysis

If a future frontier model becomes capable enough that any HR generalist can ask a general-purpose assistant "is my sick leave policy compliant" and get a decent generic answer, three things remain defensible and non-commoditized: the maintained, versioned rules database mapped to real, dated statutory text across 40+ jurisdictions that independently amend on different schedules (a curation and change-detection asset, not a one-time prompt); the ability to compute actual variance against a specific client's real, messy payroll export rather than answer a hypothetical policy question; and the counsel-reviewed, audit-ready documentation trail that is what a regulator or a PAGA plaintiff's attorney will actually ask to see, which a generic chatbot answer does not produce or stand behind.

Service Delivery Workflow

Client submits payroll accrual export, roster with work locations, and current PSL policy through a secure intake form.
Operator/AI normalizes the export into the standard schema and flags ambiguous location data for review.
Rules engine classifies each employee to the governing jurisdiction and computes expected accrual balance for the trailing 12–24 months.
Variance report drafted, ranking exposure by dollar amount and enforcement severity (PAGA-eligible, DOL-audit-prone, etc.).
Employment counsel reviews every finding and any proposed remediation language.
Client receives the Variance Report and, if engaged, a remediation ledger and corrected policy/handbook language.
Operator supports implementation with the client's payroll vendor/PEO to correct going-forward configuration.
Client enrolls in the quarterly monitoring retainer; each cycle re-runs the pipeline against the updated roster and current rules-engine version.

Operations as Product

SOPs cover: required intake fields and file formats, a completeness checklist run automatically on every upload (missing location data, gaps in the payroll ledger, ambiguous employment dates), an exception queue with defined routing rules for ambiguous cases, reviewer assignment logic (counsel review required on any output characterizing dollars "owed"), confidence scoring on jurisdiction classification, a full audit trail from raw payroll export to final delivered report, versioned gold-standard examples for QA calibration, and a root-cause/postmortem log for every finding later disputed or corrected, feeding directly back into rule refinement.

No-Holes Quality Engine

Every Variance Report passes: (1) an automated completeness check confirming every employee in the roster has a computed result (no silent drops); (2) a sample recompute by a second reviewer (human or independent script) on at least 10% of flagged variances before delivery; (3) a jurisdiction-rule freshness check confirming the rules engine version used matches the latest confirmed statutory text for every jurisdiction represented; and (4) mandatory counsel sign-off before any client-facing delivery. Any finding later shown to be wrong triggers a root-cause review and a rule or process correction, logged and versioned.

What the Human Expert Actually Does

Task	License required	Min/unit at launch	Min/unit at day 90	Automation path	Quality risk	Cannot be automated	Documentation/audit trail
Exception-queue triage (ambiguous location data)	None	15	8	Improved extraction/classification confidence scoring reduces exception volume	Misclassification if rushed	Judgment calls on hybrid/ambiguous work arrangements	Exception log with resolution rationale
Sample recompute QA check	None	20	10	Automated recompute script narrows human sample to edge cases	Missed calculation error	Final spot-check judgment	QA checklist, signed off per report
Employment counsel review & sign-off	State bar admission (employment law)	30	20	Not automatable — volume reduced via better-organized pre-review packets, not eliminated	Legal exposure if skipped	Legal characterization of "owed," remediation language, employee-facing communication	Signed review record retained per client per cycle
Client walkthrough call	None (counsel joins for high-exposure findings)	30	25	Not primarily automated — trust interface	Miscommunication of findings	Relationship, context-setting, objection handling	Call notes logged to client record

Minimum Viable Offer

The first paid offer is the standalone Sick Leave Accrual Variance Report: a one-time diagnostic, delivered in 5 business days from data receipt, priced at a flat project fee scaled by employee/jurisdiction count (see Pricing), with no software to install and no ongoing commitment required to buy the first report. This proves the wedge, generates the first dollar-quantified proof points for case studies, and creates the natural upsell into remediation and the quarterly monitoring retainer.

Fulfillment Process

The first three clients are fulfilled semi-manually: the founder/operator receives the payroll export and roster via a secure shared folder, runs an AI-assisted extraction and classification script (built in a spreadsheet plus a lightweight Python/LLM pipeline, not a customer-facing product), manually reviews exception cases, and engages a contracted employment attorney (fractional, paid per review) for sign-off before delivery. No dedicated software product is needed on day one; the jurisdiction rules database itself (a structured spreadsheet/JSON file of accrual rate, cap, carryover, and waiting-period values per jurisdiction) is the first real asset built and is what scales into an internal tool as volume grows. Automation is added incrementally — first the payroll-export parsing, then the variance computation, then scheduled quarterly re-runs — only after the manual process has been proven correct across several real clients.

Tools and Systems

Launch stack: a secure client intake form (Typeform/Google Forms + encrypted storage), a structured jurisdiction rules database (spreadsheet or lightweight JSON store), a Python/LLM-assisted extraction and classification pipeline, a document-generation template for the Variance Report (built in a standard word-processing/PDF template, not custom software), a shared exception-tracking board (Airtable/Trello-class tool), and a contracted relationship with a fractional employment attorney for review. Custom software (a client-facing dashboard, automated payroll-API integrations) is deliberately deferred until manual delivery is proven across enough clients to justify the build.

Human-in-the-Loop Quality Control

Every deliverable passes through at minimum two human checkpoints before reaching the client: an operator QA pass (completeness, sample recompute, jurisdiction-rule freshness) and mandatory licensed-counsel review of any finding characterized as owed, any remediation plan, and any employee-facing language. No report leaves the building without both sign-offs recorded in the client's audit trail.

Nonlinear Scaling and Unit Economics

50%+

target gross margin by scale (see COGS breakdown)

28% → <8%

Automation-adjacent benchmark: only 28% of mid-market shippers use dedicated compliance software and <8% use AI automation in comparable back-office categories, indicating substantial headroom for an AI-native entrant (cross-sector benchmark, directionally applied)

5 business days

target cycle time, variance report delivery

COGS breakdown per Variance Report engagement (mid-market, ~200 employees, 5 jurisdictions): model inference/extraction compute (~2% of contract value at launch, falling as prompts/pipelines are refined), hosting/software (~1%), operator review minutes (~15% at launch, falling to ~8% by day 90 as exception rates drop with a matured rules engine), licensed counsel review minutes (~20%, the least compressible cost given the non-delegable chokepoint), QA (~5%), client support/onboarding (~5%), rework/exception-handling buffer (~5% at launch, ~2% by day 90). Combined COGS at launch is roughly 48–53% of contract value, reaching the 50%+ gross margin target as automation and rules-engine maturity compress operator-review time; counsel review time is deliberately not compressed further, since it is the trust and compliance chokepoint the business is built around.

Automation %: roughly 40% of total effort automated at launch (extraction, classification, computation), rising to 65–70% by 90 days as the rules engine and exception-handling playbooks mature, plateauing around 75–80% by year one given the hard floor of required counsel review.

Throughput, cycle time, quality targets: target 8–12 Variance Report engagements per operator per month at maturity; cycle time target 5 business days from data receipt; rework rate target under 5%; quality (post-delivery correction) failure rate target under 2%; escalation-to-counsel rate stabilizing as a predictable percentage of total findings rather than trending upward.

CAC payback and conversion assumptions: given a $4,500–$15,000 initial project fee, CAC payback within the first engagement is the target (i.e., content/outbound-driven leads should not require a second sale to become profitable on acquisition cost); assumed lead-magnet-to-consultation conversion of 8–15%, consultation-to- paid-diagnostic conversion of 25–40%, and diagnostic-to-quarterly-retainer conversion of 40–60% given the report itself is the primary sales tool for the recurring retainer.

Distribution Proof Table

Channel	Why ICP reachable there	First message/angle	Expected conversion assumption	Proof source	Measurement plan	Follow-up mechanism
SEO/organic search	HR buyers already searching "paid sick leave laws by state 2026" in volume (evidenced by dense vendor/law-firm content ecosystem)	"Is your payroll actually computing this correctly? Free 5-state scan"	1–3% visitor-to-lead	Volume of existing 2026 vendor/law-firm guides on this exact topic	Search Console + lead-form conversion tracking	Email nurture into free diagnostic offer
LinkedIn (organic + targeted outbound)	VP People/HR Directors active and identifiable by title + company headcount + multi-state footprint	Diagnosis-led post: "3 accrual mistakes we keep finding in multi-state payroll exports"	0.5–2% connection-to-conversation	Public settlement/enforcement news (Alco Harvesting, NYC ESSTA) as timely hook	LinkedIn analytics + CRM-logged replies	DM to book a free diagnostic scan call
Employment law firm referral partnerships	Firms doing wage-and-hour audits want a specialist to hand off recurring accrual monitoring rather than own it themselves	"We handle the ongoing accrual math so you can focus on the dispute work"	10–20% of referred leads convert	Existing hourly-billed law firm audit market (competitive landscape research)	Referral-source tagging in CRM	Co-branded intake form
PEO/payroll-vendor partnerships	PEOs want to refer accrual-audit findings to a specialist rather than own the liability of "fixing" a client's shortfall	"We're the partner you refer accrual questions to"	5–15% of referred leads convert	PEO business model research (TriNet/Justworks bundle template policy, not audit)	Partner-referral tracking link	Joint webinar/co-marketing
Trade associations (SHRM chapters, state HR associations)	Direct access to HR-Director-level audience already primed on multi-state compliance topics	Speaking/webinar slot: "What NYC's 2026 ESSTA expansion means for your payroll"	3–8% attendee-to-lead	NYC ESSTA 2026 news cycle as timely hook	Event lead capture + follow-up email open rate	Post-event free diagnostic offer
Answer-engine/AI search optimization (AEO)	HR buyers increasingly query AI assistants directly with "is my sick leave policy compliant in California and New York"	Structured, citable content answering exactly that query with a clear CTA to the free diagnostic	Emerging channel, directional only	Dense 2026 vendor-content ecosystem confirms buyers already research this topic heavily	Referral-traffic tagging from AI-assistant-cited sources where trackable	Diagnostic landing page

Sales and Outreach Plan

The core sales motion is diagnosis-led, not demo-led: every outbound message, LinkedIn post, and landing page leads with a specific, timely compliance risk (the NYC 2026 ESSTA expansion, a recent settlement, a state's new accrual rule) rather than a generic pitch about "AI compliance tools." The free diagnostic scan (a lightweight, no-cost 2-jurisdiction check) is the primary conversion mechanism from cold or warm contact into a paid engagement; the full paid Variance Report is positioned as the natural, low-friction next step once the free scan surfaces at least one real finding.

Founder-Led Content Plan

Founder-authored content focuses on teaching the exact mechanics of the pain: how accrual formulas differ across jurisdictions, what "cost of doing nothing" looks like in real settlement dollars, what regulatory changes (like NYC's 2026 ESSTA expansion) actually require operationally, and worked, anonymized examples of variance findings. This content is the top of the SEO/LinkedIn/AEO funnel described in the distribution proof table.

First 30 Days of Content

10 educational posts: (1) "22 states + D.C. have sick leave laws — here's why your payroll system probably isn't tracking all of them correctly"; (2) "What Wood v. Kaiser actually means for your PAGA exposure"; (3) "NYC's Feb. 2026 ESSTA expansion, explained for HR, not lawyers"; (4) "The 5 most common payroll accrual misconfigurations we find"; (5) "Why 'our PEO handles it' isn't the same as 'it's correct'"; (6) "What a $6.175M sick leave settlement actually looked like operationally"; (7) "Carryover vs. front-load: the accrual choice most companies get wrong"; (8) "Remote hires are the #1 source of silent jurisdiction misclassification"; (9) "How proactive enforcement (NYC's CDC-data approach) changes the compliance calculus"; (10) "A plain-English glossary of sick leave accrual terms every HR generalist should know."
3 diagnostic teardown formats: anonymized "we found this variance" case walkthroughs; a "spot the misconfiguration" interactive quiz; a before/after remediation ledger example.
2 lead-magnet angles: a free 2-jurisdiction accrual scan; a downloadable "50-state + top-20-city sick leave accrual cheat sheet."
1 webinar/live-review idea: "Live accrual audit: we'll scan a volunteer company's anonymized payroll export on screen."
1 outbound diagnosis template: a personalized LinkedIn/email message referencing the prospect's known office locations and a specific, named jurisdictional risk (e.g., "I noticed you have a New York City office — here's what changed there in February").

Lead Magnet and Waitlist Plan

Primary lead magnet: a free, no-obligation 2-jurisdiction accrual scan (the prospect submits a small anonymized data sample; the company returns a short findings summary, without engaging counsel review, clearly marked as a directional/free-tier scan rather than the full counsel-reviewed product). This captures a genuine pain signal (a prospect willing to share payroll data has real intent) and creates a qualified, warm handoff into the paid diagnostic. A waitlist for the quarterly monitoring retainer is offered to anyone who completes a paid Variance Report, to sequence capacity growth deliberately rather than overcommit before the pilot cohort's operational kinks are worked out.

Warm GTM Plan

Warm GTM starts with the founder/operator's existing professional network in HR, payroll, and employment-law-adjacent roles, offered a free diagnostic scan and asked for one honest referral each in exchange; existing contacts at PEOs and payroll vendors are approached as referral partners (not competitors) per the distribution proof table; and any early-access waitlist signups are personally called, not just emailed, to convert the first cohort.

Targeted Outbound Plan

Perfect-fit prospects (75–300 employees, confirmed multi-state footprint including at least one CA or NYC location, identifiable HR/People leader) are researched individually and approached with a specific, named jurisdictional risk rather than a generic pitch — leading with a diagnosis/opportunity memo ("here's what changed in your specific jurisdictions and why it likely affects you") rather than a demo request, consistent with the "diagnosis before demo" sales motion above.

Answer-Engine / Search Visibility Plan

Content is structured to directly and citably answer the exact questions HR buyers are already typing into search engines and AI assistants (e.g., "is my sick leave policy compliant in California and New York," "what changed in NYC sick leave law 2026"), with clear, quotable statistics and a consistent call-to-action to the free diagnostic scan, positioning the company to be cited as a source by AI-assisted answer engines as well as ranked in traditional search.

Pilot Design and Early-Demand-Trap Mitigation

First pilot cohort capped at 5 clients, selected for genuine multi-state complexity (at least CA or NYC exposure) to stress-test the rules engine against the hardest jurisdictions first. Early-access incentive: a discounted first Variance Report in exchange for a detailed feedback session and (with permission) an anonymized case-study writeup. The early-demand trap — mistaking waitlist signups or free-scan requests for validated demand — is mitigated by treating only a completed, paid Variance Report purchase as a real demand signal; free-scan conversion rate to paid is tracked explicitly and is the metric that gates any expansion of outbound spend.

Early-Access Feedback Flywheel

Every pilot client's exceptions, counsel corrections, and post-delivery questions are logged and reviewed weekly; recurring corrections become new deterministic rules, new QA checklist items, new extraction prompt refinements, or new retrieval sources (e.g., a jurisdiction whose statutory text format the pipeline handled poorly). Product feedback (something the pipeline should have caught) is distinguished from custom work (a client-specific request outside the core accrual-audit scope, priced separately) to keep the core service narrow and repeatable.

Build-Before-Scale Checkpoints

After 5 pilots: harden the intake completeness checklist and required-evidence list based on what actually caused delays or rework. After 10 pilots: harden SOPs, the exception-queue routing logic, and the reviewer/counsel checklist based on the most common finding types and correction patterns observed. After 20 pilots: pause new pilot intake until COGS, rework rate, escalation rate, and cycle time are formally measured against the targets in the Unit Economics section; only resume expansion once those numbers are within target range. Manual workarounds acceptable temporarily: spreadsheet-based rules lookups, manual counsel scheduling. Workarounds that signal the model is not scalable and must be fixed before expanding: counsel review time growing faster than client count (indicates findings are too noisy / low-confidence), or exception-queue volume not shrinking as the rules engine matures.

7-Day / 30-Day / 90-Day Launch Plans

7 Days

Build the initial jurisdiction rules database for the highest-priority jurisdictions (federal baseline, California state + top 5 CA cities, New York state + NYC, Illinois + Chicago, Washington, Colorado).
Stand up the secure intake form and a basic extraction/classification script.
Draft and publish the first 3 founder-led content pieces and the free diagnostic scan landing page.
Reach out personally to 20 warm contacts offering the free diagnostic scan.

30 Days

Deliver the first 3–5 paid Variance Reports; formalize the counsel-review process with a contracted employment attorney.
Publish the remaining first-30-days content calendar items; launch the first LinkedIn outbound sequence to perfect-fit prospects.
Begin at least one PEO or law-firm referral-partner conversation.

90 Days

Complete the 5-client pilot cohort; run the after-5-pilots hardening checkpoint.
Convert at least 2 completed Variance Report clients into the quarterly monitoring retainer.
Expand the jurisdiction rules database to the full set of 22 states + D.C. and the highest-priority additional cities/counties.
Measure COGS, rework rate, and cycle time against unit-economics targets before accepting pilot #11.

Metrics and KPIs

Free-scan-to-paid-diagnostic conversion rate (target 25–40%)
Diagnostic-to-quarterly-retainer conversion rate (target 40–60%)
Cycle time from data receipt to delivered report (target 5 business days)
Rework rate (target <5%) and post-delivery correction rate (target <2%)
Automation % of total effort (target 40% at launch, 65–70% by day 90)
Gross margin per engagement (target 50%+ at scale)
Counsel-review turnaround time (tracked to ensure it never becomes the bottleneck)

Risks and Mitigations

The most material risks are (1) mischaracterizing a finding as legal advice or "owed" without counsel review, which is mitigated by the hard, non-negotiable counsel chokepoint built into the workflow and QA engine; and (2) rules-engine staleness as jurisdictions amend their laws faster than the internal review cycle, mitigated by mandatory quarterly rules-database re-validation and a version-controlled change log. See the full risk register below for a complete, ranked accounting.

Exhaustive Risk Register

Counsel-review bottleneck — Likelihood: Medium, Impact: High

As client volume grows, licensed employment counsel review time could become the binding constraint on throughput. Mitigate by contracting multiple fractional employment attorneys, pre-organizing review packets to minimize attorney time per finding, and explicitly not compressing this chokepoint even if it caps near-term growth.

Jurisdiction rules-engine staleness — Likelihood: Medium, Impact: High

22+ states, 20+ cities/counties independently amend accrual rules on different schedules; a stale rule produces a wrong variance finding. Mitigate with mandatory quarterly (minimum) rules re-validation, versioned change logs, and a dedicated legislative-monitoring content pipeline.

Misclassification of remote/hybrid employees' governing jurisdiction — Likelihood: Medium, Impact: Medium

Ambiguous work-location data (hybrid schedules, recently relocated employees) can lead to wrong jurisdiction assignment. Mitigate with a defined exception-queue routing rule and conservative default-to-human-review policy for any ambiguous case.

Payroll export format fragmentation — Likelihood: High, Impact: Medium

Dozens of different HRIS/PEO export formats increase normalization effort and error risk. Mitigate with a growing library of format-specific parsers and a manual-review fallback for any unrecognized format.

Client relies on finding as legal certainty rather than a diagnostic — Likelihood: Low, Impact: High

A client could over-rely on the report as a legal guarantee. Mitigate with explicit disclaimers on every deliverable and requiring the client's own or contracted counsel review before any employee-facing action.

Regulatory ambiguity on licensing for claims/recovery-adjacent activity — Likelihood: Low, Impact: Medium

Though this is Inferred as not requiring insurance-adjuster or debt-collector licensure, this has not been independently confirmed by counsel in every state of operation. Mitigate by obtaining a formal legal opinion before scaling beyond the pilot cohort and by avoiding contingency/success-fee pricing tied to recovered back pay.

Competitive response from existing compliance vendors (Mosey, SixFifty) — Likelihood: Medium, Impact: Medium

An incumbent could add accrual-variance auditing as a feature. Mitigate by moving quickly to build the curated rules-engine and client base, and by leaning into the counsel-reviewed, done-for-you positioning that a self-serve software feature cannot easily replicate.

Low initial pilot conversion (early-demand trap) — Likelihood: Medium, Impact: Medium

Free-scan signups could fail to convert to paid engagements. Mitigate by tracking only paid conversions as real demand and gating outbound spend expansion on that metric.

Data security/privacy exposure handling payroll and PII data — Likelihood: Low, Impact: High

Payroll exports contain sensitive employee PII. Mitigate with encrypted intake, minimal necessary data retention, and a documented data-handling policy reviewed by counsel.

Over-automation eroding trust in findings — Likelihood: Low, Impact: Medium

Excessive automation without visible human review could undermine client confidence in a compliance-sensitive deliverable. Mitigate by making the counsel-review step visible and explicit in every client deliverable and sales conversation.

Concentration risk in early pilot cohort — Likelihood: Medium, Impact: Low

Five pilot clients is a small base; losing one or two materially affects early revenue and case-study material. Mitigate by diversifying pilot industries and by not overselling the monitoring retainer before delivery quality is proven.

State preemption law changes reducing local complexity (lower long-term TAM in some states) — Likelihood: Low, Impact: Low

Some states may pass broader preemption laws simplifying local rules, marginally reducing the complexity this service is priced against in those specific markets. Mitigate by prioritizing jurisdictions (CA, NY) least likely to preempt and by expanding into adjacent multi-state payroll-compliance services (wage statements, onboarding classification) as a hedge.

What Could Kill This

The clearest existential risks are: (1) a state legislature enacting a federal-preemption-style law that dramatically simplifies multi-jurisdiction complexity (unlikely at federal level given current gridlock, but state-by-state preemption trends bear monitoring); (2) an incumbent HR compliance platform (Mosey, SixFifty) adding a genuinely credible accrual-variance-audit feature with counsel review built in, closing the gap this business is built on; and (3) a failure to keep the counsel-review chokepoint scalable, which would either force the business into a law-firm-style hourly model (destroying the outcome-pricing thesis) or force cutting corners on the one non-negotiable trust layer.

Go/No-Go Reasoning

This candidate clears the evidence threshold: a specific, well-defined buyer (multi-state HR/People leaders); a painful, well-documented problem with a real 2026 settlement and active, strengthening enforcement (NYC ESSTA, CA PAGA); existing adjacent budget (Mosey and peers already selling $399–$1,999+/month compliance tools into this exact buyer); a credible, narrow, one-feature MVP wedge (the Variance Report diagnostic); a defensible reason to win against existing software-only and hourly-billed alternatives (the audit-and-remediate outcome they do not provide); and a believable distribution path anchored in genuinely timely 2026 regulatory news. No fatal disqualifier applies: the buyer does not need to operate any software; there is no requirement for physical labor; licensing risk is addressed with an explicit human chokepoint and an honest flag that the "no special license required" framing is Inferred, not Verified, and should be confirmed by counsel before scaling. Decision: Blueprint.

Final Recommendation

Launch the Sick Leave Accrual Variance Report as a standalone, flat-fee diagnostic targeted at 75–300-employee multi-state employers with California and/or NYC exposure, fulfilled manually/semi-manually for the first five pilot clients using a founder-built jurisdiction rules database and a contracted employment attorney for review, before investing in any custom software. Expand into the quarterly monitoring retainer and adjacent multi-state HR-compliance services only after the pilot cohort's rework rate, cycle time, and counsel-review turnaround are measured and found within target range.