How I Did It: Automated Client Annotations in RevenueCloudFX

Posted by: Macenzi Barker Date Posted: September 24, 2026
Back to Case Studies

Issue

Initiatives happen – the record of them doesn’t

Signal feed toggles, tracking changes, budget shifts, site migrations – aka the things most likely to move a client’s results – happen constantly, but are scattered across TeamworkFX and Gmail with no consistent record of when. When RCFX shows a lift or a dip two weeks later, there’s no easy or quick way to check what actually changed and tie it back to these actions.

Manually annotating every relevant change, for every client, every week, doesn’t scale. So most of it never gets logged, and most results shifts go unexplained.

Solution

How the pipeline logic works

  1. Trigger –> runs weekly inside a Claude Cowork project (no manual run needed).
  2. Scan –> pulls from TeamworkFX (dedicated actionfx list & shared queue projects) and Gmail, since a lot of client-specific work doesn’t live inside that client’s own TWFX project.
  3. Classify –> filters to signal feed/integration changes, tracking changes, campaign/budget changes, and site/dev changes. Everything else is considered noise that doesn’t contribute to RCFX changes and shouldn’t be logged in the annotations.
    • I added this category rule to prevent inundating RCFX with so many annotations that we lose sight of actions that actually had impact; you can adjust the project instructions as you see fit.
  4. Map –> looks up each client’s RCFX Site ID by header name against the master sheet roster. If there’s no match, Claude won’t guess and instead routes to the architect for manual review instead.
  5. Write –> opens RCFX, fills the native “Add Chart Annotation” form, and saves it with the date of the action, not necessarily the date Claude identified it. Always marked private to FXers only.
    • Ex. Budget is changed on 08/25, but Claude’s scan on 09/01 picked up the change -> the annotation would be added on 09/01 with a back date of 08/25
    • I prefer to save as private since it is fully automated and I wouldn’t want to publish something client-facing without reviewing first, but you can edit the instructions to exclude this rule
    • Claude uses it’s best judgement on whether this may impact forms/calls/revenue, and will decide whether to apply the annotation to CTFX/LMFX/AnalyticsFX
  6. Report –> posts a Slack digest split into what got written automatically vs. what needs manual review.
    • Uses a private, custom Slack channel only I have access to

Achievement

Weekly, autonomous annotation pipeline

Developed a Claude Cowork task that runs weekly to scan TeamworkFX and Gmail across my full client roster, classifies what it finds into four result-impacting categories, and matches each finding to the right client by a site ID-based roster lookup.

High-confidence findings get written directly into that client’s RCFX profile as a private, dated annotation. Everything else lands in a Slack digest for a five-minute manual review.

All annotations are logged in the Slack thread, so there is a running, sourced paper trail connecting initiatives to results (with citations of where Claude found these insights).

The win isn’t just the automation; it’s that every annotation is now a testable claim. Two weeks after a signal feed goes live, I’m not guessing whether it mattered. I can point to the exact date it changed and read the results against it.