Back-office · Finance · Ops

Stop assembling reports on Sunday night.

The work that quietly eats the owner's week — bookkeeping, billing prep, weekly rollups, exception triage — is exactly the work AI handles best when it is wired into the tools your team already uses. Three real builds below.

What is running

Three back-office systems we have built.

Build 1 · Bookkeeping

TillerBot

Bank-feed reconciliation, transaction categorization, and tax-prep-ready ledgers. Multi-account support, runs nightly, flags anything that needs an owner's eye instead of asking for one weekly.

  • · Daily bank-feed refresh
  • · Auto-categorization with override log
  • · Tax prep export, end-of-year ready
Build 2 · Ops dashboard

Command Center

Internal ops dashboard that monitors services, queues, and key business metrics in one place — the same pattern we drop into client engagements when the answer to “is it working?” needs to be one glance.

  • · One screen, real numbers
  • · Alerts on drift, not noise
  • · Owner-friendly, not engineer-only
Build 3 · Weekly rollups

Airtable + 365 rollups

Pulls the week's activity from CRM, calendar, billing, and project tools — drafts the Monday rollup so the team is reviewing it instead of writing it. Ships to email, Slack, or Notion.

  • · Drafted by AI, signed off by a human
  • · Exceptions called out, not buried
  • · Same template, every week, no nagging

Owner time back

The owner stops being the report-assembly bottleneck on Sunday night and Monday morning.

Fewer missed exceptions

Because exceptions are surfaced, not hidden in a spreadsheet that nobody opens.

Cleaner books

Categorization done daily, not in a panic during tax week.

Stack we have shipped against

AirtableNotionGoogle WorkspaceMicrosoft 365QuickBooksStripeHubSpotSlackPostgresFly.ioHetzner

Pick the work that owns your Mondays.

The audit looks at the back-office work eating the most owner time and tells you which slice is worth modeling first.

Start the intake →