Skip to main content

Reporting

Standing jobs that run on a schedule and deliver a written brief.

What comes in, what it makes, where it lands

GitHub, Gmail, Google Calendar

GitHub
Gmail
Google Calendar
reads

Team Standup

Summarizes your entire team's work over the past day, across GitHub, Gmail, Google Calendar, and more, then emails it out to the team.

Set up Team Standup

reads

News Watch

Watches the topics and sources that move your team's work and delivers a short brief of only the stories that matter, with why each one counts.

Set up News Watch

Gmail, Outlook

Gmail
Outlook
reads

Newsletter Digest

Reads the newsletters piling up in your inbox and files the frameworks, mentions, and data points worth keeping into one searchable digest.

Set up Newsletter Digest

Gmail, Outlook

Gmail
Outlook
reads

Portfolio Updates

Reads the update emails you receive about the companies and projects you track and files each one into a running record, with every entry linked to its source.

Set up Portfolio Updates

Every email waits in Gmail or Outlook Drafts for a person to send. The five share one customer list.

The research desk your team would hire, if it could afford one.

Reporting, done for you

The reporting category covers every standing job your team wants running in the background: a cron, a watch, a weekly brief. You describe what to watch and what matters; the agent reads, extracts, and writes up what your team needs to see — on the cadence you set, in the inbox of the teammates who signed up for it.

Reporting abilities share a common shape:

  • A source (or a list of them) — the pages, portals, feeds, dockets, or APIs to watch.
  • A match rule — keywords, parcels, tickers, parties, dollar thresholds, whatever your team tracks.
  • A brief template — what the output looks like, who it goes to, and when.
  • A schedule — daily, weekly, on-publish, or custom.

The 12 reporting abilities we ship out of the box are specific packaged versions of this shape, each one tuned to a particular source type (SF committee agendas, EDGAR filings, competitor product pages, etc.). Teams can also compose their own by describing the source, rule, template, and schedule in plain language.

Turn one on, then the rest

Each one sets itself up in a chat: it asks where your customers write, sends you to connect the accounts it needs, and runs. Turn on a second one and it finds the customer list the first one made.