Skip to main content

​
Why this matters

Every other tool waits for you to ask. The catch is that you can only ask about what you already know to look for — which means the most important shifts in your data often surface late, if at all. Chief’s ambition with proactive intelligence is to flip that model: instead of you pulling answers out, Chief pushes the signal to you. The value is that routine monitoring and recurring reporting stop depending on someone remembering to run them.

​
How it actually works

Chief proactive intelligence - building an Action by describing the work
Proactive intelligence reaches you in two ways. Actions are reusable workflows that take what Chief knows and turn it into an outcome: a draft, a report, an alert, a follow-up. You build an Action once by describing the work in plain language and choosing the output format, then run it on demand or hand it off to run on its own. The part that makes it proactive is scheduling. You can set an Action to run on a cadence, and Chief gathers the context from your sources, runs the workflow, and delivers the result where you work — in the app, in your inbox, saved to your Library, or, when your Project has a Slack channel connected, posted to that channel with Post each run to Slack. The output arrives cited and structured, ready to use. Common patterns teams set up:
  • A competitive intelligence brief delivered every Monday morning.
  • A pipeline digest every Friday afternoon.
  • A board pre-read the day before each meeting.
During a recorded, unpaused Live Session, Chief can also notice an unresolved information need, research it against public or connected sources, check the result, and surface a sourced insight without anyone asking. This path runs when Let Chief suggest things during a call is on and its display is not Off. Live Session suggestions are on and displayed by default until you change those settings. The shift is from human pull to agentic push: Chief can work on a schedule or respond to what comes up during a call, so intelligence shows up as a signal rather than waiting for you to ask for it.
ℹ️ Good to Know: Scheduled delivery covers the Actions you’ve set up. Live Session suggestions run only while that session is recording and unpaused, with Suggestions on and their display not Off. Chief isn’t continuously monitoring all your Project data outside a call. The more precisely you define an Action and its cadence, the more useful the scheduled signal that lands.

​
A worked example

Chief proactive intelligence - scheduling an Action to run on a cadence
Before each leadership meeting you used to spend an hour pulling together a pre-read. Instead, you build an Action that compiles the brief from your Project sources and schedule it to run the day before every meeting. From then on the pre-read lands in your inbox automatically — cited and structured — without anyone kicking it off. The work happens while you’re doing something else.

​
FAQ

Check that the Action is active and that its schedule and delivery channel (in-app, email, Library, or Slack) are set the way you expect. An Action can only pull from the sources in its Project, so if the underlying data wasn’t available when it ran, the output reflects that.
No. Proactive delivery comes from the Actions you create and schedule, plus suggestions during a recorded, unpaused Live Session when Suggestions are on and displayed. It isn’t blanket background surveillance of all your data outside a call. You decide which recurring work Chief runs and can turn Live Session suggestions off.
Scheduled Action outputs land in the app, in your inbox, in your Library, or in a Slack channel connected to your Project. During a Live Session, sourced findings appear as insight cards and collect under Activity → Insights. Both arrive cited and structured so they’re ready to share or act on.