Skip to main content
All Use Cases
executive

Leadership Weekly Scorecard

one scorecard every week: the five numbers that matter, why they moved, and the one decision each needs.

Best forEcommerceB2BD2cSaaSServicesStartup
Agents9 required
Duration3-5 minutes

Leadership meetings drown in dashboards that show numbers without the why. This recipe flips that: each week it pulls the KPI set from the live Stripe ledger — revenue and collections — and folds in pipeline context from HubSpot and store context from Shopify when connected. data-analyst computes week-over-week deltas with the drivers behind each move, so the scorecard reads number, delta, driver, decision needed — ending in asks, not charts. A number whose connection is missing is stated as missing, never zero-filled or faked. The scorecard stages to Slack and email exactly as they would appear, behind one approval gate; without those connections the full package waits in-hub, copy-paste-ready. Idempotent per week: reruns update the scorecard in place, never duplicate.

How it runs

Multi-agent orchestration — here's the flow, step by step.

01

Resolve the week window and the five-KPI set from memory; dedupe against the last scored week so the same week never builds twice.

workflow orchestrator
01

Pull revenue and collections from the Stripe ledger for the week, with the prior week for deltas.

payment scanner
01

Pull pipeline movement from HubSpot — new, advanced, stalled — with value by stage.

crm scanner
01

Pull order volume and store KPIs from Shopify for the week.

ecommerce scanner
02

Compute week-over-week deltas across the KPI set and name the drivers behind each move; mark missing-connection rows as missing.

data analyst
03

Write the scorecard: for each number — value, delta, driver, and the one decision it needs.

executive briefing writer
04

Draft the Slack post exactly as it would appear in the leadership channel.

slack channel operations agent
04

Stage the Slack post and email version for one-click approval; without them, hold the full package in-hub and say so.

distributor
04

Assemble the summary: KPIs covered, drivers, decisions on the table, and the in-hub footer when connections are missing.

report formatter

Required Agents

9
  • workflow-orchestrator
  • payment-scanner
  • crm-scanner
  • ecommerce-scanner
  • data-analyst
  • executive-briefing-writer
  • slack-channel-operations-agent
  • distributor
  • report-formatter

Connections

Required

gmailhubspotshopifyslackstripe

Optional

hubspotshopifyslackgmail

What it does

  • The five numbers that matter pulled live: revenue, pipeline, orders, support load
  • Week-over-week deltas with the drivers behind each move, not just the numbers
  • One decision-needed line per number — the scorecard ends in asks, not charts
  • HubSpot pipeline and Shopify store context fold in when connected
  • Support-load number grounded in the real weekly ticket stream
  • Staged to Slack and email exactly as they would appear, approval-gated
  • Missing-connection numbers stated as missing — never zero-filled or faked
  • Idempotent per week — reruns update in place, never duplicate

Example prompt

Build this week's leadership scorecard: revenue, pipeline, orders, support — with deltas, drivers, and the decision each one needs.

Ready to deploy Leadership Weekly Scorecard?

Start free. One click, full agent orchestration.

Get Started Free →