WORK ARCHITECTURE — WORKFLOW MAP
DRAFT — PENDING OPERATOR REVIEW

Client Lifecycle Workflow

The end-to-end journey: sales and pricing, onboarding, cleanup and stabilization, then the recurring weekly and monthly service loop that runs for years, with annual compliance cycles and advisory services layered on top. Detailed maps exist for onboarding, weekly bookkeeping, month-end close, and monthly review; this map shows how they chain together.

Trigger
Triggered when a new lead reaches the firm, typically through a referral
End state
The workflow ends when a client offboards, with billing stopped, access revoked, and records archived
7 phases23 processes76 core activities12 open questions
1

Client Acquisition

Firm Administrator + Owner

This phase begins when a lead reaches the firm, nearly always through referral and occasionally through a website submission; the firm does not run paid ads. The firm administrator sends a templated screening email before discovery so non-fits can be screened out early. Qualified prospects move through a discovery call, books evaluation, tiered quote, and Loom walkthrough. Ends with a Functional handoff from Owner to Firm Administrator. Transferred: the accepted quote plus the Prospective-folder materials. Acceptance criteria: quote accepted and the firm administrator moves the Prospective folder contents into the client's shared drive.

PROCESS 1.1

Lead Intake Process

Role

Firm Administrator

Trigger

Triggered by a referral or website lead arriving

End state

Ends when a discovery call is scheduled or the lead is screened out

PROCESS 1.2

Sales Discovery Process

Role

Owner

Trigger

Triggered by a scheduled discovery call

End state

Ends when the firm can see the prospect's books

PROCESS 1.3

Pricing and Quote Process

Role

Owner

Trigger

Triggered by access to the prospect's books

End state

Ends when the accepted quote lands in the Prospective folder, which triggers onboarding

2

Onboarding

Firm Administrator
Functional handoff in

This phase begins with a Functional handoff from Owner to Firm Administrator. Transferred: the accepted quote in the Prospective folder. Acceptance criteria: quote terms extractable from the PDF. The full onboarding runs: proposal and signature, Drive and Financial Cents setup, welcome packet, team handoff, kickoff. Ends with a Functional handoff from Firm Administrator to Lead Accountant at the kickoff call, with the client entering cleanup and recurring service. Detailed in the Client Onboarding Workflow map.

PROCESS 2.1

Client Onboarding Process

Role

Firm Administrator

Trigger

triggered by the accepted quote in the Prospective folder; includes pod assignment against role capacity before welcome work; platform setup and conversion work for clients that need it (QBO subscription, QBD/Sage conversions) runs during onboarding with canonical detail in the Client Onboarding Workflow map; ends when the kickoff call is held and recurring projects are scheduled

End state

ends when the kickoff call is held and recurring projects are scheduled

3

Cleanup and Stabilization

Multiple roles
Functional handoff in

This phase begins with a Functional handoff from Firm Administrator to Lead Accountant. Transferred: the client workspace, sales onboarding workbook, and outstanding items. Acceptance criteria: kickoff held and credentials confirmed. Cleanup opens with designing the project for the specific client, then coding, reconciliation, tie-out, per-statement financial cleanup, and compliance service setup where sold; the client gets weekly updates. Long-tail follow-up items split into a post-cleanup project so the cleanup project can close cleanly. Ends with a Functional handoff from Lead Accountant to Staff Accountant into recurring service. Transferred: cleaned books and recurring-service context. Acceptance criteria: recurring projects can run against stabilized books.

PROCESS 3.1

Cleanup Design and Coding Process

Role

Lead Accountant

Trigger

Triggered by the completed kickoff and cleanup project opening

End state

Ends when the cleanup project is tailored and all transactions are coded through the current month

PROCESS 3.2

Reconciliation and Tie-Out Process

Role

Lead Accountant

Trigger

Triggered when the cleanup backlog is coded

End state

Ends when accounts are reconciled and the books are tied to the most recent available tax return

PROCESS 3.3

Financial Statement Cleanup Process

Role

Controller

Trigger

Triggered by reconciled accounts

End state

Ends when statements and account structure are clean enough for cleanup completion review

PROCESS 3.4

Compliance Service Setup Process

Role

Lead Accountant

Trigger

Triggered when cleanup surfaces a payroll, payroll-conversion, or sales-tax service need

End state

Ends when required compliance service setup or conversion projects are opened and credential needs are captured

PROCESS 3.5

Cleanup Completion Process

Role

Controller

Trigger

Triggered by clean, tied-out books

End state

Ends when the client has the cleanup-complete package and administration can close billing

