# Weekly Analytics Digest, Refreshed in Place | Comma Routines

Canonical: https://commareports.com/features/routines/weekly-analytics-digest

> Replace the Monday morning analytics script with a routine. The digest re-runs on a cron, lands as a new revision on a shared Comma report, and reviewers comment in-place — same link every week.

# Weekly analytics digest, refreshed in place

Every analytics team has the Monday morning ritual. Someone re-runs the
script. Someone pastes the screenshot into Slack. The lead asks a question
that gets buried. The next Monday, it starts again.

A routine ends the ritual.

## The setup

- **Skill.** Your weekly digest generator, packaged as a Claude skill. It
  pulls the relevant metrics, formats the dashboard as HTML, and includes
  the standard sections — top movers, anomalies, week-over-week comparisons.
- **Report.** A Comma report titled something like _Weekly product analytics
  — week of …_ or kept as a rolling report with revisions per week.
- **Cadence.** Weekly (Monday 09:00 UTC), or pair with a daily interim view
  — any cadence, on any plan.
- **Reviewers.** PM lead, eng lead, design lead. Anyone who's been on the
  Slack-screenshot thread.

## The shape, week by week

**Monday 09:00.** Routine fires. The digest HTML lands as the next revision.
Comma pings the subscribers with one link.

**Monday 09:30.** PM lead opens the link, selects the row in the funnel
table that dropped 8% week-over-week, and pins a comment: _"is this real or
is the ingest delayed?"_

**Tuesday.** Eng lead opens the same link, replies to the comment with a
data answer, resolves the thread.

**Friday.** Someone asks about a chart. There's a comment from Wednesday
anchored to it explaining the move. Nobody re-finds context.

**Next Monday 09:00.** Routine fires again. New revision lands on the same
report. Last week's resolved comments stay; open ones carry forward. The
diff against last week is one click.

This is what "the report and the conversation in one place" looks like as a
default state, not as a moment of discipline.

## Why this beats the Monday morning script

| Problem with the script              | What the routine does                        |
| ------------------------------------ | -------------------------------------------- |
| "Someone forgot to run it"           | Comma fires it on the cadence                |
| Output lands in Slack                | Output lands on a document people open       |
| Comments scatter across threads      | Comments anchor to the report, in place      |
| Last week's context is lost          | Previous revisions and resolved threads stay |
| No diff against last week            | One-click revision diff                      |
| Bedrock or compute cost is unbounded | Prepaid credit pauses at $0 + per-run cap    |

## Cadence and cost

Routines run at any cadence on any plan, so weekly is just a scheduling
choice. You pay only for the AI compute each run uses:

- **Prepaid credit** — use Comma's keys and draw down a prepaid balance (at
  cost plus 20%). A typical weekly digest costs cents per run, and hosted
  runs pause at a $0 balance rather than overflowing.
- **Bring your own Bedrock keys** — even cheaper for teams that already have
  AWS committed-use discounts; the spend lands in your own AWS account, free
  on Comma.

A per-run safety cap protects the budget on either rail.

## Setup, end to end

1. **Have the skill.** If your team already has a Python or Node script
   that produces the weekly digest HTML, wrap it as a skill. If you don't,
   the skill is a prompt + a connector reference — Claude does the rest.
2. **Create the rolling report.** _Weekly product analytics_. Set access to
   the people who should see it.
3. **Add the routine.** Cadence: weekly. Day-of-week: Monday. Cost ceiling:
   default ($2/run is more than enough for most digests).
4. **Subscribe reviewers** so they get the new-revision ping.

Next Monday, the script has already run and the team has the link they
already know.

## Variations

- **Department digest.** Separate routines per function (product, growth,
  ops) posting to per-function reports.
- **Exec digest.** Tighter scope, narrower audience, monthly cadence.
- **Daily check-in pairing.** A daily routine that just emits the top-line
  numbers plus a "what changed since yesterday" section, with the full
  digest as a separate weekly routine.

## Try it

**[Create your first routine →](https://commareports.com/)**

### Related

- [Routines — full feature reference](/features/routines)
- [Automated HTML report delivery](/features/routines/scheduled-html-reports)
- [Run a Claude skill on a schedule](/features/routines/run-claude-skill-on-schedule)