pitch.payruns.co
The pay run, prepared and evidenced.
The payroll run as a typed deliverable with its evidence file attached: inputs, approvals, the register, and the postings the run implies, every line resolving to its source, re-performable by any reviewer, released only on a recorded authorization from a named human at your entity. The deposit and the filing stay with the parties the law names.
↓ scroll · arrow keys
Every entity that employs people produces the same recurring deliverable: the pay run. Gross to net for every worker, on a calendar that does not negotiate. It is the fastest metronome in the back office: closes run monthly, but pay cycles run weekly and biweekly, and this is the one deadline a company can never miss quietly, because missing it is not a reporting problem. It is people's pay.
And in most companies the run is produced as a ritual. Inputs are chased over chat before the cutoff. Changes are keyed by hand into a portal. Approval happens in a hallway or a thread. The evidence of what was approved, by whom, against which inputs, survives as a screenshot if it survives at all. The register ties to nothing; the postings the run implies are re-derived at month-end, from exports, by whoever reconciles the payroll clearing account. And the off-cycle run, the correction, the retro adjustment: exactly where errors live is exactly where the evidence is thinnest.
When a reviewer asks how gross became net for one worker in one cycle, the honest answer is a person and a portal, not a record.
The contract is stated before the code exists, so it can be read and challenged first. The deliverable this door is designed to return: the pay run for one cycle, prepared from the entity's own data under its own payroll-data consent, computed gross to net deterministically by versioned workers, and evidenced: one file carrying the inputs, the approvals, the register, and the postings the run implies, every line resolving to its source. Re-performance is the design bar: the same inputs reproduce the same register for any reviewer at any later date.
// SPECIMEN · illustrative product mechanics: designed shape, not a live response
GET /v1/payruns/{cycle}
{
"cycle": "…",
"calendar": "biweekly",
"inputs": ["time and earnings data, under the entity's payroll-data consent",
"changes since the prior run, each with its source and its approval"],
"computation": { "gross_to_net": "deterministic, versioned", "tie": "EQUAL to the register, line by line" },
"register": "every worker's line resolving to its inputs and its approvals",
"implied_postings": "the entries this run implies: prepared, never posted from here",
"excluded_acts": ["employment-tax deposit", "employment-return filing", "money movement"],
"prepared_by": "pay-run worker (versioned; agent-prepared)",
"authorized_by": "a named party at the entity · recorded authorization",
"receipt": { "outcome": "served", "reperformable": true }
}
Two rules hold the shape together. Preparation is not payment: nothing in this deliverable deposits a tax, files a return, or moves money; the excluded acts are typed on the record itself, so the boundary travels with the artifact. And nothing changes silently under a run: workers are versioned, and the deliverable cites the version that produced it.
Everything on this slide is design, not product. The pay-run capability is entity-gated roadmap in the vertical's own offer register; no call shown here can be made today, and this deck says so rather than demoing around it.
Preparing a pay run is unreserved work. What comes after it is not, and this door draws the line exactly where the vertical's own canon draws it. Depositing employment taxes and filing employment returns on an entity's behalf engages a distinct authorization regime (a reporting-agent or payroll-agent authorization, and in some arrangements a statutory agent designation). That is a role this brand has not taken, has no entity to take it with, and does not claim: pay runs are prepared and evidenced, with the deposit and the filing left to the parties the law names. By owner law in that canon, no surface of this brand may describe it as the entity's payroll agent, and this record renders the rule as design rather than as a disclaimer.
The rest of the boundary follows the family's grain. Nothing here moves money: releasing a payment run against a bank rail is a separate act, designed in the vertical's register to sit behind the entity's own rails and a recorded dual-control authorization, and it is not offered at this door. Nothing here expresses assurance and nothing here signs: no opinion, no return, no filing, in any register. Nothing posts to the entity's books without a recorded authorization from a named party: agent workers prepare, a named human at the entity authorizes, and the entity remains the author of its own pay and its own books. The sign-off is never simulated, never defaulted, never softened into a checkbox.
payruns.co stands in the .co accounting-instrument family: five domains that each name a work product of the finance back office, with the trial balance leading, because the tie-out is where every other instrument proves out. The pay run feeds it twice: the money it moves is money the balances record, and the postings it implies are entries the tie-out must survive.
the controller
the tie-out: the period assembled, proven, and authorized · the family lead door
the accountant
entries prepared with their support attached, posted only on recorded authorization
the payroll owner
pay runs prepared and evidenced · deposit and filing left to the parties the law names
the fund controller
call notices and supporting schedules on the notice period the agreement sets
the account owner
variances surfaced against your own account names, drafted for whoever owns the account
A brand here is one ICP and one motion, distinct by rule from its siblings. trialbalance.co is keyed on the controller who owns the close: a monthly cadence, and an artifact whose reader is the reviewer. payruns.co is keyed on the payroll owner who runs the cycle: a weekly and biweekly cadence, and an artifact whose reader gets paid by it. Different chair, different clock, same register discipline; each record states the boundary, and the lead door's record carries per-door liveness evidence for the whole family.
The family's lead door serves today: the estate's own RESERVED register leaf at trialbalance.co, "Reserved for the trial balance as a work product … Nothing at this domain is live."
Two adjacent payroll artifact names are filed alongside this door in the vertical's own domain matrix, each with a recorded 301 target into payruns.co for when the suite ships, and each serving its own honest leaf today:
paystubs.click serves today: the estate's RESERVED register leaf, "Reserved for pay stubs as a work product."
certifiedpayroll.click serves today: the same register-leaf pattern, reserved for certified payroll reporting (prevailing-wage reporting) as a work product.
Primary motion is B2H2A: the entity buys, the payroll owner directs, and agent workers prepare the run under that direction, with the recorded authorization of a named human as the only path to a release. Secondary is B2A2B: the entity's own systems calling the same workers mid-cycle on its behalf. The channel matches the coordinate: the domain IS the shelf position, because a work product named at its own address is findable by the humans who produce it and the machines that will.
No motion is proven. The first entity that takes the run as a deliverable, one cycle, one payroll-data consent, one named authorizer, is the claim that matters, and it posts when it has happened.
The work behind the instrument, assembly, gross-to-net computation, tie checks, evidence filing, is precisely the work that migrates Human → Agentic → Generative → Code, and the pay cycle is the fastest metronome in the back office: a metered deliverable that recurs weekly and biweekly by definition, with no licensed-supply cost on this brand's books. What never migrates is the authorization: that stays human and named by design, which is the product's trust seam, not its cost center. And what never enters the margin at all are the reserved acts: the deposit and the filing are not performed here at any price.
Deliverable-metered, posted-card doctrine, releasing in the served-record class: the deliverable exists and is receipted, or nothing meters. The figures publish when a card is live; none is asserted before then.
Entities, cycles run, deliverables served. Not presentable until the reporting basis resolves; no figure appears in this deck before then.
This record is candid about its own status in the estate. The finance vertical's canon rules that one flagship, monthend.finance, carries the close suite, with the .co instrument names as 301 aliases "until a SKU is real"; and in that flagship's own register, the pay-run capability is the model of restraint: a name that may render while the capability may not. This record follows the lead door's election instead: trialbalance.co at the head of the instrument family, payruns.co standing behind it as the pay-run door. That election is a graduation ahead of the fin ruling, queued for ratification, not a fact accomplished by publishing a deck. If the one-flagship ruling stands, this record re-files as the pay-run section of monthend.finance and loses nothing true; if the election is ratified, the door says so at its own address first, exactly as the fin record requires.
The apex serves today and files itself honestly: "payruns.co · RESERVED · apis.finance family register … Reserved for pay runs as a work product … Payroll run preparation and evidence files, with reserved acts left to the parties the law names. Nothing at this domain is live." The live leaf and this record agree on every present-tense fact, boundary included.
The fin canon's ruled flagship, monthend.finance, also serves today: the same RESERVED register-leaf pattern. Neither door has shipped a product surface; the filing question is about which name leads, not about any live claim.
Which coordinate carries the pay run, the flagship door with the instruments as sections, or the instrument family with this door holding the payroll chair, is an open estate decision. This deck wears it openly, and no green claim above depends on the outcome.
Stated plainly: this deck precedes everything except the coordinates. No product surface has shipped at this door or any door in the family: no catalog, no card, no callable worker. The apex serves the estate's own RESERVED register leaf, filed on purpose, and every amber in this deck is deliberate: the record is built before the product, and says so.
The apis.finance hub serves today, with its own live surface and a published family map. The register filing runs one way for now: this leaf files ITSELF under the "apis.finance family register" on its own page (evidence on the apex claim above), while the hub's published family map does not yet list the books doors: a hub-side register seam this deck wears openly, queued in the estate's decision queue.
What payruns.co serves is a placeholder, not a product. The first product claim this brand can post is a real front door at its own address.
The claim that matters: an external entity's cycle, run against a scoped program: the pay run prepared, evidenced, re-performable, released on that entity's named human's recorded authorization, with deposit and filing untouched exactly as designed. It posts when it has happened, with the receipt discipline as the evidence.
This record is the front door today: the door itself is filed RESERVED at payruns.co, and says so.
If this was forwarded to you: payruns.co is the pay-run door of a family of domains named for the work products of the finance back office, led by trialbalance.co. It is designed so the artifact behind other people's pay carries its own evidence: inputs, approvals, register, and implied postings in one re-performable file, prepared by agent workers, released only by a named human at the entity, with the employment-tax deposit and the employment-return filing left, by design and by law, to the parties the law names. Nothing is live yet: the door serves an honest RESERVED placeholder, every claim in this deck carries its own state and evidence, and the brand is candidly pre-launch, including about an open filing question it would be easier not to mention. If you own a pay cycle: this record is the front door. If you know who does: forward this.