An Orkeste reporting analyst compiles the recurring reports nobody wants to assemble: sprint progress from Jira, Linear or Trello, revenue from Stripe, operational data from Airtable. It writes a plain-language summary of what moved and posts it where the team already reads.
Every Friday afternoon, compile the Jira issues completed this week and the key Stripe figures into a short summary. Post it to #team-updates after approval and email a copy to the stakeholders.
Weekly sprint summaries, monthly revenue summaries, operational digests: assembled from the source tools at the cadence you set.
Turns counts and changes into a short plain-language summary of what moved and why it matters, per audience.
One report can combine Jira, Linear, Trello, Stripe and Airtable, the cross-tool assembly that eats a person’s afternoon.
Posts to Slack or Teams, emails stakeholders or writes to a Notion page, after a person approves the draft.
Reports are drafted, then wait for approval before they reach a channel or a stakeholder inbox. You catch the misread figure before the company does.
You describe the report in the agent briefing: sources, figures, cadence, audience. Ready-made workflows cover the common cases, and you adapt them the way you would brief a new analyst.
The approval step is there so a person checks the draft before it is published, and every run is kept in the Control Room with what the agent did.
It reads and updates Airtable tables. With Google Sheets, agents see your spreadsheets by name but do not read or write cells today.
Connect the sources, write the briefing, set the schedule. Most teams adjust the format over one or two runs before it runs untouched.