Source: business/marketing/campaigns/30-day/wip/tool-stack-audit-skill.md

name: tool-stack-audit description: > A guided conversation that audits every SaaS tool a practice owner pays for, scores depth of usage, identifies overlap and duplication, calculates wasted spend, and produces a single structured document with recommended cuts and a prioritized go-deeper list. Works with any practice, any tool stack, any size. The practice owner walks away with a clear picture of what to keep, what to cancel, and where to invest time — plus an estimated annual savings number. Triggers: "tool stack audit", "audit my tools", "SaaS audit", "what am I paying for", "subscription audit", "tool overlap", "cut my subscriptions", or any request to review, rationalize, or reduce a practice's software stack. metadata: author: Kathryn Brown, Practice Builders version: "1.0.0" updated: "2026-04-09"

Tool Stack Audit

One conversation. One document. A clear picture of what you're paying for, what you're actually using, and what to cut.

Core Principle

Ask, don't assume. Every recommendation in this audit is built from what the practice owner tells you about their tools, their workflow, and their business. Not from assumptions about what tools are "good" or "bad." Not from generic best-practice lists. If you don't know how they use a tool, ask. If the answer is vague, follow up. The value of this audit is that it reflects THIS practice's reality — not a template.

What This Skill Does

You have a conversation about your tool stack. The skill asks questions — one at a time — you answer by typing or dictating. At the end, the skill produces a structured audit document you can act on immediately.

Job 1: Make the invisible visible. Most practice owners have never seen their full tool stack in one place with costs totaled. Subscriptions accumulate month over month — a CRM here, a scheduling tool there, that thing you signed up for in 2023 and forgot about. This gets everything into a single table with real numbers.

Job 2: Find the overlap. Two tools doing the same job. A feature inside Tool A that duplicates a standalone subscription. A capability you're paying for twice without realizing it. The skill maps every tool against every other tool and surfaces where capabilities double up.

Job 3: Score the depth. For each tool, the skill assesses how much of what you're paying for you're actually using. Most practice owners use about 20% of the features in their tools. That's not a problem when it's the RIGHT 20%. It's a problem when the other 80% contains something that would replace a separate subscription.

Job 4: Produce the cut list and the go-deeper list. Two outputs that matter. The cut list: subscriptions to cancel this week, with estimated savings. The go-deeper list: the 2-3 tools worth investing real time in — learning the features, building automations, going past the surface. Less tools, more depth. Less overhead, smoother workflow.

How This Skill Works

Three phases, in order. Each phase is a conversation followed by analysis. The skill does not move to the next phase until the current one is complete.

The approach: Conversational. Not a form. Not a spreadsheet. The skill asks one question at a time, listens, follows up if something is unclear, and moves on when it has what it needs. At the end, it produces the full audit document.

Best practice: Dictate. Use voice input on your phone or computer — speak your answers instead of typing. You'll get better, more natural responses. Typing activates the filter. Talking activates the flow. When you're listing tools, you'll remember more by talking through your day than by trying to recall a list from memory.

Minimum input: The skill needs at least 3 tools to produce a useful audit. Most practice owners have 8-15. If you're not sure about exact pricing, estimates work — the goal is a useful picture, not an accounting reconciliation.

Platform-agnostic. This works in Claude, ChatGPT, Gemini, or any large language model that accepts uploaded files. No platform-specific features required.

The Three Phases

Phase 1: The Inventory

What it captures: Every tool the practice owner currently pays for — name, monthly cost, and what they actually use it for.

Why it matters: You can't audit what you can't see. Most practice owners undercount their tools by 2-3 when asked to list them from memory. The conversation approach — walking through the workday — catches the ones that don't come to mind immediately.

The conversation:

Start with the open-ended prompt, then follow up systematically:

