Direct answer
Define the systems of record and a fixed reporting window, take one structured snapshot from each source, calculate changes in code, and use AI to explain only the material movements. Deliver a consistent report with source links, decisions, risks, and owner follow-ups instead of a dashboard dump.
01
The workflow
- 01
Fix the reporting contract
Choose the cadence, timezone, section owners, authoritative systems, comparison period, and delivery destination before automating the narrative.
- 02
Collect one settled snapshot
Read the permitted product, CRM, support, finance, and project sources. Persist the values and source links used for the report so a later rerun cannot silently change history.
- 03
Calculate, then explain
Use deterministic code for totals and deltas. Ask the model to interpret the important movements, find related context, and flag uncertainty rather than performing arithmetic in prose.
- 04
Deliver an operating review
Publish the same section structure each week: movements, explanations, risks, decisions, and follow-ups grouped by owner.
02
Finished artifact
A decision-ready weekly review
A leader should be able to see what changed, why it matters, and who owns the next move without opening five tools.
- Period-over-period movements from settled values
- Explanations linked to source context
- Risks and decisions that need attention
- Follow-ups grouped by owner and date
- Exceptions for missing or stale source data
03
Setup checklist
- Name one authoritative source for each reported metric.
- Define the reporting window, timezone, and late-data policy.
- Choose materiality thresholds for changes and risks.
- Set the section order and delivery destination.
- Review the first four reports for noisy or unsupported explanations.
Authority boundary
Internal report can post automatically; board/investor versions stay draft-first.
Start with the smallest useful authority. Expand it only after the team has reviewed settled outputs and the exception path is working.
Product evidence
Weekly executive review
Turn shipped work, pipeline, support, finance, and open loops into one weekly operating review.
- Trigger
- Scheduled
- Finished output
- Weekly review in Slack, PDF, or deck with decisions and next actions.
- Supported sources
- Slack, GitHub, Linear, HubSpot, Stripe, Google Sheets
04
Sources and verification
These links support the system capabilities and product workflow described above. The page was reviewed on 2026-08-31.