An Invoice Dispute Taught Me to Scope Differently

A client disputed an invoice for roughly ten extra hours on a GTM audit, arguing the work fell within the original scope. I genuinely believed it didn't. We went back and forth for two weeks, and the frustrating part was that both of us were arguing in good faith — the scope document itself just wasn't specific enough to adjudicate who was right.

The original scope said 'audit the existing tagging implementation and document findings.' Reasonable-sounding sentence. Completely useless for settling a dispute, because it doesn't define what counts as part of the audit versus what counts as a separate remediation task discovered during the audit. I'd found and partially fixed three broken tags along the way, treating it as helpful initiative. The client read 'document findings' as including any fixes I made in the process of finding them.

What the dispute actually cost

We settled it, eventually, splitting the difference — which satisfied nobody and ended a relationship that had been going well up to that point. The money mattered less than the trust it cost. A client who's had one invoice argument with you reads every future invoice more skeptically, even after the dispute is resolved.

A vague scope line doesn't prevent disputes. It just guarantees the dispute happens after the work instead of before it.

• Scope documents now explicitly separate 'audit and document' from 'fix anything found during the audit' as distinct line items with separate authorization
• Any work outside the explicit scope gets a one-line written confirmation before I do it, even if it seems obviously beneficial
• Time tracking now includes a short note per entry tied to a specific scope line, not just a total, so a dispute six weeks later has something concrete to check against
• I now flag ambiguous scope language back to the client during scoping, specifically asking 'does this include X or not' instead of assuming my reading is shared

The lesson wasn't about billing more carefully. It was about writing scope documents specific enough that a dispute, if one happens anyway, has an actual document to settle it instead of two reasonable people arguing from two reasonable readings of the same vague sentence.