saascode
hr, payroll & talent·run 105 · May 2026

HRSelfDriving

An embedded workflow compiler separating customer intent, structured rule proposals, deterministic tests, payroll review, approval, activation, execution evidence and rollback.

Genesis score6.54/10
Make HRSelfDriving real.0/500
500 more votes and HRSelfDriving is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The case

Vertical payroll providers often force customers into a fixed exception and approval workflow even when industries and organizations handle unusual hours, final pay, bonuses or review chains differently. The supplied research confirms a low-code payroll rule interface that can serve as a compilation target, plus API-first payroll vendors that could embed a workflow layer. General workflow engines exist, but the research found no reviewed product compiling customer-authored plain language into this specific payroll-rule structure.

HRSelfDriving would preserve provider, tenant, policy owner, jurisdiction assertion, source policy, plain-language request, extracted condition, ambiguity, structured rule proposal, rule version, fixture, expected result, observed result, failure, payroll-specialist finding, legal-review requirement, approval, effective period, activation request, platform acknowledgment, execution event, notification, exception, correction, rollback and source readback as distinct records. Generated rules remain proposals until qualified owners resolve ambiguity and approve a tested version.

A successful compile proves syntax, not correct payroll, lawful classification or complete edge-case coverage. A passing fixture proves only the supplied case. A signature supports bounded integrity and approval evidence; it does not establish legal validity or informed review. Approval is not activation, platform acknowledgment is not execution, and execution is not a correct worker outcome. No agent may change pay, employment status, time, tax settings or benefits, or activate a rule without explicit external authority.

The pilot should use synthetic workers and a nonproduction tenant for one narrow exception workflow. It must compare generated structure with a manually approved rule, exercise ambiguous language and prove rollback. The buyer hypothesis is a product or implementation leader at a vertical payroll provider seeking customer-configurable workflows, but provider appetite, customer demand, supported jurisdictions, regulatory ownership, embedding cost and business model remain unverified.

Who pays — and why

A product, implementation or payroll-platform leader at a vertical payroll provider responsible for safe customer-configurable exception workflows.

What it unlocks
A structured intent record separating customer source policy, plain-language request, extracted conditions, ambiguity, affected population, jurisdiction and prohibited interpretations
A deterministic review harness linking rule proposal, compiler version, fixtures, expected and observed results, failures, payroll findings and corrections
A controlled release trail separating approval, effective period, activation request, platform acknowledgment, execution evidence, exception, rollback and source readback
How Genesis scored it
6.54across seven criteria
tension 7temporal 7blindspot 5buyer 8leverage 8convergence 5why-not 5
8
Buyer persona

Product and implementation leaders at vertical payroll providers are actionable, though vendor appetite and budget need validation.

8
Asymmetric leverage

A versioned rule language, fixture library and approval workflow can be embedded across providers after integration.

5
Why nobody did it

A real low-code compilation target exists, but the historical barrier beyond payroll complexity is not strongly evidenced.

Why it scored well

The input identifies a clear embedded-software buyer, a confirmed low-code payroll compilation target and a concrete customer-authored exception workflow.

What's holding it back

Demand is based on limited signals, the distribution hypothesis is unproven and compiling ambiguous payroll policy creates substantial legal, operational and worker-impact risk.

Signals detected3 sources crossed
SignalSupplied official-interface research

SignalSupplied vendor research

SignalSupplied competitor comparison

Direction briefhrselfdriving.md
hrselfdriving.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.