hr, payroll & talent·run 220 · Jun 2026

Reportescape

A read-only HR reporting layer that normalizes kept-in-place employee systems, versions metric definitions and delivers access-controlled reports with source reconciliation.

Genesis score6.10/10
Make Reportescape real.0/500
500 more votes and Reportescape 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 opportunity
3Confirmed adjacent analytics competitors
0Reviewed headless low-cost equivalents
The case

Mid-market HR teams can tolerate an imperfect employee system but still struggle to produce consistent headcount, turnover, compensation-band and pay-gap reporting across payroll and recruiting sources. Reportescape connects read-only, normalizes identities and employment events, and computes metrics from an approved semantic contract. The supplied research confirms expensive enterprise people analytics, a mid-market competitor with annual minimums and a newer regional entrant, while supporting a lower-cost headless reporting gap. Those products and services are observed market references, not fixed product pricing. Data extraction does not make a metric defensible: employment status, effective dates, worker types, compensation units, currencies and demographic fields require owner-approved definitions. Source record, identity match, normalized event, metric population, calculation, suppression, HR review, report delivery, employee correction and business decision remain separate. Pay-gap and demographic cuts are descriptive analyses subject to legal, privacy and statistical review, not proof of discrimination or fairness. The product can improve reproducibility and avoid a migration. It cannot repair bad source data silently, provide legal conclusions, rank employees or guarantee retention or equitable outcomes.

Who pays — and why

A mid-market people analytics, HR operations or compensation leader keeping existing employee systems but needing repeatable cross-source reporting.

Market signalValidate by employees, source systems, metric packs, scheduled reports, recipients, retained history and implementation supportPeople analytics platforms, HR reporting modules and data consulting are observed market references, not fixed product pricing
What it unlocks
A metric contract defining population, worker type, event, effective date, denominator, period, currency, compensation basis, demographic use, suppression, owner and version.
A lineage model separating source record, connector extraction, person match, normalized employment event, correction, exclusion and data-quality issue.
A delivery chain from reconciled snapshot through approved calculation, privacy review, recipient authorization, report export, acknowledgement, correction and separately governed employment decision.
How Genesis scored it
6.10across seven criteria
tension 8temporal 7blindspot 5buyer 7leverage 7convergence 5why-not 7
8
Productive tension

Teams want quick answers without migration, while employment metrics require precise definitions, privacy and accountable interpretation.

7
Temporal window

Reporting dissatisfaction and available connectors support a current window.

5
Convergence

Three cross-references and one inbound connection provide moderate convergence.

Why it scored well

A clear mid-market buyer, verified enterprise price ceiling and a reusable metric semantic layer support a focused bolt-on.

What's holding it back

Identity matching, effective dates, privacy and legal interpretation are hard, while existing analytics vendors can add lighter connectors and tiers.

Signals detected3 sources crossed
SignalCompetitor research

SignalCompetitor research

SignalMarket research

Direction briefreportescape-hr-metric-layer.md
reportescape-hr-metric-layer.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.