Recurring deliverables · document tooling

Work.

The recurring deliverables and document tooling that Goroshi LLC ships every month. Every figure on this page traces to a source file in the operator's archive.

Scale

Numbers that ship every month.

Residential doors

~90

McHenry County + adjacent

Recurring documents

~6

Per calendar month

Workers on roster

7

Vetted residential trades

Recent restaurant month

$433K

20,421 customers, 31 days

Recurring document deliverables

Six packets, every month, on time.

Each runs on its own renderer with locked design tokens. New month, new data, same Apple-tier output in one command. Every renderer is re-runnable, every PDF is vector, every dollar traces.

MonthlyRestaurantTo accountant

Restaurant sales packet.

Single-page PDF with daily sales breakdown, third-party delivery reconciliation, credit-card deposit tracking, customer counts. Ships with companion CSV (line-item review) and IIF (QuickBooks Desktop import). Cadence: by the fourteenth.

  • Hero recommendation: monthly total + 3-up summary (total / customers / avg per day)
  • 31 daily rows with day-of-week + tabular-number column alignment
  • Explicit reconciliation strip: gross + Mojo + tax + third-party = total
  • Provenance footer with source CSV hash and render date
MonthlyReal estateTo property entity

Per-property labor invoice.

Multi-page Apple-tier invoice covering every door under contract at the locked monthly rate. Net 15 terms, ACH remit-to block, full line-item breakdown.

  • Page 1 hero: amount due, property count, due date
  • FROM / BILL TO addresses validated against config — renderer fails loudly if any address field is still placeholder
  • Red "OPERATOR ACTION REQUIRED" banner if any fill markers remain — can't ship trash
  • 3-page layout with totals block on the final page, remit instructions below
MonthlyReal estateTo owner

Rent roll consolidation.

Single-page summary of every door, every lease, every payment status. Owner sees the whole book on one page each month: who paid, who's late, who's mid-renewal, who turns over next.

  • One row per property, sortable columns: door / tenant / rent / status / lease-end
  • Aging buckets: current / 1-30 / 31-60 / 60+ days late, color-coded hairlines
  • Roll-up totals: occupied %, expected gross monthly, actual collected, variance
As neededReal estateDecision document

Lease decision brief.

Two-page Apple-tier brief for owner review when a major lease decision lands. Driven by a Monte Carlo NPV analysis (10,000 paths, seed-locked for reproducibility) with explicit amendment-by-amendment value tables.

  • Page 1: hero recommendation, 3-up summary, decision matrix (Drafted vs Amended), top-5 amendments
  • Page 2: full amendment ranking, risk profile, 4-option signature-ready decision checkboxes
  • Reproducible via documented seed and renderer script — quarterly refresh on demand
QuarterlyReal estateTo owner

Per-property operating review.

One short PDF per property showing maintenance history, expense ratios, lease expiry calendar, and recommended actions. Owner can read the whole book in under thirty minutes.

  • Per-property hero card: address, current tenant, current rent, lease expiry
  • 12-month expense trail by category (HVAC, plumbing, roofing, landscaping, other)
  • Recommended action: renew / re-list / capital improvement / hold
AnnualRestaurantTo CPA

Year-end tax-prep packet.

Rolled-up monthly packets into a single year-end summary with sales-tax filings cross-referenced. CPA opens one file and has everything they need for the return.

  • 12 monthly packets indexed in a cover table
  • Sales tax filings reconciled month-by-month against state remittance records
  • Year-over-year comparison: gross, sales tax, third-party, customer count

Tooling

How the documents get built.

Every recurring document type has a dedicated Python renderer with locked design tokens (Helvetica, ink/muted/hairline palette, hero-three-up-table hierarchy). The data lives in canonical JSON + CSV files. The renderer reads the data and emits a vector PDF.

New month, new data, same Apple-tier output — one command. No Word templates. No Excel exports. No copy-paste. The renderer is the design system. The data is the truth. The PDF is the artifact.

Renderers fail loudly when data is missing or inconsistent. Sums cross-check against subtotals. Placeholder fields surface in red banners on the rendered output so unfilled drafts can't accidentally ship.

If any of this fits

Direct correspondence only.

Short email with what you have and what you need. One operator on the other end. Response within one business day.