How I Did It: Turning a Data Issue into a Proactive Client Win

Posted by: Macenzi Barker Date Posted: November 11, 2026
Back to Case Studies

Issue

The AM flagged that our client’s October 2026 revenue looked far below October 2025: 104 closed-won deals and about $1.3M last year, versus 8 RCFX deals and ~$300K this year. The client was not worried at this point, so we didn’t want to create a fire where there wasn’t one. I used our internal huddle to find out whether the gap was real.

It wasn’t a performance problem. It was three data issues:

  • Four October 2026 closed-won deals were in the CRM but missing from RevenueCloudFX, most likely because the sales team hadn’t updated their statuses before the monthly export ran.
  • The October 2025 baseline was inflated. When uploads switched from lead ID to deal ID, many records existed twice. Only 28 of 87 CRM closed-sold jobs matched true closed-won statuses (32%).
  • Paid search pipeline was empty, because most CRM records sat at “New Lead” contact status and never moved to the “Open” or “Working Sales Process” deal status. New Lead does not create a deal in Revenue CloudFX.

The client’s reports for current-month data were mostly right. The year-over-year comparison was what was off, and that was our side to fix. We didn’t want to wait to loop in the client in the event they started digging deeper into the reports and could flag the discrepancies before we addressed them directly.

Now, the real issue -> how do I effectively communicate this to the client without causing panic or creating more work for them?

Solution

The approach

I brought the client an issue we had already found and were already fixing, and I asked for only one small thing in return. The message conveyed “here is what we found, here is what we’ve done about it, and here is the one thing that helps.” That order is what kept it calm.

How I did it

  1. Diagnosed before writing anything. I compared the raw CRM export against the RevenueCloudFX deal stage mapper, so I could show exactly why the counts differed.
  2. Fixed what I could before contacting the client. I re-uploaded any missing October deals, submitted a developer task to remove the duplicate records, and planned a 2025 year-to-date backfill to correct YoY reports.
  3. Fixed the process, not just the data. Some deals were missed because the monthly export ran before the sales team updated statuses. Alicia and I moved the upload to the 5th, which still lands the day before her NinjaCat reports are run.
  4. Aligned with the Account Manager on the story. Alicia and I agreed on the framing: your current reports are right, the year-over-year deltas will shift, and no action is needed from the client beyond a sales team reminder. Alicia also mentioned that our POC doesn’t work in the CRM, so I drafted a sales team email for him.

How the message was built

Each choice in the email was made to lower the temperature while staying accurate.

  • Reassurance first. The second paragraph opens with “Good news: it’s all very fixable, and the only thing we need from you is a quick note to your sales team.” The client knows the ask is small before reading any detail.
  • Findings in plain terms, with the fix attached. Every issue is paired with what was done: “I’ve re-uploaded them,” “our developers are removing them and will reprocess 2025.” Nothing is left as an open problem.
  • Neutral cause for the missed deals. I wrote that the deals “hadn’t been updated yet when our monthly upload ran.” That is a timing issue, not blame. The duplicates are framed as our side: “when we switched our data uploads from using lead ID to deal ID.”
  • Told him what he’d see. One line warns that year-over-year numbers may look slightly different starting in November, and that current-month data is now accurate. No surprise later.
  • Two numbered asks. Pass along the email, and update sales data by the 5th. Short and easy to say yes to.
  • Account Manager copied. Alicia raised the flag, so cc’ing her showed the loop was closed on her question too.

The email for the client’s sales team

I wrote the email Tim could forward as-is. That took the work off his plate, and it let me speak at the sales team’s level instead of his. This is the version I included:

Subject: Action needed: CRM status updates by the 5th of each month

Hi team,

To make sure our marketing reporting reflects the work you’re doing, please follow these two steps in the CRM moving forward:

Once a lead has a Deal ID, change its status from “New Lead” to “Open” or “Working Sales Process.” Leave a record as “New Lead” only if it is truly new and has no Deal ID yet, as records in the “New Lead” status don’t show up in our pipeline reporting.
Make sure all sales for the prior month are entered and updated by the 5th of every month. That’s when we pull data for reporting, and anything not updated by then gets left out.
These updates will help us show the full impact of your sales efforts.

Thank you,
Tim

Why it works:

  • It is signed by Tim, so he can copy, paste and send with no edits.
  • It gives two steps with the exact status names, so the sales team doesn’t need to ask what “open” means.
  • It explains the reason once (pipeline reporting), and ends on what’s in it for them: showing the full impact of their sales efforts.

Achievement

The achievement is not the email itself. A client who wasn’t asking questions yet was about to see an October comparison that looked like a drop of about $1M, and the cause was our data, not their sales. Instead of waiting for that question, we found the cause first, fixed our side, and fixed the upload timing so it doesn’t repeat.

It also surfaced a gap the client didn’t know about: paid search pipeline could never be reported while records sat in a certain CRM status. The client now owns that fix, and offered on his own to reinforce it with dealers in his next marketing communication. The client responded with thanks and gratitude, not concern!

Snippet/Screenshot/Link

Here’s the full email I sent to our POC:

Hi Tim,
I hope your week is going well!

Alicia raised a flag on the October year-over-year numbers, so I took a closer look at the data behind them.

Good news: it’s all very fixable, and the only thing we need from you is a quick note to your sales team.

Here’s what we found:

  • Four October closed-won deals were in your CRM but hadn’t been updated yet when our monthly upload ran. I’ve re-uploaded them, and we can regenerate the October reports once the cleanup is done.
  • The October 2025 comparison was inflated by some duplicate records from when we switched our uploads from lead ID to deal ID at the end of last year. Our developers are removing them and will reprocess 2025 so everything lines up.
    • Note: You may see slightly different year-over-year numbers starting in November, but the current-month data is now accurate
  • Paid search pipeline reporting is empty right now because most records are still marked “New Lead” in the CRM and never move to an ‘open’ project sales status.

Here’s where we could use your help:

  • Could you pass along the email below to your sales team? It explains how to update statuses so your pipeline shows up in reporting.
  • We’ve moved our monthly upload date to the 5th, so sales data must be updated in the CRM by then to be included in our monthly reports.

—
Subject: Action needed: CRM status updates by the 5th of each month

Hi team,

To make sure our marketing reporting reflects the work you’re doing, please follow these two steps in the CRM moving forward:

Once a lead has a Deal ID, change its status from “New Lead” to “Open” or “Working Sales Process.” Leave a record as “New Lead” only if it is truly new and has no Deal ID yet, as records in the “New Lead” status don’t show up in our pipeline reporting.
Make sure all sales for the prior month are entered and updated by the 5th of every month. That’s when we pull data for reporting, and anything not updated by then gets left out.
These updates will help us show the full impact of your sales efforts.

Thank you,
Tim

—

Please let me know if you have any questions!
Macenzi

And this was the client’s response:

That’s great news, thanks Macenzi!