Claude Cowork · Anthropic
Build the weekly sales KPI report from Slack, CRM and meeting notes
A sales team manager at Japanese IT firm Classmethod set up Claude Cowork to compile the weekly sales activity report that used to be gathered by hand from several tools. It now runs on a schedule every Monday morning.
What they did
Cowork was connected to the Slack channel where reps post daily reports, to HubSpot for deals and activities, and to a Google Drive folder of weekly team meeting notes. A Markdown file defined the KGIs, KPIs and report layout (deal highlights, won deals split into new customers and expansions, meetings, new leads, proposals). The workflow was saved as a skill and scheduled for 9:30 every Monday.
How it went
The author says the manual weekly aggregation work disappeared, along with the counting mistakes that came with it. No time savings are quantified.
Worth knowing
Vague instructions pulled in off-topic Slack chatter until the channel, timing and fields were spelled out, and Claude had to ask for the exact HubSpot property names. The author warns that a KPI-only summary can hide process work that does not show up in the numbers.
Try it with Claude Cowork
Every Monday at 9:30, read last week's posts in <your daily report Slack channel>, the deals and activities in <your CRM>, and the meeting notes in <your weekly notes folder>. Build a weekly sales report using the KPI definitions in <your KPI definition file>: highlights, won deals split by new customers and expansions, meetings held, new leads and proposals sent. Ignore casual chat, and ask me if a CRM field name is unclear.
We wrote this prompt from the case. Replace the parts in angle brackets with your own details.
What this label means: User reports
Someone using it at work posted about it. Any numbers are theirs, so we write "the poster says".
Real cases of AI agents at work, from every major agent, each linked to where it was first reported. Rewritten in our own words, most with a prompt you can try. These are not Wize customers.