- Ian, who runs marketing ops and analytics, shows how Claude Cowork automates his weekly metrics review — producing a detailed doc for the marketing team and a one-slide summary for leadership that previously meant pulling data from a half-dozen places.
- His process runs on connectors and skills: a skill to prep the review, a skill to proofread it, and a skill to manage action items, which together capture the process so it runs the same way each week and can be shared with the team.
- A scheduled task does the prep on its own every Sunday evening; Ian then steers the narrative on Monday, has Claude flag mismatches and verify every number to a source, ships the doc and Slack message, creates an Asana task for follow-ups, and feeds the week's learnings back into the skill.
Claude Cowork for marketing ops
- The weekly metrics review has two outputs: a detailed doc with full detail for the marketing team and a one-slide summary for leadership, which used to require pulling data from a half-dozen places.
- Ian's process runs on connectors and skills: a skill that preps a review, a skill that proofreads it, and a skill that manages action items — together these capture the process so it runs the same way each week and can be shared with the team.
- A scheduled task runs every Sunday evening: it reads last week's review and the meeting transcript, checks Slack for what sales is focused on, and queries the warehouse, leaving a folder with the numbers and a few suggested focus areas by Monday morning.
- Claude pulls the numbers, but the human steers the narrative and decides the focus — some weeks responding to a sales priority, a product launch, or, in this case, the quarter turn and the team's Q2 plans.
- The prep skill makes Claude flag mismatches and ask questions instead of guessing — for example, when a sales-team reorg made reporting no longer match, Claude showed the gap and asked how to handle it.
- The proofreading skill checks that every number in the draft traces back to a verified data source, so the team can be confident in what's reported; drafting starts with the metrics table and headlines, then expands once the outline is approved.
- On "ship it," Claude finalizes the doc, writes the Slack message for the team channel, turns follow-ups into Asana tasks, and creates the leadership slide (what changed, why, what to do); finally Ian asks Claude what to learn into the skill for next week, and updates the shareable skill so anyone can run it.
Claude Cowork — Anthropic's workspace where Claude does multi-step work like preparing and proofreading a weekly metrics review.
Skill — A reusable definition that captures a process (prep, proofread, manage action items) so it runs the same way and can be shared.
Connectors — Integrations (Slack, the data warehouse, Asana) that let Claude pull and push data across tools.
Scheduled task — An automation that runs Claude's prep on its own, here every Sunday evening.
Metrics review — Ian's weekly deliverable: a detailed doc for the team and a one-slide summary for leadership.
Warehouse — The data warehouse Claude queries for the week's numbers.
Hi, I'm Ian. My job is marketing ops and analytics, which means I help the marketing team market better with the help of data. Every week I put together a metrics review containing a doc with full detail for the marketing team and a one-slide summary for our leadership. This used to be pulling data from a half-dozen places. With Claude Cowork, I drop in the week's context, Claude verifies the data, and I steer the narrative.
My process with Claude runs on connectors and skills. A skill that preps a review, a skill that proofreads it, and a skill that manages action items. Together, the skills capture the process so I can run it the same way each week and share the process with the team. I'll show you.
So Claude starts to work on its own. Every Sunday evening, a scheduled task reads last week's review and the meeting transcript, checks Slack for what the sales team is focused on, queries the warehouse. Claude leaves me with a folder containing the numbers and a few suggested focus areas. So on Monday morning, I open Cowork. "Good morning, Claude. How did the prep go?" And the takeaways and suggested focus are waiting.
Claude's really great at pulling the numbers, but it is up to me to steer the narrative and make the call on focus. Some weeks we're responding to a sales priority, some weeks a product launch. This week we're at the quarter turn, so we should spend some time on the team's plans. "Um, let's focus on Q2 plans this week. Can you review the QBR doc?" I drop in the quarterly review doc and tell Claude what to lead with. As part of the prep skill, when something doesn't line up, Claude flags it and asks questions instead of guessing the answer. So this week the sales team did a tiny reorg and our reporting doesn't match theirs anymore. Claude shows me the gap and asks how I want to handle this. "Good call. Please follow the sales team."
As part of its proofreading skill, Claude checks that every number in the draft traces back to a verified data source, so I can feel confident about what we're reporting. The first draft is just the metrics table and headlines. I want to make sure the outline is right before we fill it in. Once the headlines look good, I tell Claude to expand them. The prep skill tells Claude to add supporting detail and examples to help the team better understand the main point, while leaving the headlines we agreed on exactly the same.
Once everything looks right, I say "ship it." Claude finalizes the document that the team will read before the review and writes the Slack message for the team channel. Any follow-ups become an Asana task so nothing falls through the cracks. Finally, Claude creates the leadership slide from the same data and narrative. It's what changed, why, what to do about it.
One last thing. I ask Claude what we learned during this week's process that should go into the skill for next week. That new sales team structure, the corrections I made — all get saved. Claude updates the skill, and because it's a skill, I can share it with the team so anyone can run it, get the same results, and dive deeper using Claude Cowork.
TL;DR
- Ian, who runs marketing ops and analytics, shows how Claude Cowork automates his weekly metrics review — producing a detailed doc for the marketing team and a one-slide summary for leadership that previously meant pulling data from a half-dozen places.
- His process runs on connectors and skills: a skill to prep the review, a skill to proofread it, and a skill to manage action items, which together capture the process so it runs the same way each week and can be shared with the team.
- A scheduled task does the prep on its own every Sunday evening; Ian then steers the narrative on Monday, has Claude flag mismatches and verify every number to a source, ships the doc and Slack message, creates an Asana task for follow-ups, and feeds the week's learnings back into the skill.
Takeaways
- The weekly metrics review has two outputs: a detailed doc with full detail for the marketing team and a one-slide summary for leadership, which used to require pulling data from a half-dozen places.
- Ian's process runs on connectors and skills: a skill that preps a review, a skill that proofreads it, and a skill that manages action items — together these capture the process so it runs the same way each week and can be shared with the team.
- A scheduled task runs every Sunday evening: it reads last week's review and the meeting transcript, checks Slack for what sales is focused on, and queries the warehouse, leaving a folder with the numbers and a few suggested focus areas by Monday morning.
- Claude pulls the numbers, but the human steers the narrative and decides the focus — some weeks responding to a sales priority, a product launch, or, in this case, the quarter turn and the team's Q2 plans.
- The prep skill makes Claude flag mismatches and ask questions instead of guessing — for example, when a sales-team reorg made reporting no longer match, Claude showed the gap and asked how to handle it.
- The proofreading skill checks that every number in the draft traces back to a verified data source, so the team can be confident in what's reported; drafting starts with the metrics table and headlines, then expands once the outline is approved.
- On "ship it," Claude finalizes the doc, writes the Slack message for the team channel, turns follow-ups into Asana tasks, and creates the leadership slide (what changed, why, what to do); finally Ian asks Claude what to learn into the skill for next week, and updates the shareable skill so anyone can run it.
Vocabulary
Claude Cowork — Anthropic's workspace where Claude does multi-step work like preparing and proofreading a weekly metrics review.
Skill — A reusable definition that captures a process (prep, proofread, manage action items) so it runs the same way and can be shared.
Connectors — Integrations (Slack, the data warehouse, Asana) that let Claude pull and push data across tools.
Scheduled task — An automation that runs Claude's prep on its own, here every Sunday evening.
Metrics review — Ian's weekly deliverable: a detailed doc for the team and a one-slide summary for leadership.
Warehouse — The data warehouse Claude queries for the week's numbers.
Transcript
Hi, I'm Ian. My job is marketing ops and analytics, which means I help the marketing team market better with the help of data. Every week I put together a metrics review containing a doc with full detail for the marketing team and a one-slide summary for our leadership. This used to be pulling data from a half-dozen places. With Claude Cowork, I drop in the week's context, Claude verifies the data, and I steer the narrative.
My process with Claude runs on connectors and skills. A skill that preps a review, a skill that proofreads it, and a skill that manages action items. Together, the skills capture the process so I can run it the same way each week and share the process with the team. I'll show you.
So Claude starts to work on its own. Every Sunday evening, a scheduled task reads last week's review and the meeting transcript, checks Slack for what the sales team is focused on, queries the warehouse. Claude leaves me with a folder containing the numbers and a few suggested focus areas. So on Monday morning, I open Cowork. "Good morning, Claude. How did the prep go?" And the takeaways and suggested focus are waiting.
Claude's really great at pulling the numbers, but it is up to me to steer the narrative and make the call on focus. Some weeks we're responding to a sales priority, some weeks a product launch. This week we're at the quarter turn, so we should spend some time on the team's plans. "Um, let's focus on Q2 plans this week. Can you review the QBR doc?" I drop in the quarterly review doc and tell Claude what to lead with. As part of the prep skill, when something doesn't line up, Claude flags it and asks questions instead of guessing the answer. So this week the sales team did a tiny reorg and our reporting doesn't match theirs anymore. Claude shows me the gap and asks how I want to handle this. "Good call. Please follow the sales team."
As part of its proofreading skill, Claude checks that every number in the draft traces back to a verified data source, so I can feel confident about what we're reporting. The first draft is just the metrics table and headlines. I want to make sure the outline is right before we fill it in. Once the headlines look good, I tell Claude to expand them. The prep skill tells Claude to add supporting detail and examples to help the team better understand the main point, while leaving the headlines we agreed on exactly the same.
Once everything looks right, I say "ship it." Claude finalizes the document that the team will read before the review and writes the Slack message for the team channel. Any follow-ups become an Asana task so nothing falls through the cracks. Finally, Claude creates the leadership slide from the same data and narrative. It's what changed, why, what to do about it.
One last thing. I ask Claude what we learned during this week's process that should go into the skill for next week. That new sales team structure, the corrections I made — all get saved. Claude updates the skill, and because it's a skill, I can share it with the team so anyone can run it, get the same results, and dive deeper using Claude Cowork.