Gamut
Productivity & Internal Ops

Weekly Status Digest Agent

A weekly status report that writes itself, explains the why, and closes out last week's open risks.

Updated

Connects with

SalesforceSalesforceHubSpotHubSpotGreenhouseGreenhouseGoogle SheetsGoogle SheetsLookerLookerGoogle DriveGoogle DriveNotionNotion
Download template

The problem it solves

Most weekly status reports are a scramble of copy-pasted numbers with no story and no follow-through on last week's risks. This agent pulls the 4-8 metrics that matter, compares each to a baseline, explains what changed and why, and tracks every prior flag to resolution, so your team reads a real status report instead of assembling one.

Who it's for

  • Functional leads in recruiting, marketing, sales, ops, engineering, or CS who owe a weekly update
  • Heads of department reporting metrics up to executives
  • RevOps and business-ops teams who compile cross-team status reports
  • Founders and chiefs of staff preparing board-ready KPI summaries
  • Project and program managers who maintain a recurring weekly project status report

What it does

  1. 1

    Read last week's digest

    Pull the most recent prior digest from your archive and note every item flagged under risks and what changed.

  2. 2

    Pull this week's metrics

    Collect the current value for each of your 4-8 metrics from the system where it lives and the matching baseline value.

  3. 3

    Compute deltas and flag anomalies

    Calculate each metric's absolute and percentage change versus baseline and flag any movement past your anomaly threshold.

  4. 4

    Investigate the anomalies

    Break flagged metrics down by sub-dimension and check for process changes or events to form an evidence-backed hypothesis on cause.

  5. 5

    Write the narrative

    Apply your chosen style so every number carries a hypothesis and every flag gets an owner and a next action.

  6. 6

    Close last week's flags

    Mark each prior risk RESOLVED, STILL OPEN, or WORSENED with a one-sentence note on its current state.

  7. 7

    Build the digest for your audience

    Assemble headline, numbers table, what changed, prior flags, this week's risks, and a look ahead, tuned to IC, exec, or board level.

  8. 8

    Archive and post

    Append the digest to your storage so future runs can close its flags, then post the same report to your Slack channel or DM.

Key benefits

  • Turns a recurring chore into a one-click weekly project status report that reads like an analyst wrote it
  • Every number arrives with a comparison and a cause, never a bare figure
  • Open risks get closed out each week instead of quietly accumulating
  • One project management status report template adapts from IC detail to board-level summary
  • Pulls metrics from wherever they actually live, so no manual data gathering
  • Cites source records and dashboards so readers can drill into any number

Sample use cases

A recruiting lead owes a Monday update on pipeline health across five open roles.

The agent pulls applicants, interviews, and offers from the ATS, flags a 40% drop in one role's funnel, traces it to a paused job board, and posts the digest with that risk and a next action.

A head of marketing needs an executive-ready status report without tactical noise.

The agent compresses to the top four KPIs versus plan, leads with the headline and risks, and produces a clean project status report the exec can read in under a minute.

Last week's digest flagged churn as a risk owned by the CS lead.

This week the agent pulls the current churn figure, marks the flag RESOLVED, STILL OPEN, or WORSENED, and writes one sentence on where it now stands.

A founder wants a board-level summary built from numbers spread across Salesforce, a Google Sheet, and Looker.

The agent gathers each metric from its source, compares to the planned target, and assembles a KPIs-versus-plan digest with only the risks and asks the board needs to see.

Key integrations

  • Salesforce

    Pulls sales and revenue metrics from CRM records as a data source.

  • HubSpot

    Sources marketing and sales pipeline metrics for the digest.

  • Greenhouse

    Provides recruiting funnel metrics such as applicants, interviews, and offers.

  • Google Sheets

    Reads metrics maintained in spreadsheets, including planned targets and baselines.

  • Looker

    Pulls metrics and KPIs from existing BI dashboards.

  • Google Drive

    Archives each weekly digest so future runs can close out prior flags.

  • Notion

    Alternative storage for archiving digests and tracking open risks week to week.

  • Slack

    Delivers the finished digest to a channel or DM every Monday morning.

Unlike a project management status report template you fill in by hand, the digest leads with the story and treats the numbers table as reference. Every figure appears next to a comparison and a hypothesis, every risk carries an owner and a next action, and any unavailable data source is called out explicitly rather than silently dropped.

Because each digest is archived on every run, the agent can reach back to last week's flags and classify them as resolved, still open, or worsened. That close-out loop is what turns a recurring project status report from a snapshot into an accountable, week-over-week record.

Getting started

  1. Import the workspace — Add the Weekly Status Digest template into Gamut to set up the agent and its weekly schedule.
  2. Run the onboarding interview — The agent-onboarding skill launches automatically to capture your function, your 4-8 metrics and their sources, your archive, your Slack destination, audience level, and anomaly threshold.
  3. Give it a first task — Ask it to pull this week's raw numbers without writing narrative or posting, so you can confirm every metric resolves correctly before the first full run.

Frequently asked questions

Does the agent post the status report on its own or wait for approval?

On its default Monday-morning schedule it builds and posts the digest automatically to your Slack channel or DM. You can run it on demand instead and review the draft before it posts, and the recommended first task pulls raw numbers only so you can verify the setup first.

Which systems does it pull metrics from?

It reads from wherever your metrics live, including Salesforce, HubSpot, Greenhouse, Google Sheets, and Looker, and it archives each digest to Google Drive or Notion before posting to Slack. During onboarding you name which system each metric comes from.

How is this different from a project status report template in Excel or filling one out manually?

A static project status report template excel file holds numbers but writes no narrative and tracks no follow-through. This agent gathers the data for you, explains what changed and why, and closes out last week's flagged risks every run, so nothing falls through the cracks.

Can one digest work for both my team and my executives?

Yes. The same weekly project status report template tunes to your audience: IC and manager views include tactical detail and linked source records, exec views lead with the headline and top metrics, and board views show only KPIs versus plan plus risks and asks.

What counts as an anomaly, and can I control how sensitive it is?

By default the agent flags any metric that moves 25% or more week-over-week, then investigates the cause. You can raise the threshold for noisy metrics or lower it for tighter sensitivity during onboarding.

How much does it cost?

The Weekly Status Digest template is free to import from the Gamut marketplace. You connect your own accounts during onboarding, and no extra API keys are required.