CHAPTERS
- 0:08 – 0:38
Marketing ops weekly metrics review: the workflow and deliverables
Ian explains his role in marketing ops/analytics and the recurring weekly metrics review he produces. The output includes a detailed doc for the marketing team and a one-slide summary for leadership, which previously required manual data gathering from many sources.
- •Role: improve marketing performance using data
- •Weekly cadence: metrics review every week
- •Two deliverables: detailed doc + leadership one-slide summary
- •Old process pain: pulling data from ~6 different places
- 0:38 – 0:53
Automating the review with Claude Cowork: connectors + reusable skills
He introduces Claude Cowork as the system that now runs much of the process. The workflow is encoded into multiple “skills” so it’s repeatable weekly and shareable across the team.
- •Claude Cowork uses connectors to access needed systems/data
- •Skills encode the repeatable process
- •Key skills: prep the review, proofread the review, manage action items
- •Standardization makes it easier to run and share the workflow
- 0:53 – 1:08
Sunday scheduled prep: gathering context from last week + sales focus + warehouse
A scheduled task kicks off each Sunday evening to prepare Monday’s review. Claude reads the prior review and meeting transcript, checks Slack for sales priorities, and queries the data warehouse, then organizes outputs into a folder.
- •Scheduled automation runs Sunday evening
- •Inputs: last week’s review + meeting transcript
- •Context check: Slack to see what sales is focused on
- •Data pull: queries the warehouse and compiles results
- •Output: folder with numbers and suggested focus areas
- 1:08 – 1:38
Monday morning check-in: reviewing takeaways and choosing the narrative focus
Ian starts Monday by asking Claude how prep went and reviewing the suggested takeaways. Claude can surface metrics well, but Ian emphasizes that humans still decide the storyline and priorities for the week.
- •Ian reviews Claude’s takeaways/suggested focus areas
- •Claude excels at pulling and summarizing numbers
- •Narrative steering remains Ian’s responsibility
- •Focus varies by week (sales priority, product launch, etc.)
- 1:38 – 1:54
Quarter-turn example: shifting focus to Q2 plans using the QBR document
This week’s context is a quarter transition, so Ian decides the review should emphasize Q2 plans. He provides the QBR doc and instructs Claude what to lead with.
- •Decision: focus this week on Q2 planning at the quarter turn
- •Input: quarterly business review (QBR) doc
- •Directing Claude: explicit guidance on what to lead with
- •Combines performance reporting with forward-looking planning
- 1:54 – 2:09
Handling inconsistencies: Claude flags gaps instead of guessing (sales reorg)
During prep, Claude detects a mismatch between marketing reporting and the sales team’s new structure. Rather than making assumptions, Claude highlights the discrepancy and asks Ian how to resolve it.
- •Prep skill includes validation checks for alignment issues
- •Claude surfaces a reporting mismatch caused by a sales reorg
- •Claude asks clarifying questions instead of guessing
- •Human decision: choose the source of truth for reporting structure
- 2:09 – 2:19
Aligning to sales reporting: choosing to “follow the sales team”
Ian instructs Claude to update the review to match the sales team’s structure. This ensures cross-team consistency and avoids conflicting interpretations of results.
- •Instruction: align reporting to the sales team’s structure
- •Improves consistency across marketing and sales metrics
- •Prevents confusion from conflicting categorizations
- •Demonstrates human oversight in automated workflows
- 2:19 – 2:29
Proofreading and verification: trace every number back to a source
Ian describes the proofreading skill that audits the draft for data integrity. Claude checks that each metric in the report is tied to a verified data source, increasing confidence in what’s shared.
- •Dedicated proofreading skill validates the draft
- •Every number must trace to a verified data source
- •Reduces risk of reporting errors and misstatements
- •Builds trust for both team and leadership audiences
- 2:29 – 2:39
Drafting approach: headlines first, then expand with supporting detail
The first draft focuses on the metrics table and key headlines to confirm the structure. After agreeing on the outline, Ian asks Claude to expand the content while preserving the agreed headlines exactly.
- •Initial draft: metrics table + headlines only
- •Ian reviews outline before adding narrative depth
- •Claude expands headlines with detail and examples
- •Constraint: keep agreed headlines unchanged
- 2:39 – 3:10
Publishing and follow-through: finalize doc, Slack message, Asana tasks, leadership slide
Once approved, Ian tells Claude to finalize and distribute the outputs. Claude prepares the team-facing document, drafts the Slack announcement, converts follow-ups into Asana tasks, and generates the leadership slide focused on change,原因, and actions.
- •Command to finalize: “Ship it”
- •Outputs: final doc for the team + Slack message for the channel
- •Follow-ups become Asana tasks to prevent drops
- •Leadership slide: what changed, why, and what to do about it
- 3:10 – 3:34
Continuous improvement: capturing learnings and updating the skill for next week
Ian closes by describing a feedback loop where Claude captures process learnings and incorporates them into the skills. Changes like the new sales structure and any corrections Ian made are saved so the workflow improves and can be shared for consistent results.
- •Post-run reflection: ask Claude what to add to next week’s skill
- •Persist changes: sales structure updates and manual corrections
- •Claude updates the skill so the process evolves over time
- •Shareable skills enable others to run the same workflow consistently
