pitch.trialbalance.co
The artifact that proves a period.
A trial balance assembled and tied out as a deliverable, with evidence attached — every line resolving to its entries and support, re-performable by any reviewer, authorized by a named human at your entity. Behind it, a family of doors named for the instruments of the back office: the journal entry, the pay run, the capital call, the flux.
↓ scroll · arrow keys
Every accounting period, everywhere, must end in the same artifact: the trial balance — every account, its balance, debits equal to credits. It is the one deliverable a close cannot skip, the sheet the auditor starts from, the record the CFO's numbers stand on.
And in most closes it is produced the same way it was produced thirty years ago: exports pulled from the ledger, the billing system, and payroll; reconciled by hand in a spreadsheet; entries chased over chat; support scattered across inboxes and drive folders. The tie-out holds because one person — usually the controller — remembers why each figure is what it is. When review asks how was this figure produced, the honest answer is a person, not a record. When that person leaves, the close leaves with them.
The instruments that feed the artifact have the same shape of problem: the journal entry whose support is an email thread, the pay run whose evidence is a portal screenshot, the capital call assembled against a notice period nobody put on a clock, the flux written the night before the board meeting. Each is a work product. None is treated like one.
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 trial balance for one period, assembled from the entity's own ledger connection, tied out — debits equal credits, subledgers agree to control accounts — and evidence-attached: every line resolves to the entries behind it and the support behind those. Re-performance is the design bar: the same inputs reproduce the same figures for any reviewer at any later date.
// SPECIMEN — illustrative product mechanics, designed shape, not a live response
GET /v1/periods/{period}/trial-balance
{
"period": "…",
"basis": "accrual",
"totals": { "debits": "…", "credits": "…", "tie": "EQUAL" },
"lines": [
{
"account": "1010 · Operating cash",
"balance": "…",
"resolves_to": ["journal entries for the period", "bank reconciliation, closed on its tie-out"]
}
],
"prepared_by": "trial-balance 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 posting: agent workers assemble, compute, and draft — nothing posts to the entity's books without a recorded authorization from a named party at the entity. And nothing changes silently under a close: workers are versioned, and the deliverable cites the version that produced it.
Everything on this slide is design, not product. The worker that produces this deliverable is 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.
Each domain in this family names a work product, not a company. The trial balance leads because it is where the other instruments prove out: entries post so the balances are right, pay runs and call notices move the money the balances record, the flux explains what moved — and the tie-out is where they all have to agree.
the controller
the tie-out — the period assembled, proven, and authorized
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
Every door in the family serves today, and what each serves is the same honest thing: the estate's own RESERVED register leaf — a placeholder filed on purpose, stating plainly that nothing at the domain is live. Serving is a liveness fact, not a product claim, and each door carries its own evidence:
journalentries.co serves today: the estate's RESERVED register leaf, filed in the apis.finance family register — "Reserved for journal entries as a work product."
payruns.co serves today: the same register-leaf pattern, reserved for the pay run as a work product.
capcalls.co serves today: the same register-leaf pattern, reserved for the capital call as a work product.
fluxanalysis.co serves today: the same register-leaf pattern, reserved for flux analysis as a work product.
The instruments end where the law's reserved acts begin, and the boundary is the design rather than a disclaimer. Nothing here expresses assurance — no audit, no review, no attest opinion in any register; the deliverable is prepared for the entity, and any assurance on it belongs to a licensed firm independent of both the entity and this platform. Nothing here signs — not a return, not a filing. Pay runs are prepared and evidenced; the deposit and the filing are left to the parties the law names. Capital-call notices go out on the notice period the agreement sets — the platform prepares and delivers on the clock; it does not set the clock. And above all: the entity closes its own books. Agent workers prepare; a named human at the entity authorizes; the sign-off is never simulated, never defaulted, never softened into a checkbox.
Primary motion is B2H2A: the entity buys, the controller directs, and agent workers prepare the instruments under that direction — with the recorded authorization of a named human as the only path to a posting. Secondary is B2A2B: the entity's own systems calling the same workers mid-close 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 tie-out as a deliverable — one period, one ledger connection, one named authorizer — is the claim that matters, and it posts when it has happened.
The work behind these instruments — assembly, computation, tie-out checks, drafting — is precisely the work that migrates Human → Agentic → Generative → Code, and the close runs monthly by definition: a metered deliverable on a metronome cadence, 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.
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, periods closed, 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 sections of that one door until a SKU is real; and the fin record commits that "if one ever becomes a door of its own it will say so at its own address before it says so here." This record is the pitch-deck program's election of trialbalance.co as the lead of the instrument family — a graduation ahead of that ruling, queued for ratification, not a fact accomplished by publishing a deck. If the one-flagship ruling stands, this record re-files as the instrument 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: "trialbalance.co · RESERVED · apis.finance family register — Reserved for the trial balance as a work product … Nothing at this domain is live." The live leaf and this record agree on every present-tense fact.
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 leads the close suite — the flagship door with the instruments as sections, or the instrument family with this door at its head — 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 any door in the family — no catalog, no card, no callable worker. Every 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: each .co leaf files ITSELF under the "apis.finance family register" on its own page (evidence on the leaf claims 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 trialbalance.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 period, closed against a scoped program — the trial balance assembled, tied out, evidence attached, authorized by that entity's named human. 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 trialbalance.co, and says so.
If this was forwarded to you: trialbalance.co is the lead door of a family of domains named for the work products of the finance back office — the trial balance, the journal entry, the pay run, the capital call, the flux — designed so the artifact that proves an accounting period carries its own evidence and is re-performable by any reviewer, with agent workers preparing and a named human at the entity authorizing. Nothing is live yet: every 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 close: this record is the front door. If you know who does: forward this.