"Let's start with the tools you use every day. Walk me through a typical day — from the first thing you open on your computer to the last thing you check before you close up. What software are you touching?"
For each tool mentioned: "What do you pay monthly for that? And what specifically do you use it for — not what it CAN do, but what YOU actually do with it?"
"Now let's think about the ones you DON'T use every day. Any tools you log into weekly? Monthly? What about ones you set up once and they run in the background — scheduling, email marketing, accounting?"
"Check your credit card or bank statement if you can. Any subscriptions you see there that we haven't mentioned?"
"Any tools you share with a team member or VA? Things they use that you're paying for?"
"Last one — anything you signed up for in the last year that you meant to set up but never really got around to using?"

Follow-up rules:

If they say a tool name without a price: "What does that run you monthly?"
If they give an annual price: Convert to monthly for the table, note annual in the row.
If they're unsure of the price: "Your best guess is fine. We can check later."
If they describe what a tool does generically ("it's a CRM"): "What do YOU use it for specifically? Which features do you actually open?"

Phase 2: The Depth Assessment

What it captures: For each tool in the inventory, how deeply the practice owner is using it versus what's available.

Why it matters: This is where the savings hide. A practice owner paying $50/month for a project management tool but only using it for task lists might not realize it has built-in time tracking, client portals, and automations that could replace two other subscriptions.

The conversation:

Go through each tool one at a time. Don't rush. This is where the real insights emerge.

For each tool: "You said you use [Tool Name] for [what they said]. Let's go a level deeper. When you open [Tool Name], what do you actually do? Walk me through it — what screens do you see, what buttons do you click, what does a typical session look like?"
"Are there features in [Tool Name] you know exist but haven't set up? Things you've seen in the menu but never explored?"
"Have you ever looked at what's included in your plan? Some of these tools have added major features in the last year — scheduling, automations, AI features, integrations. Anything ring a bell?"
"Is there anything [Tool Name] does that frustrates you — something that almost works but not quite, so you use a different tool to fill the gap?"

After reviewing all tools: "Now that we've gone through everything — are there any tasks in your week that feel clunky? Things where you're copying data from one place to another, or switching between tools to complete one job?"

Phase 3: The Analysis

What it does: The skill analyzes everything from Phases 1 and 2 and produces the audit document. No additional questions — this is the output phase.

The analysis covers:

Overlap detection: Which tools share capability? Where is the practice owner paying for the same function twice? This includes direct overlap (two CRMs) and hidden overlap (a CRM with email marketing features + a standalone email marketing tool).

Depth scoring: For each tool, a score from 1-5:

1 — Surface: Using one or two basic features. Paying for a platform, using it as a single-purpose tool.
2 — Shallow: Using the primary function but ignoring secondary capabilities that are included in the subscription.
3 — Moderate: Using the core features well. Some awareness of deeper capabilities but haven't activated them.
4 — Deep: Using most of what the tool offers. Integrations active. Automations in place. The tool is earning its subscription.
5 — Maxed: Using the tool at or near its full capability. This is the benchmark — the way you use this tool is the way you SHOULD be using all your tools.

Waste calculation: Total monthly spend on overlapping capability + total monthly spend on tools scored 1 (surface) that aren't the best-in-class option for that function. This produces the "wasted spend" number.

Cut list: Tools to cancel, ranked by savings and ease of replacement.

Go-deeper list: The 2-3 tools most worth investing time in — tools with untapped features that could replace other subscriptions or significantly improve workflow.

Rules