PROCESS 3.6

Post-Cleanup Billing Process

Role

Firm Administrator

Trigger

Triggered by the cleanup-complete notification

End state

Ends when the final payment and post-cleanup surveys are complete

PROCESS 3.7

Post-Cleanup Follow-Up Process

Role

Lead Accountant

Trigger

Triggered by cleanup completion and the separate post-cleanup project

End state

Ends when the post-cleanup relationship checkpoint, intro sheet, and referral-source thank-you are complete

4

Recurring Service Delivery

Multiple roles
Functional handoff in

This phase begins with a Functional handoff from Lead Accountant to Staff Accountant. Transferred: stabilized books and the recurring project schedule. Acceptance criteria: recurring projects live in Financial Cents with correct dates. The engine of the business: weekly bookkeeping feeds month-end close feeds monthly review and delivery, repeating for the life of the client. Bill pay and invoicing run inside the weekly bookkeeping workflow; payroll administration, sales tax, and mixed beverage filings run as their own recurring projects in Process 4.4; standing service administration, including bill pay setup, point-of-contact changes, and periodic client audits, runs alongside the loops in Process 4.5. Add-ons are deliberately activated 30 to 90 days after onboarding. Ends only when the client moves toward offboarding; the annual compliance phase runs alongside every year.

PROCESS 4.1

Weekly Bookkeeping Process

Role

Staff Accountant

Trigger

triggered by the weekly recurring project; ends when the week's transactions are categorized, bill pay and invoicing are current where applicable, weekly reporting has been sent to subscribed clients, and unresolved review items are in front of the client

End state

ends when the week's transactions are categorized, bill pay and invoicing are current where applicable, weekly reporting has been sent to subscribed clients, and unresolved review items are in front of the client

PROCESS 4.2

Month-End Close Process

Role

Staff Accountant

Trigger

triggered by the monthly recurring project after month end; ends when the close hands to the lead accountant for review

End state

ends when the close hands to the lead accountant for review

PROCESS 4.3

Monthly Review Process

Role

Lead Accountant

Trigger

triggered by the close handoff; ends when the client has financials and notes through the portal

End state

ends when the client has financials and notes through the portal

PROCESS 4.4

Recurring Compliance Process

Role

Lead Accountant

Trigger

Triggered by recurring compliance templates for clients whose engagement includes them

End state

Ends when the required payroll, sales tax, or mixed beverage filing is complete for the period

PROCESS 4.5

Client Service Administration Process

Role

Firm Administrator

Trigger

Triggered by a client change event, the audit cycle, or the August fee review window

End state

Ends when client records, fees, and tooling reflect current reality

5

Annual Compliance

Multiple roles

This phase begins as the annual compliance cycle opens around year end. Transferred: the year's contractor payment lists, the reconciled December close, and prior-year tax-return materials. Acceptance criteria: December close complete enough to start the staged year-end review and 1099 package eligibility identified. For 1099s, the workshop recorded Basic-tier clients as excluded, while the team handoff example offers Basic clients 1099 prep available for an additional fee; working state is that 1099 filing is not included in Basic and runs only where the package includes it or the client buys it as an add-on. W-9 collection also happens opportunistically through the year. Year-end work is split between a staged multi-role review and a close-out process: lead pre-work and tie-out, staff review, lead review, controller final review, then client delivery, book lock, accountant handoff, and new-year payroll rate setup. Ends when 1099s are filed where included, year-end review is complete, the package is delivered, and the accountant AJE loop and new-year rate setup are open or complete as applicable.

PROCESS 5.1

1099 Filing Process

Role

Staff Accountant

Trigger

Triggered by year end for clients whose package includes 1099 filing or whose Basic package buys it as an add-on; the filing platform is Tax1099

End state

Ends when W-9 requests, filings, archive copies, and billing tracker updates are complete

PROCESS 5.2

Year-End Review Process

Role

Lead Accountant

Trigger

Triggered by the completed December close

End state

Ends when material balances are tax-ready and the review is complete

PROCESS 5.3

Year-End Close-Out Process

Role

Controller

Trigger

Triggered by the completed year-end review

End state

Ends when the accountant AJE loop is open and the new-year rates are set

6

Advisory Services

Controller
Functional handoff in

This phase begins with a Functional handoff from the lead accounting function into the advisory function. Transferred: delivered monthly financials for clients whose tier includes advisory. Acceptance criteria: monthly package delivered and the client ready for scheduling. In the confirmed ladder, Basic and Full Service sit below the controller advisory entitlement; the controller advisory call is Premium and above. CFO Partner adds a quarterly forward-looking CFO call and an annual budget and cash-flow forecast. A separate fractional-CFO engagement, sold on its own quote with 2 to 3 meetings a month, remains distinct and is not mapped here. Ends as a standing rhythm that continues for the life of the advisory engagement.

