What happens today
The patchwork
- A gut feeling that some clients cost more than they pay
- Utilization reports nobody reconciles against billing
- Write-offs discovered a quarter too late
- Every partner with a different theory and no proof
Inspector playbook
Find the margin leaks
$340K recovered, in an afternoon.
- 5 min read
- Intermediate
- 4 moves
- Run quarterly
The number
You walk into the ops review knowing exactly where the money is going and which three fixes recover the most.
$340K a year
The situation
From a hunch that money is leaking to a map of exactly where.
Hand Inspector your project data, team hours, and billing. A swarm of specialists digs into each corner (scope creep, under-billed hours, projects that quietly run past budget) and the lead consultant hands back one report on where the margin is going and what to do about it.
With Inspector
The workflow
- One analysis across projects, hours, and billing at once
- Every leak traced back to the row it came from
- A prioritized list, biggest recoverable dollar first
- You walk into the ops review knowing exactly where the $340K is.
How the work moves
Four moves.
Inspector runs each move in the open: you watch the specialists work and see the evidence behind every finding before it reaches the final report. Skip freely once you know which parts carry the weight.
Inspector at work
One brief travels through the whole job. Context stays attached until the finished work lands.
Kickoff
Tell Inspector what a healthy margin looks like for your business.
Inspector starts with your target and asks only for what it needs. No intake form, no kickoff call: just the goal and where the data lives.
Gather
Point it at your project data, time tracking, and invoices.
A team of specialists pulls each source, cleans it, and cross-checks it against prior quarters. Every number carries a citation back to the row it came from.
Reason
Let the specialists find where the money slips.
Each agent goes deep on one domain (scope, utilization, rates, write-offs) and thinks out loud where it matters. Assumptions surfaced, trade-offs named, every leak ranked by recoverable dollars.
Deliver
Read the one report. Take it to the ops review.
The lead consultant synthesizes every finding into one prioritized strategy, in the format your team already reads. You act on the top three, not sift through forty tabs.
Prompts worth keeping
Paste these into Inspector.
Three prompts: a kickoff, a full run, and a packaging pass. Copy the one that matches the phase you're in. Rewrite any detail to fit your business.
Kick it off
You are Inspector. I want to find the margin leaks in my services business: read my project data, team hours, and billing, and tell me exactly where money is slipping through. My goal: walk into the ops review knowing where roughly $340K a year is going and how to recover it. Walk me through the first move and tell me what you need from me.
Run it in one shot
Run the full playbook end-to-end: tell me what a healthy margin looks like, then point yourself at my project data, time tracking, and invoices. Assign a specialist to each domain (scope creep, under-billed hours, projects over budget, write-offs), cross-check against prior quarters, and rank every leak by recoverable dollars. Ask before skipping any step. Show your work as you go.
Package the output
Deliver the output as a single report I can take to the ops review: lead with "$340K a year", then the receipts behind each leak, ranked biggest first. Call out anything that changed assumptions mid-run and cite the row each number came from.
What goes in. What comes back.
Inputs in, outputs out.
Inspector runs on the inputs on the left and hands back the artifacts on the right. Skip any input, the specialists will ask for it the first time they need it.
Give it
- Project data (PM tool, spreadsheet, or export)
- Team hours from time tracking
- Billing and invoice history
Get back
- One prioritized report, every leak cited
- A ranked list of recoverable dollars
- A structured file you can hand to finance
The finished artifact
A finished analysis, not a pile of spreadsheets.
Every run ends the same way: one packaged report in the channel your team already reads. Here's a preview of what shows up.
Inspector → your team
Margin leaks found, ranked and ready to review
playbooks
Thu 9:12 AM
Here's this quarter's margin analysis. I ran the specialists across projects, hours, and billing, flagged what shifted against last quarter, and packaged the findings for the ops review: top recoverable dollars first.
- Tell Inspector what a healthy margin looks like for your business.
- Point it at your project data, time tracking, and invoices.
- Let the specialists find where the money slips.
- Read the one report. Take it to the ops review.
What moved
$340K a year
You walk into the ops review knowing exactly where the money is going and which three fixes recover the most.
margin-report.pdf · leaks.csv · summary.key
Before you run it
Where teams stall.
Three ways we see this go sideways and how to avoid each one.
Keep judgment with the team. The playbook should make the work clearer, not hide the assumptions behind it.
- Pointing Inspector at one source and hoping. The leaks hide between systems: give it projects, hours, and billing together or the picture stays half-lit.
- Running it once and shelving the report. Put it on a quarterly cadence so the fixes hold and new leaks surface before they compound.
- Chasing every finding at once. Inspector ranks by recoverable dollars for a reason: act on the top three, then re-run.
Questions
Before you start.
Project records, team hours, and billing history: those three together are where margin leaks live. You can start with exports or a spreadsheet paste for the first pass; connect the tools of record once you want it to run on its own each quarter.
Your PM tool shows one system in isolation. Inspector assigns a specialist to each domain (scope, utilization, rates, write-offs) and the lead consultant synthesizes them into one strategy, so you see leaks that only appear when hours, projects, and billing are read against each other.
Every finding is traceable to the row it came from, and the specialists surface their assumptions as they work rather than burying them. Review the first run against a project you know cold: once the receipts check out, the trust compounds from there.
Quarterly is the sweet spot: often enough to catch leaks before they compound, spaced enough that each run has real change to analyze. Inspector keeps context across runs, so every quarter it flags what shifted instead of starting from scratch.
