All articles
GuideExample

A Monday brief for leadership: three sources, one note, no new numbers

By Team Two · Last updated September 23, 2026 · 2 min read

This is an example, not a customer story, and not a measured result.

Monday, 7:00. The leadership channel wants one note before the week starts. Not a board deck. A note: what moved in the pipeline, what engineering finished, and whether the month's cost sheet still matches the plan someone already typed into a spreadsheet.

The three pulls

  • Pipedrive: deal totals by stage, from the deals the agent can see. Not a second CRM.
  • Jira: issues completed last week on the board you named, plus anything still blocked.
  • The finance sheet in the workspace: the plan-versus-actual rows someone exported. The agent does not log into the accounting system unless you have connected a tool that can.

It renders one chart from those rows, pipeline value by stage. The chart uses the figures it just fetched. It does not smooth them and it does not invent a target.

The note in the channel

The Slack post is short enough to read on a phone. Three blocks, each with the source named. A blocked Jira issue is quoted, not summarized into "engineering is behind." A deal that slipped stage is named, not turned into a story about the quarter.

If a number is missing, the note says missing. A leadership brief that fills gaps is worse than a short one.

The sentence only a person should write

The CEO or CFO adds the "so what." The agent will draft that sentence if asked, and the draft stays in the thread until someone edits it. It does not email the board. A deck, if you want one later, is a follow-up that still cites the same three sources.

Cost of the model calls behind a brief like this is a separate question, covered in Three questions to ask about your AI bill.

Frequently asked questions

Can this run every Friday as well?+

Yes. Scheduled jobs take a cron expression and a timezone, and they can deliver to Slack or email.

Can it include product usage?+

Only from a source you connect or a file you upload. There is no built-in usage warehouse for your customers' product.

See Team Two working in your own Slack or Teams.

Book a demo. We'll set up a first agent on your documents and show you how the controls work.

Book a demo

Related articles