PROCESS 6.1

Advisory Call Process

Role

Controller

Trigger

triggered by monthly package delivery to an advisory-tier client; ends when the month's advisory call is held or the three-month skip pattern is escalated

End state

ends when the month's advisory call is held or the three-month skip pattern is escalated

7

Offboarding

Firm Administrator + Lead Accountant
Functional handoff in

This phase begins with a Functional handoff from the service team to Firm Administrator. Transferred: the decision that service is ending and the last service date. Acceptance criteria: administrator notified after final financials are sent. Billing stops, recurring work stops, access unwinds everywhere, and records archive. The firm deliberately keeps offboarding human-led with minimal AI involvement because terminations are sensitive. This phase ends the workflow when the final survey is out, the QuickBooks subscription is transferred, and the client folder is in Inactive.

PROCESS 7.1

Service Termination Process

Role

Firm Administrator

Trigger

Triggered by an offboarding decision

End state

Ends when nothing further will be charged or produced for the client

PROCESS 7.2

Access Removal Process

Role

Lead Accountant

Trigger

Triggered by the last client service date passing

End state

Ends when the firm holds no access to client systems

PROCESS 7.3

Archive and Exit Process

Role

Firm Administrator

Trigger

Triggered by completed access removal

End state

Ends when the relationship is formally closed with feedback captured

WORKFLOW MAP REVIEW

Notes & Assumptions

Sources and confidence

  • Phase 1 is now validated by the 2026-07-07 workshop and is no longer a one-call reconstruction.
  • Phase 3 was restructured per the workshop and the Client - Cleanup and Client - Post Cleanup templates.
  • Phase 6 is grounded in workshop testimony: advisory-tier service is part of the standard quote, while fractional CFO is a separate workflow.
  • Phases 2 through 5 and 7 trace to Financial Cents templates: Client Onboarding, Kick-Off Call, Cleanup, Post Cleanup, recurring loop templates, 1099 End of Year, Tax Returns, and Client Offboarding.
  • Setup, conversion, and client-admin template family folded in 2026-07-08: Adding QBO Subscription, QBD/Sage conversions, Bill Pay Set-up (QBO and Bill.com), Payroll Conversion, Point of Contact Change, Client Audit. These are client-conditional projects TGF never carried.
  • TGF Holdings validates the chain end to end: created March 13, onboarding closed May 11, cleanup opened March and still open, roughly ten weekly instances, three month-end closes, three reviews, plus open Tax Returns, 1099s, and two Vendor Cleanup projects.
  • The whole map is marked DRAFT pending the follow-up review session (~2026-07-14).

Structure notes

  • Processes 2.1, 4.1, 4.2, 4.3, and 6.1 are reusable process references; their canonical definitions live in the detailed workflow maps. Activities shown here are summaries, not re-definitions.
  • Process 2.1 intentionally carries seven summary activities. That is acceptable here because the canonical onboarding map carries the detailed seven-phase process.
  • Phase 4 runs continuously and phase 5 annually; the linear phase order flattens what is really a loop with an annual overlay.
  • Old advisory draft activities for separate reporting, strategy, and quarterly CFO calls were removed. The monthly advisory call is canonical in the Monthly Client Review Workflow; CFO cadence belongs to a separate future workflow.

Role notes

  • Phase 1 screening is owned by the firm administrator; discovery and pricing are owned by senior/owner roles. A second senior accountant also runs discovery calls.
  • Pods equal staff, lead, and controller, with a CFO added when sold. People float across roles by client complexity.
  • Controller ownership of the Financial Statement Cleanup Process is tentative: the cleanup template assigns chart-of-accounts cleanup to the Lead Accountant while the workshop described statement cleanup as controller-level judgment; both positions logged.
  • Process 4.4 role follows the FC template roles: Payroll Administration, OK Sales Tax Filing, and Mixed Beverage Return all carry Lead Accountant; staff involvement unconfirmed.
  • Thirteen users exist in Financial Cents; the definitive user-to-role mapping remains a session question.