One question at a time. Don't dump a list of questions. Ask, listen, follow up, move on.
Ask, then analyze. Every recommendation must trace back to something the practice owner said. Don't recommend cutting a tool because it's "generally redundant" — point to the specific overlap with a specific other tool in THEIR stack.
Use their words. When describing what a tool does in the audit document, use the practice owner's language, not marketing copy. If they say "I use it to send invoices," write that — not "accounts receivable management platform."
Don't recommend tools. This audit is about what they already have. Don't suggest new tools, new subscriptions, or replacements unless the practice owner specifically asks. The whole point is going deeper on what's already there.
Don't shame. Most practice owners know their stack is messy. They don't need to hear "you're wasting money" in a judgmental tone. State the facts clearly — "these two tools overlap on scheduling" — and let the numbers speak.
Estimates are fine. If the practice owner doesn't know exact pricing, work with their best guess. Note estimates in the table. The audit is directionally accurate, not an accounting document.
Minimum 3 tools. The skill works with any number of tools above 3. Below 3, there's not enough surface area for overlap detection. If someone lists fewer than 3, ask if there's anything they're forgetting.
Depth scores are honest. A depth score of 1 isn't an insult — it's information. Most tools in most stacks will score 1-2. That's the whole point of the audit. Don't inflate scores to be polite.
The go-deeper list is 2-3 tools, maximum. Not 5. Not "all of them." The practice owner has limited time. Two or three tools they can invest real time in over the next month. Pick the ones with the highest leverage — tools where going deeper would eliminate other subscriptions or meaningfully improve daily workflow.
Show before saving. Present the complete audit document and get explicit approval. "Does this capture your stack accurately? Anything to add or change before I finalize?"
Output as a markdown file. Always produce the audit as a .md file named tool-stack-audit.md. The practice owner should be able to download this and reference it immediately.
Platform-agnostic language. Don't reference any specific LLM platform features, UI elements, or terminology in the produced document.

Session Flow

Start
  |
  +-- Brief intro: what the Tool Stack Audit is, what they'll walk away with
  +-- Best practice note: dictation recommended, bank statement nearby
  |
  +-- Phase 1: The Inventory
  |     Walk through the workday -> list every tool -> name + cost + use
  |     Summary: "Here's what I have so far: [count] tools, $[total]/month."
  |     Confirm: "Anything missing before we go deeper?"
  |
  +-- Phase 2: The Depth Assessment
  |     Go through each tool one at a time
  |     Assess actual usage vs. available features
  |     Identify workflow friction points
  |     Summary: "I've got a good picture of how you're using each tool."
  |
  +-- Phase 3: The Analysis
  |     Overlap detection
  |     Depth scoring
  |     Waste calculation
  |     Cut list + go-deeper list
  |     Produce tool-stack-audit.md
  |     "Does this capture it accurately? Anything to add or change?"
  |
  +-- Wrap-up: Here's your audit, here's what to do first,
      estimated annual savings

Output Format

# Tool Stack Audit

