Last month we talked about using Claude to draft individual SOPs—the building blocks. This month, Parkins Financial zooms out because a stack of beautifully written SOPs isn’t the same thing as a workflow, in the same way that owning a full set of Lego bricks isn’t the same thing as owning a Lego castle.

Clients don’t experience your firm one document at a time. They experience it as a sequence: intake, review, approval, delivery, and follow-up. If any handoff in that sequence is unclear, the SOPs underneath it don’t matter, no matter how well each individual step is written.

This post covers:

• Why documented tasks and working workflows are two different things
• The step-by-step method Parkins Financial uses to map and validate a complete client workflow with Claude
• Common workflow failure patterns to watch for
• How this fits into the Implement. Train. approach introduced last month

The Gap Between “We Have a Process” and “The Process Works”

Most finance and accounting teams already have pieces of a workflow written down somewhere—a checklist here, an email template there, or a folder of “how we do close” notes from years ago that references systems no longer in use.

Individually, these documents may be excellent. Collectively, they often fail to create a working system because they’re missing the connective tissue between them.

Common gaps include:

• Who owns each task across departments and organizations
• What actually triggers the next step
• Where the process typically breaks down
• How exceptions should be escalated
• How information moves between systems

Without these connections, even well-written SOPs can’t prevent workflow issues.

Why Workflow Gaps Are So Easy to Miss

Workflow gaps often remain invisible because everyone involved knows their own responsibilities exceptionally well.

An AP clerk understands invoice processing.

A controller understands reviewing the close package.

The disconnect usually happens between those responsibilities, where assumptions replace documentation.

Experienced employees naturally compensate for missing workflow steps through habit and experience. Unfortunately, that knowledge rarely makes it into documentation. When those employees leave, so does the undocumented knowledge, exposing hidden weaknesses in the process.

How Parkins Financial Uses Claude to Map the Whole Workflow

1. Inventory Existing Documentation

We provide Claude with every document related to a process, including:

• SOPs
• Checklists
• Templates
• Relevant email conversations

Claude summarizes each document while identifying the required inputs and outputs for every step.

2. Find the Workflow Seams

Claude compares the output of one step with the input of the next to uncover issues such as:

• Missing approvals
• Undefined ownership
• Undocumented dependencies
• Incomplete handoffs

These hidden gaps often become the source of recurring operational problems.

3. Draft the Workflow in Plain Language

Before creating flowcharts, Claude produces a narrative version of the workflow explaining:

• What triggers each step
• Who owns it
• What happens next
• How exceptions are handled

This format makes it easier for stakeholders to review and validate the workflow before visual diagrams are created.

4. Create a Visual Workflow

Once the written workflow has been validated, Claude helps generate:

• Process maps
• Swimlane diagrams
• Client-facing workflow summaries

These visuals improve communication, onboarding, and ongoing training.

5. Pressure-Test with Real Scenarios

Rather than relying on hypothetical situations, Parkins Financial tests workflows using real historical events, including:

• Late invoices
• Missing approvals
• System outages
• Vendor documentation issues

If the documented workflow doesn’t account for these situations, it’s revised until it does.

6. Assign Ownership

Every workflow receives:

• A designated owner
• Review schedules
• Update triggers based on staffing or system changes

This ensures workflows remain accurate and effective over time.

Common Workflow Failure Patterns

As workflows are mapped, several recurring problems typically emerge.

Phantom Owner

A documented task exists, but no specific person is accountable for completing it.

Silent Dependency

One step depends on another, but no notification or trigger exists to signal when work should begin.

Orphaned Exception

An unusual situation is handled correctly only because one experienced employee knows what to do—even though it’s never documented.

Mismatched Cadence

Processes that depend on one another operate on different schedules, creating delays and confusion.

Why This Matters More Than Individual SOPs

Clients rarely complain about a missing SOP.

Instead, they notice:

• Missed deadlines
• Delayed approvals
• Poor communication
• Tasks falling through the cracks

These are workflow failures—not documentation failures.

Using Claude to build and validate complete workflows transforms “We’re organized” into “Nothing falls through the cracks.” That’s a significantly stronger value proposition for both clients and internal teams.

How Parkins Financial Supports Your Team

Workflow mapping is where the Build phase evolves into Implement.

Build

Inventory existing documentation, analyze workflows with Claude, and identify process gaps before they become larger operational issues.

Implement

Validate workflows with your team, pressure-test them against real situations, create visual documentation, and assign ownership.

Train

Once workflows are finalized, we help your team learn how to consistently follow the new process so improvements become permanent—not temporary.

A Practical Starting Point

If you’d like to begin improving your workflows, start with one process your team regularly finds frustrating.

Parkins Financial recommends:

• Choose one recurring process that frequently causes issues.
• Gather every SOP, checklist, template, and related document.
• Have Claude summarize inputs and outputs for every step.
• Validate the workflow with the people who perform it.
• Test it against real historical exceptions.
• Create a visual workflow and assign a clear owner.

Ready to Improve Your Client Workflows?

Strong firms aren’t built on individual documents—they’re built on connected, repeatable workflows.

Parkins Financial helps finance and accounting teams use Claude to design smarter workflows, eliminate bottlenecks, improve collaboration, and build systems that support long-term growth.