Your customer blames implementation. Your CSM says they went live. Now what?

It's the most common standoff in B2B SaaS: the customer says the implementation never worked, your customer success manager says they went live in Q3, and the invoice sits in the middle, unpaid, while two departments argue about who's right.

We see this dispute constantly—and the resolution is almost never found in the argument. It's found in the handoff record.

The handoff record decides

Somewhere between the sales handoff and the go-live celebration, there's a document trail that settles the question. If your CSM can produce it, the dispute is already half-won:

• The scope document—what was promised at signing, in writing
• The acceptance sign-off—the email or portal click where the customer acknowledged go-live
• The training record—who attended, when, and what was covered
• The ticket history—what problems were actually raised, and whether they were resolved
• The usage record—if users logged in after go-live, the platform worked well enough to use
• The date it changed—the exact day "not ready" became "won't pay"

The most powerful single document is the acceptance. A customer who signed off on go-live and then uses the platform for three months before claiming it never worked has a credibility problem—and the file knows it.

What actually happened (usually)

In our experience, the "implementation failed" dispute is rarely a lie and rarely the whole truth. What usually happened: the implementation hit a snag, someone didn't escalate, the champion left or got distracted, and the invoice aged into a convenient grievance. The customer isn't evil; they're just human—and humans retroactively justify unpaid invoices.

That's why the collector's job isn't to referee an argument about implementation quality. It's to rebuild the timeline—what was delivered, what was accepted, what was used—and let the customer's own usage history make the case. Nobody argues with their own login logs.

How to keep it from happening next time

The prevention is boring and cheap: get the acceptance in writing at go-live, record the training, and keep the tickets. Companies that do this have a 90-second answer to the "it never worked" objection. Companies that don't have a six-month dispute.

The short version

When the customer blames implementation and your CSM says they went live, don't referee the argument—pull the handoff record. Scope. Acceptance. Training. Tickets. Usage. The file will tell you who's right, and it will tell the debtor why they're paying. And if the file has holes, that's the lesson: the next contract's acceptance sign-off is cheaper than the next dispute.