Every services business leaks revenue. The client asks for "one small thing," the account manager says yes, the team does the work, nobody bills for it. Repeat across 30 clients and the leak is real money. The industry benchmark is 5-15% of revenue, which on a $5M agency is $250k-$750k a year.
The problem is detection. Scope drift does not show up on a dashboard. It is buried in email threads, hidden in delivered-but-not-invoiced work, and scattered across SOWs nobody has reread in six months.
Connecting Google Drive, Gmail, and QuickBooks to Claude through CorpusIQ turns scope drift detection from a theoretical good practice into a monthly audit that actually runs.
Why scope drift is invisible
Three reasons it hides.
First, the leak happens in writing, but the writing is distributed. The SOW is in Drive. The "quick favor" request is in email. The delivery happened on a Zoom call. The invoice that should have included the extra work is in QuickBooks, and the extra line never got added. No single system contains the evidence.
Second, scope creep feels like good client service. Saying yes builds goodwill. Billing for every micro-request feels petty. Account managers who want repeat business default to absorbing the work.
Third, auditing for it is tedious. Reading every SOW, scrolling every email thread, cross-referencing invoices. Nobody has time. So it never gets done.
The scope drift audit, reframed
The audit logic is simple. For each active client:
- What does the SOW commit to?
- What has the client asked for in email since the SOW was signed?
- What has actually been billed in QuickBooks?
- Where is the gap between promise, request, and invoice?
Doing this manually for one client takes an hour. For twenty clients, nobody does it.
Doing it with Claude takes five minutes per client.
The prompt
For each active client, ask Claude:
Pull the most recent SOW for [CLIENT NAME] from Drive. Summarize the scope.
Then search Gmail for the last 90 days of emails with anyone from [CLIENT DOMAIN].
List any requests, commitments, or deliverables mentioned that are not explicitly
in the SOW.
Then pull the last 6 months of invoices for [CLIENT NAME] from QuickBooks.
Summarize what was billed and the total.
Compare. Flag: (1) work mentioned in email that does not match the SOW,
(2) work mentioned in email that has no corresponding line item in any invoice,
(3) any pattern suggesting recurring out-of-scope work.
Claude synthesizes the three sources. The output is a list of specific items to investigate: "Email dated May 3 from client requesting additional landing page review, not referenced in SOW, no invoice line item found. Possible uncompensated scope expansion."
Act on each one. Either bill for it, document it as a relationship investment, or build a change order template and use it going forward.
What to do with the findings
Three outcomes for any flagged item.
Bill for it retroactively. Some clients are fine with a "we forgot to invoice this" conversation. Most are, if the work was genuinely delivered and the amount is reasonable.
Document it as an intentional investment. If you chose not to bill as a goodwill gesture, at least know you did. Unseen investments compound into resentment.
Change the process upstream. Repeated flags for the same client or the same type of work are a process signal. Build a change order requirement into your engagement.
How to set it up
- Sign up at corpusiq.io. Solo $29.95/month covers all three connectors.
- Connect Google Drive (for SOWs), Gmail (for client emails), QuickBooks Online (for invoices).
- Add CorpusIQ MCP to Claude.
- Run the audit prompt client by client, monthly or quarterly.
Running it at scale
For agencies with 30+ clients, the audit becomes a time commitment even with Claude's speed. Two strategies.
Quarterly rather than monthly. The leak rate does not change much month to month. A thorough quarterly audit catches most of what a monthly audit would and takes 25% of the time.
Tiered prioritization. Run the audit in full on your top 20% of clients by revenue. Run a spot-check (SOW versus invoice only, no email scan) on the rest. The revenue leak is Pareto-distributed; the top clients account for most of it.
What this does not catch
Some scope leakage is invisible even to this audit.
Uncompensated time in internal meetings about client work. Not captured in email or invoices.
Over-servicing that stays within scope. If the SOW allows for "reasonable revisions" and your team does 14 revisions, that is scope absorbed, not scope drift.
Goodwill work done in person or on calls with no written record. Nothing for Claude to query.
The audit catches the writing-based leakage. Which is most of it, at most services businesses.
See also
FAQ
How much revenue does the average services business leak to scope creep?
Informal industry surveys put it between 5% and 15% of gross revenue, depending on how disciplined change orders are. Agencies at the upper end are the norm, not the exception.
Can this replace a project management discipline?
No. It catches leakage after the fact. You still need scope discipline upstream. What this adds is a monthly audit that flags what slipped through.
Which connectors do I need at minimum?
Drive for SOWs, one email source (Gmail or Outlook), and QuickBooks. All three are necessary to triangulate.