Signals are how Brainis notices things. Detectors run continuously against your live data and raise a signal when a condition worth attention occurs.
What the detectors watch
A sample of the built-in catalog:
- ›Revenue - deal stalled, deal likely to close, heavy discounting, stale lead source, renewal upcoming, account health low.
- ›Work and delivery - task overdue, sprint slipping, project scope creep, approval bottleneck, recurring manual task.
- ›People - employee overloaded, employee underused, one-on-one missed, training overdue.
- ›Hiring - candidate stalled in stage, detractor candidate feedback.
- ›Finance - invoice overdue, late payment predicted, cash gap forecast within 30 days.
Where signals surface
Command Center, Signals is the inbox: open signals, their severity, and the recommended next move for each. Signals also feed the relevant AI Manager and can appear in your daily digest, so the important ones find you.
Responding
Each signal offers its next move: create the follow-up task, nudge the owner, run the matching play, or trigger a playbook. Wiring a signal type to an automatic response is possible and contract-governed - most teams automate the notification and keep the action human. See Playbooks and automations.
Tuning
Detector rules have thresholds ("stalled" after how many days?) you can adjust per your rhythm. Mute a signal type that does not fit how you operate - an ignored signal inbox is worse than a smaller, honest one.
Tip: Review the signal inbox in your Monday routine before planning the week: it is a pre-built list of what quietly went wrong.