Size the surface.
Use IRS, BLS, Census/SUSB, SBA, state DOR, and practitioner sources to estimate employers, payroll cadence, filings, notices, penalties, and compliance volume.
Most payroll systems ask you to trust the output. Runbook lets you verify the liability record.
The real pain is not abstract proof. It is the day a worker asks why their check changed, a CPA asks where a tax number came from, a mid-year switch threatens W-2s, or an agency notice arrives from a period everyone thought was handled.
Runbook operates on a single rule: every approved payroll run creates an append-only record of the accrued payroll liabilities it calculated, settled, filed, corrected, and preserved.
Runbook still has to answer the same buyer questions as Gusto, QuickBooks, ADP, Square, and OnPay. The difference is what happens when ordinary payroll confidence is not enough.
That is the category gap: most providers prove trust through scale, guarantees, reports, and support. Runbook adds a liability record that can be replayed.
Government statistics can show payroll compliance is large. They cannot prove that Runbook's record model is valuable. The sandbox is how we measure that narrower correctness claim.
Use IRS, BLS, Census/SUSB, SBA, state DOR, and practitioner sources to estimate employers, payroll cadence, filings, notices, penalties, and compliance volume.
For each real case, capture event type, time already spent, dollars at stake, missing evidence, current provider, and whether the packet answers the key question.
If CPAs send packets, employers pay for corrections, and sandbox cases convert to payroll interest, correctness becomes more than a positioning claim.
The honest answer is: the individual pieces are familiar, but the combination is rare in small-business payroll and hard to retrofit after the fact.
They use scale, tax guarantees, support teams, security pages, awards, and reports. Those matter. They do not usually give a third party a portable artifact that can replay the run from source facts and rule snapshots.
The system records facts bitemporally, computes with cited rules, derives corrections without rewriting settled runs, and seals the result. The proof is not a screenshot; it is a record that can be checked.
A payroll provider can add AI chat, prettier reports, and faster payments. Rebuilding mutable payroll state into event history, rule snapshots, correction lineage, and verifiable artifacts is much harder.
Runbook becomes superior when a worker question, agency notice, CPA review, provider switch, or agent-prepared payroll can be answered faster and with better evidence than the incumbent can provide.
Runbook should not claim to beat mature providers on operational breadth today. It should claim a sharper operating standard: full-service payroll built so every material number can explain, correct, and verify itself from the payroll record.
This should become Runbook's signature product walkthrough: our version of “run payroll in minutes,” but built around explanation and verification.
Payroll is prepared with workers, hours, taxes, deductions, employer cost, accrued liabilities, and assertions.
A late raise, missed timecard, garnishment order, W-4 change, or YTD import changes the record.
The operator opens the amount and sees the source facts, calculation, and cited rule snapshot.
Runbook leaves the original settled run intact and computes the exact delta under current knowledge.
The approved run produces a proof artifact with canonical digest, signature, and registry status.
A CPA, auditor, worker, or agent verifies the artifact without trusting Runbook's dashboard.
Clean payroll buyers buy convenience. Messy payroll buyers understand proof faster.
They inherit payroll messes, notices, year-end reconciliations, and provider exports that do not explain themselves.
They need YTD, wage bases, local taxes, and W-2 continuity to survive the provider change.
They already know that support tickets and exports are not the same as evidence.
Missouri, Kansas, Kansas City, and St. Louis turn local payroll complexity into a proof problem.
Agents need records they can verify, not pixels they can scrape.
They still need ordinary payroll breadth: filings, funding, support, worker portal, and year-end forms.
Runbook is for teams that need more than a report when payroll gets questioned.
Try the correctness sandbox