SYSTEM BUILD

V1 operating system · client outcomes not yet measured

●  CPA firms — Deterministic Document Intake

Tax season,
without the inbox chaos.

A document-intake operating system for CPA firms: client emails are swept every 15 minutes, attachments extracted and filed into deterministic client folders, every intake logged to Sheets, and the firm notified. Designed, built, and tested in builder test runs — client outcomes not yet measured.

CPA reviewing client tax documents with the intake pipeline on screen
BY THE NUMBERS — IMPLEMENTATION FACTS
15 min

Intake sweep cadence — the dedicated intake inbox is polled every 15 minutes through the season.

13 files

Full test run processed end-to-end — extract, folders, Drive, Sheets, notify. Test evidence, not a client season.

ZIP-aware

Archives handled automatically — detected, decompressed, normalized, and merged with loose files.

1 folder

One deterministic folder per client — generated names, verified before anything uploads.

WHAT THIS COULD CHANGE IN A 150-CLIENT TAX SEASON

Illustrative model — not a measured client result.

1,000+

Documents organized — what the modelled workflow can file across a 150-client season, from roughly 450 submission emails.

<5 min

Email to organized record — illustrative intake-to-filed processing target.

40–50 hrs

Seasonal admin work — estimated manual effort potentially removed.

MANUAL INTAKE

  1. Email arrives
  2. Open inbox
  3. Download files
  4. Find or create folder
  5. Upload manually
  6. Update tracker
  7. Send receipt
  8. Remember follow-up

WITH THE SYSTEM

  1. Email arrives
  2. Files organized
  3. Tracker updated
  4. Receipt sent
  5. Firm sees next action

WHAT 40–50 HOURS REPRESENTS

At an assumed $30–$45/hour admin or bookkeeping cost, roughly $1,200–$2,250 of modelled administrative capacity — plus an estimated $4,500–$7,500 in avoided seasonal admin capacity, treated as hypothetical hiring equivalent, not money saved.

Actual results depend on client volume, workflow, document mix, and firm operating practices.

TRACEABLE INTAKE

Each document moves through Gmail, Drive, and the operational tracker with a visible record of what happened — what arrived, when, and where it went.

IndustryCPA firms — tax-season document intake
StackGmail · Google Drive · Google Sheets · n8n — installed around the firm’s existing accounts
Operating needEvery client document captured, filed into the right folder, and tracked — without manual inbox triage
Build walkthroughWatch the system build — construction demo, not outcome evidence
01 — THE OPERATING PROBLEM

Documents arrive faster than anyone can file them.

Every tax season, client documents arrive as email attachments — PDFs, phone photos, ZIP archives — spread across weeks and multiple emails per client. Somebody has to download each one, rename it sensibly, sort it into the right Drive folder, update a tracker, and chase whatever never arrived. That somebody is usually whoever has a free minute, which means it happens late, inconsistently, or not at all.

  • The inbox becomes the filing system — documents live in email threads, not folders
  • ZIP archives arrive and sit unopened because nobody has time to unpack them
  • The same document gets saved twice under two different names
  • Missing-document follow-up runs on memory and sticky notes
  • There is no record of what arrived, when, or where it went
  • The partner can’t see intake status without asking the person doing the filing
02 — THE OLD PROCESS

How it typically runs today.

CLIENT EMAILS DOCUMENTS ↓ lands in someone's inbox STAFF DOWNLOADS ATTACHMENTS (when they get to it) ↓ renamed by hand, maybe DRAGGED INTO A DRIVE FOLDER (the right one, hopefully) ↓ ZIPs skipped for later TRACKER UPDATED FROM MEMORY ↓ missing docs chased by memory FILING DEADLINE — gaps discovered late
03 — SYSTEM ARCHITECTURE

One inbox in, organized records out.

Deterministic Document Intake replaces manual triage with a scheduled sweep: a dedicated intake inbox clients send to, an n8n workflow that extracts and files everything on a 15-minute cadence, Google Drive as the document store, and Google Sheets as the audit log. Deterministic means the folder a document lands in is computed from rules, not chosen by whoever is filing that day.

DEDICATED INTAKE INBOX — clients send documents here, not to someone's inbox ↓ every 15 minutes n8n INTAKE SWEEP — fetch new mail, extract attachments ↓ ZIP DETECTION — archives decompressed, contents normalized, merged with loose files ↓ CLIENT FOLDER RESOLUTION — deterministic names, verified or created ↓ DRIVE UPLOAD — files land in the right client folder, binary + metadata verified ↓ SHEETS LOG — every intake event recorded with its source ↓ NOTIFICATION EMAIL — the firm sees what arrived ↓ EMAIL LABELLED PROCESSED — the inbox stays clean
Gmail — intake transport: the dedicated inbox clients send to n8n — workflow engine: the 15-minute sweep and all filing logic Drive — document store: deterministic per-client folders Sheets — audit log: every intake event with its source

DETERMINISTIC FILING

The folder a document lands in is computed from client identity and filing rules — the same input always produces the same folder. No judgement calls at filing time, no “I’ll sort it later” pile.

04 — INSIDE THE SYSTEM

The actual workflow.

This is the production n8n canvas — the real automation, not a diagram drawn for the website:

n8n workflow canvas: 15-minute intake sweep, attachment extraction, ZIP handling, folder generation, Drive upload, Sheets logging, notification

Scheduled sweep

Every 15 minutes the workflow polls the dedicated intake inbox for new mail. Nothing waits for a human to notice it — arrival is detected on a schedule, around the clock, through the whole season.

Extract + ZIP handling

Attachments are extracted from each message. ZIP archives are detected, decompressed, and their contents normalized — then merged with the loose files so downstream steps see one uniform set of documents.

