WORK ARCHITECTURE — WORKFLOW MAP
DRAFT — PENDING OPERATOR REVIEW

Client Onboarding Workflow

A new client moves through proposal signature, Drive and Financial Cents setup, welcome packet, internal team handoff, and kickoff preparation. Most activities run as Claude automation against the Financial Cents API, Google Drive, and Canva; manual activities remain where no API exists.

Trigger
Triggered when a prospect accepts a quote and the Quote PDF is filed in the client's Prospective folder in Google Drive
End state
The workflow ends when the kickoff call is complete and the client enters recurring weekly and monthly service
7 phases17 processes52 core activities6 open questions
1

Pre-Signing Setup

Firm Administrator

This phase begins when an accepted quote lands in the Prospective folder. The client record, primary contact, and onboarding project are created in Financial Cents, the proposal is drafted, and the engagement goes out for signature. Ends with an External handoff from Firm Administrator to Client. Transferred: the proposal and engagement letter for signature. Acceptance criteria: the client signs and their ACH details are captured through the Bank Transfer Authorization Form, the one-time billing form.

PROCESS 1.1

Client Record Creation Process

Role

Firm Administrator

Trigger

Triggered by the accepted quote appearing in the Prospective folder

End state

Ends when the client, primary contact, and onboarding project exist in Financial Cents with admin tasks auto-assigned

PROCESS 1.2

Proposal Preparation Process

Role

Firm Administrator

Trigger

Triggered by the completed client record

End state

Ends when the engagement is out for signature with the client

2

Post-Signing Setup

Firm Administrator + Lead Accountant
External handoff in

This phase begins with an External handoff from Client to Firm Administrator. Transferred: the signed engagement PDF. Acceptance criteria: signed PDF discovered and filed to the Perm File. The client's Google Shared Drive and Financial Cents workspace are fully wired: folder structure, engagement filing, resources, portal visibility, and QBO hygiene. Clients arriving without QuickBooks Online, or on QuickBooks Desktop or Sage, run the platform setup and conversion work here before cleanup can begin. Ends when the client's digital workspace is complete and verified.

PROCESS 2.1

Drive Setup Process

Role

Firm Administrator

Trigger

Triggered by the signed engagement PDF arriving

End state

Ends when the Drive structure is complete with team manager access

PROCESS 2.2

Financial Cents Wiring Process

Role

Firm Administrator

Trigger

Triggered by the completed Drive setup

End state

Ends when the client portal is verified and the client-facing onboarding checklist is live

PROCESS 2.3

Accounting Platform Setup Process

Role

Lead Accountant

Trigger

Triggered by the signed engagement for a client without a working QuickBooks Online file

End state

Ends when the client's books live in QuickBooks Online with connected bank feeds

3

Team Assignment and Welcome

Owner + Firm Administrator
Role handoff in

This phase begins with a Role handoff within firm administration, from setup work to team assignment and welcome work. Transferred: the wired client workspace and the quote terms. Acceptance criteria: workspace verified complete. The pod is assigned against role capacity, then the tier welcome packet and email go out; pod assignment itself is only partially documented.

PROCESS 3.1

Team Assignment Process

Role

Owner

Trigger

Triggered when the client workspace is ready for welcome work

End state

Ends when the client's pod is selected for the welcome packet and team handoff

PROCESS 3.2

Welcome Packet Creation Process

Role

Firm Administrator

Trigger

Triggered by confirmed team assignment

End state

Ends when the packet PDF is in the client Perm File

PROCESS 3.3

Welcome Email Process

Role

Firm Administrator

Trigger

Triggered by the exported packet

End state

Ends when the welcome email is sent with the packet attached and the client added to staff groups in Financial Cents

4

Internal Team Handoff

Firm Administrator

This phase begins when the welcome email has gone out and the pod is confirmed. The Sales Onboarding workbook, budgeted hours, and the team handoff email are produced here; together they form the Functional handoff from Firm Administrator to the assigned service team that Phase 7 receives. Acceptance criteria: the Sales Onboarding Service resource is linked on the client's onboarding project in Financial Cents. Ends when the assigned team has everything needed to run the kickoff.

PROCESS 4.1

Sales Onboarding Workbook Process

Role

Firm Administrator

Trigger

Triggered by the sent welcome email

End state

Ends when the workbook's Sales Info and Pre-Kick-Off tabs are complete with budgeted hours per tier

PROCESS 4.2

Team Handoff Email Process

Role

Firm Administrator

Trigger

Triggered by the completed workbook

End state

Ends when the assigned team has been formally handed the client

5

Administrative Completion

Firm Administrator

This phase begins when the team handoff completes and the manual admin checklist opens; the work shifts from automated setup back to hands-on administration within Firm Administrator ownership. Entry criteria: the wired client workspace and open manual admin checklist are ready, and every manual admin item must be checked in the onboarding project. Dashboards, app access, credentials, recurring schedules, and billing verification all land here. Ends when credentials are tested, the team is notified, and fees are confirmed paid or scheduled.

PROCESS 5.1

Dashboard and App Setup Process

Role

Firm Administrator

Trigger

Triggered by the completed team handoff

End state

Ends when dashboards and apps reflect the new client

PROCESS 5.2

Credential and Schedule Setup Process

Role

Firm Administrator

Trigger

Triggered by dashboard and app setup finishing

End state

Ends when the team of three confirms working credentials in Financial Cents chat

