Claude Cowork for marketing ops

1. 0:00 – 0:08

   Intro

   1. SPSpeaker0:00

      [upbeat music]

2. 0:08 – 0:38

   Marketing ops weekly metrics review: the workflow and deliverables

   1. SPSpeaker0:08

      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 pulls and verifies the data, and I steer the narrative. My process with Claude runs on connectors and

3. 0:38 – 0:53

   Automating the review with Claude Cowork: connectors + reusable skills

   1. SPSpeaker0:38

      skills. A skill that preps a review, a skill that proofreads it, and a skill that manages action items. Uh, 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.

4. 0:53 – 1:08

   Sunday scheduled prep: gathering context from last week + sales focus + warehouse

   1. SPSpeaker0:53

      So Claude starts the work on its own. Uh, 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

5. 1:08 – 1:38

   Monday morning check-in: reviewing takeaways and choosing the narrative focus

   1. SPSpeaker1:08

      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, uh, 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,

6. 1:38 – 1:54

   Quarter-turn example: shifting focus to Q2 plans using the QBR document

   1. SPSpeaker1:38

      "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

7. 1:54 – 2:09

   Handling inconsistencies: Claude flags gaps instead of guessing (sales reorg)

   1. SPSpeaker1:54

      it and asks questions instead of guessing the answer. So this week the sales team did tiny reorg and our reporting doesn't match theirs anymore. Claude shows me the gap and asks how I wanna handle this. [upbeat music] Um,

8. 2:09 – 2:19

   Aligning to sales reporting: choosing to “follow the sales team”

   1. SPSpeaker2:09

      "Good call. Please follow the sales team." As part of its proofreading skill, uh, Claude checks that every number in the draft traces back to a verified data source so

9. 2:19 – 2:29

   Proofreading and verification: trace every number back to a source

   1. SPSpeaker2:19

      I can feel confident about what we're reporting. The first draft is just the metrics table and headlines. I wanna make sure the outline is right before we fill it in.

10. 2:29 – 2:39

    Drafting approach: headlines first, then expand with supporting detail

    1. SPSpeaker2:29

       Once the headlines look good, uh, I tell Claude to expand them. The prep skill tells Claude to add supporting detail and examples to help the team better understand

11. 2:39 – 3:10

    Publishing and follow-through: finalize doc, Slack message, Asana tasks, leadership slide

    1. SPSpeaker2:39

       the main point while leaving the headlines we agreed on exactly the same. Once everything looks right, I say, "Ship it." Uh, Claude finalizes the document that the team will read before the review and writes the Slack message for the team channel. [upbeat music] Any follow-ups become Asana tasks so nothing falls through the cracks. Finally, Claude creates a leadership slide from the same data and narrative. It's what changed, why, what to do about it. One

12. 3:10 – 3:33

    Continuous improvement: capturing learnings and updating the skill for next week

    1. SPSpeaker3:10

       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. [upbeat music]

Episode duration: 3:34