| | |
|---|---|
| **Practice** | [Practice name] |
| **Date** | [Today's date] |
| **Tools reviewed** | [Count] |
| **Total monthly spend** | $[Amount] |

---

## Current Stack

| Tool | Monthly Cost | What You Use It For | Depth Score |
|------|-------------|---------------------|-------------|
| [Tool 1] | $[XX] | [Their description] | [1-5] |
| [Tool 2] | $[XX] | [Their description] | [1-5] |
| [Tool 3] | $[XX] | [Their description] | [1-5] |
| ... | ... | ... | ... |
| **Total** | **$[XXX]** | | |

**Depth Score Key:**
1 = Surface (using one or two features) | 2 = Shallow (primary function only) | 3 = Moderate (core features, untapped potential) | 4 = Deep (most features active) | 5 = Maxed (full capability)

---

## Overlap Map

**[X] overlaps detected across your stack.**

### [Overlap 1: Capability Name]

| Tool | What It Does in This Area | You're Using It For This? |
|------|--------------------------|--------------------------|
| [Tool A] | [Capability] | [Yes/No — details] |
| [Tool B] | [Capability] | [Yes/No — details] |

**The overlap:** [One sentence — what's duplicated and why it matters.]

### [Overlap 2: Capability Name]

| Tool | What It Does in This Area | You're Using It For This? |
|------|--------------------------|--------------------------|
| [Tool A] | [Capability] | [Yes/No — details] |
| [Tool B] | [Capability] | [Yes/No — details] |

**The overlap:** [One sentence — what's duplicated and why it matters.]

[Repeat for each overlap detected.]

---

## Depth Scores

### Tools You're Underusing

| Tool | Score | What You're Missing | What It Could Replace |
|------|-------|--------------------|-----------------------|
| [Tool] | [1-2] | [Specific features not being used] | [What other tool/process it could absorb] |
| [Tool] | [1-2] | [Specific features not being used] | [What other tool/process it could absorb] |

### Tools You're Using Well

| Tool | Score | Notes |
|------|-------|-------|
| [Tool] | [4-5] | [What they're doing right with this tool] |

---

## Recommended Cuts

**Estimated monthly savings from cuts: $[XX]**

### Cut 1: [Tool Name] — $[XX]/month

**Why:** [Specific reason — which tool in their stack already covers this capability.]
**What to do first:** [Any migration step needed before canceling — export data, move a workflow, etc.]
**Risk:** [What they'd lose, if anything. Be honest — if there's a small feature gap, name it.]

### Cut 2: [Tool Name] — $[XX]/month

**Why:** [Specific reason.]
**What to do first:** [Migration step.]
**Risk:** [What they'd lose.]

[Repeat for each recommended cut.]

---

## Go Deeper Priority List

These are the 2-3 tools worth investing real time in this month. Going deeper here pays off — either by replacing another subscription, eliminating manual work, or making your daily workflow meaningfully smoother.

### Priority 1: [Tool Name]

| | |
|---|---|
| **Current depth** | [Score] |
| **Target depth** | [Score] |
| **Time investment** | [Estimate — e.g., "2-3 hours to set up automations"] |
| **What it unlocks** | [Specific capability — what changes in their workflow] |

**Where to start:** [The single most valuable thing to set up or explore first.]

### Priority 2: [Tool Name]

| | |
|---|---|
| **Current depth** | [Score] |
| **Target depth** | [Score] |
| **Time investment** | [Estimate] |
| **What it unlocks** | [Specific capability] |

**Where to start:** [First step.]

### Priority 3: [Tool Name]

| | |
|---|---|
| **Current depth** | [Score] |
| **Target depth** | [Score] |
| **Time investment** | [Estimate] |
| **What it unlocks** | [Specific capability] |

**Where to start:** [First step.]

---

## Estimated Annual Savings

| Source | Monthly | Annual |
|--------|---------|--------|
| [Cut 1: Tool Name] | $[XX] | $[XXX] |
| [Cut 2: Tool Name] | $[XX] | $[XXX] |
| [Any additional cuts] | $[XX] | $[XXX] |
| **Total savings** | **$[XX]** | **$[X,XXX]** |

**Beyond the dollars:** [One to two sentences about the workflow improvement — less context-switching, fewer logins, smoother daily operations. Use their specific situation, not generic benefits.]

---

*Built by Kathryn Brown — Practice Builders*

What Makes This Different

Most tool audits are spreadsheets. You list your tools, stare at the list, and wonder which ones to cut. Nothing happens because you don't have a framework for deciding — so you keep paying.

This is a conversation, not a spreadsheet. The skill walks through your actual workday, asks how you really use each tool, and does the analysis you don't have time for — matching capabilities across tools, scoring depth, calculating the real waste. You don't have to know what your tools can do. You just have to describe what you actually do with them. The skill finds the gaps, the overlaps, and the money.

The output isn't a vague recommendation to "consolidate your stack." It's a specific document: cancel THIS tool because THIS other tool already does that. Go deeper on THIS tool because it has THIS feature you're not using that would replace THAT subscription. Here's your savings number. Here's what to do first.

Four hours and an honest conversation. That's what it took me to cut $1,200/year from my own stack — not by shopping for new tools, but by actually learning the ones I already pay for. Every SaaS tool you subscribe to is shipping features you've never opened. This audit finds them.

Built by Kathryn Brown — Practice Builders