PROCESS 5.3

Billing Verification Process

Role

Firm Administrator

Trigger

Triggered by completed workspace setup

End state

Ends when money and housekeeping items are all confirmed

6

Kickoff Preparation

Firm Administrator + Client

This phase begins when the kickoff call is scheduled; kickoff prep is largely automated within Firm Administrator ownership. Entry criteria: kickoff date, received items, and the outstanding client checklist state are available. Acceptance criteria: outstanding items read from the client checklist in Financial Cents. The kickoff prep email is rendered and sent the day before the call. In parallel the client completes their onboarding checklist in the portal. Ends when the client walks into kickoff knowing exactly what is still outstanding.

PROCESS 6.1

Kickoff Prep Email Process

Role

Firm Administrator

Trigger

Triggered by a scheduled kickoff call

End state

Ends when the client has the prep email

PROCESS 6.2

Client Checklist Completion Process

Role

Client

Trigger

Triggered by the checklist appearing in the client portal after post-signing setup

End state

Ends when every client-facing checklist item is complete

7

Kickoff Call

Lead Accountant
Functional handoff in

This phase begins with a Functional handoff from Firm Administrator to Lead Accountant. Transferred: the complete client workspace, Sales Onboarding workbook, and outstanding items list. Acceptance criteria: lead accountant schedules the kickoff from the handoff email. This phase ends the workflow when the kickoff call is held, recapped, and the client enters recurring weekly and monthly service with a 90-day call scheduled.

PROCESS 7.1

Kickoff Call Process

Role

Lead Accountant

Trigger

Triggered by the team handoff email

End state

Ends when the recap email is out and the 90-day call is scheduled

PROCESS 7.2

Client Tool Setup Process

Role

Lead Accountant

Trigger

Triggered by tool decisions made on the kickoff call

End state

Ends when the client's tools, training, and users are live

WORKFLOW MAP REVIEW

Notes & Assumptions

Sources and confidence

  • Built from the Financial Cents "Client Onboarding" template (rebuilt 2026-07-03), Jennifer Sanders' Onboard-Client-Admin Checklist CSV (2026-07-06), the Client's Onboarding Checklist template, and the "Client - Kick-Off Call" template. Activity 3.1.1 remains draft because the capacity check is only partially documented; Activity 3.1.2 is active because the pod assignment appears in real welcome and handoff artifacts.
  • Setup and conversion activities trace to the Financial Cents template family: Adding QBO Subscription (7454924), QBD to QBO Conversion (8966471), Sage to QBO Conversion (8966482), Dext Training (8573106). These are client-conditional projects TGF never carried, which is why the first drafts missed them.
  • TGF Holdings ran the March version of this workflow: created March 13, tagged "Client info received" March 30, onboarding survey and 45-day check-in in April, closed May 11 with 32 of 32 tasks and the single client task complete.
  • The whole map is marked DRAFT pending the follow-up review session (~2026-07-14).

Structure notes

  • Process 6.2 is intentionally single-activity: client-owned external work with one deliverable, running parallel to the firm's prep.
  • Process 3.2's copy/personalize/export steps are deliberately kept as separate activities: they map a Claude automation pipeline where each step is a separately checkpointed sub-skill.

Role notes

  • Firm Administrator owns phases 1 through 6 per the template's auto-assignment. Confirmed by the team's description of the role as owning "the front."
  • "Client" is used as the external party on process 6.2.
  • Team assignment must exist by phase 3 for the welcome packet; the Team Assignment Process captures the partially documented assignment mechanism.

Assumptions to verify

  • Phase ordering between 5 and 6 is inferred: the template lists manual admin items after kickoff prep, but the CSV orders prep last. Treated here as parallel tracks that both close before kickoff.
  • The onboarding project TGF received in March came from an older template than the July 3 rebuild. Differences between the two versions are not mapped.
  • 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.
  • Add-on services (bill pay, invoicing, payroll administration, sales tax) are not in the normal quote and are deliberately activated 30 to 90 days after start, with a 30-day minimum. This affects when recurring schedules get extended with add-on templates.
  • Financial Cents released an API update on 2026-07-07 that may allow automating parts of client setup; capabilities still need verification. Templates are also exportable to CSV.
  • Several onboarding steps are already automated, including Drive folder structure creation and the engagement-to-payment chain.
FOR THE MAPPING SESSION

All open questions (6)

Phase 1: Pre-Signing Setup

Jump to phase ↑
  • Q4

    The CSV's "create the onboarding project" step points at the Kick-Off Call template ID. Is that intentional chaining or a leftover to fix?

Phase 2: Post-Signing Setup

Jump to phase ↑
  • Q6

    Which current clients came from QuickBooks Desktop or Sage, and how often do conversions actually occur?

Phase 3: Team Assignment and Welcome

Jump to phase ↑
  • Q2

    Who makes the pod call for a new client, and when?

    The welcome packet needs all three roles by phase 3.

Phase 5: Administrative Completion

Jump to phase ↑
  • Q1

    Phase 5 says "set client up in various apps": which apps, and does the list vary by tier?

Phase 7: Kickoff Call

Jump to phase ↑
  • Q5

    The 90-day call now lives in the Post Cleanup template; was TGF's 45-day check-in a one-off?

Workflow-wide

  • Q3

    What changed between the onboarding template TGF ran in March and the July 3 rebuild, and why?