Assumptions to verify

  • Function split applied (2026-07-07 workshop): staff accounting, lead accounting, controller accounting, CFO, and advisory are mapped as distinct functions, so handoffs between them are typed Functional. The full split was confirmed by the operator on 2026-07-08 (staff accounting and lead accounting are their own functions); the earlier decision-record wording that kept staff/lead role-level is superseded.
  • Cleanup to recurring service was originally described by the team as a role handoff within the pod, but the full function split makes Lead Accountant to Staff Accountant a Functional handoff in this map.
  • Stale Financial Cents projects are expected: open projects can be long-tail follow-ups, not remaining work. Any agent consuming Financial Cents state needs explicit staleness rules.
  • Capacity management runs through an internal capacity app pulling QuickBooks Time against expected role utilization and budgeted hours per client. The workshop placed budgets in the master tracker, while the team handoff email example draws budgeted hours from the per-client Service Fee Template refined by the lead after kickoff; the relationship between those two homes remains open in Q7. The app is being rebuilt as a Claude-designed dashboard; the platform name was unintelligible in the transcript, possibly Base44. A Capacity App Hours Update template exists. This is a firm-internal workflow and out of scope for the client lifecycle map.
  • Fractional CFO services are a separate workflow to map later.
  • The recurring service loop is assumed identical across tiers except for the advisory call and client-conditional add-ons; tier differences may run deeper.
  • Future idea, not a constraint: replace email-reply screening with an intake form that auto-creates the Prospective folder and tracker entry (workshop; explicitly not current-state).
  • 1099 improvement direction (future-state): move the current spreadsheet work into dedicated Financial Cents W-9 and 1099 projects, with year-round collection and AI support for client emails and W-9 chase.
  • Engagement-level: every activity AI will assist requires explicit exit/validation criteria before automation (Claude-does / Codex-reviews pattern).
  • The 2026 Paxus 1099 workbook is the current source for Process 5.1; no separate step-by-step training documents arrived in the folder.
  • Cleanup-template tasks "Add Paxus' monthly draft recurring expense to QBO" and "Add internal notes template to FC Notes" are SOP-level detail inside 3.1.1/3.1.2, not separate activities.
  • TGF sits in three different staff client groups simultaneously (and one named person is absent from the user list), so pod assignment conventions need explaining.
FOR THE MAPPING SESSION

All open questions (12)

Phase 1: Client Acquisition

Jump to phase ↑
  • Q7

    Budgeted hours appear in both the workshop's master tracker position and the handoff-email Service Fee Template example refined by the lead after kickoff. Which is canonical, is the capacity app platform Base44, and should budgeted hours move there long-term?

    The transcript rendered the platform name unintelligibly; Base44 is the best guess.

Phase 3: Cleanup and Stabilization

Jump to phase ↑
  • Q9

    Confirm the "Client Overview Questionnaire" (video intro + per-client operating context) is the client intro sheet the Post Cleanup template refers to.

Phase 4: Recurring Service Delivery

Jump to phase ↑
  • Q12

    Who runs the client setup audit (template 13564745) and on what cadence?

Phase 5: Annual Compliance

Jump to phase ↑
  • Q8

    The 1099 filing platform is confirmed as Tax1099. Does Tax1099's API cover the vendor W-9 request step (the automation candidate from the workshop)?

  • Q10

    The 1099 workbook archives filed forms to Dropbox ("1099's Filed in Dropbox") while everything else lives in Google Drive - is Dropbox an active archive or legacy naming?

  • Q11

    Walk the Tax Returns template (7959692): what does the firm actually do for client tax returns versus the outside tax accountant?

Phase 6: Advisory Services

Jump to phase ↑
  • Q4

    Map the fractional CFO workflow as its own engagement (separate quote, 2 to 3 meetings a month, cross-function participation). When?

Workflow-wide

  • Q1

    Tier ladder confirmed from the July 2026 quote and handoff examples: Basic -> Full Service -> Premium -> CFO Partner. Where does the "Platinum" label in the review template fit (legacy name or live tier), and is the cleanup assessment's "Tier 1 (Simple)" vocabulary a separate cleanup-complexity scale?

  • Q2

    Map the thirteen Financial Cents users to roles: the role map is known from the session, but the definitive user-to-role roster is still needed.

  • Q3

    Who is TGF's pod today?

    The client sits in three different staff groups and one group's name matches no current user.

  • Q5

    Multi-entity relationships: the quote example prices two entities on one quote with one team ("monthly financial statements (both entities)"), and 1099 billing consolidates related entities ("Billed with apartments"). How are the relationships structured in Financial Cents and QuickBooks?

  • Q6

    The Client Overview Questionnaire captures most per-client variables (method, software, payroll provider, classes, receipts policy, deposit rules, intercompany). Is it the canonical capture doc, and what does the team track that it misses (billing rail, bank account counts, tier, pod)?