Deterministic filing

Client folder names are generated from rules, then listed or created and verified. Files are checked — binary and metadata — before upload, so a corrupt or unreadable file never silently lands in a client folder.

Log + notify

Every intake is logged to Google Sheets with its source, the firm gets a notification email summarizing what arrived, and the processed email is labelled — the inbox stays clean by construction.

05 — CAPABILITIES

What the system does.

A dedicated intake inbox — clients send documents to one address, not to whoever’s email they remember
ZIP archives handled end-to-end — detected, decompressed, normalized, merged with loose files
Deterministic client folders — the same input always files to the same place
Files verified before upload — binary and metadata checks catch corrupt or unreadable documents
Every intake logged to Sheets — what arrived, when, where it was filed
Firm notified per intake — processed emails labelled so the inbox stays clean
06 — OPERATOR INTERFACE

What the firm sees.

Two artefacts, from a real test run — the notification email the firm receives, and the Drive folder the client’s documents land in:

Notification email: tax documents successfully processed — client ID, file count, folder name, processing date, uploaded files list

Above: the intake notification — client ID, 13 files processed, the deterministic folder name, processing timestamp, and the full uploaded-file list. One email per intake, no digging through threads.

Google Drive folder for a client intake showing deterministically named tax documents

Above: the client’s Drive folder — every file renamed deterministically (document-type_client-id), filed in one place, ready for preparation work.

TEST RUN — BUILDER’S OWN TEST ACCOUNT, NOT A CLIENT SEASON
07 — IMPLEMENTATION

Installed around the firm’s existing accounts.

StageFocusKey results
Stage 1Map the seasonDocument types, client list, folder conventions, and the firm’s current triage pain — measured before anything is installed.
Stage 2ConfigureDedicated intake inbox created, deterministic folder rules set, Sheets tracker structured, notification template approved. The firm’s existing Drive stays untouched.
Stage 3AcceptTest intake runs against the test account — ZIPs, multi-attachment emails, odd filenames — reviewed by the firm before activation.
Stage 4MeasureHonest baselines captured, then Day-30/60/90 evidence snapshots through the season. Verified, unknown, or not available — missing data never becomes zero.
08 — SAFEGUARDS

What the software can do — and what still needs a person.

ActionSystem authorityHuman requirement
Reading intake mailAutomaticIntake inbox only — never anyone’s personal mail
Filing documentsAutomatic, within client foldersDeterministic rules; firm reviews folder conventions
Deleting anythingNoneThe system never deletes mail, attachments, or Drive files
Client-facing emailNotification template onlyTemplate approved by the firm; no freeform sending
Missing documentsSurfaced, never assumedThe firm chases — the system shows what’s absent
Tax preparationNoneFiling documents is not preparing a return — preparers do that work

FAILURE HANDLING

A file that fails verification is quarantined from the upload — flagged in the log and the notification — rather than filed hopefully. The firm sees exactly which document needs attention instead of discovering it at preparation time.

09 — BEFORE / WITH SYSTEM

Operating models, compared.

LIFE WITHOUT THIS SYSTEM

  • Inbox triage by whoever has a free minute
  • ZIP archives pile up unopened
  • Folders organized by personal habit
  • Tracker updated when someone remembers
  • Missing documents discovered at the deadline
  • No record of what arrived or when
  • Status visible only to the person filing

WITH THE SYSTEM

  • Dedicated inbox swept every 15 minutes
  • ZIPs decompressed and normalized automatically
  • Deterministic folders — same input, same place
  • Every intake logged to Sheets with its source
  • Missing documents visible as they happen
  • Arrival record per file, per client
  • Notification email keeps the whole firm current
10 — WHAT ISN’T PROVEN

No bullshit.

  • A passing test run is not a tax season under load
  • A filed document is not a reviewed tax return
  • A notification sent is not proof anyone read it
  • Modelled savings are not measured savings
  • Thirteen test files are not 1,000 client documents
  • A working workflow is not a firm that has adopted it
11 — STACK & OWNERSHIP

Built on tools the firm already trusts.

Installed around the firm’s existing Google accounts — not hidden inside a Laneo black box. The firm owns its inbox, Drive, Sheets, n8n instance, and all business data.

GmailGmail Google DriveGoogle Drive Google SheetsGoogle Sheets n8nn8n
  • Gmail — the intake transport: a dedicated inbox clients send documents to
  • Google Drive — the document store: deterministic per-client folders
  • Google Sheets — the audit log: every intake event with its source
  • n8n — the workflow engine: the 15-minute sweep and all filing logic
12 — BUILD NOTES

What implementation uncovered.

  • ZIPs are the silent killer. Clients compress precisely the documents firms dread unpacking — handling archives automatically removes the most-skipped step in manual triage.
  • Deterministic naming beats clever naming. Rules produce the same folder every time; anything fancier introduces a new way for two people to file the same client differently.
  • Label-processed keeps the inbox honest. Without it, the intake inbox becomes a second archive nobody trusts — the label is what makes “swept” verifiable.
  • Verify before upload, not after. A corrupt file filed hopefully is worse than a corrupt file flagged — the check has to gate the upload.
13 — WHAT THIS MAKES POSSIBLE

Once intake is visible.

When every document is captured, filed, and logged with its source, the firm stops running tax season on memory. Preparers start with complete folders, partners see intake status without asking, and missing-document follow-up becomes a list instead of a worry. None of that is a measured claim — it’s what a visible intake operation allows.

See whether this system
fits your firm.

Book a free 20-minute Process Review. We’ll map how your intake works today, find the biggest gap, and tell you honestly whether there’s anything worth installing.

Book a Free Process Review →

The review is free. Any third-party software or usage costs remain separate.

Find your biggest leak →