CEO Weekly Report

Read a week of Slack across sales, dev, leadership, and health-check channels, extract a per-department pulse, and synthesize a polished executive brief for the CEO.

Best for

CEOs · Chiefs of Staff · Founders

Runs with

Slack · Executive brief · Department pulse

At a glance

Outputs

Capabilities

Teams

Core outputs

• Executive summary
• Department pulses
• Decisions required
• Watch list

Capability requirements

MCP

What it solves

Late, subjective, and dependent on one person manually stitching four channels together, every week.

A dependable weekly rhythm. Not whoever had time to write it up.

No more manual briefing work for chiefs of staff and founders.

Decisions and risks flagged with explicit urgency — not buried in prose.

Workflow

1. Pull the trailing window of Slack history from four operating channels.
2. Extract a structured pulse — wins, blockers, risks, sentiment — per department.
3. Synthesize a CEO-ready brief with decisions required and a watch list.

Implementation

Review the underlying FML blueprint — the sessions, tools, and typed schemas that define this workflow — and see exactly how it is instructed for repeatable execution.

FML Blueprint

Filename: ceo-report.fml

Parameters

• lookBackDays - Number of days of Slack history to retrieve (for example: '7')
• reportWeekOf - Week-ending date label, for example 'March 21, 2026'. Leave blank to auto-detect.

Components

DepartmentPulse Schema

• wins: string[]
• blockers: string[]
• risks: string[]
• sentiment: strong|steady|concerning|unclear
• notableThreads: string[]
• headline: string

Sessions

extract-sales-signals

Focus on:

• deal updates
• pipeline movement
• customer wins or losses
• quota progress
• objections heard in the field
• pricing or competitive mentions

extract-dev-signals

Focus on:

• features shipped
• bugs in production
• incidents
• deployment status
• technical debt discussions
• scope changes
• any signs of timelines slipping or accelerating

extract-leadership-signals

Focus on:

• strategic discussions
• directional decisions made or deferred
• cross-functional priorities
• goal progress or slippage
• resourcing conversations
• escalations
• issues requiring CEO visibility or intervention

extract-health-check-signals

Focus on:

• alerts
• outages
• degraded services
• on-call escalations
• infrastructure bottlenecks
• deployment failures
• remediation work
• operational risks that could affect customers or team throughput

Session for Building CEO Report

You are the Chief of Staff preparing the weekly CEO report. The structured signals available are:

• salesSignals
• devSignals
• leadershipSignals
• healthCheckSignals

Report Requirements

• executiveSummary must be a 3-5 sentence memo, not bullets
• companyMomentum.overallSentiment must be one of: accelerating, steady, mixed, at-risk
• The departments object should be synthesized directly from signals.
• Populate all required fields explicitly.