// How it works
From CRM signals to one clear action
Sighub uses deterministic rules on HubSpot metadata. There is no AI, no predictive model, and no health score. Just signals and severity.
The three states
Every company is evaluated into one of three states:
- Renewal Risk: a contract renewal may be at risk.
- Engagement Risk: communication has slowed or stopped.
- Healthy: no active risk signals detected.
Each company carries one primary signal at a time. Renewal Risk takes priority over Engagement Risk when both could apply.
What Sighub reads
Sighub evaluates risk using metadata from HubSpot objects associated with each company:
- Company properties (name, owner, currency, mapped contract date and value)
- Email metadata such as timestamps, direction, and status. Never the body.
- Meeting timestamps. Never notes or content.
- Ticket status (open and closed counts). Never content.
- Contact activity timestamps
- Deal amounts and currencies
- Company
hs_last_logged_call_date. Never recordings or content.
What counts as engagement
"Activity" is the most recent of:
- Company
hs_last_logged_call_date - Last associated meeting timestamp
- Associated contact
hs_lastactivitydate - Last inbound email reply timestamp
"Recent activity" means the latest activity is less than 14 days old. Recent activity can suppress certain engagement risk triggers.
An "inbound reply" is an associated email whose direction is INBOUND/INCOMING (or whose status indicates REPLY while direction is not OUTBOUND). A "future meeting" is any associated meeting with a timestamp in the future.
Open tickets are detected by status: a ticket is considered open unless its status contains "CLOSED" or "RESOLVED".
Renewal Risk
Renewal Risk is evaluated only when a mapped Company contract end date exists and is a valid date. A renewal is "active" when the date is within the configured renewal window (30, 60, or 90 days) or already overdue.
Severity
High, any of:
- Contract end date is overdue
- Contract end date is within 14 days
- Within 30 days and no meeting is scheduled before the renewal date
Medium: renewal is within window, but none of the high conditions apply.
A stale inbound reply (28+ days) can be added as supporting evidence, but a stale reply alone does not trigger renewal risk.
Engagement Risk
Engagement Risk applies in two scenarios:
When no contract date exists
Severity is based on combinations of:
- No activity for 30, 45, or 60+ days
- No inbound reply for 30, 45, or 60+ days (when no recent activity)
- No inbound reply ever recorded plus no future meeting
- 3+ open tickets with no recent activity
- No future meeting plus stale reply (when no recent activity)
When a contract date exists but renewal risk is not active
- Medium: inbound reply is stale (28+ days) but less than 42 days old
- High: last inbound reply is 42+ days old
- Critical: last inbound reply is 60+ days old
Healthy
Accounts without active risk signals are marked healthy. Healthy accounts are not highlighted, so the focus stays on accounts that need attention.