Auditing Your Workflows for AI Leverage
Use Claude itself to find where your agency's time actually goes
Don’t guess — audit
Most agency owners have a rough sense of where time goes: “reporting takes forever” or “onboarding is a mess.” That’s not specific enough to act on. Before you apply Claude anywhere, spend one focused session mapping your actual workflows — the steps, the handoffs, the documents produced at each stage. Claude is a good partner for this audit itself, not just for the fixes that come after it.
Run a workflow audit as a conversation
The fastest way to do this is to braindump a workflow to Claude exactly as it happens today, warts and all, and have it reflect the structure back to you. You’re not asking Claude to fix anything yet — just to help you see the shape of the process clearly.
I want to map our client onboarding process so I can find where
we're wasting time. Here's roughly what happens today, in the
order it happens, based on our last 5 onboardings:
1. Contract signed in PandaDoc
2. Account lead manually creates a folder in Google Drive
3. Someone (usually me) emails a welcome message - no template,
written fresh each time
4. We schedule a kickoff call, usually 1-2 weeks out
5. Kickoff call happens, someone takes notes in a doc
6. Notes sit in the doc, nobody reformats them into next steps
7. First deliverable is often late because nobody assigned
owners from the kickoff notes
Walk through this with me step by step. For each step, tell me:
- Is this a decision, a handoff, or a document being created?
- Where does it look like time or clarity is being lost?
- Which steps could start from a template or standard input?
Don't propose solutions yet - just help me see the process clearly first.This produces a clean map you can act on, and it usually surfaces the real bottleneck (in the example above: step 6, notes that never turn into an owned action list — which is exactly what Lesson 10 solves).
Score what you find
Once you have workflows mapped, score each step on three axes before deciding what to fix first.
| Axis | Question |
|---|---|
| Frequency | How often does this step happen — daily, weekly, once per client? |
| Pain | How much founder or senior-staff time does it eat, and how visible is the pain to the team? |
| Data sensitivity | Does this step touch client-confidential or regulated data? (See Lesson 3 before touching anything scored high here.) |
Fix high-frequency, high-pain, low-sensitivity steps first. They’re the fastest wins and the safest place to build confidence with your team before tackling anything more sensitive.
Tip: Run this audit separately for each major workflow — lead intake, onboarding, reporting, offboarding — rather than trying to map your whole agency in one conversation. Smaller, focused audits produce sharper output.
Turn the audit into a backlog, not a to-do list
Resist the urge to fix everything the week you find it. Ask Claude to turn the scored list into a prioritized backlog with a suggested owner and a rough “first draft this week” vs. “revisit next quarter” split. That backlog becomes your syllabus for the rest of this course — Lessons 5 through 11 map almost directly onto the workflows you’ll surface here.
Try it: Pick your most painful recurring workflow and run it through the prompt above, using your agency’s real steps. Save the output — you’ll use it again in Lesson 12 to build your full ops playbook.