Runbook

Solutions

Payroll pages for the buyers who feel the pain first.

The first Runbook buyers will not all say “I need provable payroll.” They will say they are switching providers, cleaning up payroll, answering a notice, handling local taxes, or supporting clients who do not trust the export.

Small business payroll.

The default buyer needs payroll to feel complete before they care about architecture.

Build obligation

Pay employees and contractors

Payroll runs, contractor payments, direct deposit, manual checks, final pay, bonuses, and off-cycle pay.

Build obligation

Handle tax work

Withholding, employer tax, deposits, filings, W-2s, 1099s, and filing issue workflows.

Live

Keep evidence

When someone asks why, the answer comes from facts, rules, calculations, and the sealed payroll record.

CPAs and bookkeepers.

Advisor pages should become a channel strategy, not a footnote.

Advisor jobCurrent painRunbook answer
Review payrollScreenshots, register exports, and unclear edits.Client run queue with review notes, assertions, and proof packets.
Clean up a clientPrior-provider exports that do not explain wage bases.Attested founding facts and visible YTD transfer assumptions.
Answer noticesManual evidence gathering across payroll, tax, and bank records.Notice response packet with run, liability, payment, rule, and correction evidence.
Scale the practiceEvery client has a different payroll source of truth.Portfolio-level review built around comparable records.

Missouri, Kansas, and local tax.

Regional complexity is not a side note. It is a credible wedge for payroll truth.

Kansas City and St. Louis

Local payroll tax questions need jurisdiction, work location, resident status, rule source, liability, and settlement evidence.

Cross-border employers

MO/KS work patterns create practical questions around withholding, unemployment, local taxes, and worker support.

Local guide library

Runbook should ship state and local guides with citations and examples, then connect them back to payroll records.

Payroll notices and amendments.

A notice is where payroll software becomes evidence software.

1

Receive notice

Identify period, jurisdiction, tax type, amount, deadline, and stated issue.

2

Find affected runs

Locate payroll periods, liabilities, payments, filings, and corrections tied to the notice.

3

Assemble evidence

Package facts, rules, calculations, deposits, settlement status, and human approvals.

4

Draft response

Prepare a human-reviewed response with citations and the payroll evidence attached.

5

Record outcome

Store agency response, payment or amendment, and the resulting payroll event.

6

Keep history

The notice becomes part of the payroll record, not a disconnected support ticket.

Agent-mediated payroll.

Agents are a future interface, but the buyer benefit is practical: less manual review without letting a model calculate or approve payroll.

Agents propose. Humans approve. Runbook computes. Quittance proves.

That sentence should stay consistent across the site. It keeps the AI story useful without putting AI in the calculation path.

Start with the buyer’s payroll problem.

Proof lands when it answers a pain they already recognize.

Discuss solution fit