Cross-team weekly digest
Revenue, pipeline, ops, product – one narrative, source-linked, with the "so what" already drafted.
By team · Executives
Business 360, one weekly read.
A co-worker that builds your weekly business digest – across teams, with source links – so Monday starts informed.
§01 · Weekly work
The one weekly read that cuts across the org.
Executive workflows are about synthesis, not generation. A co-worker stitches the signals from finance, sales, product, and ops – so the Monday read is already drafted when you sit down.
Anomaly summary
What moved outside the normal band this week, across every connected source – flagged for review, not blasted.
Decision-prep packets
For the meeting that needs context: options, evidence, tradeoffs, references – pulled together in advance.
Board narrative draft
The quarterly narrative – built on the same weekly signals – drafted as a starting point, not a finished product.
§02 · Co-worker
One co-worker, every source you've connected.
The executive co-worker reads across all the systems your teams already use. Drafts the weekly read. Waits for approval from the COO before it lands.
RIY-EXE-01
Connected
Finance
Sales CRM
Marketing
Product & Ops
Executive co-worker
read·draft·approve
Business 360 drafted
Anomaly digest queued
Decision packet ready
§03 · Engines
The agent engines doing the work.
For executives, all four engines run together – visualisation, persistence, anomaly watch, and deep analysis. The shape of the weekly read demands every layer.
Dashboard Agent
Refreshes the executive view every Monday – revenue, pipeline, ops, the trendlines that matter – annotated.
Visual · Recurring
Goal-Based Agent
Carries the "draft the weekly read" goal across steps – gather, synthesise, draft, queue for COO sign-off.
Persistent · Step-aware
Anomaly Detection Agent
Watches the metrics that should be steady. Flags the one chart that broke the band, with the context attached.
Watchful · Proactive
Data Analysis Agent
Reads across the connected sources and writes the explanation – the "so what" the executive read needs.
Analytical · Cited
§04 · Sample workflow
The weekly exec read, in inbox by 7am Monday.
A real engagement pattern – what the team asked for, what the co-worker did, what got approved by the COO, and what landed for the leadership team before standup.
What was asked
"Get me one read, across the org, every Monday – before the week eats it."
A CEO wanted a single Monday-morning read that synthesised the week across finance, sales, product, ops, and marketing – without a chief of staff spending two days assembling it.
What the co-worker did
Read 7 source systems. Drafted the digest. Linked every claim.
Across Sunday, the co-worker pulled from the warehouse, the CRM, the marketing BI tool, the support ticket system, the product analytics, the engineering ops dashboard, and the operating model in Sheets. It assembled the cross-team digest, annotated what moved, and attached source links on every line.
What got approved
The COO reviewed at 6:30am, edited three lines, approved.
The COO opened the draft in approval queue at 6:30am, tightened three claims, removed one over-reaching forecast, approved. Nothing left the approval gate until the COO said yes.
What shipped
In the leadership team's inbox at 7:00am Monday.
An implementation-led engagement that took 4 weeks – including the security review for cross-system access and the rollback plan. Monday morning is informed. The leadership read is the same every week, with the model getting sharper as the COO's edits feed back in.
§05 · Get started
Bring the one weekly read your leadership team relies on.
We'll map it with you, identify the minimum context across teams, and ship a working version in 2—4 weeks – your data, your tools, COO approval before it lands.