Cross-functional status brief
Most leadership weeks open with a round of chasing: who is behind, what changed, what needs you. This agent reads the places your teams already report — project tickets, planning docs, channel updates — and writes one brief covering each function, with every statement linked to where it came from. You read it before the leadership meeting instead of assembling it during one.
Step by step
Agree what counts as a function
We map the teams, initiatives and sources that belong in the brief, and what a healthy update looks like for each.
Pull the week's activity
The agent reads project tickets, planning docs and the channels where teams post progress, over the period you set.
Group by team and initiative
Updates are sorted against your list of live initiatives, so an owner sees their section rather than a wall of activity.
Compare against last week
Anything that has not moved, or that contradicts the previous brief, is separated out rather than buried in the detail.
Write the brief with sources
Each line carries a link to the ticket, document or message behind it, so you can open the detail when a line surprises you.
You release it to the team
The brief waits for you. Nothing posts to the leadership channel until you have read it and released it.
Exactly what this agent can see, touch and change
The same five controls sit behind every Askollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelFounders and chief executives whose functions report through different tools, where the weekly picture has to be assembled by hand. It earns its keep in the hour before a leadership meeting.
Escalation
When it asks a personYou approve the brief before it posts to the leadership channel
Applications & Rights
Which tools it uses, and what it may do in each
JiraRead only
NotionRead only
Google DriveRead only
SlackReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Founders and chief executives whose functions report through different tools, where the weekly picture has to be assembled by hand. It earns its keep in the hour before a leadership meeting.
What you’ll need
- Project tool and team channels connected
- An agreed list of live initiatives and owners
- A named channel or recipient for the brief
- One executive who approves before it goes out
What you get
- A weekly cross-functional brief with citations
- A flagged list of initiatives that have gone quiet
- An archive of past briefs to compare against
What it doesn’t do
It reports what teams have written down. Work discussed on a call and never recorded anywhere will not appear, and the agent does not chase people for missing updates unless you ask it to draft the nudge.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
How does it know what our initiatives are?
You give it the list during the co-build session, and it reads from the same place you keep it: a Notion database, a project board, a planning doc. When an initiative is added there, it appears in the next brief. Nothing is inferred from activity alone.
Will it surface things a team would rather handle quietly?
It reports on the sources you connect and the initiatives you list, so a channel left out of scope is invisible to it. This is worth settling openly at the start. A brief that quietly reads private channels costs more trust than it saves time.
What if two teams describe the same thing differently?
The brief keeps both accounts and cites each one rather than picking a winner. Disagreement between functions is usually the most useful line in the brief, so we surface it instead of smoothing it over.
Can other leaders get their own version?
Yes. We usually configure a full brief for the chief executive and narrower ones per function, reading the same sources with different scope. Each version keeps its own approver.