Weekly reporting with Claude on real files: projects, skills and a QA checklist
How I use Claude on real files for weekly CX reporting and campaign QA: standing project context, a checklist skill, and a person signing off.
Every Monday used to start with the same ritual: export from HubSpot, paste into a sheet, clean, chart, write three paragraphs, check the numbers twice. Claude working directly on the files changed the shape of that morning.
Before and after
The old Monday
- Export, paste and clean by hand
- Re-explain the format each week
- QA depends on who is tired
- Numbers checked twice by eye
With Claude on the files
- Claude reads the exports in the project folder
- Standing project instructions hold the format
- A checklist skill runs the same checks
- Claude lists every number it could not verify
The setup
01Projectone folder per report, with its instructions
02Inputsthis week's exports dropped in
03DraftClaude writes the summary and the charts
04Checkthe QA skill runs against the draft
05Sign-offa person reads it and sends it
What lives in the QA skill
Every number traces to a fileno number from memory
Week-on-week changes are labelledup, down or flat, with the base
Segments match the CRM definitionsVIP, churn risk, dormant, new
Customer data stays outno names or phone numbers in the summary
Unclear items are listed at the endfor the person who signs off
The skill is the part that scales. Anyone on the team can run the same report with the same checks, and the sign-off stays with a person.