Full Intake and Operational Blueprint

This is the paid intake that follows the free snapshot. It is where the real diagnostic work starts.

When this is used

Only after the snapshot has been reviewed, a paid diagnostic is approved, and the client is moving into the deeper intake phase.

What this intake covers

  • Detailed business baseline and stakeholder context
  • Current accounting, payroll, invoicing, and operational software
  • Books-behind condition and cleanup depth
  • Current workflow, handoffs, and control gaps
  • Desired outcomes, reporting needs, and decision-use cases

What is requested from the client

  • Last 3 months of bank statements
  • Last 3 months of credit card statements
  • Accountant-level access to current bookkeeping software
  • List of recurring subscriptions and known problem areas
  • Supporting records specific to payroll, tax, POS, or inventory if applicable

Detailed intake sections

1. Business baseline

Business structure, leadership contacts, team size, CPA relationship, and timing pressures.

2. Software stack

Accounting platform, other tools, versions, integrations, and where the stack is fighting itself.

3. Current friction

Broken processes, document chaos, bottlenecks, recurring leaks, and compliance pain points.

4. Workflow reality

Who handles what today, where tasks stall, and what is falling through the cracks.

5. Desired future state

Reporting expectations, operating rhythm, preferred cloud platform, and what a usable system should feel like.

What comes out of it

Operational findings

Clearer diagnosis of where the bookkeeping and back-office problems actually live.

System direction

Whether the current stack should be cleaned up, replaced, or reconnected.

Option A / Option B roadmap

A structured plan for cleanup, migration, support, or staged implementation.

Ready-to-scope engagement

The intake becomes the basis for pricing, service agreement prep, and kickoff.

Where this fits in the process

The free snapshot stays short. The full intake carries the detail. That separation keeps the front-end conversion clean and gives the paid diagnostic phase the depth it needs.